Created attachment 115463 [details] No Philippine Peso in Currency Symbols I select "Insert > Special Characters..." to open the "Special Characters" dialog box. No matter where I look I cannot find the Philippine Peso sign. It should be under Currency Symbols. The character looks like this: ₱ This symbol is U+20B1 in Unicode 3.2 standard.
For me not reproducible with LO 4.4.2.2, Win 8.1. I have it in my list. Which version of LO are you using?
Created attachment 115464 [details] I'm using 4.4.2.2. Same version. I'm using 4.4.2.2.
Thanks for your very fast reply. Then it is maybe a Linux only problem?
If it helps, I got my LO from the 4.4 PPA, package version 1:4.4.2~rc2-0ubuntu1~trusty1.
Could it be that I was just looking at the wrong place? Can you please show me a screenshot of where you found it in your LO? I am willing to mark this invalid if it is just a user mistake on my part.
You looked at the same place as I, but I have several characters more than you. Maybe somebody else can check it with Linux if he/she has the same like you.
Created attachment 115465 [details] Special Characters in Windows I installed LO in a Windows VM, and I confirm Andy's observation that the Peso sign indeed appears in the Windows version of LO. Therefore the issue is either limited to Linux or just my system.
Created attachment 115468 [details] Special Characters in Ubuntu It's not just my system. I get the same result running LO from an Ubuntu 14.04 Trusty Live DVD.
Created attachment 115469 [details] Special Characters in Linux Mint Same result on Linux Mint 17. So it's either a Linux issue or an issue with the packaged version in Ubuntu repositories and PPA.
This is maybe related to ICU. Maybe the Debian-packaged version of LO (which goes also to Linux Mint and Ubuntu, of course) is built using an old version of ICU.
Adolfo, I just downloaded Debian 8 Jessie and tested it from the Live DVD. As expected, I got the same result as Ubuntu and Mint. Therefore this issue is at least Debian-wide. I am downloading Fedora now to test if it is the same for non-Debian distros.
Created attachment 115500 [details] Special Characters in Fedora I found that the bug also exists in Fedora. Therefore it is not limited to Debian-based distros, and is probably Linux-wide.
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.1.5 or 5.2.1 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20160920
Still fails in LO, but works in Wordpad. You will not find this character in the special characters menu, but entering it via ALT+8369 will fail, too! You will get a dotted matrix instead of a Philippine Peso sign. 1. Start Writer 2. Enter ALT+8369 -> You get a matrix of dots 3. Start Wordpad 4. Enter ALT+8369 -> You get the peso sign 5. Start Notepad 6. Enter ALT+8369 -> You get the dotted matrix again! Tested with different fonts like Liberation Sans, Arial,... Version: 6.0.5.2 (x64) Build ID: 54c8cbb85f300ac59db32fe8a675ff7683cd5a16 CPU threads: 4; OS: Windows 10.0; UI render: GL; Locale: en-US (de_DE); Calc: CL
Dear Bamm, 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! Warm Regards, QA Team MassPing-UntouchedBug
Suggestion to merge the Philippine Peso currency In LibreOffice Calc, I notices that there are three currencies PHP ₱ Hiligaynon PHP Php English (Philippines) PHP Php Iloko The fact is, there is only one currency in the Philippines. I suggest combining them all and make it look like this: PHP ₱ English (Philippines) This format is used all throughout the country.
Dear Bamm, 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
Hi Everyone, This seems to be fixed now. I don't know which version of LibreOffice fixed it but I just checked and it's already there. Thank you all for all the hard work at continually improving LibreOffice. As an end user, I appreciate your effort. Bamm
Closing per Comment 18
Why is the resolution WORKSFORME when it was clear that it didn't work for anyone before (and has in fact been confirmed with duplicates) and it only began working after fixes were made? Why isn't it resolved FIXED? WORKSFORME means that the bug could not be reproduced and is therefore closed for not being a bug that can be confirmed.
(In reply to Bamm from comment #20) > Why is the resolution WORKSFORME when it was clear that it didn't work for > anyone before (and has in fact been confirmed with duplicates) and it only > began working after fixes were made? Why isn't it resolved FIXED? > > WORKSFORME means that the bug could not be reproduced and is therefore > closed for not being a bug that can be confirmed. Please check https://bugs.documentfoundation.org/page.cgi?id=fields.html#bug_status
Ah I understand. I wish there was a "WORKSNOW" resolution. Does it mean that the commit that added it is impossible to be identified?
(In reply to Bamm from comment #22) > Ah I understand. I wish there was a "WORKSNOW" resolution. Does it mean that > the commit that added it is impossible to be identified? It should be possible to identify, if someone is bothered enough to bibisect it (https://wiki.documentfoundation.org/QA/Bibisect).
> It should be possible to identify, if someone is bothered enough to bibisect > it (https://wiki.documentfoundation.org/QA/Bibisect). I get it now. Thanks for the explanation. I'm fine now with WORKSFORME.