I’m a developer, but my English is poor… How can I create a good English source file?
This is an important issue because:
- English is most popular language on the world, and customer usually use this language as UI language (not Polish or Hindi), whenever an application hasn’t implemented their native language first.
- For this same reason, typically finding a translator from English to Polish is easier than from Hindi to Polish. So, when your English version is imperfect what is the case even if you see yourself as fluent in a foreign language it will cause in some very odd or even dangerous results in targeted translations.
To resolve this issue , you can create a project with English as original and translation language. Next find a native English translator and send him your project. His translation will be something between a proof-read and rewriting of your “dummy” English. When you receive his project with high quality English items you can:
- Import this project to your main project, build output files and next create new project based on these output files. However, in this case your Sisulizer out put files (sources for new project sent to other translators) should be an accurate copy of your source files. So you need always use “Localized files” option, not e.g. “Resource DLLs” (e.g. for Delphi) in “Files” tab of source properties.
- You can import English project to your main project and use English translations as alternative original. Alternative original feature is described in this article on our blog. This solution doesn’t require re-build of your source files and creation of new Sisulizer project.
I think you could experiment with both ideas and next select most appropriated solution for your application and workflow.
Janusz
Did you enjoy this post? Why not leave a comment below and continue the conversation, or subscribe to my feed and get articles like this delivered automatically to your feed reader.
Comments
No comments yet.
Leave a comment