CEO and founder of Lingohub. Envisioning a multilingual digital world. Email me if you have questions about how Lingohub can help you take your products global.

Helmut Development 0 Comments

SHARE

Introducing “Export settings” for resource files

Programming holds a lot of pitfalls, character encodings and handling time are just two examples. Many of them exist only because of historical reasons, but still have to be handled today. Dealing with many different frameworks and programming languages means dealing with different requirements as well. At lingohub we always prefer a standard solution, but we know that sometimes you do not have a choice. In your projects, one step of your work process is actually exporting the resource files of your translation languages when done. Here is where encoding becomes important again. For example, the predefined standard encoding for properties files is ISO-8859-1, however, some frameworks require UTF-8 for properties files. As a developer you do not have much of a choice in such a situation, so we decided to give you the best of both worlds. We use good standard settings for exporting resource files, but give you the option to change it the way you like:

Export Settings

Blank content handling

Decide what lingohub should do when the content of a phrase is empty. The three options are:

  • Skip the phrases with the blank content.
  • Keep the phrase with the blank content in the export.
  • Use the source language content instead of the blank content.

Encoding

Currently lingohub supports four different export encodings:

  • UTF-8
  • UTF-16LE
  • ISO8859-1
  • ISO8859-1 with character escaping

Just to be clear, this only affects export settings and not import. The imported files encoding will be automatically determined by the lingohub system.

All these settings are created based on our customer feedback. If you require other options as well, don’t hesitate to contact us.