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

Re: [i18n]Source packages and translation templates q.

On Mon, Sep 06, 2010 at 08:22:01PM +0100, Darren Salt wrote:
> I demand that Roger Leigh may or may not have written...
> > On Mon, Sep 06, 2010 at 05:53:02PM +0100, Darren Salt wrote:
> >> I demand that Neil Williams may or may not have written...
> >>> Churn is the problem here, IMHO. Many packages just change too fast at
> >>> specific times to allow generated files like the POT into the VCS. i.e.
> >>> the source code is changing and whether or not the translatable strings
> >>> actually change, committing the POT every time (because it timestamps
> >>> itself every time it is checked) is a PITA.
> >> Agreed. There have been times when I've taken a diff and stripped out any
> >> hunks which change only line numbers...
> > There's a solution to this:
> > Add --no-location to XGETTEXT_OPTIONS in po/Makevars.
> > Now those stupid comment lines with the source file and line number
> > are no longer generated (what use were they in the first place?)!
> Well... I'm aware that some translators have made use of this information...

Couldn't they just have used "grep"?  IMO the disadvantages of
having that constantly changing information far outweigh the
advantage of having it there for occasional use (and IME most
of the time the translators just get the po file by mail and
never look at the source).

Being able to merge/cherry-pick without having hundreds of
conflicts is also a major advantage.

How often do people make use of the information, and what for?
(I'd be genuinely interested to know; I haven't had any
complaints since I turned them off, but getting concrete
information about their usefulness is difficult.)  Do any
translators have any comments?


  .''`.  Roger Leigh
 : :' :  Debian GNU/Linux             http://people.debian.org/~rleigh/
 `. `'   Printing on GNU/Linux?       http://gutenprint.sourceforge.net/
   `-    GPG Public Key: 0x25BFB848   Please GPG sign your mail.

Attachment: signature.asc
Description: Digital signature

Reply to: