Created attachment 97827 [details] Original pdf LaTeX supports different font properties: slanted and italic, but LibreOffice makes them the same. Steps to reproduce: 1. Open the example pdf with LibreOffice Draw 2. Export it as pdf 3. Compare the result with the original The example pdf file was created from TeX source (see attachment 96230 [details] for bug 76500) by pdflatex. I test the issue with LibreOffice 4.1.4.2 and 4.3.0.0.alpha1+ Build ID: b166e7af2bc3f6750b1f56adf004a115229d4c2d TinderBox: Linux-rpm_deb-x86_64@46-TDF, Branch:master, Time: 2014-04-22_05:17:38 on Debian x86_64 As far as I understand LibreOffice does not support slanted font property. If it is too difficult to add it, at least preserve the property to let make small changes without document corruption. For testing the case, make sure that you have “Computer modern” font installed (see bug 76500)
Created attachment 97828 [details] After roundtrip
The font used in the original pdf is "Computer Modern". This font is not installed on my Ubuntu and LibreOffice replace it by an available near font. Do you have it on your system? Please could you make a pdf test file with a more common font in order to eliminate the possibility of a problem linked to this font? Set status to NEEDINFO. Please set it back to UNCONFIRMED once you have provided the requested informations. Thank you for your understanding. Best regards. JBF
Created attachment 102716 [details] Computer Modern font from TeX Live Hello. I am sorry for delay. LaTeX uses its own fonts and I have no idea how make it use more common font. I attach “Computer modern” font from TeXlive and its TrueType version which I created with FontForge, File names means: cmr – normar cmbx – boldface cmsl – slanted cmti – italic The result depends (at least in Window 7) on font installation order. If cmti have been installed before cmsl, both slanted and italic text are shown as italic. Both cmti and cmsl are mark as italic typeface of Computer Modern. Maybe LibreOffice can not correctly work if one font typeface have different variants.
Created attachment 102717 [details] TrueType Computer Modern created by FontForge
Confirmed: Ubuntu 14.04 x64 LibreOffice 4.4 Build Date: Mon Jul 21 13:38:10 2014 -0400 New - confirmed Thanks for reporting
** 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 on a currently supported version of LibreOffice (5.0.0.5 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-09-03
I changed product to "LibreOffice" (affects all parts of the suite) and "inherited from OOo" (it was always this way). Install this font on your system: http://www.ctan.org/tex-archive/fonts/erewhon/opentype As you can see, it offers "italic" and "slanted" variants. Slanted and italics are two different things on typography, the first one being just a tilted (slanted, in fact) version of the regular font and the second one providing a more "rounded", unique design. LibO is confounded by this two variants and only shows one of them: in fact, the UI offers "italics" but instead gives you the "slanted" version. Tested on LibO 5.0.1.2 on Linux (openSUSE 13.2, 64 bits, KDE 4.14.9 with Spanish locale) with official LibO binaries.
Created attachment 118666 [details] Screenshot showing the character dialogue On the screenshot you can see that only "regular", "italics", "bold" and "bold italics" are offered for erewhon typeface, and that the "italics" gives in fact the "slanted" variant so we have two errors here.
** 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 on a currently supported version of LibreOffice (5.1.5 or 5.2.1 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20160920
The problem of LibO not being able to tell apart italic from slanted variants is still present on 5.3.4.2 Another font to play with: http://www.ctan.org/pkg/xcharter To add more information: there is a command line application on Linux, otfinfo, that provides information about OpenType fonts. With the "-i" flag you get things like font family, shape, etc. otfinfo -i XCharter-Italic.otf Family: XCharter Subfamily: Italic Full name: XCharter Italic PostScript name: XCharter-Italic etc. otfinfo -i XCharter-Slanted.otf Family: XCharter Subfamily: Slanted Full name: XCharter Slanted PostScript name: XCharter-Slanted etc. But LibO offers 4, not 6, variants, calling "italic" the slanted version. The only workaround to get true italics is to delete the slanted files. But then, of course, you cannot use the slanted versions.
** 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! Warm Regards, QA Team MassPing-UntouchedBug
Problem still present in LibO 6.0.5.2
Created attachment 149301 [details] XCharter LO fonts - example PDF The problems with the XCharter fonts is how the font family names and style groups are configured. Both the italic fonts and the slanted font are configured as italic in the same style group. This confuses LO - and any other older app using style groups (R/I/B/BI). This PDF shows a modified (fixed) version of the fonts working properly in LibreOffice on Windows. The fonts are in the ZIP attachment below. Please test on Linux. Note: This is the same issue with the Erewhon fonts - a modified/fixed version works fine.
Created attachment 149302 [details] XCharter-LO-fonts_2019-02-14 - ZIP file These are modified fonts which work properly in LibreOffice on Windows. Please test in LibreOffice on Linux.
Issue of OP here, mishandling of italic vs. slanted faces of Computer Modern when both are present on system is not from the PDF print/export filter, nor form the poppler based PDF import filter. So this is not a PDF filter issue. Rather, the issue is cross platform and is a font handling limitation. Closing as duplicate of bug 105298, or as in see also bug 35538 and its os specific font mishandlings. Would note that our other PDF insertion filter, pdfium based, correctly renders the subset glyphs per font style to document canvas--but fails even more so when text runs of the Draw graphic object get a 'break' apart. PDF "touch-up" with LibreOffice will always be a losing proposition, and why we provide our "hybrid" PDF with an embedded ODF stream. *** This bug has been marked as a duplicate of bug 105298 ***
Why should this one be a duplicate of ReportBuilder (Base)? Problem there has nothing to do with fonts.
(In reply to Robert Großkopf from comment #16) > Why should this one be a duplicate of ReportBuilder (Base)? Problem there > has nothing to do with fonts. It isn't, nor is it marked such. Thinking of a different issue?
(In reply to V Stuart Foote from comment #17) > (In reply to Robert Großkopf from comment #16) > > Why should this one be a duplicate of ReportBuilder (Base)? Problem there > > has nothing to do with fonts. > > It isn't, nor is it marked such. Thinking of a different issue? Oops, sorry Robert! Found the typo... not 103387, rather bug 103378 corrected.