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

Problems with Umlauts #96

Open
gstangl opened this issue Apr 9, 2024 · 6 comments
Open

Problems with Umlauts #96

gstangl opened this issue Apr 9, 2024 · 6 comments

Comments

@gstangl
Copy link

gstangl commented Apr 9, 2024

I have problems with German umlauts in Google Docs. It looks fine when I export it to PDF. When I print it, it looks all wrong, though. The umlauts are all displaced.

I attached a screenshot. On the left is the original PDF, on the right is a scan of the printout.
PDF vs Scan

@kenmcd
Copy link

kenmcd commented Apr 9, 2024

My guess is you are using the TTF fonts.
On my phone at the moment so I cannot check the fonts...but
Some printer drivers cannot handle nested components - and the components (the umlauts here) end up in odd places.
OTF fonts cannot use components so they do not have this issue.
So the work-around is to use the OTF fonts instead.

@Jolg42
Copy link

Jolg42 commented Apr 13, 2024

I didn't test this yet, but maybe it's worth trying:

@gstangl A colleague reported a similar visual issue, but the rendering is of a webpage in a browser, about the backtick character.
See image (9)
I told them to try using the latest version of the font here https://github.com/jpt/barlow/tree/1.5/fonts

@jpt
Copy link
Owner

jpt commented Apr 20, 2024

https://github.com/jpt/barlow/archive/refs/heads/1.5.zip

I have pushed an update that should fix this, can you try the fonts in archive above?

@jpt jpt mentioned this issue Apr 24, 2024
@Jolg42
Copy link

Jolg42 commented Apr 25, 2024

The problem I mentioned in my previous comment with the back-ticks is fixed in that new version. Thanks a lot 🙌🏼 💚

@gstangl
Copy link
Author

gstangl commented Feb 22, 2025

We are using Barlow mainly via Google Docs. The issue is still there unfortunately.

@jpt
Copy link
Owner

jpt commented Feb 22, 2025

We are using Barlow mainly via Google Docs. The issue is still there unfortunately.

I appreciate your frustration. I could merge in 1.5 here, but it is unclear to me if Google would accept it in their own repos as they have a new requirement for non-interactive builds (using fontmake, rather than the Glyphs app) for their font collection, which is reasonable. But, this is dependent on glyphsLib, their tool for such non interactive builds, actually working, which may not be the case for Barlow (some of my simpler fonts have been unsupported by glyphsLib for nearly 4 years). So, I will have a look, and maybe we will get lucky about Barlow making it though the gauntlet swiftly, but it’s also possible I will need to work with Google to get all the features it needs into glyphsLib first. I will give you an update when I find out. I haven’t had much time for volunteer work lately, but I expect to have some time at the end of April if not sooner. At the very least I can get 1.5 into the master branch here soon. Apologies for the delay.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants