Closed Bug 250741 Opened 20 years ago Closed 20 years ago

Line-break should be allowed after hyphens + Soft hyphens should be rendered

Categories

(Firefox :: General, defect)

x86
Windows 2000
defect
Not set
minor

Tracking

()

RESOLVED DUPLICATE of bug 9101

People

(Reporter: hfk, Assigned: bugzilla)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040626 Firefox/0.9.1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040626 Firefox/0.9.1 1. Line-break should be allowed after hyphens (unless followed by number): Very long words (typically those made of 2 or more words related by an hyphen) should be wrapped after the hyphen if necessary (for example : at the end of a line). It is conventional to break such words after hyphen. 2. Soft hyphens should be rendered : From W3C Recommendations: > 9.3.3 Hyphenation > In HTML, there are two types of hyphens: > the plain hyphen and the soft hyphen... > In HTML, the plain hyphen is represented > by the "-" character (- or -). > The soft hyphen is represented by the > character entity reference ­ > (­ or ­) The most common use of the soft hyphen is for hyphenation in a page layout. The soft hyphen is used for hyphenation when a line break occurs. It is removed automatically when the text is reformatted and the hyphenation is no longer necessary. Currently, Web publishing is a less automated use of text layout. HTML authors are the 'typographer' and they are responsible for formatting the text. Web browsers do not automatically provide hyphenation as do page layout applications. Reproducible: Always Steps to Reproduce: 1. Create a HTML page containing a paragraph with a lot of compound words and a paragraph with a lot of soft hyphenated words. 2. It is best to set the paragraphs' alignement to JUSTIFY in order to get the point. Also set the paragraphs' width to a small value (300px or 15em). 3. The lines were the space between words is to large (often followed on the next line by a large compound or soft hyphenated word) will show you what the proplem is. It's ugly and webmaster has no control over hyphenation. Typography is very important.
Please reopen this bug if you disagree with the resolution. Thanks for using Bugzilla. *** This bug has been marked as a duplicate of 9101 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
(In reply to comment #1) > Please reopen this bug if you disagree with the resolution. Thanks for using > Bugzilla. > > *** This bug has been marked as a duplicate of 9101 *** Thanks, But that's only a duplicate of the Soft Hyphen Bug. The Deadly non-breaking Normal Hyphen Bug still remains: "Line-break should be allowed after hyphens".
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
(In reply to comment #2) > (In reply to comment #1) > > Please reopen this bug if you disagree with the resolution. Thanks for using > > Bugzilla. > > > > *** This bug has been marked as a duplicate of 9101 *** > > Thanks, > But that's only a duplicate of the Soft Hyphen Bug. > > The Deadly non-breaking Normal Hyphen Bug still remains: > "Line-break should be allowed after hyphens". That's bug 95067. Reduping to one of these (please don't put multiple issues in one bug report.) *** This bug has been marked as a duplicate of 9101 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago20 years ago
Resolution: --- → DUPLICATE
(In reply to comment #3) > (In reply to comment #2) > > (In reply to comment #1) > > > Please reopen this bug if you disagree with the resolution. Thanks for using > > > Bugzilla. > > > > > > *** This bug has been marked as a duplicate of 9101 *** > > > > Thanks, > > But that's only a duplicate of the Soft Hyphen Bug. > > > > The Deadly non-breaking Normal Hyphen Bug still remains: > > "Line-break should be allowed after hyphens". > > That's bug 95067. Reduping to one of these (please don't put multiple issues in > one bug report.) > > > *** This bug has been marked as a duplicate of 9101 *** Sorry for all that, I am new to Bugzilla :/
You need to log in before you can comment on or make changes to this bug.