Topics

Hi, I am creating a set of dictionaries and I am giving you the link already now even if the readme file is still missing:

http://ambaradan.i-iter.org/voxhumanitatis/file/189696514ca7/dictionaryformids

License is cc-by-sa, license holder is Vox Humanitatis (http://www.voxhumanitatis.org)

I myself cannot manage the dfm dictionary creation from here. These files over time will be extended with basic terminology but also specific one. Maybe there is someone here reading who would like to care about the transformation of these files. Over time data from other resources will come along. I just received various text files that first of all need cleaning. For example for French-German. The textfile has approx. 80.000 entries - after cleaning this will be less, but considering its size: the data I received for a group of langauges will give us nice dictionaries.

Please contact me through the contact form on http://www.voxhumanitatis.org - I cannot come around all too often here.

Thank you!

Cheers, Bina

Sorry if I ask the obvious, but I read so many things at one time that I don't remember what is where and re-reading all is just too much right now.

What I understood out of an e-mail if I remember well is that DfM automatically sets the UI language to the language of the phone. That is if the UI language of my mobile phone is German, I get a German UI.

Do I have the possibility to chose any of the UI languages present in DfM, let's say Neapolitan, even if the UI of my mobile phone is German?

This question is relevant for quite some languages, because if we think about Africa in particular the UIs of phones are often not localized in the local language since the official language is French or English. The selection of languages for the localization we go for depends from this feature.

Actually these are two connected questions or better various points.

1) As to the UI localization: is the source file a language.properties file? If so: it can be directly translated using OmegaT. This would avoid the conversion. Furthermore: translators are not used to do by "themselves" that is, copy from the page etc. So a file should be ready to be downloaded and translated instead of having to create an own one by copying and pasting and then adding a new language. This is just a hint - I know it is not difficult to do a copy/paste, but I also know my colleagues.

Their workflow is:
*take source file
*load it in CAT-Software
*translate
*export to target

1.1) How are the translations and updates maintained?

2) Like mentioned in the mail: IMHO it would make sense to have "UI-Translation-days" going on around International Mother Language Day on 21 st of February. We will have a translation marathon for Dictionary entries.
http://www.voxhumanitatis.org/content/international-mother-language-day-2010
we also have a facebook group for that:
http://www.facebook.com/profile.php?id=682271047&ref=ts#!/group.php?gid=209376066111&ref=ts

3) Language codes: your page is linked to ISO 639-2 langauge codes which in the meantime anyway is not enough because it leaves out over 6000 languages existing in the world. Is there a possibility to support ISO639-3 language codes?

I think that's all for now.

Cheers, Sabine