Bug 94103 - Start or end points moved in PDF conversion of OTF fonts drawn with Inkscape
Summary: Start or end points moved in PDF conversion of OTF fonts drawn with Inkscape
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-09-10 16:46 UTC by ivan louette
Modified: 2017-11-13 17:01 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Image of the start or end point moved vertically (114.36 KB, image/jpeg)
2015-09-10 16:46 UTC, ivan louette
Details
One of he fonts I use (30.16 KB, application/x-font-ttf)
2015-09-10 16:48 UTC, ivan louette
Details

Note You need to log in before you can comment on or make changes to this bug.
Description ivan louette 2015-09-10 16:46:57 UTC
Created attachment 118579 [details]
Image of the start or end point moved vertically

I draw my own font glyphs with Inkscape, cut/paste them to FontForge and generate OTF fonts. But when I use these fonts in Writer and export the result to PDF the result in Pdf browsers shows the start point of the outline moved vertically while the end one remains in place.

No problems exporting texts with the same font applied from Word, Indesign, Inkscape, Xara.

This problem doesn't occur if I generate Type 1 or TTF fonts.
Comment 1 ivan louette 2015-09-10 16:48:19 UTC
Created attachment 118580 [details]
One of he fonts I use
Comment 2 ivan louette 2015-09-10 16:51:51 UTC
I work on Kubuntu 14.04 and use Libre Office 4.2.8.2 Build ID : 420m0 (Build : 2)

But the problem was already there for a long time.
Comment 3 ivan louette 2015-09-10 18:08:00 UTC
This isn't the fault of Inkscape or SVG format because every glyph I draw directly inside FontForge has the same problem at the start/end point when exported to an OTF font used in Writer and then exported to PDF.
Comment 4 ivan louette 2015-09-10 18:40:52 UTC
The bug disappears if I generate a Type 1 font in FontForge, reload this Type 1 in FF and generate an OTF (but generating Type 1 in FF from curves drawn in SVG alterates them).
Comment 5 ivan louette 2015-09-17 11:05:01 UTC
It seems that the problem is solved if I set the font cadratin to 2000 instead of 1000 in FontForge before generating an Open Type font. Does Libre Office Writer need this level of precision to export correctly to PDF ?
Comment 6 Buovjaga 2015-09-20 11:23:42 UTC
To be sure, please test the 1000 setting with LibO 5.0. You can use this ppa: https://launchpad.net/~libreoffice/+archive/ubuntu/ppa

Set to NEEDINFO.
Change back to UNCONFIRMED, if the problem persists. Change to RESOLVED WORKSFORME, if the problem went away.
Comment 7 ivan louette 2015-09-20 16:50:51 UTC
I tested in LibreOffice 5.0 (installed from the ppa you indicated to me) another of my own fonts created with cadratin set to 1000 and the same problem occurs. Then I set it to 2000 and the problem disappears again.
Comment 8 Buovjaga 2015-09-21 08:08:45 UTC
I asked on the IRC dev channel and it was suggested that you tweak the start point by half a unit and see what happens.

A rounding error in LibO code somewhere is suspected.
Comment 9 Buovjaga 2016-11-12 08:31:29 UTC
Please try with a fresh 5.3, which has the new layout engine: http://dev-builds.libreoffice.org/daily/master/?C=M;O=A

You also didn't respond to my comment 8

Set to NEEDINFO.
Change back to UNCONFIRMED, if the problem persists. Change to RESOLVED WORKSFORME, if the problem went away.
Comment 10 QA Administrators 2017-05-31 10:50:46 UTC Comment hidden (obsolete)
Comment 11 ivan louette 2017-05-31 15:49:19 UTC
Hi,

I tried a fresh 5.3 some months ago and it didn't resolve this issue.

However if I change the grid precision of my font from 1000 EM to 2000 EM after finishing its design the problem disappears totally.
Comment 12 ivan louette 2017-05-31 15:50:33 UTC
I must precise that changing Grid precision solves the problem for any versions of LibreOffice
Comment 13 Xisco Faulí 2017-11-13 17:01:20 UTC
(In reply to ivan louette from comment #12)
> I must precise that changing Grid precision solves the problem for any
> versions of LibreOffice


Closing as RESOLVED WORKSFORME