[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-i18n-doc
Subject:    Re: Improving ISO Codes in KDE
From:       Freek de Kruijf <f.de.kruijf () gmail ! com>
Date:       2011-04-26 8:46:50
Message-ID: 201104261046.50394.f.de.kruijf () gmail ! com
[Download RAW message or body]

Op maandag 25 april 2011 23:49:17 schreef Albert Astals Cid:
> A Dilluns, 18 d'abril de 2011, John Layt va escriure:
> > Hi guys,
> > 
> > I raised this idea about a year ago without a result, but I'd like to
> > have another go at it.
> > 
> > In short, adopting iso-codes would be a major step backwards without a
> > major data and translation donation from KDE, including setting up new
> > translation teams on TP for iso-codes.  I don't think this is an option.
> 
> Agreed, it would mostly seem as an hostile takeover from our side and
> duplicate the places we work in.

I also do the ISO translations in TP next to the KDE translations for the 
Dutch language. So we could encourage KDE translators to do these specific ISO 
translations in TP. They can do only the relevant ISO .po files.

But I like John's pragmatic approach in this matter.
 
> > An alternative approach has occured to me.  We actually have almost all
> > the data and translations we need within KDE to develop our own solution
> > within kde-runtime (even for Subdivisions from KGeography), we just need
> > to suffle what we already have around a bit and merge in some stuff from
> > iso-codes.
> > 
> > I'm suggesting we remove our Country and Currency Codes, Names and
> > translations from the .desktop files we currently have and split them
> > into .xml and .po files using some scripting, leaving the locale
> > settings still in separate files.  In theory this could even reduce the
> > installed footprint of KDE as you would have only the translations you
> > need.  Once in this format it would be eaiser to either donate the files
> > to iso-codes or move them to kdesupport or fd.o as a new project.
> > 
> > As I mentioned, the Subdivisions Code has 4551 strings to translate and
> > iso- codes has few complete translations.  However KGeography has 6825
> > strings for Countries, Subdivisions and Capitals which should contain
> > most of those strings, even better all shipping KDE languages are at or
> > near 100% complete. A bit of smart scripting could see a near complete
> > implementation.
> 
> lokalize already has some sort of let me try to be smart and autocomplete
> this translation for you.

Currently I have separate Translation Memories for the translations in KDE and 
GNU (TP). But it is easy to merge these into one TM. So the work in one area 
can benefit from the work in the other area. But at least one translator in a 
language should have these files on his system. Most of this work in my 
language is finished in the period that KBabel was the tool and at that time 
there was only one TM like system. In lokalize <Ctrl>+<Alt>+B is my friend.
 
> > What would be the best way for me to script such a migration so that the
> > translators don't have to manually copy the existing strings?  I presume
> > I can just take the current .po file created by scripty for the 
> > .desktop files, edit it to remove the line references and other .desktop
> > file translations and add in new strings from iso-codes, rename it and
> > save to the new location and just wait for it to be merged with the .pot
> > from the new xml file?
> 
> That should work yes.

Of course you can do it this way, but in the current systems, merging these 
efforts is not very difficult for a translator, so you could concentrate on 
more urgent matters.

-- 
fr.gr.

Freek de Kruijf
[prev in list] [next in list] [prev in thread] [next in thread]