We localize a cross-platform client application based on C ++. The first pass of localization was made in a big hurry for a large partner in a short time, and now it is time to reorganize it.
We currently have an XML string file for each locale, with a shared key and localized value for each resource. However, sending our optional technical localizers, the XML file is not perfect - they are not aware of the encoding of special characters, etc. I would like to use a simple, well-known format such as Excel / csv with localizers (also good, because we also have server-side localization, which can be on another tab of the same file), and then the code generates line files from there . Excel doesn't seem to like to output CSV UTF-8 files, which is annoying and prevents me from dumping some quick scripts to automate the conversion of Excel → string files.
This problem has been solved hundreds of times. What workflows have people found best, especially when localizers are external to the company? I am looking for something easy for non-technical users, and also easy for the development team to then use to create a file of strings in some simple format like XML.
source
share