Description: When export to PDF, the font color at the "section 1 footer" of a document changed from White to Black. Steps to Reproduce: 1.Open the sample document in LibreOffice (25.8.2.2 - latest available version) 2.Click on Export to PDF 3.Open the generated PDF Actual Results: The text color is in black. Expected Results: The text color should be in white as same as in the MS word. Reproducible: Always User Profile Reset: No Additional Info: Version: 25.8.2.2 (X86_64) Build ID: d401f2107ccab8f924a8e2df40f573aab7605b6f CPU threads: 22; OS: Windows 11 X86_64 (build 26100); UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded
Created attachment 203715 [details] Sample file
Created attachment 203716 [details] Text_White_to_Black_issue.png
Actually, No! Nothing to do with the export/print to PDF. You don't describe your work flow for manipulating this document with LibreOffice, assume a headless workflow, bcz you would notice the changed formatting when document is open in Writer. However, when imported from OOXML to LibreOffice document canvas, the formatting of the table contained in the footnote has already lost its assigned style. The direct formatting of the table is incomplete before an attempt to export/print to PDF is made. Apparent when the document is open in LibreOffice Writer. You can correct this LibreOffice filter import issue by manually assigning the correct style for the footnote. The style is imported from this document and available in Writer as a 'Custom style' titled "Coversheet Footer" Use the SideBar Navigator deck to select the Table object in the first page's footnote (it is Table 5 in my rendering on 25.8.2.2 on Win11) then with selection made assign from the SideBar Styles deck the document's custom style 'Coversheet Footer' to replace the generic template provided 'Footer' style. Then either export/print from the Writer session, or save to ODF format for additional editing. I would not directly save back to OOXML .docx @Miklos, Tomaž any perspective on misbehavior of our import filter here. Why the footer on the first page did not get the correct style even though it is parsed with the document? =-testing-= Version: 25.8.3.1 (X86_64) Build ID: 52ad9dd1c984050a9fb6932dbfb16e86a49e9758 CPU threads: 28; OS: Windows 11 X86_64 (build 26200); UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded
(In reply to V Stuart Foote from comment #3) s/footnote/footer/g
> any perspective on misbehavior of our import filter here Sorry, no idea off the top of my head. Certainly looks like a DOCX import bug, but would need more investigation to be sure.