> 5) We have been working for translating docs into Japanese using
> EUC_JP encoding. Converting to HTML is no problem, but we cannot
> get correct results for sgml-> RTF conversion at all. The
> translated docs are just not be able to read, showing random
> characters. It seems that openjade supports multibyte encodings at
> least according to their manuals, but I can not get it working. I
> have asked to dssslist but I have not gotten usefull helps yet.
>
> A qustion comes to my mind: Is really sgml is an appropriate doc
> format for us? For me, LaTeX seems more handy. It can generate HTML
> using latex2html, and of course can produce beautiful hard copies
> AUTOMATICALLY for English and other languages including Japanese.
Tatsuo, when I added SGML reference pages to the back of my book, I took
the HTML-generated output from SGML and loaded that into LaTeX. I did
have to do a few things:
convert SGML to HTMLhtml2latexadd * to \subsection* ?remove \newlineremove \backslashremove \begin_inset Figure { ? }
to?remove trailing space from Descriptionno table conversionchange $$ to $ $no SQL query conversion, all on one line ,
programlisting and synopsisspace-period and space-comma
It actually was pretty quick. The fixes were more cleaning up strange
conversion from HTML to LaTeX.
As far as I can see, SGML gives us rich content tags, so we can do
things like pull the SGML ref manual pages headings right into pgsql's
help system. However, what it doesn't give you is much control over
appearance except how to map the tags to appearance. You can't tweek
appearance in SGML unless you make special tags for certain appearances.
-- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610)
853-3000+ If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill,
Pennsylvania19026
