Open mia-entropy opened 1 month ago
When exporting from the gs2 file on my Windows computer the ligatures work in LibreOffice. However the OTF file exported on Linux also don't have working ligatures when copied on Windows. It thus seem to be an issue when exporting to OTF on Linux (or more specific case) specifically.
Edit: I copied the font exported on my Windows computer over on my Linux one and the ligatures works too. So it's definitly the export process that have an issue.
Hello! This seems like a very interesting bug. I do not have access to a Linux machine for testing. I'm wondering if you can help me out - can you send me the two .otf files, the one exported from windows and the one exported from linux? I can open them with some advanced font tools to see if there are any differences, or if I can easily reverse-engineer / understand why they are being exported differently. You can post them here, or you could email them to mail@glyphrstudio.com
Might also help to know what browser you are using on windows / linux to do the exporting.
Thanks for the bug report!
Describe the bug & what the expected behavior should be:
I'm working on my conlang's script font which is a "reverse abugida" (central vowel on which consonants attaches). In the editor "live preview" the ligatures works perfectly, but when exported to OTF they don't work in any software (tested in GIMP, LibreOffice, in HTML with CSS; all on Linux). Ligatures are used to offset the consonants to follow the script structure.
My font eberban_glyphr.gs2
Steps to reproduce the bug:
Other notes & screenshots:
String
In LibreOffice it renders like so:
![image](https://github.com/user-attachments/assets/ed300f61-7d9a-419e-93c4-cef4fe57d518)
plla
is rendered like so in the live preview: