Created attachment 39659 [details] actual example Impress is not showing the Unicode characters correctly when it is in fullscreen/run mode. The Unicode characters shows correctly in edit mode but once you press F5, it gets garbled. Additionally, there are instances wherein the ASCII range characters disappears in fullscreen/run mode when it is followed by Unicode characters. In this case, the Unicode characters appears correctly. See attachment for an actual sample. First noticed this in LibreOffice beta1 under Ubuntu 10.10 64-bit. The same thing happens in LibreOffice beta2 under Ubuntu 10.10 Netbook Remix 32-bit.
hmm I can't even get this to open fullscreen, soffice exits console o/p is power@linux-imfd:~/OOO_BUILD_MASTER/ooo-build/INSTALL_DIR/program> nv50_screen_get_param:149 - Unknown PIPE_CAP 29 nv50_screen_get_param:149 - Unknown PIPE_CAP 29 nv50_screen_get_param:149 - Unknown PIPE_CAP 29 nv50_vbo_vtxelt_to_hw:153 - unsupported vbo format: PIPE_FORMAT_R64G64B64_FLOAT ** (bug-buddy:8296): WARNING **: Couldn't load /etc/xdg/autostart/ksmolt-autostart.desktop: Invalid key name: X-KDE-autostart-condition[$e] Missing separate debuginfo for /usr/lib64/libstdc++.so.6 => thorsten
Confirmed. A few are missing.
Fixed a crash inside the opengl transitions alongside. A race apparently, when trying to dispose textures on a display that was not yet initialized.
Sounds like the same issue I reported for OpenOffice.org 3.2 on Ubuntu Linux, see OOo bug 115486, http://www.openoffice.org/issues/show_bug.cgi?id=115486
This is a Impress bug, therefore changed Component accordingly. And: is this bug still open, or is it fixed now?
Just to give an update. On pc Debian x86-64 with 3.5 branch updated today (and brand new LO profile), Unicode doesn't display on first slide in edit or fullscreen mode. However, everything is ok with slide 5 (which contains the "Peso") in both mode. Now perhaps it's normal and that i would just need a specific font. Noticed this on console : warn:legacy.osl:6402:1:/home/julien/compile-libreoffice/libo_3_5/sw/source/core/text/porlay.cxx:1279: Heavy InitScriptType() confusion + several times (about 30 ?) : warn:legacy.osl:6402:1:/home/julien/compile-libreoffice/libo_3_5/sw/inc/swrect.hxx:308: SVRect() without Width or Height
This bug has not been touched by its owner for a long time. To make it clearer which bugs should be fixed by someone else please take following action: - If you are the owner, and you are actively working on the bug, please give it an update. - If you are the owner, and you do not plan to work on it in the near future, please reassign it to the default assignee and change its status to NEW.
Sorry guys, cannot currently commit time to this -> freeing the bug for others to pick it up.
Hi, Current status on ubuntu 13.10 x64, LibreOffice Version: 4.2.0.1 Build ID: 420m0(Build:1) - No porblems in first page and Peso sign - Slides #7 and 10 has display problems in both edit and presentation mode. Best regards, Zeki
Did you test, if your linux could see this unicode in other programs: web browser on wikipedia (https://en.wikipedia.org/wiki/Tagalog_%28Unicode_block%29 or https://en.wikipedia.org/wiki/Miscellaneous_Symbols_And_Pictographs )or text editor?? For example some unicodes could no be seen on Ubuntu 12.04 if you don't install ttf-ancient-fonts
Please, is it possible to have a screencopy for each slide showing what we should see ? Best regard. JBF
Created attachment 102918 [details] Screenshots of slides 7 and 10 from presentation showing correct rendering. (In reply to comment #9) > - Slides #7 and 10 has display problems in both edit and presentation mode. (In reply to comment #10) > Did you test, if your linux could see this unicode in other programs: web > browser on wikipedia > (https://en.wikipedia.org/wiki/Tagalog_%28Unicode_block%29 or As indicated in these comments the non-displayed characters are codepoints in the Tagalog Unicode block. With installed font support the slides render as expected in both edit and slideshow mode under Debian 7 x86_64 running v4.1.6.2 Build ID: 40ff705089295be5be0aae9b15123f687c05b0a and v4.3.0.2 Build ID: 14ed55896fdfcb93ff437b85c4f3e1923d2b1409. Free Tagalog fonts available here: http://www.mts.net/~pmorrow/fonts.htm I used the Baybayin Lopez one to produce the attached screenshots. I think this can be RESOLVED as NOTABUG.
As a result of comment 12 status set back to NEW. I will leave for another to confirm and close.
Caolán/thorsten: Following Owen's comment and since the subject, thought you might be interested in this one.
works for me too, might have been a problem with glyph substition in full screen mode vs normal. If anyone still has the problem then attach the output of fc-list -v to this bug before reopening
Created attachment 103463 [details] Slide 7 with glyph bug I have the bug with glyph on slide 7 and slide 10 in fullscreen mode and in view mode too The glyphs are not smooth and have a lot of pixels. Tested on Ubuntu 12.04.4 x86_64 with: * LibreOffice 3.5.7.2 Version ID : 350m1(Build:2) * LibreOffice 4.3.0.3 Build ID: 08ebe52789a201dd7d38ef653ef7a48925e7f9f7
Created attachment 103464 [details] fc-list -v on Ubuntu 12.04.4 fc-list -v where slide 7 's glyph with a lot of pixel.
Created attachment 103470 [details] After install BayLopez.ttf No change after install BayLopez.ttf
REOPENED wrong status - setting back to NEW.
** 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.0.4 or later) 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 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 your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-12-20
** 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.6 or 5.2.3 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-20170103
Unicode pictographs are no longer shown: https://bugs.documentfoundation.org/show_bug.cgi?id=116731
** 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 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
Dear JC John Sese Cuneta, 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
Dear JC John Sese Cuneta, 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
The original issue seems to be long fixed. The pixelated glyphs come from unifont, if this is the only font installed that supports these characters (or for some reason FontConfig prefers it over other fonts) you will get the bad looking glyphs, but there is no bug here, it is just a and outdated-looking font. Closing as I don’t think there is anything remaining to fix here.