Date: Thu, 19 Jun 1997 11:48:42 +0400 (MSD) From: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= <ache@nagual.pp.ru> To: Satoshi Asami <asami@cs.berkeley.edu> Cc: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG, cvs-doc@FreeBSD.ORG Subject: Re: cvs commit: doc/ja_JP.EUC/handbook Makefile Message-ID: <Pine.BSF.3.96.970619113642.22875B-100000@lsd.relcom.eu.net> In-Reply-To: <199706190704.AAA19688@silvia.HIP.Berkeley.EDU>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 19 Jun 1997, Satoshi Asami wrote: > * You just broke charset= for FreeBSD EUC handbook. > > Sorry about that. We Japanese have gotten used to explicitly specify > the document encoding, so this doesn't really "break" anything for us. > > If you really must insist, I can add a version check in the Makefile, > but is it really necessary to go that far? Yes, it seriously breaks both HTTP standards and conforming browsers (Lynx is nearest example, and maybe Tango). All pages without charset= treated as strictly 8859-1 pages per standards! I'd like to see FreeBSD following standards too independently of amount of lamers which not specify charset= for their HTML pages. If we consider this thing from another point of view (forget about standards), we realise that it is really difficult to find something at Japanese HTML page without charset= because ASCII chars are hidden among other ISO8859-1 junk. Don't tell me about Japanese-Audetect, it is confused with Russian pages which treated as Japanese ones. Also I don't understand why I forced to manually switch to EUC encoding when I walk into Japanese page while the browser itself must do it for me automatically. So, please restore this thing somehow to see our hanbook at FreeBSD WWW with charset= -- Andrey A. Chernov <ache@null.net> http://www.nagual.pp.ru/~ache/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.970619113642.22875B-100000>