Description: I am looking to set Noto Sans as the font family for my custom style in my presentations. However, when I save my presentation in PPTX format, close it, then reopen it, the set custom typefaces are gone; instead, the Liberation Sans font comes into place when I add new slides. Steps to Reproduce: 1. Open "Master Slides", as well as "Styles" in the right panel. 2. Click on every available style, set them to use the font family Noto Sans. 3. Save this presentation as a template (.otp). 4. Save this presentation as PPTX. 5. Close and reopen this presentation. 6. Add a new slide. Actual Results: The new text fields appear to use the font family Liberation Sans, which is the default font for the whole LibreOffice suite. Expected Results: Any subsequent new slides shall use the Noto Sans family for text layout. This is what happens in Microsoft PowerPoint. Reproducible: Always User Profile Reset: Yes Additional Info: I believe that LibreOffice shall NOT be replacing fonts by itself upon reopening files, without explicit consent or awareness of the user. Microsoft Office NEVER does the same thing.
Created attachment 161464 [details] This is the problematic PPTX file that describes my problem. This is the problematic PPTX file that describes my problem.
Created attachment 161466 [details] This is the template that uses Noto Sans as default family.
Created attachment 161467 [details] This even happens with a built-in template that specifies custom fonts.
Can reproduce this. The styles also change the font to Liberation, if the OTP is saved as a POTX (PPT Template). Version: 7.1.0.0.alpha0+ (x64) Build ID: 2047a5978ac8188e61da9cd3b2f40d86df5570bb CPU threads: 4; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-US Calc: threaded
Created attachment 169212 [details] How the original file and its PPTX versions Master Slide looks Quite a problem in: Version: 7.2.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 7eb289c49cc7245ef3001a39be0c15d06bbe875b CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: en-US (hu_HU); UI: en-US Calc: CL
Dear Tianxing Yang, 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