Created attachment 119623 [details]
font problem example
Hi. I downloaded a free ODF font called Trench and I formatted the text so only its outline would be visible. When I convert the file to .pdf, the text form changes, the distances between the characters "perimeter" become the same. See the file to see what I mean, please. Thanks.
Please attach a file with the font and the font (if it's free and under a license that you can share it). Also the related PDF would be good.
Marking as NEEDINFO - once attached please mark as UNCONFIRMED. Thanks
Created attachment 119626 [details]
here is the formatted text
Created attachment 119627 [details]
the distorted text in .pdf
this is the link to the free font: http://www.1001fonts.com/trench-font.html#license
> the distorted text in .pdf
Er, actually what’s distorted here is not the PDF’s output, which shows the correct font forms (i.e., it displays as the font was drawn).
At least in MY screen, I see the font is the same, but the characters are diferent than in the virtual writing sheet: in the .pdf file, the inner distance between the characters outline is always the same, while in the .odf file, there are "wider" parts of the characters, and "thinner" ones, and that's the idea. The .pdf file "erases" the characters' outline "configuration" and keeps it "straight standard". It eliminates the character "style".
I guess Adolfo was responding to how you described the attachment: "the distorted text in .pdf", while a more appropriate wording would have been "text looks ok in pdf export" or something like that.
It doesn't matter, if the text has an outline character formatting.
Win 7 Pro 64-bit, Version: 184.108.40.206 (x64)
Build ID: 37b43f919e4de5eeaca9b9755ed688758a8251fe
Locale: fi-FI (fi_FI)
In my computer, trench is shown ok in Write, but gets all thin in .pdf...
(In reply to jlbraga from comment #8)
> In my computer, trench is shown ok in Write, but gets all thin in .pdf...
The thin form is correct, compare to 1001fonts.
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.
There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.
If you have time, please do the following:
Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/
If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.
Please DO NOT
Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not
appropriate in this case)
If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/
2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword
Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!
This is still present
Version: 220.127.116.11 (x64)
Build ID: a64200df03143b798afd1ec74a12ab50359878ed
CPU threads: 2; OS: Windows 10.0; UI render: default; VCL: win;
Locale: en-US (en_US); UI-Language: en-US