Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Glyph rendering problems/improvements #15

Open
milotype opened this issue Feb 19, 2020 · 6 comments
Open

Glyph rendering problems/improvements #15

milotype opened this issue Feb 19, 2020 · 6 comments
Labels
enhancement New feature or request

Comments

@milotype
Copy link
Contributor

milotype commented Feb 19, 2020

Hi,
titles and subtitles have font encoding issues across several languages (croatian, hungarian, russian), scripts (latin extended, cyrrillic) and document formats. Diacritics don't render correctly in all documents. Sometimes they are bolder, sometimes they are lighter and somtimes they render with a different font.
Check attachements below.

In the case of croatian:

Croatian

1-CroatianTitle
2-CroatianText

Hungarian

3-HungarianPDFandWEB
4-HungarianTextPDF

Russian

5-RussianTitleWEB

@milotype
Copy link
Contributor Author

The png-images and the PDF files actually also have problems with diacritics …

@amotl
Copy link
Contributor

amotl commented Jan 5, 2023

Dear Milo,

thank you for outlining those quirks, mostly related to cyrillic characters. We appreciate it very much.

We worked on improving the rendering a while ago already, and think it got better. For your reference, those are links to the corresponding spots you've mentioned.

In order to be able to eventually close this issue, we will be happy about your feedback on this topic.

With kind regards, and a happy new year,
Andreas.

@milotype
Copy link
Contributor Author

milotype commented Jan 8, 2023

Overall the .png files look better for latin, cyrillic and greek, but they still don't seem to use one and the same font. For other scripts I'm not an expert.

I hope that my following observations will help:

Differenes in the Croatian versions:

  • Croatian .png file
    croatian png file

  • Croatian single page file
    croatian single page

German double s:

The german "double s" dosn't look good, neither in the .png file, nor in the "Single page" version.

  • German .png file
    german png file

  • German single page file
    german single page

Issues in other scripts:

There are still issues in "Single page" versions in greek, cyrillic, hebrew:

  • they use different fonts then in the .png file (serif fonts)

Proposed solution:

Maybe you could consider to generally use some of the following fonts, because neither the font FuturaMaxiBold nor Futura have have extended character sets:

Side notes:

  • I'm aware that this is a complex issue. When setting the font-family in CSS, maybe it might help to define some OS-specific fonts in the list and to make sure to set sans-serif at the end.

  • Also, if possible, check that the generation of .png files and "Single page" files are identical, in order to generate identical outputs.

My environment:

Mac OSX 10.11.6
Firefox 78.15.0

@amotl
Copy link
Contributor

amotl commented Jan 8, 2023

Dear Milo,

thanks a stack for taking the time to respond, and for your valuable suggestions. I will try to adjust the fonts, according to your recommendations, within the next iteration.

German

The German ẞ does really look bad. Thanks for spotting!

Croatian

On the Croatian facebook poster, I would like to ask about the spot where you still found the misrendered ČITAŠ, because I can't spot it within the resources referenced below. Please note that some resources, like the mosaic pictures, have not been refreshed yet. Can you reference specific URLs to problematic resources you are observing?

image

Others

There are still issues in "Single page" versions in greek, cyrillic, hebrew: They use different fonts then in the .png file (serif fonts).

I agree the Hebrew font has serifs on the web view, thank you. However, I can't spot much of a difference on e.g. Greek or Ukrainian between the web view and the rendered artefact. If it's just my ignorance, please apologize ;]. Can you point out specific differences, including corresponding URLs?

Hebrew

Greek

Ukrainian

Further notes

For your reference, my workstation is on macOS 10.15.7 and Firefox 108.0.2, and the production rendering is taking place on Debian GNU/Linux 11 (bullseye), using DeckTape/Puppeteer, effectively wrapping a Chromium 99.0.4844.0 instance.

Please note that artefacts for specific languages, currently cs,hu,hr,pl,ru,tr,zh, are rendered on macOS instead of Linux 1, using the same PosterKit machinery. It yields better font quality, probably because better system fonts are available there. This is happening at the PosterKit Makefile.

Your contributions and suggestions on this topic are very much appreciated. Apologies that I am so slow on implementing your recommendations.

With kind regards,
Andreas.

Footnotes

  1. It might be the reason for some deviances your are observing. However, even if the rendered artefacts have higher priority, this does not mean we should leave the web-based versions behind, so your reports are very much welcome.

@amotl amotl changed the title Font encoding problems Glyph rendering problems/improvements Jan 8, 2023
@amotl amotl added the enhancement New feature or request label Jan 8, 2023
@milotype
Copy link
Contributor Author

milotype commented Jan 8, 2023

@amotl
I've just checked the site with my iPhone 6, version 12.5.6.
Everything looks much better there in most latin, greek, cyrillic and hebrew scripts. :-)
So maybe/probably my old Firefox and MacOS cause the problems ... :-(

1. Still there seem to be issues in German:

  • German .png file
    german png

  • German "Single page" file
    german single page

2. Still there seem to be issues in Czech outputs (different fonts used within the .png file):

czech

@amotl
Copy link
Contributor

amotl commented Jan 9, 2023

Thank you again!

  • I will try to address the ẞ issue for German and the difference in font selection for Czech on the next iteration.
  • The rendering issue of the capital S fortunately did not make it to the PDF, right? So, it has lower priority for me, but thanks for spotting! I think it may be a glitch with the auto-fitting library in webview mode.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants