Re: Updating po files on make dist

fre, 23.05.2003 kl. 18.52 skrev Christian Rose:
> fre 2003-05-23 klockan 16.48 skrev Kjartan Maraas:
> > A single command resolves the problem and I really think the benefits of
> > having a consistent po dir outweighs the downside here...
> What would those benefits be? Cosmetic reasons?
> I fail to see other benefits by forcefully regenerating every po file
> everywhere with every release and putting those changes back into cvs.
> What purpose does such bitshuffling serve, except cause cvs conflicts?
> We do have intltool and the translation status pages these days, so we
> don't need constantly regenerated files being put back into cvs. So
> what's the benefit?

- the tarball matches what's tagged as the release in CVS
- there is a speedup on make dist for larger modules
- obsolete strings are marked as such, removing the possibility that
someone translates obsolete stuff because they forget to do a msgmerge
with a current template before they start
- we don't have to change change any tools
- we can end this thread? :-) (just kidding, I ran out of arguments)

Even so, I don't have a very strong opinion on this issue and it's not
like all maintainers already commit all the changes to CVS...


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