<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<font size="-1"><font face="Helvetica, Arial, sans-serif">That's a GOOD
example, but a BAD movie!<br>
BJB<br>
</font></font><br>
Jose Maria Sanchez de Ocana wrote:<br>
<blockquote
cite="mid50f175090602031055x4873bc3cn3c9103607a955d0c@mail.gmail.com"
type="cite">
<pre wrap="">Hmm... actually that was another BAD example! What about "Yesterday I
went to watch Terminator V" ?
Jose
On 2/3/06, Jose Maria Sanchez de Ocana <a class="moz-txt-link-rfc2396E" href="mailto:jsandeo@gmail.com"><jsandeo@gmail.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hello, Todd
Those were actually examples that don't cover all real cases. How
about "I was born in december 1st" ? I just don't want that "1st" to
be an orphan.
Thanks,
Jose
On 2/3/06, Powell, Todd <a class="moz-txt-link-rfc2396E" href="mailto:Todd.Powell@hq.doe.gov"><Todd.Powell@hq.doe.gov></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Jose,
We've developed some standard rules for our end users when it comes to
knowing where to place non-breaking spaces, and one of the most commonly
encountered is "place one before any number". It would seem to me that
this kind of a rule could be used in all the examples you gave.
It doesn't handle the hanging "real" word problem, but at least it won't
separate "January 3, 2005" onto two lines.
HTH,
Todd
-----Original Message-----
From: <a class="moz-txt-link-abbreviated" href="mailto:owner-xep-support@renderx.com">owner-xep-support@renderx.com</a>
[<a class="moz-txt-link-freetext" href="mailto:owner-xep-support@renderx.com">mailto:owner-xep-support@renderx.com</a>] On Behalf Of Jose Maria Sanchez
de Ocana
Sent: Friday, February 03, 2006 12:33 PM
To: <a class="moz-txt-link-abbreviated" href="mailto:xep-support@renderx.com">xep-support@renderx.com</a>
Subject: Fwd: [xep-support] Orphans & widows at the line break level
I've thought about trying that, but after a first analysis of the
problem (i.e. where in a string to replace blanks with non-breaking
spaces), I've realised it's the typical problem that looks simple at
first glance but is actually pretty tricky... it's actually similar to
hyphenating, but not quite the same. It is really more of an
orphans/widows kind of problem, but at the line level.
Thanks anyway,
JSO
---------- Forwarded message ----------
From: Broberg, Mats <a class="moz-txt-link-rfc2396E" href="mailto:mabr@flir.se"><mabr@flir.se></a>
Date: Feb 3, 2006 6:15 PM
Subject: RE: [xep-support] Orphans & widows at the line break level
To: <a class="moz-txt-link-abbreviated" href="mailto:xep-support@renderx.com">xep-support@renderx.com</a>
Jose,
Wouldn't using a non-breaking space (U+00A0) when typing the text be a
possibility?
Best regards,
Mats Broberg
________________________________
From: <a class="moz-txt-link-abbreviated" href="mailto:owner-xep-support@renderx.com">owner-xep-support@renderx.com</a> on behalf of Jose Maria Sanchez de
Ocana
Sent: Fri 2006-02-03 17:20
To: <a class="moz-txt-link-abbreviated" href="mailto:xep-support@renderx.com">xep-support@renderx.com</a>
Subject: [xep-support] Orphans & widows at the line break level
Hello,
I'd like to know if there's a way in XSL-FO/XEP to control orphans &
widows not only at the page break level, but also at the line break
level. My problem is that, for certain texts, I'd like to prevent lines
from breaking at words that are too short. For example, I have the text:
"Long Beach Road, 2" I wouldn't want this sort of text to be broken
right before the "2", thus leaving a single character as an orphan in
the block's last line. I'd either want the text to be stretched into a
block with one line less, or to be broken leaving "Road, 2" on the last
line. Likewise, I wouldn't want a text such as "Madison Av. 1 - 2" to be
broken right after the 1, leaving "- 2" on the last line, and a lonely
"1" as a widow at the end of the previous one.
Thanks,
JSO
-------------------
(*) To unsubscribe, send a message with words 'unsubscribe xep-support'
in the body of the message to <a class="moz-txt-link-abbreviated" href="mailto:majordomo@renderx.com">majordomo@renderx.com</a> from the address you
are subscribed from.
(*) By using the Service, you expressly agree to these Terms of Service
<a class="moz-txt-link-freetext" href="http://www.renderx.com/terms-of-service.html">http://www.renderx.com/terms-of-service.html</a>
-------------------
(*) To unsubscribe, send a message with words 'unsubscribe xep-support'
in the body of the message to <a class="moz-txt-link-abbreviated" href="mailto:majordomo@renderx.com">majordomo@renderx.com</a> from the address
you are subscribed from.
(*) By using the Service, you expressly agree to these Terms of Service <a class="moz-txt-link-freetext" href="http://www.renderx.com/terms-of-service.html">http://www.renderx.com/terms-of-service.html</a>
</pre>
</blockquote>
</blockquote>
<pre wrap=""><!---->
-------------------
(*) To unsubscribe, send a message with words 'unsubscribe xep-support'
in the body of the message to <a class="moz-txt-link-abbreviated" href="mailto:majordomo@renderx.com">majordomo@renderx.com</a> from the address
you are subscribed from.
(*) By using the Service, you expressly agree to these Terms of Service <a class="moz-txt-link-freetext" href="http://www.renderx.com/terms-of-service.html">http://www.renderx.com/terms-of-service.html</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Brian J. Butler
BJB Software, Inc.
76 Bayberry Lane
Holliston, MA 01746
E-mail: <a class="moz-txt-link-abbreviated" href="mailto:bjbutler@bjbsoftware.com">bjbutler@bjbsoftware.com</a>
Web: <a class="moz-txt-link-freetext" href="http://www.bjbsoftware.com">http://www.bjbsoftware.com</a>
Phone: 508-429-1441
Fax: 419-710-1867
</pre>
</body>
</html>