Created attachment 149210 [details] bugdoc Open the attached document in LibreOffice 6.1.6. The document font is bold. In 6.1.4.2 the font is normal. Looks like a regression in either 6.1.5 or 6.1.6.
Created attachment 149211 [details] actual
Created attachment 149213 [details] expected
Created attachment 149214 [details] bugdoc compared OO and LO 6.3+ Seems to me that text was always bold. No repro not bold. Test in Windows.
Maybe it's Linux only, at least OpenOffice 3.2 on Linux displayed the text non-bold (as shown in attachment 149213 [details]).
I can't reproduce it in Versión: 6.2.0.3 Id. de compilación: 98c6a8a1c6c7b144ce3cc729e34964b47ce25d62 Subprocs. CPU: 1; SO: Windows 6.1; Repres. IU: predet.; VCL: win; Configuración regional: es-ES (es_ES); Idioma de IU: es-ES Calc: threaded nor in Versió: 6.1.4.2 ID de la construcció: 1:6.1.4-0ubuntu0.16.04.1~lo2 Fils de CPU: 4; SO: Linux 4.15; Renderitzador de la IU: per defecte; VCL: gtk3; Configuració local: ca-ES (ca_ES.UTF-8); Calc: group threaded however, using the bisect repositories i can reproduce it in Version: 6.3.0.0.alpha0+ Build ID: c7ad7849d54fd3dad67e7779102f65b8b2f04881 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); UI-Language: en-US Calc: threaded and Version: 4.4.0.0.alpha0+ Build ID: ffeb03625f31fd3a88b7c0f0bccf57d0aeeca25c only reproducible in development enviroments ??
There is a difference in LibreoOffice 6.1.4.2 TDF version vs Ubuntu version. In the Ubuntu version it is shown as non-bold while in the TDF version it is shown as bold.
michaelweghorn> for me, text of tdf#123397 doc is shown in bold with libreoffice package 1:6.1.5~rc1-2 in debian testing
content.xml: <text:p text:style-name="P8">01<text:tab/>Wohnsitz des Antragsgegners oder eines Mitantragsgegners</text:p> <style:style style:name="P8" style:family="paragraph" style:parent-style-name="Table_20_Contents"> <style:paragraph-properties fo:text-align="justify" style:justify-single-word="false"> <style:tab-stops> <style:tab-stop style:position="0.397cm"/> </style:tab-stops> </style:paragraph-properties> </style:style> styles.xml: <style:font-face style:name="Arial1" svg:font-family="Arial" style:font-adornments="Standard" style:font-family-generic="swiss" style:font-pitch="variable"/> <style:style style:name="Table_20_Contents" style:display-name="Table Contents" style:family="paragraph" style:parent-style-name="Standard" style:class="extra"> <style:text-properties style:font-name="Arial1" fo:font-size="7pt" fo:font-weight="normal"/> </style:style> so we have style:font-adornments="Standard" and fo:font-weight="normal", i don't see where the bold is supposed to come from?
styles.xml: <style:style style:name="Standard" style:family="paragraph" style:class="text" style:master-page-name=""> <style:text-properties style:font-name="Arial Black" fo:font-size="10pt" fo:font-weight="900"/> </style:style> somehow the fo:font-weight="900" of the parent style "Standard" is not overwritten by the fo:font-weight="normal" of the derived style "Table Contents".
if you use e.g. de_DE locale, you get "Regular" font weight. but with en_US you get "Black" font weight. the problem is that this style: <style:style style:name="Table_20_Contents_20__28_user_29_" style:display-name="Table Contents (user)" style:family="paragraph" style:parent-style-name="Standard"> <style:paragraph-properties ns3:contextual-spacing="false" fo:margin-top="0.049cm" fo:margin-bottom="0.049cm" style:vertical-align="middle"/> <style:text-properties style:font-name="Arial" fo:font-size="7.5pt" style:font-name-complex="Arial" style:font-size-complex="7.5pt"/> </style:style> "Table Contents (user)" will be mapped to the same internal SwTextFormatColl as the built-in style "Table Contents", but *only* if it matches the locale's translation of "Table Contents".
this could be fixed by: 1) reworking SwFormat etc. (haven't checked which of the 5-6 classes are actually subclasses of SwFormat) in Writer document model so it stores the "programmatic name" (as used in ODF/other file formats) instead of the "UIName" that is shown in the UI, and then moving the FillUIName / FillProgName conversions out of the "unocore" classes and into all UI classes that display style names. 2) making use of the SwFormat's m_nPoolFormatIds as a second part of the lookup key, so that we can store styles with same name but one has a pool-id and the other does not; not sure which/how many places would need to know whether they want a pool-style or not though. either of these is a bit of work; anything simpler looks like it's going to cause some kind of problem or other...
Dear Michael Stahl, This bug has been in ASSIGNED status for more than 3 months without any activity. Resetting it to NEW. Please assigned it back to yourself if you're still working on this.
Dear Samuel Mehrbrodt (CIB), 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://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
Seems very minor, can be easily fixed with setting Default Style, which is empty, to Regular font style. But Default Style should not be empty. Maybe this should be closed.
Dear Samuel Mehrbrodt (allotropia), 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