https://issues.apache.org/ooo/show_bug.cgi?id=124375
[email protected] <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |ACCEPTED Assignee|[email protected] |[email protected] |g | Summary|Active optional hyphens |Active optional hyphens |invisible for the NuevaStd |invisible in exported |font in exported PDF |tagged-PDF on Mac OS|Mac OSX, 10.9 |Mac OSX, 10.7 --- Comment #17 from [email protected] <[email protected]> --- It shows that the problem happens on CoreText-layouted text for the case of tagged PDF export. The root cause are the different interpretation on whether a soft-hyphen should be visible or not [1]. http://www.cs.tut.fi/~jkorpela/shy.html CoreText follows the modern interpretation of keeping it invisible. With Writer's "portion concept" it is impossible to know for lower layers whether a portion is at the line end. So Writer usually doesn't emit the soft-hyphen at all, but replaces it with a dash. Writer doesn't do this replacement if it exports to the tagged PDF file format, though. The solution to consolidate these different interpretations on what each layer of AOO and the platform should do is to either - force Writer to emit the same unicode independent on whether the target is a display, a printer, a plain PDF or a tagged PDF - or force CoreText to treat the soft-hyphen the same as a dash character -- You are receiving this mail because: You are on the CC list for the issue. You are the assignee for the issue. You are watching all issue changes.
