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

Re: release notes and msgid-previous (was: Re: (forw) Release update: deep freeze, planned dates, and remaining bugs

Thanks to everyone for their replies. :)

On 04/02/2009, at 1:04 AM, W. Martin Borgert wrote:

Quoting Clytie Siddall <clytie@riverland.net.au>:
What's our deadline for completing the release-notes translation?

We didn't yet agree on a deadline, but I suggest sth. like
Sunday, 2009-02-08 23:59 UTC for the English version and
Thursday, 2009-02-12 23:59 UTC for translations. OK?

That's enough time for translations, provided there aren't many more changes. Is there much more to be done, apart from the TODO's (which hopefully aren't large changes)?

Last-minute changes will be hard for doc-writers and translators alike. :S

It would really help if the release-notes (and any other document
translations using PO format) used the gettext feature msgid-previous
[1] (as D-I and many debconf files do). This feature makes it much
easier to see what changes have occurred in strings. It's especially
helpful with complex or long strings: documentation files are a
classic case.

Yes, there are two lines in the Makefile starting with UPDATEPO,
of which one is uncommented. Please change this in your local copy.
(We have to support etch, were po4a does not have --previous.)

Thanks for that info. :)

I've copied the svn-updated release-notes/Makefile into release-notes/ vi/ and uncommented (removed #) the UPDATEPO line containing "-- previous". So the next run of po4a (with the next lot of changes, I'm assuming) will give me msgid-previous? Yay! :D

That, and the syntax highlighting in my PO editor, certainly make editing complex strings much easier. Less headaches per ball of string(s).

from Clytie

Vietnamese Free Software Translation Team

Reply to: