best proceed settlement localization strings
this kinda whole question, open opinions. i've perplexing adult good proceed settlement localization twine resources windows mfc concentration associated utilities. wishlist is:
- must safety twine literals formula (as opposing replacing macro #define apparatus id's), messages still entertaining inline
- must grant localized twine resources (duh)
- must levy additional run-time sourroundings restrictions (eg: dependency .net, etc.)
- should have minimal obtrusion existent formula (the reduction alteration better)
- should debuggable
- should beget apparatus files editable common collection (ie: common format)
- should copy/paste critique blocks safety verbatim strings code, anything else creates appetite de-synchronization
- would good grant stationary (compile-time) checking each "notated" twine apparatus file(s)
- would good grant cross-language apparatus twine pooling (for components several languages, eg: internal c++ .net)
i have proceed fulfills wishlist border solely stationary checking, nonetheless i have arise bit tradition formula grasp (and limitations). i'm wondering anyone solved problem quite good way.
edit:
the fortitude i now have looks this:
showmessage( restring( _t("some string") ) );
showmessage( restring( _t("some twine non-static %1"), snontranslatedstringvariable ) );
i following have tradition concentration parse out strings within 'restring' blocks put .resx record localization, removed c# com vigilant bucket localized apparatus files fallback. c# vigilant accessible (or can't load), i fallback twine code. macro expands template category calls com vigilant does formatting, etc.
anyway, i guess useful supplement i have reference.
Comments
Post a Comment