On Wed, Apr 7, 2010 at 17:08, Mitja Kleider mitja@kleider.name wrote:
Hi Ævar,
I am not sure if you are the right person to contact, but I remember you worked on getting the translations to translatewiki.
I wrote some translation strings for a new OSM tool and now found out that most of them are already available in the OSM tranlatewiki collection. I would like to use it to provide the tool in many languages, but there are still some strings missing.
Do you know how to add new strings to translatewiki?
In detail, those are missing in comparison to my translation file (translation is German):
msgid "phone" msgstr "Telefon"
msgid "fax" msgstr "Fax"
msgid "website" msgstr "Webseite"
msgid "collection_times" msgstr "Leerungszeiten"
msgid "opening_hours" msgstr "Öffnungszeiten"
msgid "operator" msgstr "Betreiber"
Also, I do not know a good prefix for msgctxt. Maybe "poi.details." would fit. The msgids are tags, the string should be used in a human readable POI description. If you have any idea for a better msgctxt prefix, I am fine with anything.
I would be glad if you know how I can add those myself, I guess there will be more to come, like translation for the cuisine tag and possible values, maybe more.
I'm cc-ing the mediawiki-i18n list which discusses Translatewiki et al.
Adding a new project to translatewiki means:
* Having your translations in a format they already understand or write an adapter, you can see the supported formats (I think) here: http://svn.wikimedia.org/svnroot/mediawiki/trunk/extensions/Translate/ffs/ * Having them agree to add it. * Having it in the OSM SVN or somewhere else where they can pull/push your translations, just look at the activity in sites/rails_port/config/locale/* for reference.
I guess that by "most of them are already available" you mean you got them from the config/locale/*.yml files for nominatim. You should be aware that those may not be as useful as you think, due to the way they're presented in the UI they're not in the nominative case in some languages, for example in Icelandic we translate:
"Hotel X"
as:
"Hótelið X"
meaning:
"The Hotel X"
Depending on the context you want to present your strings in you may not be able to piggy-back on these translations for that reason.
Is your project already working & supports more than one language? Is it being used by anything? It's probably better to wait a bit until you know how to answer questions like the above before your tool is added to Translatewiki.
Am Mittwoch, den 07.04.2010, 17:36 +0000 schrieb Ævar Arnfjörð Bjarmason:
On Wed, Apr 7, 2010 at 17:08, Mitja Kleider mitja@kleider.name wrote:
Hi Ævar,
I am not sure if you are the right person to contact, but I remember you worked on getting the translations to translatewiki.
I wrote some translation strings for a new OSM tool and now found out that most of them are already available in the OSM tranlatewiki collection. I would like to use it to provide the tool in many languages, but there are still some strings missing.
Do you know how to add new strings to translatewiki?
In detail, those are missing in comparison to my translation file (translation is German):
msgid "phone" msgstr "Telefon"
msgid "fax" msgstr "Fax"
msgid "website" msgstr "Webseite"
msgid "collection_times" msgstr "Leerungszeiten"
msgid "opening_hours" msgstr "Öffnungszeiten"
msgid "operator" msgstr "Betreiber"
Also, I do not know a good prefix for msgctxt. Maybe "poi.details." would fit. The msgids are tags, the string should be used in a human readable POI description. If you have any idea for a better msgctxt prefix, I am fine with anything.
I would be glad if you know how I can add those myself, I guess there will be more to come, like translation for the cuisine tag and possible values, maybe more.
I'm cc-ing the mediawiki-i18n list which discusses Translatewiki et al.
Adding a new project to translatewiki means:
I did not want to add it as a new project, but wanted to add new strings to the existing project http://translatewiki.net/w/i.php?title=Special% 3ATranslate&task=view&group=out-osm-site
I guess that by "most of them are already available" you mean you got them from the config/locale/*.yml files for nominatim. You should be aware that those may not be as useful as you think, due to the way they're presented in the UI they're not in the nominative case in some languages, for example in Icelandic we translate:
"Hotel X"as:
"Hótelið X"meaning:
"The Hotel X"Depending on the context you want to present your strings in you may not be able to piggy-back on these translations for that reason.
That is the right context. By most of them are already available I meant that there is "geocoder.search_osm_nominatim.prefix.*" like here http://translatewiki.net/w/i.php?title=Special:Translate&task=view&language=is&group=out-osm-site&offset=500.
You mentioned SVN for synchronization. Is this the desired way to add strings to existing projects? Is there any place where new strings should be discussed in advance?
On Wed, Apr 7, 2010 at 17:54, Mitja Kleider mitja@kleider.name wrote:
I did not want to add it as a new project, but wanted to add new strings to the existing project http://translatewiki.net/w/i.php?title=Special% 3ATranslate&task=view&group=out-osm-site
You still haven't answered what project you're working on. Are you working on nominatim itself? In that case those strings are applicable to being added to the nominatim namespace. If it isn't and you just want to add a few more then just adding them anyway probably doesn't do any harm, the strings that are there already are just from some one-off top100 list if I recall correctly.
However if your project is separate from the OSM website then it should have its own subproject, just like Potlatch does now.
You mentioned SVN for synchronization. Is this the desired way to add strings to existing projects? Is there any place where new strings should be discussed in advance?
You maintain a master file like en.yml in config/locales/en.yml in the rails_port directory. Translatewiki syncs that regularly, if there are any new strings they're made available to translators.
They then translate them and they're commited back to the *.yml files that aren't en.yml.
Just do `svn log http://svn.openstreetmap.org/sites/rails_port/config/locales/' to see how it happens.
Am Mittwoch, den 07.04.2010, 18:05 +0000 schrieb Ævar Arnfjörð Bjarmason:
On Wed, Apr 7, 2010 at 17:54, Mitja Kleider mitja@kleider.name wrote:
I did not want to add it as a new project, but wanted to add new strings to the existing project http://translatewiki.net/w/i.php?title=Special% 3ATranslate&task=view&group=out-osm-site
You still haven't answered what project you're working on. Are you working on nominatim itself?
No, it is an effort to produce human readable text from the OSM tags of POIs and is still in a proof of concept state. It is using gettext and my own translation, which is the same as geocoder.search_osm_nominatim.prefix.* plus a few detail description strings. The POI title is in the same context as in Nominatim, like in your example "Hotel <Name of the hotel>" meaning "The hotel <name>". In the detailed description only a few tags are supported by now (like telephone, fax, website). The goal is to make human readable text for as many tags as possible. I mentioned cuisine for restaurants as an example.
In that case those strings are applicable to being added to the nominatim namespace. If it isn't and you just want to add a few more then just adding them anyway probably doesn't do any harm, the strings that are there already are just from some one-off top100 list if I recall correctly.
I agree. If I get requests for further prefixes, I will add them to en.yml in the OSM SVN. This should be useful for Nominatim, too.
The detail descriptions are not available in Nominatim yet, the OpenStreetBrowser is providing some human readable text (at least addresses, maybe more). I think they could be available on the OSM website as something like /browse/{node,way,relation}/readable, but there is no rails code for it yet.
However if your project is separate from the OSM website then it should have its own subproject, just like Potlatch does now.
Okay, that would be the case at the moment. However, I think the prefixes (like Nominatim's) and "detail names" (or however we could call it) can be shared by many applications and we should avoid duplicate translation effort for the same purpose.
On 7 April 2010 22:13, Mitja Kleider mitja@kleider.name wrote:
Am Mittwoch, den 07.04.2010, 18:05 +0000 schrieb Ævar Arnfjörð Bjarmason:
However if your project is separate from the OSM website then it should have its own subproject, just like Potlatch does now.
Okay, that would be the case at the moment. However, I think the prefixes (like Nominatim's) and "detail names" (or however we could call it) can be shared by many applications and we should avoid duplicate translation effort for the same purpose.
Translatewiki.net offers translation memory (albeit simple). There is no need to worry about duplicated effort. Instead, we should ensure that the strings can be translated properly into all languages and are accompanied with extensive translation hints.
-Niklas
mediawiki-i18n@lists.wikimedia.org