Date: Sun, 29 Aug 1999 14:12:09 +0900 From: Jun Kuriyama <kuriyama@FreeBSD.org> To: doc@freebsd.org Subject: Re: Japanese FAQ on the Web is broken Message-ID: <14280.49449.39009.25288P@localhost.sky.rim.or.jp> In-Reply-To: In your message of "Thu, 26 Aug 1999 21:18:30 %2B0100" <19990826211830.C86126@catkin.nothing-going-on.org> References: <19990826192109K.matusita@matatabi.or.jp> <19990826211830.C86126@catkin.nothing-going-on.org>
next in thread | previous in thread | raw e-mail | index | archive | help
From: Nik Clayton <nik@freebsd.org> > The "normal" way to tell the stylesheets what language your document is > written in is to add the 'lang="xx"' attribute to the first element in > your document. For example, the Japanese Handbook (or FAQ) should start > <book lang="ja"> > If you look at the Spanish FAQ you'll see it starts > <book lang="es"> > For reasons I don't fully understand (Jun Kuriyama is the expert here) > this isn't working properly for the Japanese translation. I believe Jun > has patches for this problem for the stylesheets, but they have not yet > been incorporated in to the version we use (I think that's the case, but > Jun might well correct me on this point). Some days ago, Norm's dsssl-docbook-modular begins to contain Japanese i18n modules. It is encoded in Unicode with UTF-8 but my old patches and Japanese Documentation Project are using EUC-JP encoding. I've discussed about it with original author of Norm's Japanese modules, and we decide it is good way to include UTF-8, EUC-JP and Shift_JIS encoding in Norm's distribution in current situation of Japanese encoding scheme problem. But (of course, it's my fault) this work has not be done. So Japanese Handbook will not use 'lang="ja"' until this feature is implemented. > This is a rather convoluted way of saying > If the tools that process the Japanese documentation have the command > line flag '-ilang.ja' passed to them, add the additional HTML header > tags "Content-Type", and set it to "text/html; charset=EUC-JP". > This is what your web browser is looking for before it will switch to using > a Japanese font -- note that you could still have told your browser to > use a Japanese font and the page would like fine, but it's that header > in the HTML (do "View Source" in any of the Japanese HTML pages to see it) > that tells your browser to do this automatically. Just FYI, according to HTTP/1.1 specification, using "META" tag for guessing encoding scheme is not the best way. Our pages should return charset parameter in HTTP header (not HTML header). Jun Kuriyama // kuriyama@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14280.49449.39009.25288P>