Pseudo-translation added!

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.

Have more questions? Submit a request


  • 3
    Emmanuel Cinneri

    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 :

    1. Add to each side of strings a bounding character.
      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.}

    2. Have the possibility to have for example all vowels replaced by accented vowels in the corresponding target language. This to catch the correct support in the software of the foreign language:
      ex: Thîs ìs à sâmplë têst.

    3. Have the possibility to expand the pseudo translation by x% by adding additional character in the string
      ex: This is a sample test.çàéôü

    4. And of course the possibility to have all the above cases at once.
      {Thîs ìs à sâmplë têst.çàéôü}

    I think this will be a more appropriate approach for pseudo-localization testing.



  • 2
    Emmanuel Cinneri

    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,


  • 0
    Mareike Bouriga

    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: 


    Kind regards, 


Please sign in to leave a comment.