Re: build of etch release-notes from svn, conflicts with sgml vs po: ro, pt, ru
(I am not responsible for the translation and I am not saying that I will
do the necessary steps to remove the duplication, but I have looked over
the diff and I am communication what I saw.)
2009/1/12 Simon Paillard <firstname.lastname@example.org>:
> Dear russian, portuguese and romanian l10n team,
> During the build of etch release notes, it appears that some of your
> translations are performered in the po files, some other in the SGML.
> Please see below what you should perform to update the po file before
> the SGML can be safely removed.
As I understood, the po-s should be updated automatically with the
proper templates, shouldn't they?
> On Mon, Jan 12, 2009 at 10:13:26AM +0100, Jens Seidel wrote:
>> On Sun, Jan 11, 2009 at 10:51:07PM -0800, Matt Kraai wrote:
>> > On Sat, Jan 10, 2009 at 09:10:01PM +0100, Simon Paillard wrote:
>> > > The Etch build seems to be ok (at least the html part).
>> > >
>> > > In order to switch to the SVN source instead of old CVS on www-master:
>> > > * svn co svn://svn.debian.org/svn/ddp/manuals/tags/release-notes/etch
>> > > * modify the crontab in order to "svn up" instead of "cvs up"
>> > Done. Thanks for the instructions.
>> Thanks. So it is probably OK to work in tags/ to fix remaining minor issues?
>> Normally such work happens on a branch.
> Anyway SVN doesn't make the difference between a tag and a
>> But as work on the Etch version stopped there should indeed no problem
>> with it.
> As spotted by Rhonda, some sgml files are stored in the (etch) SVN
> together with their po source, as a consequence :
> $ svn status | grep -v ^?
> M ro/release-notes.ro.sgml
> M pt/release-notes.pt.sgml
> M ru/release-notes.ru.sgml
> Unfortunately, they cannot be removed straight away from the SVN,
> because the translations are not consistent in PO and SGML :
> Please see the diff between the SGML present on the SVN and the SGML
> generated from the PO :
I looked at the diff and the new version (the working copy in the diff) was
replacing translations with the english texts, or just adding more paragraphs.
There were NO paralel translations (at least they were not visible in the diff,
thus they would result in the same sgml, so no problem).
If I am understanding correctly, the po files should be updated and old
translation would be fuzzied, like with any regular gettext-ized package, so
I think is safe to drop the romanian sgml.
> Then update the PO so that no translated string gets lost when the SGML
> will be removed from the SVN.
> The right place to change the po is :
Why are we talking about *ETCH* release notes? is a parallel release like it
was done with sarge+etch when etch was initially released is planned?
"Imagination is more important than knowledge" A.Einstein