Description: see steps to reproduce Steps to Reproduce: 1. Run Writer 2. type "AB" 3. Select "A" 4. context menu-> character->character 5. "Font Color" in Font "Effects" Tab 6. Select "Red" 7. OK 8. Select "B" 9. main menu-> format->Asian phonetic guide 10.Set "b" as ruby text for "B" 11. OK Actual Results: "b" is shown in red color Expected Results: "b" is shown in default black color Reproducible: Always User Profile Reset: No Additional Info: Version: 6.3.0.0.alpha0+ (x64) Build ID: 82fb7f9f90a3ba9d53b3412124e513aa78ddca10 CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; TinderBox: Win-x86_64@42, Branch:master, Time: 2019-02-05_23:41:03 Locale: ja-JP (ja_JP); UI-Language: en-US Calc: threaded
Confirm with Version: 6.3.0.0.alpha0+ Build ID: f8c4459bbda62cb905d0c007cac044f3410ab76b CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; regression, works in 6.0.7
This seems to have begun at the below commit. Adding Cc: to Mark Hung ; Could you possibly take a look at this one? Thanks 3e278e12f3500738012cc2f579c68156f3306541 is the first bad commit commit 3e278e12f3500738012cc2f579c68156f3306541 Author: Jenkins Build User <tdf@pollux.tdf> Date: Sun Jan 21 09:05:06 2018 +0100 source d1bc14b318c9a412a761d243085da0895a1aed4a author Mark Hung <marklh9@gmail.com> 2018-01-20 23:35:44 +0800 committer Mark Hung <marklh9@gmail.com> 2018-01-21 08:43:14 +0100 commit d1bc14b318c9a412a761d243085da0895a1aed4a (patch) tree ea4dbeaf9c053974e690dc8b856fb4b66638ffe5 parent 121f6f3c79ea2dceb7cc3d61a56f5a56a1cb0d0d (diff) tdf#35301 Formatting ruby text on right side.
Created attachment 149057 [details] file for test
Strangely, if the file given by raal is opened by MS Word, 'b' is shown in black color.
https://opengrok.libreoffice.org/xref/core/sw/source/core/text/itrform2.cxx?r=56e95f8e#1259 Just out of curiosity: 1. Is there any way to get the next portion to this SwRubyPortion? 2. From which portion does this rInf come from? rInf.GetFont() is passed as the second paramter of SwRubyPortion's constructor. I don't know why the commit regressed Writer either.
Dear himajin100000, 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
Also in Version: 7.6.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 3584fd0d110b4138ec32cf55ddd07e3fb8d81333 CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded
Dear himajin100000, 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