Summary: | FILEOPEN DOCX Writer unable to recognize the font when it is defined as “Times New Roman félkövér” (Times New Roman Bold) | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | NISZ LibreOffice Team <libreoffice> |
Component: | Writer | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | NEW --- | ||
Severity: | normal | CC: | aron.budea, kelemeng, nemeth |
Priority: | medium | ||
Version: | 6.2.0.0.alpha1+ | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Crash report or crash signature: | Regression By: | ||
Bug Depends on: | |||
Bug Blocks: | 102985, 108769, 113438 | ||
Attachments: |
A screenshot showcasing the issue.
An example file with the font mentioned Screenshot in English Word 2013 |
Description
NISZ LibreOffice Team
2018-11-09 09:22:32 UTC
Created attachment 146478 [details]
A screenshot showcasing the issue.
Created attachment 146479 [details]
An example file with the font mentioned
Created attachment 146604 [details]
Screenshot in English Word 2013
This seems like something Microsoft should address, as even a different language Word version can't handle this kind of font name, either.
(In reply to Aron Budea from comment #3) > Created attachment 146604 [details] > Screenshot in English Word 2013 > > This seems like something Microsoft should address, as even a different > language Word version can't handle this kind of font name, either. Well they kinda started: this black magic does not work with the new generation C* default fonts, or any other. But until this pattern dies out: "It's impossible to work with LibreOffice". So, how about recognizing these "font formattings" and silently converting them to normal font name + character formatting? This would also help with eliminating documents created with bad user habits based on bad design ideas. (In reply to Gabor Kelemen from comment #4) > (In reply to Aron Budea from comment #3) > > This seems like something Microsoft should address, as even a different > > language Word version can't handle this kind of font name, either. > > Well they kinda started: this black magic does not work with the new > generation C* default fonts, or any other. That won't make the documents show correctly in different language Word versions, though. Additionally, I could reproduce this with the mentioned C* fonts in English with my local Word 2013 installation (eg. "Cambria bold"). > So, how about recognizing these "font formattings" and silently converting > them to normal font name + character formatting? Do you have information on how this works with other languages? Is it always <font name> + <style in current UI language>? Can the <style> part precede <font name> in any language? I also can reproduce this with "Arial fett" (created with Word 2016) and Version: 6.2.3.2 (x64) Build-ID: aecc05fe267cc68dde00352a451aa867b3b546ac CPU-Threads: 4; BS: Windows 10.0; UI-Render: GL; VCL: win; Gebietsschema: de-DE (de_DE); UI-Sprache: de-DE Calc: threaded So I think, since the bug is reproducible, I can set status to NEW, although there are some questions around this topic. Still present in Version: 7.1.2.2 (x64) / LibreOffice Community Build ID: 8a45595d069ef5570103caea1b71cc9d82b2aae4 CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: de-DE Calc: CL Dear NISZ LibreOffice Team, 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 |