On Thu, Feb 05, 2009 at 10:23:23PM +1030, Clytie Siddall wrote: > On 04/02/2009, at 1:04 AM, W. Martin Borgert wrote: >>> 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.) > > I've copied the svn-updated release-notes/Makefile into release-notes/ > vi/
The Makefile should not be copied into vi/. It assumes to be located at the top level directory of the Release Notes. > 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 Since you do not work in a Linux environment and don't have po4a installed you don't have to make anything. The person who calls "make LINGUA=vi updatepo" should remember it and do it for you. The last time I forget it, sorry. But at least I warned you that you worked on old files and tried to reduce the trouble by updating the files immediately. Nevertheless I assume the required changes to resolve these fuzzy states were only marginal as only a few small paragraphs were affected. Jens -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
