From owner-freebsd-doc Thu Nov 15 4:59:29 2001 Delivered-To: freebsd-doc@freebsd.org Received: from sekine00.ee.noda.sut.ac.jp (sekine00.ee.noda.sut.ac.jp [133.31.107.40]) by hub.freebsd.org (Postfix) with ESMTP id 8026037B417 for ; Thu, 15 Nov 2001 04:59:27 -0800 (PST) Received: from localhost (sekine01.ee.noda.sut.ac.jp [133.31.107.43]) by sekine00.ee.noda.sut.ac.jp (8.8.8+2.7Wbeta7/3.6W-12/10/97) with ESMTP id VAA05355; Thu, 15 Nov 2001 21:54:10 +0900 (JST) Date: Thu, 15 Nov 2001 21:40:17 +0900 (JST) Message-Id: <20011115.214017.71143189.hrs@sekine00.ee.noda.sut.ac.jp> To: horcicka@FreeBSD.cz Cc: freebsd-doc@FreeBSD.org Subject: Re: Why TIDY can never work correctly with ISO-8859-2 and others From: Hiroki Sato In-Reply-To: <20011115105650.W57038-100000@dual.ms.mff.cuni.cz> References: <20011115105650.W57038-100000@dual.ms.mff.cuni.cz> X-Mailer: Mew version 2.0 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Martin Horcicka wrote in <20011115105650.W57038-100000@dual.ms.mff.cuni.cz>: horcicka> And if you use char-encoding: raw - character entities with values above 255 horcicka> are not printed as entities - this is really bad in 8-bit encodings. Yes, Japanese docs also suffer from it. The input routine of tidy expands any entities first, even if -raw flag is specified. horcicka> In my opinion Tidy cannot be used for encodings it does not natively support horcicka> (i.e. for Russian and Czech (- still not in main CVS) translations of pages horcicka> and docs). I think so, too. As a workaround, we can apply a patch and use the modified version of tidy that can suppress to interpret given entities as entities themselves, but I do not know if it will be a good solution. -- | Hiroki Sato | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message