Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 82628 invoked from network); 8 Nov 2003 23:00:06 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 8 Nov 2003 23:00:06 -0000 Received: (qmail 67489 invoked by uid 500); 8 Nov 2003 22:59:50 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 67449 invoked by uid 500); 8 Nov 2003 22:59:50 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 67436 invoked from network); 8 Nov 2003 22:59:49 -0000 Received: from unknown (HELO exchange.sun.com) (192.18.33.10) by daedalus.apache.org with SMTP; 8 Nov 2003 22:59:49 -0000 Received: (qmail 16963 invoked by uid 50); 8 Nov 2003 22:59:56 -0000 Date: 8 Nov 2003 22:59:56 -0000 Message-ID: <20031108225956.16962.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: dev@cocoon.apache.org Cc: Subject: DO NOT REPLY [Bug 23796] - [PATCH] docs pages containing are sometimes too wide X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23796 [PATCH] docs pages containing are sometimes too wide ------- Additional Comments From conal.tuohy@vuw.ac.nz 2003-11-08 22:59 ------- David, can you point at some examples of author's using in such a way that it requires
 HTML formatting? I'm curious to see if these are really 
examples of source code, or just tag abuse. The  code I looked at 
didn't include such stuff. 

One approach that Nicola suggested was to use  etc or 
 and this may help. The templates I posted were really 
suited to type="xml", and with a bit of a twiddle would also suit type="java" 
(currently they don't handle //-style comments).

Maybe we could move forward more quickly by adding the templates with:



or even:



etc.

Vadim, I think your low-tech suggestion mixes concerns. Optimum line-lengths 
are a function of the output device (paper size, paper margins, screen 
resolution, browser font size, etc). For a given line of , on some 
devices line wrapping may be necessary, but on other devices not. So it's not 
really appropriate to hard-code these decisions on an individual basis in the 
xdocs.