I had mimic the resx way that is used on Visual Studio, but instead using a downloadable table from Sql Server to Sqlite. It accepts text for labels like label1.Text, as other properties like label1.Width, textBox1.MaxLength, comboBox1.Enabled, etc. As Visual Studio does.
The only view that use a mixed custom library with native OS way is login view, as the first time it runs the application do not have a database. So when user subscribe to it, it download library table as other normal tables. Of course there is many ways, like to interpret the resx file from visual studio? We opted for a table so if the translator guy corrects or create a new language, it can be made on a web page then users get changes on next normal sync without republishing the application. Our default language is write on interface builder on buttons and labels, and then library class handles it inside form loading. If no thing is found for a language, it assumes default one, like on Visual Studio. But now our windows mobile application has this library instead native windows resx handling. Karl From: Felix Collins <[email protected]> Date: Thu, 23 Feb 2012 13:24:57 +1300 To: "[email protected]" <[email protected]> Subject: [MonoTouch] Best way to handle localisation strings cross platform Hi All, Does anyone have a ready to roll system for cross platform string localisation? Our plan is to keep all languages in a big csv file and generate the platform specific resources (for droid and touch) using a custom built tool at compile time. Any thoughts? Felix _______________________________________________ MonoTouch mailing list [email protected] http://lists.ximian.com/mailman/listinfo/monotouch
_______________________________________________ MonoTouch mailing list [email protected] http://lists.ximian.com/mailman/listinfo/monotouch
