From owner-freebsd-doc@FreeBSD.ORG Sun Apr 2 17:54:58 2006 Return-Path: X-Original-To: freebsd-doc@FreeBSD.org Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C144E16A41F; Sun, 2 Apr 2006 17:54:58 +0000 (UTC) (envelope-from hrs@FreeBSD.org) Received: from mail.allbsd.org (vlsi00.si.noda.tus.ac.jp [133.31.130.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4C30F43D46; Sun, 2 Apr 2006 17:54:58 +0000 (GMT) (envelope-from hrs@FreeBSD.org) Received: from delta.allbsd.org (p6168-ipbf302funabasi.chiba.ocn.ne.jp [124.87.184.168]) (authenticated bits=128) by mail.allbsd.org (8.13.1/8.13.4) with ESMTP id k32Hsjuu060671; Mon, 3 Apr 2006 02:54:57 +0900 (JST) (envelope-from hrs@FreeBSD.org) Received: from localhost (alph.allbsd.org [192.168.0.10]) by delta.allbsd.org (8.13.4/8.13.4) with ESMTP id k32HsRtA016951; Mon, 3 Apr 2006 02:54:29 +0900 (JST) (envelope-from hrs@FreeBSD.org) Date: Mon, 03 Apr 2006 02:52:32 +0900 (JST) Message-Id: <20060403.025232.117507618.hrs@allbsd.org> To: intron@intron.ac From: Hiroki Sato In-Reply-To: <200604021732.k32HWiqn099718@zhao.intron.ac> References: <20060403.004732.73716044.hrs@allbsd.org> <200604021732.k32HWiqn099718@zhao.intron.ac> X-PGPkey-fingerprint: BDB3 443F A5DD B3D0 A530 FFD7 4F2C D3D8 2793 CF2D X-Mailer: Mew version 4.2.52 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Multipart/Signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="--Security_Multipart(Mon_Apr__3_02_52_32_2006_629)--" Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.86.2, clamav-milter version 0.86 on gatekeeper.allbsd.org X-Virus-Status: Clean Cc: freebsd-doc@FreeBSD.org, hrs@FreeBSD.org, cnproj-cvs@lists.cn.freebsd.org Subject: Re: Chinese Bookmark with DVIPDFMx X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Apr 2006 17:54:58 -0000 ----Security_Multipart(Mon_Apr__3_02_52_32_2006_629)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit intron@intron.ac wrote in <200604021732.k32HWiqn099718@zhao.intron.ac>: in> Actually, if FDP is transfered into a XSL system, only a few in> FreeBSD-specific DSSSL style sheets need to be converted into XSL style in> sheets, and those SGML DTDs need to be converted into XML DTDs with in> slight changes. After all, most of style sheets for FDP are provided in> by Norman Walsh, either in DSSSL or in XSL. FreeBSD specific DSSSL stylesheet is not small, and the resulting documents are different between DSSSL and XSLT. I have implemented SGML->XML conversion in NetBSD Documentation Project (you can see htdocs/share in their repository), but from my experiences, that work is more problematic than one you think. in> In fact, Jade/OpenJade's bugs (mainly around its tex-backend) are in> only minor. TeX's bugs and the glued relationship between Jade/OpenJade in> and TeX is the substantial of problems. Sometimes, we cannot find in> a way out for Jade/OpenJade to let TeX consider it as "correct", and in> maybe even both two sides of a problem are taken as "wrong" by TeX. Please show me some concrete examples? I am still not sure what your problem is. "Which is correct" is always determined by the Jade + JadeTeX processing model and such problems should be discussed with the authors. I am interested in it if there is a critical problem that we cannot solve now in the current framework. in> At least today XML/XSL is the developing trend rather than in> SGML/DSSSL. So many efforts are focused on XML/XSL in open source in> community all over the world. XML/XSL system supports Unicode natively, in> which means all languages including your Nipponese may be well solved. Agreed, but the switching over is not straightforward. I guess you think it is relatively easy. in> Now MySQL's docments are typeset by Apache FOP, which have better in> quality than current FreeBSD documents (http://dev.mysql.com/doc/), in> even only in English. Their PDFs have commercial-level typesetting in> styles in some details: word-splitting, margin kerning and font in> expansion, just as LaTeX + microtype package do. It seems that XSL in> system is absolutely not a simple "it works" one, at least witnessed in> by 1727-paged "MySQL 5.1 Reference Manual". So, do you have a concrete plan to adopt such typesetting framework? -- | Hiroki SATO ----Security_Multipart(Mon_Apr__3_02_52_32_2006_629)-- Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBEMA9hTyzT2CeTzy0RAgcVAKCjvPShx5UJH27kZbAnfK0/BRtbOwCg0Abc BbFGtqW4/0QEX2iS92BuZTU= =r9Fi -----END PGP SIGNATURE----- ----Security_Multipart(Mon_Apr__3_02_52_32_2006_629)----