steps: 1. open attachment 136975 [details] with 'pdf (writer)' filter in file open dialog 2. notice that text is all formatted in the default CTL font (mine is Lucida Sans) 3. close pdf 4. open pdf with its default filter in Draw 5. notice the first line is in Traditional Arabic, second is in Frank Ruehl CLM and third is in Simplified Arabic The original odt is attachment 136974 [details]. Version: 6.0.0.0.alpha0+ Build ID: 3672cdd35985201ea87463cf032fedd02c052f4d CPU threads: 2; OS: Linux 4.4; UI render: default; VCL: gtk2; Locale: en-US (en_US.UTF-8); Calc: group
Reproducible for me Version: 6.0.0.0.alpha0+ (x64) Build ID: 465092047d5fa6ec6dd369372e712d76554570ff CPU threads: 4; OS: Windows 6.19; UI render: GL; TinderBox: Win-x86_64@42, Branch:master, Time: 2017-09-26_23:16:01 Locale: de-DE (de_DE); Calc: group
** 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
Still reproducible with Version: 6.2.0.0.alpha0+ (x64) Build ID: 48cfa0b00b22f11ade53aec79b2fdddad253e1bd CPU threads: 4; OS: Windows 10.0; UI render: GL; VCL: win; TinderBox: Win-x86_64@42, Branch:master, Time: 2018-10-03_02:01:42 Locale: en-US (de_DE); Calc: CL
Dear Yousuf Philips (jay) (retired), 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
Still confirmed Arch Linux 64-bit Version: 7.1.0.0.alpha1+ Build ID: 3d3180115be3b87e76189aea2031f0caa735dbb3 CPU threads: 8; OS: Linux 5.9; UI render: default; VCL: kf5 Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded Built on 11 November 2020
Repro: Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: 736e100c516ed5326f4cccd6d22205264df51914 CPU threads: 12; OS: Linux 4.15; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: CL
Where can I find the 'pdf (writer)' filter in file open dialog?
(In reply to Kevin Suo from comment #7) > Where can I find the 'pdf (writer)' filter in file open dialog? I checked and you have to enable experimental features to see it
(In reply to Kevin Suo from comment #7) > Where can I find the 'pdf (writer)' filter in file open dialog? The list is organized by module. Writer is the second block and the import filter is listed as 'PDF - Portable Document Format (Writer) (*.pdf)' That will force the import into Writer rather than the default Draw. Not experimental on Windows builds...
OK, I see, this is exactly the same issue as reported in bug 143095. The test document in this bug uses "Traditional Arabic", "Frank Ruehl CLM" and "Simplified Arabic" fonts. All these fonts are of the names without spaces in the PDF file (i.e., TraditionalArabic, FrankRuehlCLM-Medium and SimplifiedArabic, which can be observed from a pdf viewer). In Draw PDF import and Writer PDF import, this font names are read from the PDF files. The read-in names are then have their suffixes removed, but still without spaces, and are then used directly to build-up an ODF xml stream and then used for rendering. Draw and Writer PDF import seems to use the same pre-process codes located in sdext/source/pdfimport, but they do have separate "treevisiting" codes: sdext/source/tree/drawtreevisiting.cxx and sdext/source/tree/writertreevisiting.cxx. However, the set if familyName is the same. See the following code in line 830 in the drawtreevisiting.cxx file: // family name aFontProps[ "fo:font-family" ] = rFont.familyName; aFontProps[ "style:font-family-complex" ] = rFont.familyName; and the following in line 902 of the writertreevisiting.cxx file: // family name aFontProps[ "fo:font-family" ] = rFont.familyName;
*** This bug has been marked as a duplicate of bug 143095 ***