Many clients have asked us to add pseudo-translation in our platform, and we are very happy to announce that, finally, it’s here!
It can be found under Settings > Machine translation, and its effect is the conversion of all letters in the text to uppercase when enabled.
This feature will certainly be helpful for those who, prior to translating particular texts (such as software UI interfaces), need to catch potential problems in the structure of the text or the underlying software structure.
Comments
6 comments
Hi Agathe,
This is indeed a great feature, but the main interest of pseudo-translation is to help to catch internationalization issues like characters not supported correctly by the software and/or translations that could be too long or not correctly displayed.
Having the possibility to convert all letters to uppercase will not really help to identify such issues.
I would suggest, if possible to have the possibility to :
This to ensure that the full sentence is really displayed.
ex: with the string "This is a sample test." you will get {This is a sample test.}
ex: Thîs ìs à sâmplë têst.
ex: This is a sample test.çàéôü
{Thîs ìs à sâmplë têst.çàéôü}
I think this will be a more appropriate approach for pseudo-localization testing.
Regards,
Emmanuel
Hi Emmanuel,
Thank you for your valuable feedback on this new feature release.
You also might want to explore the additional options for pseudo-translation you have in Wordbee Beebox for pseudo-translation: http://documents.wordbee.com/display/bb/Software+Localization+Connectors
Kind regards,
Mareike
Hi Mareike,
Thanks for your quick reply, In fact I'm aware about the possibility to do most of my suggestion by using the Beebox. My remarks where about having it directly in Wordbee as most of the users will be using only the Wordbee interface.
For example, if we want to add a Workflow step at the beginning of a project for automatically generate a pseudo translation to validate that there won't be internationalization and truncation issues, this will allow to update translation instructions about limitation constraint or to put in standby the project to report to our customers eventual internationalization issues and ask for an updated document.
This is why I think this kind of options will be more convenient if available and customisable directly in Wordbee interface in the same way than the file format filters.
Kind Regards,
Emmanuel
Hi Mareike,
I second Emmanuel's suggestions.
As you know, another point of pseudo-translating a file is to make sure that all the translatable texts have been extracted properly.
The 'All upper case' logic doesn't really help this purpose as it is not always visually obvious when a string has been missed by the parser. Not to mention, the source text could potentially have been in upper case anyway (in this case there is no way to know whether the text has actually been picked up or not).
So the option to replace characters by (*) or ($) would be particularly helpful.
Kind regards,
Jonathan Bourriquis
Good morning Jonathan, hope you had a good weekend. Thanks for your comment. I am glad to inform you that more options for pseudo-translation have been included in the new editor:
Have a very blessed new week Jonathan.
All the best
Wojciech
Hi Wojciech,
Great, thanks a lot for the info, I didn't know this had been implemented -- last time I checked the option wasn't there.
Have a nice day,
Jonathan
Please sign in to leave a comment.