[kde-doc-english] License translation cleanup in KDocTools, help needed

Luigi Toscano luigi.toscano at tiscali.it
Wed Apr 16 23:58:49 UTC 2014


Burkhard Lück ha scritto:
> Am Mittwoch, 16. April 2014, 01:51:42 schrieb Luigi Toscano:
>> - css files for each language. Basically all the css files are empty (apart
>> from one role in the romanian one)
> 
> Afar we has already a mail thread about the usage of these language css files 
> (in kde-i18n-doc or kde-doc-english), but I can not find this thread anymore.

Oh, this one?
http://lists.kde.org/?l=kde-i18n-doc&m=124896979211881&w=2


>> The problem comes from the translation of the licenses. I see two ways to
>> deal with them:
>> - copy the existing files from SVN with the history.
> 
> I had a look at the german files and doubt we need the history here, it is 
> mostly just one  commit for a file.
> 
>>   Pros: I'm the only one who needs to do something.
>>   Cons: I need help with the SVN->git conversion rules; need to fix the
>> encoding issues; some translations could be outdated or need some tuning
>> (some of them seems to miss the headers "this is an unofficial translation"
>> etc).
>>
>> - leave a basic css file and nothing else, let translators put the files if
>> they think it's worth.
>>   Pros: less work from me (especially the conversion rules) :), cleanup
>>   Cons: more work on you
>>
>>From my experience with mails about obsolete docbooks some teams will do 
> nothing here.

Yep :(

> 
>> What do you think about this? If you think it does not make sense to start
>> over, I will invest some time for a proper migration (with history).
>>
> Copy without history to kdoctools is sufficient, I guess that would most teams 
> do themselves.

My only concern is for proper credits. Maybe I could just copy them and add
the credits in the commit message. What do you think?

Anyway, I need to fix the encoding issues before (iconv should help)

Ciao
-- 
Luigi



More information about the kde-doc-english mailing list