Created attachment 136845 [details]
english and arabic palettes
1. open writer in arabic UI
2. open font color widget to show palette
3. notice that there is a blank space at the end of the palette
Build ID: c5a93cad149618bbd43632f1660a558c34bdbf7e
CPU threads: 2; OS: Linux 4.4; UI render: default; VCL: gtk2;
TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2017-10-07_01:12:25
Locale: en-US (en_US.UTF-8); Calc: group
Happens with Hebrew interface on version 5.4.1 as well.
I tried to find something related in the code to RID_SVXSTR_COLOR_VIOLET but didn't see anything for RTL interfaces.
Maxim, Gabor: Any thoughts on why this is happening?
I'll look into this once home from the conference.
I have seen such when I accidentally made some holes on the translation handling code and it was unable to match a color name with a translation in method SvxUnoConvertResourceStringBuiltIn :
But no idea why does it happen only for some languages and not others.
I think this may be happening because the translations of Violet and Purple are somehow identical in both languages and that is not something the framework can tolerate:
Changing the translation of Violet in he locale in a local build has fixed the problem for me.
Created attachment 137063 [details]
Changing translation of Violet fixed the problem
Still happens in:
Build ID: 9050854c35c389466923f0224a36572d36cd471a
CPU threads: 8; OS: Linux 4.9; UI render: default; VCL: gtk3;
Locale: en-US (en_US.utf8); Calc: group
OS: Debian 64bit Stretch (Debian 9.2, with some backported packages)
On pc Debian x86-64 with master sources updated some days ago, I don't reproduce this.
Noticing tdf#117969 and its fix, do you reproduce this with LO version >= 220.127.116.11?
Dear Yousuf Philips (jay) (retired),
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 http://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!