C# localization -

C# localization -

possible duplicate: c# localization , confusing me

could please share localization steps huge c# applications?

i'm pretty sure basic resource-based strategy might work when talking little medium projects.

however, if speak big products, approach should paired custom build steps , 3rd party applications used linguists.

so, please advise / share global localization strategy used in applications (big enough, :)

thank you.

basic resource-based strategy works in big enterprise applications. built-in , understandable solution, hence each , every programmer utilize without problem.

the problem is, need somehow transform resource files translation memory files (i.e. tmx) , - translators utilize standard tools.

so need localization process. different big applications? well, if set-up right process scale. onto process. point of view should this:

copy resource files appropriate folder construction (localization engineers should not work straight application code base). appropriate folder construction should somehow similar to: [project name] . . [neutral] [german] [japanese] [french] . . (each folder contains translatable resources in given language, neutral english) of course of study need transform code base of operations folder construction somehow, automated.

process translatable resources , create transkits - zip archives containing files need translated (in case seems of them). files should transformed, won't end-up sending out resx files. transformation application should read contents of resx files , set translatable strings file of format agreed translators (it excel won't recommend solution). now, can't give names of such tools, although know commercial applications exist, have worked custom ones.

send transkits translators (most translation vendors).

upon receiving translated files (transkit) back, need verify (this step crucial). need ensure transkit finish (i.e. no translatable strings missing) , technically right (i.e. file encoding correct, utf-8 or utf-16). @ to the lowest degree take glance @ file see if there no unusual characters 1/2, 3/4 or - mean broken encoding.

import transkit. reverse step of 2 - need set translated strings appropriate files.

copy translated files original code base of operations , run "localization" build.

test application localization problems (i.e. overlapping controls, clipping strings, wrong encoding, etc. - mean i18n not done right). fix localization/internationalization (localizability) defects. proceed 1 until ui/string freeze period. assumes translators utilize translation memory of kind , won't charge (or charge less) re-translating translated strings. automate possible steps , done.

apart might won't found mutual glossary of terms , linguistic review on translated content.

c# localization internationalization