Simple But Yet So Difficult To Translate: Placeholders In Software

I do some translating myself too. Already quite a long while ago I translated texts for a web application running on a small company’s website and came across a placeholder that didn’t have much information attached to it. I could see the placeholder’s name and the sentence it was embedded in. For that particular application, the placeholder name usually revealed what it was about. What I assumed it to be was the name of the user’s company/product. That made the sentence a bit difficult to translate due to Finnish grammatics, but I managed to build a somewhat natural sentence out of it anyway.

A while after that I browsed to the web site and saw what my translations looked like. Awful. The sentence structure was in some cases clumsy, in some cases the meaning was simply wrong. The placeholder didn’t stand for the user’s company/product, but for the website/service where it was used. And based on earlier translations in the translation memory I wasn’t the only translator who had been mistaken.

After that I sent an email to my contact person at one of the many agencies between me and the end client, and pointed this out. What happened? Nothing. The translations are still there. (But you shouldn’t really blame the project manager, as he was probably constantly swamped with email. Localization project managers usually are.)

What did I learn from this? Well, first of all it is critical to include enough information about placeholders for the translators. Even if they would be experienced users of the application, it might not become clear to them what different placeholders mean. Secondly, it’s important to have a translation process that supports communication and updates even after the initial translation has been finished. Communication has to be so easy that important issues aren’t left lying around even by mistake.

Microsoft Word DOCX Support Available

I’m happy to announce that we’ve added DOCX support to all projects starting from today. DOCX files can be imported under ‘Files’ -tab like any other file. Projects can hold multiple DOCX files and translation sync works between them and other files like before. It’s also possible to upload resource files and e.g. user manual to same project so everything will get translated at once.

Now additionally to websites and applications, we manage documents too. Yay!

Workspace Got Refreshed

We rolled out small but easily noticeable changes to our project workspaces today. Re-designed header, as you can see on the left is not green anymore and it’s smaller. It takes less space from valuable information making the workspaces more user friendly. The icon is a bit smaller but it pops out more clearly against the dark background.

This is a part of our project to create more clearer design to whole service. We’re doing these improvements incrementally in simple batches so your team’s productivity doesn’t suffer due to major updates. Don’t forget to let us know how you feel about this change, we truly love feedback!