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

Re: [D-I Manual] Build log for ru (02 Jan 2005) - ERRORS DURING BUILD

On Jan 02, 2005 at 04:52:14PM +0100, Frans Pop wrote:
> > !!! There were errors during the build process.
> > !!! Please check the log and correct the errors.

> The following lines seem to be unavoidable:
> dvips: Font lasx2488 at 8000 not found; scaling 600 instead.
> dvips: Such scaling will generate extremely poor output.

Nothing can be done against it with current toolchain. :( However, I do
have some other solution, see below.

> I have made sure that they will not trigger the "ERRORS DURING BUILD" 
> status in these log mails anymore.

Yes, that would be nice ;)

> If you want, I could try to filter these messages out.

I guess, it's not necessary. They'll remind us of the bad status of
localized docs :(

> For hppa:
> /usr/bin/openjade:build.tmp/install.ru.profiled.xml:1573:8:E: end tag for 
> "sect1" which is not finished
> Warning: recieved error 1 from 'openjade'; probably non-fatal so ignoring.
> For mipsel:
> /usr/bin/openjade:build.tmp/install.ru.profiled.xml:1658:8:E: end tag for 
> "sect1" which is not finished
> Warning: recieved error 1 from 'openjade'; probably non-fatal so ignoring.

These two seem to be the same. Both are IMHO bugs in the original doc: in
boot-installer/ some archs do not have any text in the section. The
english doc inserts an empty <para> to fool the tools into thinking there
is actually some text in the chapter. The bad thing about it is: po2xml
cut such empty <para>s:

Creating .xml files for language ru
- administrivia/administrivia: creating translated .xml
- appendix/random-bits: creating translated .xml
- appendix/gpl: creating translated .xml
- /bookinfo: creating translated .xml
- boot-installer/boot-installer: creating translated .xml
found empty tag para
found empty tag para
found empty tag para
- boot-new/boot-new: creating translated .xml
- hardware/hardware: creating translated .xml

Can we insert some equivalent to &nbsp; in there, so that they are not
empty? Or better: insert some warning like "doc is missing here, please
refer to the chapter 'Helping out'..."

> For powerpc:
> /usr/bin/openjade:build.tmp/install.ru.profiled.xml:2869:794:E: document 
> type does not allow element "command" here
> Warning: recieved error 1 from 'openjade'; probably non-fatal so ignoring.

Aha, this one is our fault, will get corrected Really Soon Now (tm).

And now, for the promised new solution to the PDF problem:

I'm currently experimenting with DB2LaTeX and I can currently produce nice
looking russian PDFs (I guess, Japanese too). It's good enough, has
hyphenation and good-looking fonts, but many things still need tweaking,
mostly tables. I'm on it, I think I know now how to patch db2latex the
right way. However, one thing that is difficult to implement is the
morerows property of table rows. It is used for example in the required
hardware chapter, but is not used in the contributors' table. There are
about 15 occurences in the whole manual. Any chance to remove them and
insert empty cells instead? This would enable us to use more modern and
rather upstream-alive db2latex instead of openjade.

Nikolai Prokoschenko 
nikolai@prokoschenko.de / Jabber: pronik@jabber.org

Reply to: