Description: I created a new style and set "Junicode" as the font, then set the font style to "Bold". Everything works great in the file and in global formatting, but when I save, close, then re-open the file, "Junicode" is set to "Regular" throughout the document, its "Bold" setting in the styles is set to "Regular", and I must change the setting back to "Bold" in the styles settings (RC > Modify...) for it to render correctly again. Steps to Reproduce: 1. Set "Junicode" with "Bold" as the font for a new "style" in the "Font" tab 2. Type some text set as this new style, save the file. 3. Re-open the file, note the font is no longer bold. 4. Repeat 1-3 in the same file to set it back to "Bold", note the problem repeats. Actual Results: Junicode font as a style is not Bold after set, closed, and reopened. Expected Results: Junicode font as a style should remain Bold after set, closed, and reopened. Reproducible: Always User Profile Reset: No Additional Info: I have no other bugs with this version of Writer. Here is an example file at GitHub: https://github.com/JesseSteele/pdf-bug/raw/master/Paperback.doc
Hello Thank you for reporting the bug. I can not reproduce the bug in Version: 6.2.1.2 (x64) Build ID: 7bcb35dc3024a62dea0caee87020152d1ee96e71 CPU threads: 4; OS: Windows 6.3; UI render: default; VCL: win; Locale: en-US (en_US); UI-Language: en-US Calc: CL Version: 6.3.0.0.alpha0+ (x64) Build ID: 91cdf22b88a4f7bec243c8fb187627e766d3294c CPU threads: 4; OS: Windows 6.3; UI render: default; VCL: win; TinderBox: Win-x86_64@42, Branch:master, Time: 2019-03-08_00:38:10 Locale: en-US (en_US); UI-Language: en-US Calc: CL I have saved the file as .doc
Steps: 1. Download Junicode font https://sourceforge.net/projects/junicode/files/junicode/ and install Junicode.ttf and Junicode-Bold.ttf 2. In Writer, create new paragraph style, go to Font tab and change font to Junicode and style to Bold 3. Type some text and apply the style 4. Save as .doc OR .docx and reload Repro already in 3.3.0 (Win 10) The problem is not seen with .odt or other fonts with .doc/docx. Arch Linux 64-bit Version: 6.3.0.0.alpha0+ Build ID: b8f33d053c2cbf05872cf9ddfeff4cc302ee281f CPU threads: 8; OS: Linux 5.0; UI render: default; VCL: gtk3; Locale: fi-FI (fi_FI.UTF-8); UI-Language: en-US Calc: threaded Built on 20 April 2019
Dear JesseSteele, 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 https://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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
The likelihood that this is NOTOURBUG is extremely high. But since I don't actually know, I won't close the bug report.