Localisation of page
Nike's original proposal included us localising language names here first and then transferring the whole database to CLDR. I think it might be more realistic and effective if we were to tackle the transfer to CLDR for a few locales, or just one, at a time. That way, we can prioritise the languages which most need this leg up, and which also have enough translators to complete the localisation.
So, any volunteers to pick up the communication?
I did, by e-mail, but no reply yet. I may have to poke several potential partners and shall do that one by one. May take a week or two.
Sorry, it looks like I didn't reply properly. Any ways, I just saw your e-mail (I was away from my mail over the weekend, after working very hard on preparing for the ST vetting phase to open). Please do not poke potential partners! It would be better to just file a single bug, but I'm glad to forward the e-mail to the TC if you prefer that.
I got an e-mail reply from Srl295 last monday who asked for permission to forward the note on to the CLDR technical committee, which I granted.
A rough sketch for the translatewiki.net technical part as I currently see it:
- We could use locales provided in the Local Description Markup Language LDML, an XML format designed by CLDR, to extract a set of key => value pairs per locale, which obviously can be imported into its own namespace in translatewiki.net, possibly including limited amounts of message documentation.
- The inverse process could be used to generate files with suggestions of additions and updates to be provided to CLDR.
- Other types of export formats are possible of course as well.
- While this scheme could transport all possible locale items, we do not have to support them all.
- I can do the necessary coding.