Re: release notes clarification and the situation for Romanian
On 2009-02-06 19:11, W. Martin Borgert wrote: > I will test some stuff on my > etch chroot anyway, so I will also check whether ro builds > with dblatex (backport from lenny) on etch, OK? Tested pdf for ro on etch (with the dblatex backport) and it looks fine to me. (And of course, it looks better now...) -- To UNSUBSCRIBE, email to debian-www-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: release notes clarification and the situation for Romanian
Quoting Eddy PetriÈor : > About the backport, do you already have a backport for all the needed > packages? I know dblatex and xmlroff are needed, but IIRC some of the > tex stuff was necessary, too (for UTF-8 support, for example). Or am I > confusing etch release build system with lenny's? I don't know. IIRC, all (etch + lenny) release notes are built on www-master.d.o, where dblatex and xmlroff backports are installed. If you remember the needed packages, please tell us and DSA :~) -- To UNSUBSCRIBE, email to debian-www-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: release notes clarification and the situation for Romanian
(keep me CC-ed) 2009/2/6 W. Martin Borgert : > Quoting Eddy Petrișor : >> Still, I am wondering, why wasn't Romanian using dblatex in the first place? > > To be honest: I don't remember. I will test some stuff on my > etch chroot anyway, so I will also check whether ro builds > with dblatex (backport from lenny) on etch, OK? Excellent. Note that I haven't committed yet the changes. I will when I'll get home (in about an hour or so). About the backport, do you already have a backport for all the needed packages? I know dblatex and xmlroff are needed, but IIRC some of the tex stuff was necessary, too (for UTF-8 support, for example). Or am I confusing etch release build system with lenny's? -- Regards, EddyP = "Imagination is more important than knowledge" A.Einstein -- To UNSUBSCRIBE, email to debian-www-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: release notes clarification and the situation for Romanian
Quoting Eddy PetriÈor : > Still, I am wondering, why wasn't Romanian using dblatex in the first place? To be honest: I don't remember. I will test some stuff on my etch chroot anyway, so I will also check whether ro builds with dblatex (backport from lenny) on etch, OK? -- To UNSUBSCRIBE, email to debian-www-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: release notes clarification and the situation for Romanian
(-doc and -www, please CC me) 2009/2/6 Eddy Petrișor : >>> - Should lenny's release notes be compilable on etch? >>=20 >> Yes. > > Thanks for the info, but currently we're having trouble compiling > *cleanly* the pdf version even on lenny. OK, after looking at the German PDF and seeing the difference, I managed to workaround the bug in xmlroff by switching to dblatex. It works well and I haven't seen any issues until now (diacritics are properly rendered, formatting seems to be kept properly). I made this on a lenny machine. I will commit the changes (AFAIK Romanian is deactivated) and try to see if I can build on etch (if necessary prepare the needed backports). Still, I am wondering, why wasn't Romanian using dblatex in the first place? > It seems we have hit an xmlroff bug which prevents us from compiling the > thing appropriately. The bug seems to be this: > > http://xmlroff.org/ticket/68 > >>=20 >> The build for www.debian.org will be performed on >> www-master.debian.org, which is (and will be) running etch, with some >> backported packages. If you need extra backported packages, please >> ensure that they're available via www.backports.org and let the >> debian-admin team know. > > AFAICT, there are still some unsolved issues in lenny, less talk about > etch (backports). Now are fixed: 0 e...@twix ~/usr/src/perso/__traduceri/release-notes/release-notes-trunk-svn $ make html txt pdf LINGUA=ro architecture=all PERLLIB=lib/ po4a-translate --format docbook --keep 0 --master en/about.dbk --po ro/about.po --localized ro/about.dbk PERLLIB=lib/ po4a-translate --format docbook --keep 0 --master en/installing.dbk --po ro/installing.po --localized ro/installing.dbk PERLLIB=lib/ po4a-translate --format docbook --keep 0 --master en/issues.dbk --po ro/issues.po --localized ro/issues.dbk PERLLIB=lib/ po4a-translate --format docbook --keep 0 --master en/moreinfo.dbk --po ro/moreinfo.po --localized ro/moreinfo.dbk PERLLIB=lib/ po4a-translate --format docbook --keep 0 --master en/old-stuff.dbk --po ro/old-stuff.po --localized ro/old-stuff.dbk PERLLIB=lib/ po4a-translate --format docbook --keep 0 --master en/release-notes.dbk --po ro/release-notes.po --localized ro/release-notes.dbk PERLLIB=lib/ po4a-translate --format docbook --keep 0 --master en/upgrading.dbk --po ro/upgrading.po --localized ro/upgrading.dbk PERLLIB=lib/ po4a-translate --format docbook --keep 0 --master en/whats-new.dbk --po ro/whats-new.po --localized ro/whats-new.dbk xsltproc --nonet --novalid --xinclude --stringparam draft.mode yes --stringparam profile.arch "all;alpha;amd64;arm;armel;hppa;i386;ia64;mips;mipsel;powerpc;s390;sparc;not-alpha;not-amd64;not-arm;not-armel;not-hppa;not-i386;not-ia64;not-mips;not-mipsel;not-powerpc;not-s390;not-sparc" \ --stringparam profile.condition "fixme;g-i;no-initrd;" \ http://docbook.sourceforge.net/release/xsl/current/profiling/profile.xsl ro/release-notes.dbk | xsltproc --nonet --novalid --xinclude --stringparam draft.mode yes /home/eddy/usr/src/perso/__traduceri/release-notes/release-notes-trunk-svn/preproc.xsl - > ro/release-notes.all.xml mkdir -p ro/release-notes.all.html/images cp debian.css ro/release-notes.all.html cp /usr/share/xml/docbook/stylesheet/nwalsh/images/*.png \ ro/release-notes.all.html/images cd ro && xsltproc --nonet --novalid --xinclude --stringparam draft.mode yes -o release-notes.all.html/ \ --stringparam html.ext .ro.html \ /home/eddy/usr/src/perso/__traduceri/release-notes/release-notes-trunk-svn/html.xsl release-notes.all.xml Writing ch-about.ro.html for chapter(ch-about) Writing ch-whats-new.ro.html for chapter(ch-whats-new) Writing ch-installing.ro.html for chapter(ch-installing) Writing ch-upgrading.ro.html for chapter(ch-upgrading) Writing ch-information.ro.html for chapter(ch-information) Writing ch-moreinfo.ro.html for chapter(ch-moreinfo) Writing ap-old-stuff.ro.html for appendix(ap-old-stuff) Writing relnotes-index.ro.html for index(relnotes-index) Writing relnotes-glossary.ro.html for glossary(relnotes-glossary) Writing index.ro.html for book xsltproc --nonet --novalid --xinclude --stringparam draft.mode yes /home/eddy/usr/src/perso/__traduceri/release-notes/release-notes-trunk-svn/txt.xsl ro/release-notes.all.xml \ | w3m -o display_charset=UTF-8 -cols 70 -dump -no-graph -T text/html > ro/release-notes.all.txt [ -f ro/ifxetex.sty ] || cp ifxetex.sty ro/ xsltproc --nonet --novalid --xinclude --stringparam draft.mode yes /home/eddy/usr/src/perso/__traduceri/release-notes/release-notes-trunk-svn/dblatex.xsl ro/release-notes.all.xml | dblatex --style=db2latex --xsl-user=hyphenation.xsl --param=lingua=ro --param=draft.mode=yes --output=ro/release-notes.all.pdf - Build the listings... XSLT stylesheets DocBook - LaTeX 2e (0.2.9-3) === No template matches subtitle in section. Build stdin.pdf This is pdfTeXk, Version 3.141592-1.40.3 (Web2C 7.5.6) %&
Re: release notes clarification and the situation for Romanian
Quoting Jens Seidel : > On Fri, Feb 06, 2009 at 10:41:44AM +, W. Martin Borgert wrote: > > On 2009-02-06 10:14, Jens Seidel wrote: > > > PS: Building the last Release Notes took more than 12 hours on > www-master. > > > > dblatex is much faster on lenny than on etch. Also, po4a seems > > to eat a lot of time. The more translations we have, the longer > > it takes. > > Right, I remember that updating PO files can took hours with po4a (to find > via msgmerge similar already translated fuzzy messages, it's probably > O(n^2)). > But just building DocBook/XML files from PO should need only seconds?! Indeed: "should". I have no idea, why it takes so long. (Btw. on lenny po4a is even a little bit slower than on etch.) > PS: Why has Spanish always problems building on www-master? Spanish is really > not an exotic language but the log contains: > > es/whats-new.dbk:595: parser error : StartTag: invalid element name > con linux-image-2.6 fallen si está usando una versión 2.2 o 2.4 del núcleo.< > > followed by many further errors. Looks like the translator put a wrong element into the XML, maybe an obsolete SGML one. I almost daily fix XML errors in most translations... > Another question: Why is the net access of xsltproc disabled (--nonet)? > (That's maybe required on buildds but also on www-master?) Whouldn't it solve > the errors: This is on purpose. The build process should not access the net and really does not need it. The error messages must be ignored. The newer xsltproc (lenny) does not print this messages anymore, IIRC. The DTDs are not needed for the build process anyway, but even if they would be needed, they would be accessed using XML catalogs. HTH! -- To UNSUBSCRIBE, email to debian-www-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: release notes clarification and the situation for Romanian
On Fri, Feb 06, 2009 at 10:41:44AM +, W. Martin Borgert wrote: > On 2009-02-06 10:14, Jens Seidel wrote: > > I compared the Romanian PDF file with the German one and it looks indeed > > completely > > different. But at least the content seems to be included. > > Most languages can work with dblatex, some not. They have to use > xmlroff, which is OK, but the layout does not look as good as > with dblatex, IMHO. Ah, they're build with different tools. Right, this explains it. > > I found a funny footnote in the German file > > http://www.debian.org/releases/testing/alpha/release-notes.de.pdf > > in section 4.5.8 (page 24): There is a large TeX code embedded: > ... > > Maybe a dblatex bug? Maybe. I will probably not find the time to analyse and report it ... > > PS: Building the last Release Notes took more than 12 hours on www-master. > > dblatex is much faster on lenny than on etch. Also, po4a seems > to eat a lot of time. The more translations we have, the longer > it takes. Right, I remember that updating PO files can took hours with po4a (to find via msgmerge similar already translated fuzzy messages, it's probably O(n^2)). But just building DocBook/XML files from PO should need only seconds?! PS: Why has Spanish always problems building on www-master? Spanish is really not an exotic language but the log contains: es/whats-new.dbk:595: parser error : StartTag: invalid element name con linux-image-2.6 fallen si está usando una versión 2.2 o 2.4 del núcleo.< followed by many further errors. Another question: Why is the net access of xsltproc disabled (--nonet)? (That's maybe required on buildds but also on www-master?) Whouldn't it solve the errors: I/O error : Attempt to load network entity http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd es/whats-new.dbk:5: warning: failed to load external entity "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; ]> Jens -- To UNSUBSCRIBE, email to debian-www-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: release notes clarification and the situation for Romanian
On 2009-02-06 10:14, Jens Seidel wrote: > I compared the Romanian PDF file with the German one and it looks indeed > completely > different. But at least the content seems to be included. Most languages can work with dblatex, some not. They have to use xmlroff, which is OK, but the layout does not look as good as with dblatex, IMHO. > I found a funny footnote in the German file > http://www.debian.org/releases/testing/alpha/release-notes.de.pdf > in section 4.5.8 (page 24): There is a large TeX code embedded: ... Maybe a dblatex bug? > PS: Building the last Release Notes took more than 12 hours on www-master. dblatex is much faster on lenny than on etch. Also, po4a seems to eat a lot of time. The more translations we have, the longer it takes. -- To UNSUBSCRIBE, email to debian-www-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: release notes clarification and the situation for Romanian
On Fri, Feb 06, 2009 at 02:38:57AM +0200, Eddy Petrișor wrote: > Thanks for the info, but currently we're having trouble compiling > *cleanly* the pdf version even on lenny. I compared the Romanian PDF file with the German one and it looks indeed completely different. But at least the content seems to be included. I found a funny footnote in the German file http://www.debian.org/releases/testing/alpha/release-notes.de.pdf in section 4.5.8 (page 24): There is a large TeX code embedded: \count3=-\count0\multiply\count3by64\advance\count3by#1\relax \divide\count0by64 %SPACE\count2=-\count0\multiply\count2by4096\advance\count2by#1% \divide\count2by64%\divide\count0by64 %SPACE \count1=-\count0\multiply\count1by262144\advanc \divide\count1by4096 %SPACE\advance\count0by240\advance\count1by128% ... Don't know a fix ... PS: Building the last Release Notes took more than 12 hours on www-master. What's going on? Jens -- To UNSUBSCRIBE, email to debian-www-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: release notes clarification and the situation for Romanian
Thanks for the info, but currently we're having trouble compiling *cleanly* the pdf version even on lenny. It seems we have hit an xmlroff bug which prevents us from compiling the thing appropriately. The bug seems to be this: http://xmlroff.org/ticket/68 Here is what happens (after a make clean): 0 e...@heidi ~/usr/traduceri/release-notes-svn $ make pdf LINGUA=3Dro architecture=3Di386 PERLLIB=3Dlib/ po4a-translate --format docbook --keep 0 --master en/about.dbk --po ro/about.po --localized ro/about.dbk PERLLIB=3Dlib/ po4a-translate --format docbook --keep 0 --master en/installing.dbk --po ro/installing.po --localized ro/installing.dbk PERLLIB=3Dlib/ po4a-translate --format docbook --keep 0 --master en/issues.dbk --po ro/issues.po --localized ro/issues.dbk PERLLIB=3Dlib/ po4a-translate --format docbook --keep 0 --master en/moreinfo.dbk --po ro/moreinfo.po --localized ro/moreinfo.dbk PERLLIB=3Dlib/ po4a-translate --format docbook --keep 0 --master en/old-stuff.dbk --po ro/old-stuff.po --localized ro/old-stuff.dbk PERLLIB=3Dlib/ po4a-translate --format docbook --keep 0 --master en/release-notes.dbk --po ro/release-notes.po --localized ro/release-notes.dbk PERLLIB=3Dlib/ po4a-translate --format docbook --keep 0 --master en/upgrading.dbk --po ro/upgrading.po --localized ro/upgrading.dbk PERLLIB=3Dlib/ po4a-translate --format docbook --keep 0 --master en/whats-new.dbk --po ro/whats-new.po --localized ro/whats-new.dbk xsltproc --nonet --novalid --xinclude --stringparam draft.mode yes --stringparam profile.arch "i386;not-alpha;not-amd64;not-arm;not-armel;not-hppa;not-ia64;not-mips;no= t-mipsel;not-powerpc;not-s390;not-sparc" \ --stringparam profile.condition "fixme;g-i" \ =09 http://docbook.sourceforge.net/release/xsl/current/profiling/profile.xsl ro/release-notes.dbk | xsltproc --nonet --novalid --xinclude --stringparam draft.mode yes /home/eddy/usr/traduceri/release-notes-svn/preproc.xsl - > ro/release-notes.i386.xml xsltproc --nonet --novalid --xinclude --stringparam draft.mode yes -o ro/release-notes.i386.fo fo.xsl ro/release-notes.i386.xml Making portrait pages on A4 paper (210mmx297mm) Read /usr/share/doc/docbook-xsl/README.Debian.gz section 5(a). USE_GP=3D`echo " " | grep " $LINGUA "`; \ if [ -n "$USE_GP" ]; then \ xmlroff --backend gp -o ro/release-notes.i386.pdf ro/release-notes.i386.fo; \ else \ xmlroff --backend cairo -o ro/release-notes.i386.pdf ro/release-notes.i386.fo; \ fi (xmlroff:22256): libfo-WARNING **: fo-table: table-layout=3D"fixed" but automatic table layout is specified since i-p-d=3D"auto". Object path: /FoTree[1]/FoRoot[1]/FoPageSequence[4]/FoFlow[1]/FoBlockBlock[2]/FoBlockB= lock[2]/FoBlockBlock[1]/FoTable[1] (xmlroff:22256): libfo-WARNING **: fo-table: Automatic table layout is not supported. Falling back to fixed table layout. Object path: /FoTree[1]/FoRoot[1]/FoPageSequence[4]/FoFlow[1]/FoBlockBlock[2]/FoBlockB= lock[2]/FoBlockBlock[1]/FoTable[1] (xmlroff:22256): libfo-WARNING **: fo-table-column-error: 'column-width' property must be specified when fixed table layout method is used. Object path: /FoTree[1]/FoRoot[1]/FoPageSequence[4]/FoFlow[1]/FoBlockBlock[2]/FoBlockB= lock[2]/FoBlockBlock[1]/FoTable[1]/FoTableColumn[1] (xmlroff:22256): libfo-WARNING **: fo-table-column-error: 'column-width' property must be specified when fixed table layout method is used. Object path: /FoTree[1]/FoRoot[1]/FoPageSequence[4]/FoFlow[1]/FoBlockBlock[2]/FoBlockB= lock[2]/FoBlockBlock[1]/FoTable[1]/FoTableColumn[2] (xmlroff:22256): libfo-WARNING **: fo-table-column-error: 'column-width' property must be specified when fixed table layout method is used. Object path: /FoTree[1]/FoRoot[1]/FoPageSequence[4]/FoFlow[1]/FoBlockBlock[2]/FoBlockB= lock[2]/FoBlockBlock[1]/FoTable[1]/FoTableColumn[3] (xmlroff:22256): libfo-WARNING **: fo-area-page-error: Child area overflows parent area Object path: /FoAreaTree[1]/FoAreaPage[10]/FoAreaViewportReference[1] (xmlroff:22256): libfo-WARNING **: fo-area-page-error: Child area overflows parent area Object path: /FoAreaTree[1]/FoAreaPage[12]/FoAreaViewportReference[1] (xmlroff:22256): libfo-CRITICAL **: fo_inline_fo_get_text_attr_list: assertion `FO_IS_INLINE_FO (fo_inline_fo)' failed (xmlroff:22256): libfo-CRITICAL **: fo_inline_fo_get_text_attr_list: assertion `FO_IS_INLINE_FO (fo_inline_fo)' failed (xmlroff:22256): libfo-WARNING **: fo-area-page-error: Child area overflows parent area Object path: /FoAreaTree[1]/FoAreaPage[18]/FoAreaViewportReference[1] (xmlroff:22256): libfo-WARNING **: fo-area-page-error: Child area overflows parent area Object path: /FoAreaTree[1]/FoAreaPage[18]/FoAreaViewportReference[1] (xmlroff:22256): libfo-WARNING **: fo-area-page-error: Child area overflows parent area Object path: /FoAreaTree[1]/FoAreaPage[18]/FoAreaViewportReference[1] (xmlroff:22256): libfo-WARNING **: fo-area-page-error: Child area overflows parent area Object path: /FoAreaTree[1]/FoAreaPa
Re: release notes clarification and the situation for Romanian
On Mon, Feb 02, 2009 at 04:59:35PM +0200, Eddy Petrișor wrote: > What is not clear: > - Should lenny's release notes be compilable on etch? Yes. > - On which distro will lenny's release notes be built? Etch or Lenny? The build for www.debian.org will be performed on www-master.debian.org, which is (and will be) running etch, with some backported packages. If you need extra backported packages, please ensure that they're available via www.backports.org and let the debian-admin team know. -- Matt http://ftbfs.org/ -- To UNSUBSCRIBE, email to debian-www-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: release notes clarification and the situation for Romanian
On Mon, Feb 02, 2009 at 04:59:35PM +0200, Eddy Petrișor wrote: > The Romanian team has worked to update the release-notes for both > lenny and etch. Now is clear to me/us that there are 2 sets of release > notes: > > - one for etch > - one for lenny > > Since we are a small team, we are mostly interested in the lenny release > notes. > > We know that there are some encoding issues for the *etch* release > notes if compiled on etch. Note that it is enough to recode to latin2 at po4a level or po level in order to solve that (explained on the list). > Also, there are some problems compiling lenny's release notes on etch > (packages missing which need to be backported). >From etch-backports: dblatex and xmlroff > What is not clear: > - Should lenny's release notes be compilable on etch? Yes, because www-master is running etch. > - On which distro will lenny's release notes be built? Etch or Lenny? Etch as long as www-master is runnning etch. -- Simon Paillard -- To UNSUBSCRIBE, email to debian-www-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: release notes clarification and the situation for Romanian
Please keep me (I am not subscribed) and the debian-l10n-romanian list in CC. 2009/2/2 Eddy Petrișor : > Hello, > > The Romanian team has worked to update the release-notes for both > lenny and etch. Now is clear to me/us that there are 2 sets of release > notes: > > - one for etch > - one for lenny > > Since we are a small team, we are mostly interested in the lenny release > notes. > > We know that there are some encoding issues for the *etch* release > notes if compiled on etch. Also, there are some problems compiling > lenny's release notes on etch (packages missing which need to be > backported). > > > > What is not clear: > - Should lenny's release notes be compilable on etch? > - On which distro will lenny's release notes be built? Etch or Lenny? > > -- > Regards, > EddyP > = > "Imagination is more important than knowledge" A.Einstein > -- Regards, EddyP = "Imagination is more important than knowledge" A.Einstein -- To UNSUBSCRIBE, email to debian-www-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
