Deepl translation changes font color from Automatic to None. Not seen with Light document mode but a problem in Dark mode.
Not reproduced in: Version: 24.2.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 619500d6919c227e734b119481a4b334972e0b7b CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded I tested with both "Dark" and "Light" scheme in Options > LibreOffice > Application Colors. Character font effects still use "Automatic" font colour after translating. Do you have more precise repro steps? Still an issue in a recent master? Which OS?
Created attachment 191180 [details] Sample ODT Seems this depends, here is a document where I reproduced .
Seems this is how selection is replaced. New text takes properties not of replaced text, but of previous one. So if default is None or Black, text with Automatic will be replaced with it.
Thanks, confirmed in: Version: 24.2.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 619500d6919c227e734b119481a4b334972e0b7b CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded
Created attachment 191216 [details] smaller sample ODT differentiating Automatic colour from other colours Smaller sample ODT to test: 1. set up DeepL translation experimental feature 2. select all text 3. "Tools > Translate" to e.g. German Results: Teal font colour not lost, but Automatic font colour replaced by black (which doesn't even match the Body Text style's default colour).
May be duplicate of bug 79717 ,but let us keep separately until either is fixed.
Dear Timur, 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