From OpenStreetMap Wiki
Jump to: navigation, search
Available languages — Taginfo/I18N
Afrikaans Alemannisch aragonés asturianu azərbaycanca Bahasa Indonesia Bahasa Melayu Bân-lâm-gú Basa Jawa Baso Minangkabau bosanski brezhoneg català čeština dansk Deutsch eesti English español Esperanto estremeñu euskara français Frysk Gaeilge Gàidhlig galego Hausa hrvatski Igbo interlingua Interlingue isiXhosa isiZulu íslenska italiano Kiswahili Kreyòl ayisyen kréyòl gwadloupéyen kurdî latviešu Lëtzebuergesch lietuvių magyar Malagasy Malti Nederlands Nedersaksies norsk norsk nynorsk occitan Oromoo oʻzbekcha/ўзбекча Plattdüütsch polski português română shqip slovenčina slovenščina Soomaaliga suomi svenska Tiếng Việt Türkçe Vahcuengh vèneto Wolof Yorùbá Zazaki српски / srpski беларуская български қазақша македонски монгол русский тоҷикӣ українська Ελληνικά Հայերեն ქართული नेपाली मराठी हिन्दी অসমীয়া বাংলা ਪੰਜਾਬੀ ગુજરાતી ଓଡ଼ିଆ தமிழ் తెలుగు ಕನ್ನಡ മലയാളം සිංහල ไทย မြန်မာဘာသာ ລາວ ភាសាខ្មែរ ⵜⴰⵎⴰⵣⵉⵖⵜ አማርኛ 한국어 日本語 中文(简体)‎ 吴语 粵語 中文(繁體)‎ ייִדיש עברית اردو العربية پښتو سنڌي فارسی ދިވެހިބަސް

The taginfo user interface allows you to switch to your favourite language. By default the language configured in your browser is used, but there is also a drop-down box that allows you to change it. If taginfo doesn't know about your language it uses English.

Help by translating the web site into your language

Nearly every text in the taginfo web interface can be translated into any language. All texts are in the git repository in one directory with one file per language. The format of the file should be easy to understand. There is a hierachy of labels ending in a colon (:) and after them the text. Multiline texts have a bar (|) after the label and the text in the following lines.

To view the translation status of currently supported languages see the taginfo i18n page.

If you only want to add a few translations or change some, the easiest way is to go to the github directory, click on the language file, then click "Edit". You can edit the file directly in the browser and after you are finished send a pull request with your changes. You'll need a Github account for that.

If you want to translate a larger portion it is probably best if you fork the project on github and start translating. Once you have finished all or part of the translation, check it in and send a pull request. If you can't work with github, just send me the language.yml file, but thats more difficult in the long run if changes are needed etc.

If possible you should use the English (en.yml) or German (de.yml) language versions to start translating from, because they are complete and always updated when the software is updated. Please take care to translate the OSM technical terms (such as "node", "tag", etc.) in the same way as they are generally used in your OSM community. Dictionary translations are not always right for these special terms.

You do not have to translate everything, if it is too much work. The labels are ordered roughly beginning with the more important texts so just start at the top and do as much as you can. If a text is not translated taginfo will fall back on the English text automatically. Do not put any text in your language file other than the translated text.

In the git repository there is a handy little script that checks whether you have all texts by comparing to the English text file. For instance to compare the English with the Italian text you run it as follows:

 bin/check-translations.rb web/i18n it

To check your translation you can install taginfo, but you don't have to do that, if it seems to complicated. When you send us the files, we'll updated the main taginfo site and you can see your translations there and update them if needed.

Untranslatable texts

Some texts can not be translated for one reason or another. We are aware of this and it might change in the future, but for the moment these texts are only available in one language (English usually):

  • The taginfo "internal" pages under https://taginfo.openstreetmap.org/taginfo are not translatable. These are mostly used by developers and translators who will need to known English anyway.
  • The INTERNATIONAL section on the main page and part of the "About" page. These are different for each taginfo instance and the text comes from the config file and not the place where taginfo usually gets its translations from. It would be nice if this is translatable but it needs some more work in the software to make it possible.
  • The text in the (experimental) fulltext search tab is not translatable. This should be fixed.