From owner-freebsd-doc Thu Nov 4 6:51:47 1999 Delivered-To: freebsd-doc@freebsd.org Received: from sonet.crimea.ua (OTC-sl3-FLY.CRIS.NET [212.110.136.71]) by hub.freebsd.org (Postfix) with ESMTP id 1BDEB158A6; Thu, 4 Nov 1999 06:48:48 -0800 (PST) (envelope-from phantom@scorpion.crimea.ua) Received: (from uucp@localhost) by sonet.crimea.ua (8.8.8/8.8.8) with UUCP id QAA28335; Thu, 4 Nov 1999 16:52:43 +0300 (MSK) (envelope-from phantom@scorpion.crimea.ua) Received: (from phantom@localhost) by scorpion.crimea.ua (8.8.8/8.8.5+ssl+keepalive) id JAA22675; Thu, 4 Nov 1999 09:29:22 +0300 (MSK) Date: Thu, 4 Nov 1999 09:29:22 +0300 From: Alexey Zelkin To: "Andrey A. Chernov" Cc: Wolfram Schneider , doc@FreeBSD.ORG Subject: Re: Wrong charset for russian FAQ Message-ID: <19991104092921.A22610@scorpion.crimea.ua> References: <19991031175224.51127@panke.de.freebsd.org> <19991031222100.A24848@scorpion.crimea.ua> <19991103190659.A10863@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.7i In-Reply-To: <19991103190659.A10863@freebsd.org> X-Operating-System: FreeBSD 2.2.7-RELEASE i386 Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org hi, On Wed, Nov 03, 1999 at 07:06:59PM -0800, Andrey A. Chernov wrote: > > > There is no character set defined for the russian FAQ. > > > Which means, the browsers will fall back to iso8859-1 ;-/ > > > > Usually it's not a problem. User can select any encoding by hands. > > It is a really big problem. NO encoding by hands please! > There is NO user in search engine to select. I already fixed this problem. All FAQ html files now have requried META field. > Russian charses was correct in the FAQ for years, I don't know who broke this. Looks like it was broken on linuxdoc -> docbook conversion stage. -- /* Alexey Zelkin && phantom@cris.net */ /* Tavric National University && phantom@crimea.edu */ /* http://www.ccssu.crimea.ua/~phantom && phantom@FreeBSD.org */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message