Re: [Bug-cpio] [ko-team] cpio.po unusable

[Vladimir 'φ-coder/phcoder' Serbinenko]

A short summary:
The file for Korean translation on Translations Project uses an obsolete
7-bit EUC-KR variant which isn't recognised by modern tools (they show
just gibberish with plenty of escapes). This encoding is stateful and
fixing any of usual tools will probably be a nightmare and is
unjustified. On the other hand this file if converted could be useful
for the future translation but if left in this old unusable encoding
will eventually be just discarded. So, I've wrote a small tool to
convert it to UTF-8. However since this translation wasn't updated in a
while and has no assigned translator it's not possible to upload the
transformed version. According to
http://www.gnu.org/licenses/gpl-faq.html#GPLOutput the automatic
transformation doesn't affect the copyright. Would it be possible to
have an exception for this case?
On 31.03.2012 12:59, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
> On 31.03.2012 12:34, Changwoo Ryu wrote:
>> 2012년 3월 31일 오후 7:22, Vladimir 'φ-coder/phcoder' Serbinenko
>> <address@hidden>님의 말:
>>> On 31.03.2012 12:07, Changwoo Ryu wrote:
>>>> 2012년 3월 31일 오후 6:59, Vladimir 'φ-coder/phcoder' Serbinenko
>>>> <address@hidden>님의 말:
>>>>>> >From http://translationproject.org/PO-files/ko/cpio-2.11.ko.po
>>>>>>
>>>>>> "POT-Creation-Date: 2010-03-10 15:04+0200\n"
>>>>>> "PO-Revision-Date: 1997-10-31 19:25+0900\n"
>>>>>>
>>>>>> It means this translation has not been updated since 1997.
>>>>> It means that the Korean translation wasn't updated since 1997. Others
>>>>> like German was updated recently (in January 2012)
>>>>>> So nobody cares about it anymore. Again, contact the cpio maintainer.
>>>>> AFAIU maintainer treats all translations in same way and if German
>>>>> update made sense, why doesn't Korean do?
>>>>> Also even if this domain wasn't used anymore as such, TP database is
>>>>> often used for generating translation memory and fixing encoding is a
>>>>> way to avoid misconverted string cripple into other translations. So
>>>>> IMHO updating TP copy always makes sense.
>>>> If you want it to be fixed. You are contacting a wrong place.
>>>>
>>>> Currently no Korean translator is interested with the cpio
>>>> translation. That's all. So there's no one remaining in this maliing
>>>> list to hear your feedback.
>>> I don't understand your reluctance as to just upload the file. I'm not
>>> asking you to translate anything.
>>> And you said yourself "currently". If in the future someone takes over
>>> it and sees unusable file, he's likely to discard it altogether. With
>>> this one he'll have at least few strings already translated.
>> Well, in the TP translation process, only the assigned translator(s)
>> can submit their translations. This policy is more strict especially
>> in case of GNU programs like GNU cpio. (It's one of the TP's critical
>> problems.) I was so skeptical because of it; no one in this list can
>> submit your fixed translation.
> According to http://www.gnu.org/licenses/gpl-faq.html#GPLOutput the
> output of automated conversion, like this one, retains original
> copyright and no separate assignment is necessarry. Since it's on GNU
> official website I suppose, it's authoritative for GNU translations.
>
>


-- 
Regards
Vladimir 'φ-coder/phcoder' Serbinenko

signature.asc
Description: OpenPGP digital signature