Created attachment 106217 [details]
ODT file demonstrating the problem
Steps to reproduce:
1. ....Install this font: smartfonts.net/ttf/samagana.ttf
2. ....Open the attached file in Linux and Windows systems
3. ....Observe that the letters are spread out when viewed inside Windows
4. ....Copy the text in the file and put it inside Windows Notepad and view it using 'samagana' font above. You will see the text perfectly formed.
Current behavior: Font rendering is improper inside Windows
Expected behavior: The text should show correctly spaced as in my Puppy Linux and all browsers including smart phones. This is a problem with rendering of 'liga' feature of OpenFont. According to the standard, 'liga' is implemented by default. Word developer group at MS misreads this. (MS wrote the OpenType standard identical to OpenFont).
Please read this:
I have been developing fonts since 2004. The above font is an OpenFont font made for Romanized Singhala. It is a template font, not typographically nice looking. It uses the 'liga' feature of OpenFont to the extreme with thousands of ligatures (as opposed to 5 in Calibri). It works everywhere else except in Windows.
Romanized Indic is intuitive to type and as easy as typing English. Orthographic smart fonts like 'samagana' above will eliminate digital gap in South Asia. Proper support of OpenFont affect future of Billion people.
OpenFont is implemented two ways. Some programs use the rendering engine provided by the OS. Others use rendering devices independent of the OS. Right now, recent versions of all major browsers show OpenFont fonts correctly at least for Latin-1 based fonts. The last one is Internet Explorer. Please see this web site where complex Singhala (an Indic language) is shown perfectly:
I suspect that LibreOffice depends on OS supplied rendering engine. The case is the same with AbiWord. AbiWord showed ligatures perfectly until some update to Windows ruined it. The first release of Windows 8 had MS Word showing ligatures perfectly. Then a Windows update reversed it.
I hope the above information helps developers locate the problem.
Operating System: Windows (other)
Version: 22.214.171.124 release
Created attachment 106234 [details]
Screenshot under Windows 8.1
Created attachment 106238 [details]
Screenshot under Ubuntu 14.04
Thank you Jayme.
My Puppy Linux (branched[?]from Slackware) and your Ubuntu makes the ligatures perfectly. So, my suspicion that increasingly applications depend on the OS to render fonts looks to be true. Gnumeric (a gnome project) has this identical problem.
Windows Notepad uses Uniscribe (USP10.DLL). OpenType was gradually implemented inside Uniscribe and tested on Notepad. It could be that Writer is using Uniscribe but makes wrong calls when justifying lines. Notice that the ligatures actually get constructed but spacing is incorrect. Internet Explorer 8 had this same problem and Google Chrome too to a lesser degree.
Samagana font has 2500 ligatures and constructs ligatures up to 3 levels (iterates constructing ligatures upon ligatures) needed for Sanskrit orthography, but has no problem inside Windows Notepad, all browsers, Macintosh and smart phones.
I have tried since 2004 to get MS to fix Word. In 2004 they said they won't do it as a business decision. Next two fonts I want to make are for Devanagari and Fraktur. We should preserve human history when we can. OpenFont is the perfect vehicle to liberate Indian languages and cultures along with them.
Do normal Sinhala fonts render OK on your system?
This is by far nearest to normal Singhala. Some more ligatures are needed. (Modern Singhala is called Mishra Singhala. It mixes in Sanskrit into Singhala).
It is romanized Singhala, somewhat like Icelandic, displayed using a smart font containing substitution tables that implement Singhala and Sanskrit orthography. This is what comes closest to the way Singhala has been written for a long time. I use Rev. Fr. Theodore G. Perera's grammar book in constructing the orthography. (https://openlibrary.org/books/OL21020M/Sim%CC%A3hala_bha%CC%84s%CC%A3a%CC%84va). That book has been out of print since 1950s. Most Buddhist temples have it.
There is a deviation between written Singhala and printed Singhala because of limitations in the printing industry and the typewriter. Unicode Sinhala completely ignores the grammar and is damaging common understanding of the writing tradition. (The writing system is part of the grammar).
I will repeat the question. Are fonts like Iskoola Pota display fine on your system?
(In reply to Urmas from comment #6)
> I will repeat the question. Are fonts like Iskoola Pota display fine on your
Thank you. Iskoola Pota shows well on Windows machines. It is double-byte Sinhala. Each OS has its own font that shows Unicode Sinhala. It is sort of the default font like we see Times Roman as the default font. Unfortunately, Unicode Sinhala fonts behave differently in each OS, and the standard itself is flawed and ignores grammar. (Yes, Singhala grammar starts with writing rules).
The only thing common between Iskoola Pota and my font Aruna.ttf:
is that they both show the Singhala script.
What I did was to first romanize Singhala (I spell it with a 'g'. Just bear with me. It is a habit). Romanized Singhala looks similar to a European language. That makes it acceptable in programs that were perfected over decades before Unicode. My next step was to make an Open Type font following Singhala /Sanskrit grammar. Libre Office is the best Office package out there very useful for those who are migrating to Linux. Sri Lanka is trying that and I promote it. The Science ministry there thinks favorably of my solution because of unsurmountable problems with Unicode Sinhala.
In any case, your version for Windows cannot show the text properly as you saw. It is not a problem with Singhala script or rendering rules that Unicode specifies for Unicode Singhala fonts. My font follows Open Type / Open Font rules and simply makes Singhala ligatures, about 2500 (!) of them, No browser has the problem your program displays. However, it is exactly the way MS Word behaves. IMHO, Microsoft is not the best example for rendering LATIN script. Mozilla (that used Apple as their example) is a better source for advice.
Chrome went through this stage too. You are using an older rendering engine or something like that. This is not specific to my Singhala font. I think there must be other fonts that display this problem.
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.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)
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!
This isn’t fixed yet, but one can disable ligatures manually now.
Sorry, wrong bug. This needs to be checked against master.
The font is hack font (assigning glyphs to unrelated Unicode characters). We do not support this, but the issue is fixed nevertheless.
This issue is NOT resolved.
Please see comments 1 and 2 by Adolfo Jayme to understand the bug.
I installed the latest version of LibreOffice available (126.96.36.199) after uninstalling previous two versions I had and even having cleared the system registry in Windows 10.
The problem exists exactly the same way. I used the '.odt' file originally submitted here for testing. Changed the solitary Greek Phi to capital L.
The situation in short is that all browsers, all Linux systems, all Macintosh systems, Windows Notepad, iPhone and Android phones plus Microsoft Excel and most importantly, Microsoft Word later than 2013 show the text perfectly.
LibreOffice is the odd girl standing out in the cold.
I see the comments went meandering into deeper and deeper abyss, which is understandable because it flowed for 3 years. That caused someone to name my request OBSOLETE.
The original font we used is 'samagana'. After some updates, we are now using the 'aruNa' font available here: http://smartfonts.net/ttf/aruna.ttf
Please use that font to test. (remember to change the Greek Phi into a capital L)
May I most humbly mention that you are not properly implementing ligatures either. This could be the root cause of the problem. Standard Ligatures are in the province of the font, not the application using the font. (MS Office Group also misunderstands it. English that MS wrote is clear in the standard).
The simple test is to use Calibri to show the word 'difficult' in a very large size inside Write and Notepad. the f+f+i ligature does not bind inside Write. This means that the fundamentals of OT standard are not understood as it applies to the SIMPLE SCRIPT used by Western European languages. 'aruNa', believe or not, is also a 'funny' rendering of the SIMPLE SCRIPT. The underlying code set is NOT complex Indic. Just look at the text in the ODT file to understand it. It is ROMANIZED SINHALA.
This is a rescue effort, an eminently successful one, for all South Asians. So, please let's give them LibreOffice overcoming the massive misunderstanding of Indic by Unicode so that they stop stealing Microsoft Windows by habit.
(In reply to JC Ahangama from comment #13)
> This issue is NOT resolved.
The issue is fixed in the next version of LibreOffice, 5.3, and I verified it. Please ask before re-opening.
Thank you most profusely, Khaled. May I honor you with highly Sanskritized Sinhala that you are a prophet of godly wisdom (try Monier-Williams Sanskrit dictionary for aizvaryavat and ISva. Use the aruNa font to read it in the Singhala script)
khaaled aizvaryyavaþ iixvarayeki!
It was a 5-year task to hack Singhala into a Latin font and redraw 2500 hidden ligatures in it. The people say it looks like real Sinhala though not certified by Europeans. Another miracle!