Previously Martin Quinson wrote: > First, AFAICS, they are not used yet to generate the pages. I guess it is an > ongoing work, and you will definitively switch when sure that it works, am I > right?
Yes. > Then, you choosed to use the sgml version of DocBook, and not the xml one. > That's quite sad in my point of view, since tools exists to manage the > translation of xml files easily. Would it be possible to change the headers > from: > <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> > to: > <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.1//EN" > "docbook/dtd/xml/4.1/docbookx.dtd"> Provided I can get the same quality output from it, yes. This mostly holds for the dpkg reference manual (see doc/reference.sgml). I'm currently using a combination of jade, htmldoc and a stylesheet from LDP. I still need to commit the right make bits for that though. > Even if I'm not online right now to make it sure, I guess it's related to a > commit I've seen (but erased too early) about removing useless ISO stuff. That was only for a single file where podlifter added it unnecessarily. I did try to use all the tags properly so everything should be reasonably proper XML at least. > The benefit is that using the poxml package, you can convert the english > file to a pot file (separated from the main one, not distributed in the > tarballs), then, you translate this file like any other po, and then you can > generate the (translated) xml file back. This ease greatly tracking which > file is outdated, and which part changed. That does sound nice indeed. > It wont add any build or plain depend, since this process only have to take > place on translators machines. Only man pages are distributed. I would want to have the translated po file in CVS and generate the manpages when creating a tarball we can ship. > What is your opinion here ? Is there some bad things I missed about docbook > xml, or could you imagine to switch ? If it works I'm definitely in favour of switching. Right now my main goal is converting all the existing documentation to docbook and I am familiar enough with the sgml version of docbook to get that done properly. If you can provide me with a patch to turn a docbook file into proper XML and tell me the magic commands to turn that file into goodlooking html, nroff and pdf I'll gladly switch. Wichert. -- _________________________________________________________________ /[EMAIL PROTECTED] This space intentionally left occupied \ | [EMAIL PROTECTED] http://www.liacs.nl/~wichert/ | | 1024D/2FA3BC2D 576E 100B 518D 2F16 36B0 2805 3CB8 9250 2FA3 BC2D | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
