Hi Andreas,
On Tue, 13 May 2008 22:29:51 +0200, Andreas Hoenen
<[EMAIL PROTECTED]> wrote:
benoit.guillon <[EMAIL PROTECTED]> wrote:
<snip/>
This one is hard to fix, and I guess there's no solution that works
for any
case. Please try the attached patch, and set monoseq.hyphenation to
'nohyphen'. It should improve the behaviour, but not necessarily for
very long
strings, or for some tags not covered by this parameter (a complete
use case
would be helpful).
Regards,
BG
Hi Benoît, hi Roland,
I'm still quite unsure about the problem report and about the proposed
patch.
I guess it covers the feature request: do not break the literal names, and
avoid as much as possible overfull boxes that put text in the margins (the
second point is rather from your analysis than in the request itself).
As stated by Benoît, the patch is far away from a perfect
solution, but it might help in some cases. It seems to depend heavily
on the actual document and the problematic literals within:
Attached is a small (far from exhaustive) test document [1] together
with the pdf output without [2] and with [3] the nohyphen setting. It
shows some improvement as well as some degradement:
The long numeric literals might occur only seldomly, however I would
really love to get those split without a hyphen, as in this context it
will be easily interpreted as a mathematical operator. But even worse
is loosing half of the value. IMHO the biggest problem for the split
variable name is the wrong hyphen position, not the fact that is gets
split. With nohyphen set the inter word boundaries look very huge for
the variable paragraph.
AFAIK, you cannot avoid the overfull box symptom and have good inter-word
spacing at the same time (things are strechable or not). The thing about
splitting with no hyphen is something to look at, but anyway there is no
easy way to make the split location smarter than it is (what policy to
apply? The \nolinkurl policy is good for file names but it is not an
universal solution: replacing in your test case <literal> by <filename>
for the numbers improves nothing even if it uses \nolinkurl).
Perhaps we should keep the patch as it is: an option that can be tried
if actual problems have been detected within a document, an attempt that
might help or not.
At least the option avoids as much as possible to have data in the
margins. In fact with the option we have three possible modes:
- literal not breakable, and default line streching (default) that ends to
text in the margin,
- literal not breakable, and stretchable lines that avoids text in margin
but can put too much space betwwen words,
- literal breakable at any position in the word; keeps good interword
spacing, avoids too many overfull boxes, but can add an annoying "-" in
the word.
Benoît, do you intend to integrate the patch into
the next upstream release?
Indeed.
Regards,
BG
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
