Building world-ready Windows Store apps with XAML
- Date: November 1, 2012 from 8:30AM to 9:30AM
- Day 3
- B33 Cascade
- 3-104
- Speakers: Ben Riga
- 7,198 Views
- 5 Comments
With the Windows Store you can publish your app in more than 200 markets, with a reach of over 4.5 billion people. To support that global reach, Windows 8 will ship with 109 languages and is designed to work better in more locales all over the world. With Visual Studio, it has never been easier to build an app that is world-ready. In this session we’ll show you how to use XAML to localize your app, by separating the code from any user interface text that must be translated. We’ll show you how to globalize your app so that it supports the cultural needs required by users around the world. Finally, we’ll show you the tools you need for testing and translating world-ready apps.
For more information, check out this course on Microsoft Virtual Academy:
Comments Closed
Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation,
please create a new thread in our Forums,
or
Contact Us and let us know.
Event Homepage
Follow the Discussion
Oops, something didn't work.
What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in. You need to be signed in to Channel 9 to use this feature.What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in and view them all on your notifications page.sign up for email notifications?
Consider this an early question from a distant audience:
How can I use an ampersand character in the original English text and not in a foreign language using the Multilingual App Toolkit? There appears to be encoding issues with the toolkit that I'm not sure how to work around.
@Jared: The workaround is to translate using the editor, but leave the & in the target string. Once done, save and exit the editor. In the VS IDE, open the .XLF file with the XML editor and manually replace the %%amp; with your desired character.
Thanks for the advice Cameron, but once you apply the workaround you can't use MAT again until you put %%amp; back in the translations. I have half a dozen of these amongst 300+ entries across five languages. That's quite a mess to manage. Since my build time went from seconds to minutes with the inclusion of MAT, I'm beginning to question its usefulness.
A new version of the Multilingual App Toolkit has been released that resolves the issue with the matching %%amp; requirement in the target value. The version is v1.1.1075.0 as displayed in the VS IDE Extensions and Updates dialog.
Thanks Cameron. I had to uninstall and then reinstall but it has solved both my issues. My build times are back to mere seconds again.
Remove this comment
Remove this thread
close