Share via

sudo localize & make me-a-sandwich [Free PseudoLocalizer class makes it easy for anyone to identify potential localization issues in .NET applications]

  • Article

**

This blog has moved to a new location and comments have been disabled.

All old posts, new posts, and comments can be found on The blog of dlaa.me.

See you there!

Comments

  • Anonymous
    January 27, 2011
    This is a great idea.  I'd seen examples of Microsoft's pseudo-localization before (Device Manager anyone? :)) but hadn't thought about integrating it into my WPF app.  I already use a RESX approach with a custom ResourceManager that can read and write .resx files at runtime for in-app localization (editing strings in the app), override resources, and on the fly language switching.  I also created a LocalizedViewModel base class with an indexer that returns localized strings for the most concise code and XAML, for example {Binding [btnEditLanguage]}. Anyway, it seems like it should be easy to add pseudo-localization to my system... I'll definitely give this a shot when I get back to localization (someday).  Thanks for the tip!

  • Anonymous
    January 27, 2011
    Tom, Cool - sounds pretty advanced! Thanks for sharing. :)

  • Anonymous
    January 27, 2011
    The comment has been removed

  • Anonymous
    January 28, 2011
    Tim, That's really interesting! I'm going to think about something like that for a future update. :) Thanks!

  • Anonymous
    January 30, 2011
    Do you know if it's possible to use AppResources for translating an app to a a language different of Spanish, Italian, German, english and french? I would like to have my application in "ca-ES"

  • Anonymous
    January 30, 2011
    The comment has been removed

  • Anonymous
    February 01, 2011
    BTW: There is a basic pseudiser sample on msdn.microsoft.com/.../cc163991.aspx and custom ploc culture on blogs.msdn.com/.../647915.aspx

  • Anonymous
    February 02, 2011
    slyi, Thanks for the references!