Comments on: MSBuild, XAML & international characters http://blog.caraulean.com/2009/03/24/msbuild-xaml-international-characters/ Keep it simple. It will work... Fri, 10 Feb 2012 04:38:27 +0000 hourly 1 http://wordpress.com/ By: Valeriu Caraulean http://blog.caraulean.com/2009/03/24/msbuild-xaml-international-characters/#comment-59 Thu, 21 Jan 2010 09:25:05 +0000 http://varely.wordpress.com/2009/03/24/msbuild-xaml-international-characters/#comment-59 Thank you Guido, haven’t knew that there can be issues with TFS.

As for replacing only individual characters with unicode representations – that’s a nice trick. But it’s a “no way” if you have to internationalize your application.

]]> By: Guido http://blog.caraulean.com/2009/03/24/msbuild-xaml-international-characters/#comment-58 Thu, 21 Jan 2010 09:03:14 +0000 http://varely.wordpress.com/2009/03/24/msbuild-xaml-international-characters/#comment-58 the entitiy name above should read: “[ampersand]#x25CF;” .
Grmpfl :o /

]]> By: Guido http://blog.caraulean.com/2009/03/24/msbuild-xaml-international-characters/#comment-57 Thu, 21 Jan 2010 09:01:05 +0000 http://varely.wordpress.com/2009/03/24/msbuild-xaml-international-characters/#comment-57 Hi Valeriu,
thanks for this piece of information.
In my personal experience there is one caveat with this approach:
Changing the character encoding of files under source control in an TFS / VS 2008 environment can lead to problems in comparing and merging the file if this file was checked out by others during the encoding change.
If only a few characters need to be taken from unicode, you could also reference them by their unicode entity name (e.g. “●” for the Password Character in Password box styles).
Regards,
Guido

]]>