Tests of some "difficult" words in Jarai [jra]

[livingfield]

Line 2, 3, 4: on macOS Sonoma in both LibreOffice 7.6 and Microsoft Word, The register shifter 17c9 is rendered too far to the right on some words.

Line 5 and 6: In Microsoft Word, The register shifter 17ca is missing completely when it follows two coeng consonants.
Busra Test B.docx
Busra Test B.odt

[mhosken]

Please submit pdfs or images and plain text, and perhaps images/pdfs of what you are wanting it to look like. Single words are sufficient. TIA.

…

On Thu, 21 Dec 2023, 09:01 livingfield, ***@***.***> wrote: Line 2, 3, 4: on macOS Sonoma in both LibreOffice 7.6 and Microsoft Word, The register shifter 17c9 is rendered too far to the right on some words. Line 5 and 6: In Microsoft Word, The register shifter 17ca is missing completely when it follows two coeng consonants. Busra Test B.docx <https://github.com/silnrsi/font-busra/files/13739333/Busra.Test.B.docx> Busra Test B.odt <https://github.com/silnrsi/font-busra/files/13739334/Busra.Test.B.odt> — Reply to this email directly, view it on GitHub <#4>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABLMO3OPEOEXQUF5ITMKW6TYKP3FZAVCNFSM6AAAAABA6B3XBKVHI2DSMVQWIX3LMV43ASLTON2WKOZSGA2TEMBQGE3TANQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[livingfield]

Busra Test B LibreOffice.pdf
Busra Test B MS Word.pdf

[mhosken]

fixed. I hope.

[livingfield]

No. I don't think any of these are fixed.

Here are a few problematic words in Microsoft Word 365 on Windows 11 Arm:

Most of the problems also occur in Libreoffice on Windows.

Busra.Dec2024WinLibreOffice.pdf
Busra.Dec2024inWinWord.pdf
Busra.Dec2024inWinWord.docx
Busra.Dec2024LibreOffice.odt

[mhosken]

Sorry. I think you jumped the gun in testing. The bug is fixed and checked in but not released yet. If you are testing a pre-release version, then that is different. You should see the improvement in the next release. Btw there is no need to give lots of contexts in which a font fails unless the results differ between contexts.

[mhosken]

Regarding 5 & 6 in the Word case. I am assuming that if you printed that text, the -u (downshifted shifter) would reappear and that Word is clipping the shown text on the screen. There are problems with increasing that box for such a complex case in that it will increase the default linespacing which you probably don't want.

[livingfield]

Regarding 5 & 6 in the Word case. I am assuming that if you printed that text, the -u (downshifted shifter) would reappear and that Word is clipping the shown text on the screen.

Indeed, it prints OK, and the PDF is OK. The problem is only on-screen.

[jvgaultney]

We may be able to improve 5 & 6 on screen by increasing usWinDescent. That will not affect line spacing except in really old Win apps, but would hopefully eliminate the clipping. I've now increased it slightly to include the full form of the -u even when it's the third glyph attached below. I don't know if that will help Word or not.