From: Philippe Verdy (email@example.com)
Date: Thu Jul 26 2007 - 13:03:22 CDT
I used other test pages where the bug was visible before I could fix it
using explicit CSS style markup.
This was visible on many Wikipedia pages, within side "infoboxes" whose
layout is often a small table with two narrow columns, and the first column
is a fixed label (whose singular or plural is unknown) and the second lists
one or more values. This case was not one of those requiring the use of the
"emergency line breaking" procedure that was described more precisely in the
UAX#14 update 20.
This bug is also common in many input forms (or data search result forms)
where one is allowed to input (or retrieve) one (or several) value(s)...
For your reply, the bug affects IE7 too (I know it was present in IE6 or
before) at least in XP and Vista (don't know about Windows Server 2003 or
And it affects my current version of Word (French edition), on some cases
(yes not always, I don't know exactly why the undesirable break is sometimes
avoided, because I don't know if there are other typographical
considerations that may cause it, so that Word thinks that more breaks are
not needed). It may depend on the effective localization of the hyphenator,
I have not tried by forcing the English language.
> -----Message d'origine-----
> De : firstname.lastname@example.org [mailto:email@example.com] De la
> part de Michael Maxwell
> Envoyé : jeudi 26 juillet 2007 17:47
> À : firstname.lastname@example.org
> Cc : Michael Maxwell
> Objet : RE: UAX#14-20: undesriable line breaking opportunities (parenthese
> and quotation marks)
> Philippe Verdy wrote:
> > Hmm... Why does it not work, say in Internet Explorer,
> > Firefox, and even MS Word ??? The first rule of LB30 should
> > avoid breaking "word(s)", but I'm still seeing the line break
> > everywhere between "word" and "(s)"
> Hmm... I just tried this in IE (v6), Firefox (v2), and Word (2003 SP2).
> It behaves correctly in Firefox and Word, but not in IE. (I don't know
> how it behaves in the new IE v7.)
> For IE and Firefox, I used the following web page as a test case:
> and narrowed the window until "Word(s)" was forced to move. For Firefox,
> when the critical point comes, the entire string "Word(s)" moves onto the
> next line; with IE, only the "(s)" moves. (There are two instances of
> "Word(s)", one at the top of the page and one near the bottom. In each
> browser, they behave consistently.)
> For Word, I just typed in a string that included "word(s)", and continued
> typing random words to its left until it was forced to wrap.
> Mike Maxwell
> CASL/ U Md
This archive was generated by hypermail 2.1.5 : Thu Jul 26 2007 - 13:05:47 CDT