看板 FB_doc 關於我們 聯絡資訊
----Security_Multipart(Thu_Jan_17_15_27_04_2008_608)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit "Murray Stokely" <murray@stokely.org> wrote in <2a7894eb0801162124x76d7132y8de9f4a1d314d8aa@mail.gmail.com>: mu> Is there any reason not to update the docproj port to use tidy-devel rather mu> than tidy? The released version of tidy is nearly 8 years old and produces mu> xhtml that doesn't validate. The newer -devel releases produce more correct mu> xhtml. IIRC the reason was the encoding support and entity handling. Tidy's -raw option did not work for several 8-bit encodings because tidy always expands a numerical entity into a raw character at the parsing stage, so entities such as &copy; are broken (it will typically be converted to corresponding raw iso8859-1 characters) in the output HTML file. I know the latest version of tidy has preserveEntities option but not sure if it works with encodings which did not work with the old tidy. I will give it a try. -- | Hiroki SATO ----Security_Multipart(Thu_Jan_17_15_27_04_2008_608)-- Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQBHjvU4TyzT2CeTzy0RAsSHAJ0QYMVvX0iri97ZQf+RTIlRvH7YtwCfX90K jgBjsZuLIg5aCxJo19Mbo+o= =AniV -----END PGP SIGNATURE----- ----Security_Multipart(Thu_Jan_17_15_27_04_2008_608)----