[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: DDTP: Please remove pl_PL and merge it with pl

On Sun, Jul 15, 2007 at 12:24:14PM +0200, Jens Seidel wrote:
> On Sat, Jul 14, 2007 at 08:17:47PM -0500, Ming Hua wrote:
> >
> > Of course, I didn't suggest to drop them.  I've now downloaded the
> > Translation-zh file and found out that they are all simplified (zh_CN)
> > translations, so should be merged into zh_CN.  I'll do this via email
> > interface in the following days (I need to learn using DDTP), and it's
> > safe to turn off accepting zh translations now.
> It's not difficult but could nevertheless require a few hours of work:
> Obtain the current zh_CN translation via a subject line
>  GET <package name> zh_CN.UTF-8
> Wait for the mail and decide wether the zh_CN or zh translation should
> be used (or merge both). Copy the translation into the proper mail
> attachment part and send it back to pdesc@ddtp.debian.net. That's all.
> (You can send multiple messages back at once, but test with a single one
> first.)

Thanks for the note.  I am working on this.

> Thanks for the explanation. Nevertheless using an already translated
> description into zh_TW as default template for zh_CN would be useful,
> right? Same for pt and pt_BR.

It would be useful, yes, but probably not for every translator.  I
personally like to compare with zh_TW translations when working on zh_CN
ones, but I know some translators don't like the other script.

The translation for zh_TW can't be used as is for zh_CN anyway, since
the scripts are still different even both are using UTF-8, and
conversion is required.  As there is always political tension in such
issues, I suggest not to implement sending zh_TW translation as the
default template for zh_CN without discussion among zh_CN translators.
I am not doing DDTP translation myself so I would rather not be
involved.  The Chinese DDTP translations doesn't seem very active now

> Michael, could you implement this? I also suggest to assume that the
> user always requests UTF-8 encodings if he didn't explicitely specified
> the encoding. So please always send "Description-<lang>.<encoding>:"
> messages, where <encoding> defaults to UTF-8. Thanks.


Reply to: