Created attachment 54647 [details] LibreOffice Writer in a Fedora 16 virtual machine showing Á À Â Ã Ā In LibreOffice Writer under Linux, if you type the capital letter "A" and then a Unicode combining character (e.g. U+0301 which draws an acute mark above the preceding character), you will see the acute mark drawn too low, overlapping with "A". To reproduce this bug, start "charmap" in GNOME or "kchar" in KDE, type "A" in the charmap program's "Text to copy" field, and then go to the combining character U+0301 and insert it to the "Text to copy" field. Now you should have an Á (A with an acute mark). Now copy this text into LibreOffice Writer, and now you see, whatever font you use, the acute mark is always drawn too low, crossing with "A". This is caused by LibreOffice/OpenOffice's Linux font rendering engine, I think. Windows versions of LibreOffice/OpenOffice don't have this bug at all. The attached screenshot is a LibreOffice Writer in a Fedora 16 virtual machine showing Á À Â Ã Ā. Each of them is the capital letter A plus a combining character (U+0301, U+0300, U+0302, U+0303, U+0304). You can see the diacritics are drawn too close to "A". The font used is Liberation Serif, but this bug applies to all fonts.
Created attachment 54648 [details] AbiWord in a Fedora 16 virtual machine showing Á À Â Ã Ā In contrast, AbiWord running in the same Fedora 16 virtual machine can show the same text much better.
Confirming. Although Libreation Sans is a very bad example, as it doesn't contain combining diacritics and LO has to fall back on another font and thus mix fonts with very likely different metrics (one font for the base letter, and a different font for the diacritic). Works fine with graphite-based fonts like Gentium Not sure whether Abiword "cheats" by replacing the combining sequence by the respective single letter...
Christian Lohmaier: Now I tested Gentium fonts. "Gentium" and "GentiumAlt" still have this problem; "Gentium Basic" and "Gentium Book Basic" don't have the problem. Also, I don't think AbiWord cheats, because from my AbiWord screenshot you can see the third A's diacritic (^) is a little left to where it should be.
Christian Lohmaier: If "mix fonts" as you said is the case, maybe LO should force the base letter to use the diacritic's font.
*** Bug 27977 has been marked as a duplicate of this bug. ***
As a suggestion, if Graphite/SIL fonts are so crucial for LibreOffice/Linux's proper text rendering, why doesn't LibreOffice ship with SIL fonts and choose one SIL font as LO's default document font?
Created attachment 89657 [details] ODT and screenshots showing rendering under v3304 through v4132. This report basically deals with the Unicode FAQ "Q: Yes, I can represent (for example) X with circumflex by use of X with a combining circumflex: <U+0058, U+0302>. But it doesn't display correctly. The circumflex comes out misplaced, not properly over the “X”.": http://www.unicode.org/faq/char_combmark.html#12b There has been steady improvement in LO (and possibly the fonts shown in the attached) with respect to the handling of combining characters. The attached ODT was created under Ubuntu 10.04 x86_64 running v4.1.3.2 Build ID: 70feb7d99726f064edab4605a8ab840c50ec57a and provides an example in 36pt of A (U+0041) combined with these combining marks indicated in the description: - Combining grave accent (U+0300) - Combining acute accent (U+0301) - Combining circumflex accent (U+0302) - Combining tilde (U+0303) - Combining macron (U+0304) ... using the main fonts (not all variants e.g., condensed, mono, etc.) that are distributed with LO v4.1.3.2 as well as Arial and Times New Roman. This document was then viewed under the same OS using these versions of LO (not ideal I know, but still indicative): - v3.3.0.4 OOO330m19 Build: 6 - v3.4.6.2 OOO340m1 Build: 602 - v3.5.7.2 Build ID: 3215f89-f603614-ab984f2-7348103-1225a5b - v3.6.7.2 Build ID: e183d5b - v4.0.6.2 Build ID: 2e2573268451a50806fcd60ae2d9fe01dd0ce24 - v4.1.3.2 Build ID: 70feb7d99726f064edab4605a8ab840c50ec57a Screenshots from each are shown. Obviously the earlier version are not going to render all fonts well as many were not included until a later version (thus there is some font substitution). Even so the results are encouraging. Here is a summary: v3.3.0.4 - Gentium Basic, Gentium Book Basic OK v3.4.6.2 - no change v3.5.7.2 - Linux Libertine G OK, Linux Biolinum G partially OK (tilde and macron display incorrectly) v3.6.7.2 - Liberation Sans, Liberation Serif both have regression in tilde v4.0.6.2 - DejaVu Sans, DejaVu Serif, Arial, Times New Roman OK, Source Code Pro error in general display v4.1.3.2 - Liberation Sans, Liberation Serif, Open Sans, PT Serif, Source Code Pro OK The only outstanding rendering issue as at v4.1.3.2 is with Linux Biolinum G for the tilde and macron characters indicated. Obviously this is not a comprehensive combining character test and so other (untested) fonts and character combinations may render differently.
Laszlo Nemeth added to the CC list for this bug as Linux Biolinum G is one of his fonts, so he may be able to indicate if I have made a mistake somewhere in my testing or if this is a known problem with the font or LO.
In v4.2.5.2 for Windows it looks almost completely corrected except for: ÃĀ in the Linux Biolinum G font.
Created attachment 105825 [details] Screenshot showing rendering under LOv4304 (same for LOv4162, LOv4263, and LOv4400 2014-09-05). I can confirm comment 9 that in the Linux Biolinum G font these characters: - Combining tilde (U+0303) - Combining macron (U+0304) ... are still not rendered correctly. Tested under GNU/Linux using: - v4.1.6.2 Build ID: 40ff705089295be5be0aae9b15123f687c05b0a - v4.2.6.3 Build ID: 3fd416d4c6db7d3204c17ce57a1d70f6e531ee21 - v4.3.0.4 Build ID: 62ad5818884a2fc2e5780dd45466868d41009ec0 - v4.4.0.0.alpha0+ Build ID: 652b807658a54cd2ccd04ebc6900d2cf1ce85015 TinderBox: Linux-rpm_deb-x86_64@46-TDF, Branch:master, Time: 2014-09-05_01:32:46 All versions render the same as shown in the attached screenshot.
** 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.1 or preferably 5.0.2.2 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 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 your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-10-14
Still repro. Note: in character map program, you can search (ctrl-f) for U+0303 and U+0304 to quickly locate them. Win 7 Pro 64-bit Version: 5.2.0.0.alpha0+ Build ID: 9784ff3d878eaa21491fbd779e57d7d4710f5449 CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; TinderBox: Win-x86@39, Branch:master, Time: 2016-01-30_01:31:57 Locale: fi-FI (fi_FI)
There is nothing for us to fix here, all are font bugs.