Timeline for Effective Strategies for Localization in .NET
Current License: CC BY-SA 2.5
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 5, 2015 at 20:33 | history | locked | CommunityBot | ||
| Aug 9, 2011 at 23:35 | comment | added | Scott Rippey | @caveman @taylonr: String.Format is a great recommendation, but when it comes to plural forms, check out open-source Smart.Format ... it extends String.Format with localizable plural formatting and more. It's easily extensible too. SmartFormat | |
| Aug 3, 2011 at 19:23 | history | migrated | from stackoverflow.com (revisions) | ||
| Jun 29, 2011 at 14:11 | comment | added | Crippledsmurf | Environment.GetFolderPath can be used to get valid paths to common paths such as My Documents without depending upon the English name for those folders. | |
| Apr 10, 2011 at 15:04 | comment | added | Sylver | Great answer! As a translator, I have a few extra suggestions: Use a simple format for string resources. XML, JSON are easy to prepare for translation. Pictures with text can not always be avoided (website banners). In that case, add a language code to the resource and a bit of code to grab the translated picture if it exists. String concatenation can be replaced by string formating ("Welcome, {0}!", userName), allowing the translator to move the name at it's proper place. | |
| Apr 10, 2011 at 14:27 | comment | added | David Waters | @Jimmy C : Good answer, maybe you could expand on it to include some talk about right to left languages (hebru, Arabic) | |
| Apr 2, 2011 at 15:52 | comment | added | klabranche | @Jimmy-C Great answer! | |
| Apr 2, 2011 at 6:49 | comment | added | Naraen | Good list JimmyC. "Never hardcode any paths to Windows folders" reminded me of "Always use Path.Combine" instead of string concatenation for windows paths. | |
| Mar 10, 2011 at 18:45 | comment | added | taylonr | @Smart do something in your resource like "{0}, {1}" then when you localize it, use string.format and pass in the greeting and username. Plus this gives you the benefit of having "Current {0} speed is {1} {2}" and you can pass in "Engine", "50" and "MPH", and when you translate your sentence, you can move {0} etc around to where they make sense in that language | |
| Mar 10, 2011 at 18:33 | comment | added | smartcaveman | @Jimmy C, how do you go about building strings for language-independent logical consistency? | |
| Mar 10, 2011 at 17:52 | history | answered | Jimmy Collins | CC BY-SA 2.5 |