Starting with internationalization¶
Have a project and want to translate it into several languages? This guide will help you do so. Several typical situations are showcased, but most of the examples are generic and can be applied to other scenarios as well.
Before translating any software, you should realize that languages around the world are really different and you should not make any assumption based on your experience. For most of languages it will look weird if you try to concatenate a sentence out of translated segments. You also should properly handle plural forms because many languages have complex rules for that and the internationalization framework you end up using should support this.
Por último, pero no por ello menos importante, a veces puede ser necesario añadir algo de contexto a la cadena traducida. Imaginemos que un traductor recibe la cadena Sol para traducir. Sin contexto, la mayoría de la gente la traduciría como nuestra estrella más cercana, pero en realidad podría usarse como una abreviatura de domingo.
Choosing internationalization framework¶
Choose whatever is standard on your platform, try to avoid reinventing the wheel by creating your own framework to handle localizations. Weblate supports most of the widely used frameworks, see Localization file formats for more information (especially Translation types capabilities).
Our personal recommendation for some platforms is in the following table. This is based on our experience, but that can not cover all use cases, so always consider your environment when doing the choice.
Plataforma |
Formato recomendado |
|---|---|
Android |
|
iOS |
|
Qt |
|
Python |
|
PHP |
|
C/C++ |
|
C# |
|
Lenguaje de programación Perl |
|
Ruby |
|
Extensiones web |
|
Java |
|
JavaScript |
The more detailed workflow for some formats is described in following chapters:
Ver también