From owner-freebsd-doc@FreeBSD.ORG Sun Jul 28 22:09:14 2013 Return-Path: Delivered-To: doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 1CA5BFFE; Sun, 28 Jul 2013 22:09:14 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C32B22D12; Sun, 28 Jul 2013 22:09:13 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.7/8.14.7) with ESMTP id r6SM9CcZ012090; Sun, 28 Jul 2013 16:09:12 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.7/8.14.7/Submit) with ESMTP id r6SM9C0q012087; Sun, 28 Jul 2013 16:09:12 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Sun, 28 Jul 2013 16:09:12 -0600 (MDT) From: Warren Block To: Gabor Kovesdan Subject: Re: Another CSS suggestion: pre-wrap In-Reply-To: <51F57C6E.9050608@FreeBSD.org> Message-ID: References: <51F558D2.1010808@FreeBSD.org> <51F56688.5040900@FreeBSD.org> <51F57011.2000603@FreeBSD.org> <51F57C6E.9050608@FreeBSD.org> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Sun, 28 Jul 2013 16:09:12 -0600 (MDT) Cc: doc@FreeBSD.org X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Jul 2013 22:09:14 -0000 On Sun, 28 Jul 2013, Gabor Kovesdan wrote: > On 2013.07.28. 21:37, Warren Block wrote: >> >> Line numbering is nice sometimes, although sometimes it's easy to confuse >> with content. Syntax highlighting could be useful in places like the >> Architecture Handbook, but as you say, we don't have it now. >> >> Would you agree that using this line wrap now would not prevent switching >> to other methods in the future? > I believe it is possible to make them work together. But using these > extensions requires using Saxon as the XSLT processor, which is > Java-based and slower than xsltproc. Even if we end up using Java for > PDF rendering, it would be better to keep the XHTML build fast and > Java-free so that committers can easily test their work. Do you mean Java is needed to do the linewrap on XHTML, or that it would be needed to do line numbers and syntax highlighting?