[prev in list] [next in list] [prev in thread] [next in thread]
List: gdb-patches
Subject: RFA: start of i18n
From: ac131313 () ges ! redhat ! com (Andrew Cagney)
Date: 2002-06-26 20:15:00
Message-ID: 3D1A832D.3020706 () ges ! redhat ! com
[Download RAW message or body]
> Date: Sat, 22 Jun 2002 11:51:03 -0400
>> From: Andrew Cagney <ac131313@cygnus.com>
>
>> >
>> > Speaking as a translator, freezing the strings before the release is a
>> > good practice. It would be nice if GDB followed it.
>
>>
>> How much before? 1 week, 1 month, ...
>
>
> A couple of weeks at least. It depends on the number of messages to
> translate, but I expect GDB to have a lot of them.
>
>
>> - branch gdb
>> - week later, freeze strings
>>
>> that leaves ~4-6 weeks.
>
>
> That might not be a good idea, since freezing strings only a week
> after the branch is too early; chances are later changes will have to
> modify the messages to some extent.
>
> It's better to leave 2 weeks extra between the day you are confident
> a release is ready and the actual release. Then just resync with the
> Translation Project database before you tar the release.
Ok. Lets try it. For 5.3 (~sep) perhaphs not seriously(1), but for 6.0
(~jan).
Andrew
(1) I'm going to assume that 5.3 won't be very i18n.
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic