Issue 121467 - Breakiterator sometimes does not realize correct hyphenation opportunity
Summary: Breakiterator sometimes does not realize correct hyphenation opportunity
Status: CONFIRMED
Alias: None
Product: Writer
Classification: Application
Component: formatting (show other issues)
Version: 3.4.1
Hardware: All All
: P3 Normal (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks: 121500
  Show dependency tree
 
Reported: 2012-12-12 15:47 UTC by stfhell
Modified: 2012-12-21 08:55 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
no_hyphenation_1: Writer does not hyphenate a word (522.18 KB, application/zip)
2012-12-12 16:21 UTC, stfhell
no flags Details
no_hyphenation_2: Writer does not hyphenate a word (733.09 KB, application/zip)
2012-12-18 10:40 UTC, stfhell
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description stfhell 2012-12-12 15:47:45 UTC
The breakiterator used in Writer sometimes does not recognize correct linebreak or hyphenation opportunities. (With hyphenation activated, of course, and where Writer knows how to hyphenate a word.)

This has the following effect: Writer does not hyphenate a word although there is room enough on the line and although the automatic hyphenation algorithm can handle the word.

It happens very frequently when typographical quotation marks are present, but not in every case. Sometimes it is enough to add some character somewhere in the line with the word to make Writer hyphenate this word correctly.

I will attach sample documents. But it seems the line-breaking behaviour is at least often only reproducible with identical formatting environments: If you change the font or if Writer uses font substitution, the line breaks differently. And with other fonts, Writer may haphentate the word in question without any problems.

System used for recent tests: AOO 3.4.1 German under Ubuntu 12.04 (AMD64). But the same problem also existed in earlier versions of OOo and still exist in LibreOffice.
Comment 1 stfhell 2012-12-12 16:21:46 UTC
Created attachment 80019 [details]
no_hyphenation_1: Writer does not hyphenate a word

Test kit no_hyphenation_1: ODT and screenshots with descriptions under AOO 3.4.1.

The word "ununterbrochen" on line 2 is not hyphenated although most of it would fit in line 1. Writer hyphenates the word if

(a) you choose some other font: Gentium, Arial, Charis SIL, Linux Libertine O, Lucida Std, Tahoma, Deja Vu (Sans/Serif) will work; Times New Roman, Liberation Serif and FreeSerif or Calibri won't work.

or

(b) you add 1 or more characters before the word somewhere in line 1: Some characters will work (letters, ?, -, +, !, brackets, accents, TAB), others won't work (., ;, /, :, |, comma, 2 or more spaces).
Comment 2 stfhell 2012-12-18 10:40:41 UTC
Created attachment 80040 [details]
no_hyphenation_2: Writer does not hyphenate a word

Another sample file with screenshots. In paragraph 2, a word is not hyphenated.
System: AOO 3.4.1 64 bit under Ubuntu 12.04/AMD64, with font Georgia from the free MS corefont pack.

The behaviour is dependent on the font used for formatting:
When I use Georgia 9 pt, Writer starts hyphenating whenever I add or delete even a single character in the text up to and including '("sinnenfreudige")'.
When I use Georgia 10 pt, Writer also hyphenates (without changing any text).
When I change font to Times New Roman 10 pt, Writer hyphenates. But when the enumeration style is changed and font set to Times Roman 9 pt, Writer does not hyphenate (see screenshots, p. 2).
When I format with Arial 10 pt, Writer hyphenates, when I use Arial 9 pt, it does not.
Also the characters that can be inserted to make Writer hyphenate the word vary: In some tests "," or "." did not work, in some tests they did.

All this is very erratic behaviour: hyphenation seems to depend on the font _or_ the font size. I first thought that the bug could be font related, but all this probably indicates that it could be something different. I also have the impression that the presence of typographical quotation marks have something to do with it, I notice missed hyphenation opportunities very often when I use these.
Comment 3 binguo 2012-12-21 08:55:57 UTC
Marked it as Confirmed.