New Choose the column in your CSV or Excel file to pseudolocalize
Pseudolocalization offers developers a way to test an app before translating anything. After all, internationalizing your app can be some work if the app wasnâ€™t designed that way from the start. You need to:
1) Make sure all user-facing texts are tagged or exported for localization
2) Update number and date formats to use regional settings
3) Expand the UI for flexibility, since most languages take up more space than English, and a few take up less
4) Ensure right-to-left text works if you plan on Arabic or Hebrew localizations
Just writing that list makes me want to ask for help! Luckily, Babble-on has provided a free pseudolocalization service to help developers with issue #1 for many years now. It works with a whole bunch of formats, from iOS .xliff and .strings, to Android .xml and Windows .resx. For game developers in particular, it also works with CSV and Excel XLSX documents. However, itâ€™s always been a little tricky with those because the â€˜source languageâ€™ column can be different from document to document.
Our latest enhancement helps with just that.
Before we had defaulted to Column B, since most developers user a â€˜keyâ€™,â€™sourceâ€™ type format. Now, the choice is yours!
After uploading a CSV or Excel document to our pseudolocalization cost estimator, youâ€™ll be able to specify which column your source text is located in. And of course, you’ll also get a free estimate of what it would cost to translate that text into any language. Although our pricing is straightforward â€” pay only by the word â€” we happily translate all duplicate lines for free. This cost estimator will let you know exactly how much you save there for those countless ‘Done’ and ‘Cancel’ buttons you’ve got!
Try it out, and if you have any questions, ask us for help at Babble-on.