Conversation

Notices

1. Foone🏳️‍⚧️ (foone@digipres.club)'s status on Wednesday, 09-Oct-2024 04:35:21 JST Foone🏳️‍⚧️

   Libreoffice what the fuck is this kerning?
   I didn't type "th at", that's "that"

   • Rhialto (rhialto@mastodon.sdf.org)'s status on Wednesday, 09-Oct-2024 05:42:52 JST Rhialto

     in reply to

     @foone maybe it is emulating (the kerning of) MSWord.

   • Foone🏳️‍⚧️ (foone@digipres.club)'s status on Wednesday, 09-Oct-2024 05:42:52 JST Foone🏳️‍⚧️

     in reply to

     • Rhialto

     @rhialto bad kerning for bad kerning compatibility

   • fontenot (fontenot@mastodon.social)'s status on Wednesday, 09-Oct-2024 06:10:42 JST fontenot

     in reply to

     @foone Can I ask what font, OS, and LibreOffice version this is? I did a lot of research on this in the past and contributed to bug reports at the Document Foundation about the issue.

     This looks like a failure to use subpixel positioning on the glyphs, so the position of the 'a' glyph is rounded to the nearest glyph and looks very weird. LibreOffice switched to using subpixel positioning for all rendering with version 7.4, but I could imagine this happening with weird font / hinting settings.

   • Foone🏳️‍⚧️ (foone@digipres.club)'s status on Wednesday, 09-Oct-2024 06:10:42 JST Foone🏳️‍⚧️

     in reply to

     • fontenot

     @fontenot Sure!
     It's Liberation Serif, Windows 10, and LibreOffice 6.3.3.2. (I haven't updated it in a while so that's probably way out of date)

   • Foone🏳️‍⚧️ (foone@digipres.club)'s status on Wednesday, 09-Oct-2024 06:34:27 JST Foone🏳️‍⚧️

     in reply to

     Same font, Same OS, just updated my Libreoffice.

   • fontenot (fontenot@mastodon.social)'s status on Wednesday, 09-Oct-2024 06:35:17 JST fontenot

     in reply to

     @foone Oh cool, thanks! Yes I think if you try out 7.4 you'll find the problem goes away. It looks like just the rounded glyph position issue, I have a whole blog post about it: https://adamfontenot.com/post/libreoffice_7_4_has_a_new_approach_to_text_rendering

     I did guess it was Windows based on the weird (IMO) hinting, but I think that's unrelated here.

   • Foone🏳️‍⚧️ (foone@digipres.club)'s status on Wednesday, 09-Oct-2024 06:35:17 JST Foone🏳️‍⚧️

     in reply to

     • fontenot

     @fontenot yep, that fixed it! Thanks!

     https://digipres.club/@foone/113273928323006241

   • Foone🏳️‍⚧️ (foone@digipres.club)'s status on Wednesday, 09-Oct-2024 07:43:34 JST Foone🏳️‍⚧️

     in reply to

     • F4GRX Sébastien

     @f4grx no, it did that. I changed nothing, just hit update

   • F4GRX Sébastien (f4grx@chaos.social)'s status on Wednesday, 09-Oct-2024 07:43:35 JST F4GRX Sébastien

     in reply to

     @foone and you removed/changed subpixel antialiasing.

   • fontenot (fontenot@mastodon.social)'s status on Wednesday, 09-Oct-2024 09:45:52 JST fontenot

     in reply to

     @foone Maybe you also changed your zoom level or font size? The revised text is quite a bit larger (when you reverse the upscaling on the original image).

     I'm curious whether, at the same size, the shape of the 'c' glyph is as cursed as it is in the before image. I can't think of any LibreOffice bug that might cause that, although they've done some strange things on Windows in the past IIRC.

   • Foone🏳️‍⚧️ (foone@digipres.club)'s status on Wednesday, 09-Oct-2024 09:45:52 JST Foone🏳️‍⚧️

     in reply to

     • fontenot

     @fontenot I didn't fiddle with the zoom in LibreOffice, I just forgot to rescale the screenshot when I posted it to mastodon