Hi, On Fri, Sep 05, 2008 at 04:01:41PM +0200, Rainer Gerhards wrote: > First of all, there seems to be a minor nit with the current set of > files. Please have a look at what happens here: > > -------------------------------- > [EMAIL PROTECTED] rsyslog]# xml2po -v > 0.12.2 > [EMAIL PROTECTED] rsyslog]# make -C man/ja create-pot > make: Entering directory `/home/rger/proj/rsyslog/man/ja' > /usr/bin/xml2po -e -o rsyslogd.8.pot ../C/rsyslogd.8.xml (snip) > UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position > 4930: ordinal not in range(128) > make: *** [rsyslogd.8.pot] Error 1 > make: Leaving directory `/home/rger/proj/rsyslog/man/ja' > ---------------------------------- > Do you have an idea how I can find out what exactly to fix (I think I > understand that there is in invalid character in rsyslogd.8.xml, but the > error message is not very helpful at pointing me at the actual trouble > source ;)). This is an well-known annoying issue of python. 'ascii' is the default internal encoding so that this happens.
There are many ways to "fix" this but to upgrade the latest gnome-doc-utils (0.13.1; this problem is solved already), looks the best. > >From an upper level view, I now understand the workflow as follows: > > When I update the documentation, I update the files in ./man/C. These > are kept in docbook format and these are the only sources for the > English language documentation. > > After I have updated these files, every translator needs to run > > $ make -C man/<lang> update-po > > to update the PO files. The translators will work on the .po files only. correct if [s]he or other made the required files (PO) already. > When they are (sufficiently ;)) finished, the man files need to be > regenerated. Let me elaborate a bit on this process, I'd like to get to > some details. > > As far as I understand, this results in the .po files being converted > back to docbook. Then, docbook is used to generate the ultimate > destination, e.g. the man files. The same process is used to generate > the English files, except that the docbook tools are run directly, > because there were no interim .po files. exactly. DocBook XML files just play an intermediate format role a. to generate man pages (result) b. to generate POT (and PO indirectly) to facilitate translation > Is this description correct? I am asking because I think it would make > sense to generate different formats (man, html, pdf at least) from the > same set of source files. So I understand that .po is just an interim > step which makes translation easier, but there will be a translated > version which in turn can be processed into any format that docbook > tools support. absolutely correct. > I'd greatly appreciate your feedback. If you know how to do it, I would > also greatly appreciate if you could provide me a patch (or > instructions) on how to generate pdf from the "man files". (snip) OK, I'll try to make it. wait for a while, please. Unfortunatelly, xml to pdf transformation process is much complicate than html/man/other text based formats and it brings another dependencies - fonts and XSL-FO processor :-P - satoru _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog
