Why would you use a pseudo translation on a file?
There are a few good reasons why someone would want to pseudo translate a file or application.
Translation can be costly and pseudo translation is virtually free so you get to test if your product will work in the new language before you translate it.
Before you start the real translation process, there are two things you need to know:
- Can the translators see, access and translate every word in your application or file?
- Can your application process the translated text after your application is translated?
After translation, your application will still function correctly; however, layout bugs/issues can now be found easily. Sometimes translated text can be longer than English so translation can cause dialog box clipping. Some strings that might be concatenated or hardcoded in the code might cause a program to crash when translated. This testing process is known as internationalization testing (i18N).
How do you pseudo translate a file?
The process of pseudo translation is relatively straightforward:
- Firstly, replace all the vowels in the application or file with accented versions; replace the following: a=á e=é i=í o=ó u=ú or other similar combination depending on the language, of course
- In some cases you might double the characters to test string expansion. So ‘Hello’ would become ‘Hééllóó’
The advantage of this is that after translation…
- your English speaking team can still test your product – the words will just look a bit strange
- you can see quickly if every string in your product is visible to the translation team
- you can check your application will work after you translate it (adding foreign characters)