Description: It is of type; https://xkcd.com/2109/ Please see enclosed sample. .odt has a black "A" followed by a red "1" when file/export to .xhtml the "A" becomes red. export to .pdf will not make "A" red. I have no clear idea of how this string originally (years ago) was created. Steps to Reproduce: 1.expoert enclosed document to .xhtml 2.check the result 3. Actual Results: a red "A" Expected Results: a black "A" Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: en-US Module: TextDocument [Information guessed from browser] OS: Linux (All) OS is 64bit: yes
Created attachment 150033 [details] file contains sample string
I confirm it with Version: 6.3.0.0.alpha0+ (x64) Build ID: 91cdf22b88a4f7bec243c8fb187627e766d3294c CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; TinderBox: Win-x86_64@42, Branch:master, Time: 2019-03-08_00:38:10 Locale: en-US (de_DE); UI-Language: en-US Calc: threaded If you change colour of the A from "automatic" to "Black" export works well.
Also reproduced in Version 4.1.0.0.alpha0+ (Build ID: efca6f15609322f62a35619619a6d5fe5c9bd5a)
Bug still present in Version: 7.1.0.3 (x64) / LibreOffice Community Build ID: f6099ecf3d29644b5008cc8f48f42f4a40986e4c CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL
Reproduced in 7.2 alpha1. Note that Save As > HTML looks as expected. Version: 7.2.0.0.alpha1+ / LibreOffice Community Build ID: b1c0734ffe0f395757b6e0cea7830d820231afeb CPU threads: 8; OS: Linux 4.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2021-05-18_03:16:20 Calc: threaded
Dear Ola Smith, 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
Problem remains in 7.3.7.2 (Latest version available in Kubuntu 22.04.2) The problem seems to be associated with the original string "<black>A<space><red>1" itself. When I copy/paste the string into a new File/New/Text Document the error remains. A newly written "<black>A<space><red>1" comes out as expected in the same .html file. My guess is that the original "A" is not a plain "<black>A" but still carries with it memories of a previous career as a "<red>A", now totally invisible. But the problem remains - a black A should never be anything other than a black A ....
@Svante, I thought you might be interested in this issue
<text:p text:style-name="P1"> <text:span text:style-name="T2">A</text:span> <text:span text:style-name="T3"> </text:span> <text:span text:style-name="T4">1</text:span> </text:p> Interesting! The Paragraph P1 contains the color red and T2 does not contain a color black to overwrite it! I am going to tell Michael Stahl about it to get a second opinion. It is not necessary an XHTML filter issue on first glance: <style:style style:name="P1" style:family="paragraph" style:parent-style-name="Standard"> <style:paragraph-properties fo:margin-left="1.265cm" fo:margin-right="0cm" fo:text-indent="0cm" style:auto-text-indent="false"> <style:tab-stops /> </style:paragraph-properties> <style:text-properties fo:color="#ff0000" style:font-name="FreeSans" fo:font-size="10pt" officeooo:paragraph-rsid="00041ba9" style:font-size-asian="10pt" style:font-size-complex="10pt" /> </style:style> <style:style style:name="T1" style:family="text"> <style:text-properties style:use-window-font-color="true" fo:font-weight="bold" fo:background-color="transparent" loext:char-shading-value="0" style:font-weight-asian="bold" style:font-weight-complex="bold" /> </style:style> <style:style style:name="T2" style:family="text"> <style:text-properties style:use-window-font-color="true" fo:font-weight="bold" officeooo:rsid="0005faa8" fo:background-color="transparent" loext:char-shading-value="0" style:font-weight-asian="bold" style:font-weight-complex="bold" /> </style:style>
Michael Stahl was so kind to explain. The relevant value is: https://docs.oasis-open.org/office/OpenDocument/v1.3/os/part3-schema/OpenDocument-v1.3-os-part3-schema.html#property-style_use-window-font-color Everything not being the background is the foreground and I will try some heuristic to see if the background is "dark", than font color is white, otherwise the font color will be black (most of the time in this situation). Taking over this issue! Thanks for the nice test case!