xaml - Silverlight localization -
what avaliable options translating silverlight 5 application (prism + mef)? if possible to:
- not have resx files (i don't way managed)
- rather have xaml string extracted , translated (i think there tool microsoft, marked xaml nodes custom attribute , extracted strings)
- have translations in external assemblies (in prism modules) , load them when needed
- change language @ runtime
i'm open suggestions , best practices on topic.
edit: locbaml talking above, looks it's not avaliable silverlight
i know number of traditional answers, put forward original tried (and succeeded) doing ourselves more efficient localisation of silverlight:
localisation of silverlight projects after completion
it uses attached properties provide hooks, in xaml, dynamic changing of localisation strings. when first parsed code gets chance make changes related elements, , language swap means reloading current page.
the localisation strings come down server database using simple ria services call. entries returned simple key/value pairs chosen language.
this method not have (quite large) overhead of traditional binding methods see lot of. download only chosen language strings when app starts up. potentially allows edits/corrections sent server (if can bear overhead of editor in app... did lot of work).
p.s. using prism, works in silverlight app there no dependencies (e.g. on unity etc).
pps. post code snippets system when home tonight.
(resx "last century")
Comments
Post a Comment