Date: Thu, 08 May 1997 15:49:34 +0900 From: Hiroyuki HANAI <hanai@astec.co.jp> To: ache@nagual.pp.ru Cc: hanai@FreeBSD.ORG, CVS-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG, cvs-share@FreeBSD.ORG Subject: Re: cvs commit: src/share/doc/ja_JP.EUC/handbook mirrors.sgml Message-ID: <19970508154934Q.hanai@astec.co.jp> In-Reply-To: Your message of "Wed, 7 May 1997 21:21:24 %2B0400 (MSD)" References: <Pine.BSF.3.96.970507211433.1341A-100000@nagual.pp.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
From: <ache@nagual.pp.ru> Date: Wed, 7 May 1997 21:21:24 +0400 (MSD) > Just walking in Japanese handbook I found that it is done incorrectly > in terms of HTML internationalization. It not specifies page charset > anywhere. When the page not specify its charset, iso-8859-1 always assumed > according to latest standard. Yes, I know that problem. However, to add <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=EUC-JP">, lines into HTML files of Japanese handbook, we need to hack the sgmlfmt. Also, we should change the DOCTYPE declaration of HTML files for Japanese handbook because current sgmlfmt generates the HTML 3.2 compliant files and their first line begins with <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN">. On the other hand, DOCTYPE declaration for internationalized HTML files should be: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML i18n//EN">. Now, I have no idea and have left the problem as it is :-( John! Do you have any idea? As a practical matter, almost all the Web clients, which supports Japanese, can detect the Japanese character encoding automatically and above problem is not fatal. -- HANAI Hiroyuki/Ph. D./hanai@astec.co.jp ASTEC Inc./BR Ichigaya 6 Minami-cho Shinjuku-ku Tokyo 162 JAPAN (81)3-5261-5974(Tel)/(81)3-5261-5980(Fax)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19970508154934Q.hanai>