Issue 127357 - Apple Chancery font not displaying properly
Summary: Apple Chancery font not displaying properly
Alias: None
Product: Impress
Classification: Application
Component: formatting (show other issues)
Version: 4.1.3
Hardware: Mac OS X 10.9
: P5 (lowest) Normal (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
: 127391 (view as issue list)
Depends on:
Reported: 2017-03-12 23:07 UTC by Stoney4630
Modified: 2017-05-02 08:00 UTC (History)
4 users (show)

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

pdf example using O-O 4.01 which works correctly (29.27 KB, application/pdf)
2017-04-24 03:16 UTC, Stoney4630
no flags Details
pdf example using O-O 4.1.3 which fails formating (4.70 KB, application/pdf)
2017-04-24 03:19 UTC, Stoney4630
no flags Details
pdf example using O-O 4.1.3 failure (resending) (19.61 KB, application/pdf)
2017-04-24 03:29 UTC, Stoney4630
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description Stoney4630 2017-03-12 23:07:00 UTC
The Apple Chancery font is a very beautiful font which, among other things, displays, for some letters, that letter differently depending upon whether it is the final letter on a line or the final letter of a word within a line.  At the end of a line some letters such as 'n' 't' 'h' 'f' 'd' and 'u' have extensions,or "tails," which extend to the right adding to the elegance of the font.  These have disappeared in the last two versions of Open Office, with end-of-line appearance same as end-of-word. 

For what its worth, this has always been a problem with Microsoft Word.

I am using an Apple iMac running, of course, OS-X.  This problem does not change with different versions of OS-X, but does with different versions of O-O.  Problem currently exists with O-O 4.1.3.  Last known to display properly in O-O 4.0.1.  First broken in 4.0.2.  Also worked correctly in O-O 3.4.1 and 4.0.0.
Comment 1 oooforum (fr) 2017-03-14 14:34:07 UTC
Already reported

*** This issue has been marked as a duplicate of issue 124496 ***
Comment 2 mroe 2017-03-15 07:58:12 UTC
For me issue 124496 describes a complete other issue. There is reported that different variants of a font are not listed in AOO and therefore they cannot be used. But here the OP /uses/ a font but the output isn't as it should.

Maybe Issue 125314 could be go in the same direction.

@OP: For a good issue reporting it needs at least a screenshot to show the problem. And if the defect also is shown in an exported PDF, then it should be also attached.
Comment 3 Keith N. McKenna 2017-03-18 19:50:30 UTC
I agree with mroe that this is a completely different issue than issue 124496. This issue is concerned with a specific font rendering differently between different versions of AOO on macOS. Issue 124496 deals with different variants of fonts (bold,etc.) not being available in the AOO fonts dropdown. I believe that this issue should stand alone to allow a Mac user to confirm.

Setting as re-opened
Comment 4 Stoney4630 2017-04-24 03:16:12 UTC
Created attachment 86034 [details]
pdf example using O-O 4.01 which works correctly
Comment 5 Stoney4630 2017-04-24 03:19:22 UTC
Created attachment 86035 [details]
pdf example using O-O 4.1.3 which fails formating
Comment 6 Stoney4630 2017-04-24 03:26:26 UTC
Comment on attachment 86035 [details]
pdf example using O-O 4.1.3 which fails formating

This example failed to send properly.  Sending another.
Comment 7 Stoney4630 2017-04-24 03:29:51 UTC
Created attachment 86036 [details]
pdf example using O-O 4.1.3 failure (resending)

86035 is no good and should be deleted in favor of this one.
Comment 8 oooforum (fr) 2017-04-24 16:41:44 UTC
*** Issue 127391 has been marked as a duplicate of this issue. ***
Comment 9 kalle 2017-05-02 08:00:08 UTC
If the kerning bug reported as issue 127391 is indeed covered by this issue, then perhaps the bug summary could be updated to reflect that and the priority could be bumped up accordingly. Kerning that is broken across the board is pretty clearly on another level of urgency than swashes missing from an obscure Apple font.

What's the plan here? If support for type kerning and/or the Mac platform is no longer a priority for this project, I would hope that the maintainers would state it publicly. I for one need to quickly decide whether to wait this out or start migrating my document library onto another word processor.