It's actually already set up to be localized easily.
Find whichever campaign to want to localize in the filesystem. You're looking for a path that looks like Data/StreamingAssets/ContentPacks/<campaign name> (e.g. HongKong, hk_coda, dead_man_switch, and I forget the names of the Dragonfall ones). Open the project.cpack file within it in the editor.
Then, from the Tools menu, choose Extract Content Pack Localization. This will generate a Strings.pot file in resources/locale/ within the campaign directory you can edit with Poedit (https://poedit.net/). Open the program, choose create a new translation, and select your Strings.pot file.
When you're done translation in Poedit, save the .mo file it generates and copy it into <campaign dir>/data/loc/ru (for Russian). The campaign should now play translated.
No need to bother with the editor at all except for the original content.
As a bonus, if it's the Hong Kong campaign you want to do, here is a link to the .pot file (since it's easy enough to generate): https://drive.google.com/file/d/0B-IrcQ6zAXcYdE82b2Vab3dLVjg/view?usp=sharing Be warned: there are 24545 messages to translate.
Poedit (https://poedit.net) can indeed translate XLIFF files.
What you link to is POEditor, a paid software-as-a-service product that they named this way to cause exactly this kind of confusion with Poedit :(
As far as I know, the current industry standard is gettext's .PO files, and the most suggested tool is PoEdit.
Sounds like you're on the right track-- once you download the survey it will be in a .po file format, which you can translate in most translation software including Poedit (poedit.net) which has a free version. Here are some instructions I found on the SM help page:
To add a survey language:
https://help.surveymonkey.com/articles/en_US/kb/Multilingual-Surveys
Once you get the survey translated and verified by a linguist, I would follow the rest of the instructions on the help page for importing and adding the language picker. I hope this helps and let me know if it works!
Are you familiar with gettext and its message extraction tooling xgettext
?
I use the xgettext
frontend Poedit to extract the messages from PHP, Javascript, Nunjucks and Volt templates. I would want to be able to use a template "helper" in Vue like this {{ t('Search Here') }}
and then have an xgettext
template parser be able to pull it out. Also I would need {{ n('File', 'Files', fileCount) }}
. So I need to be able to add a list of template helper functions to Vue templates. Is there a way to do this?
As far as parsing .vue files I would use some kind of HTML parsing library to pull out the Javascript in the <script> tag and to run that through the native xgettext
Javascript parser and then pulling out <template> part and running that through something like the Swig template parser.