Lexend Deca not printing correctly - lowercase e, w, y, h, n and uppercase M, W, Y.

[jnc0614]

I created a project using the Lexend Deca Font on Google Docs and had it printed through Kindle Direct Publishing (a print-on-demand service). When I received the printed material, the Lexend font didn't print correctly. I contacted Kindle Direct Publishing and they told me that the font through Google Docs is corrupt. If the font is printed in a large font size (about 50 and above) the lower case "e" and capital M, capital W, both lower and uppercase Y do not print correctly. Is there anything that can be done to fix this issue so I can print a document from Google Docs with Lexend Deca through a printing service? Incidentally, the document prints without any problem on my home printer.

I've attached some photos so you can see the problem when the font is printed through Kindle Direct Publishing. I'll also attach the information from the KDP printing department.

[kenmcd]

It appears the overlaps were not removed from the static fonts.
Some applications/printers will have a problem with this.
I just checked and the fonts currently available for download from Google Fonts still have this problem.
And these are the fonts you are using on Google Docs.

I also just checked the repository and the static fonts there look OK.
Here: https://github.com/googlefonts/lexend
You can download the ZIP of the repository here:
https://github.com/googlefonts/lexend/archive/refs/heads/main.zip
That will get you the static fonts without any overlaps.

Until the fonts are updated on Google fonts, this is your only option.
Install the static fonts from the repository locally.
Download your document so you can edit it locally.
Then export your PDF with these working fonts.

[jnc0614]

kenmcd, thank you - this is very helpful information.

When you suggest "download your document so you can edit it locally", does that mean I can use Google Docs offline to edit it locally, or will I need to use another platform like Word, Pages or InDesign to accomplish this?

[kenmcd]

When you suggest "download your document so you can edit it locally", does that mean I can use Google Docs offline to edit it locally, or will I need to use another platform like Word, Pages or InDesign to accomplish this?

Yes.
I am not very familiar with Google Docs, but it is my understanding that you can download your documents in editable formats such as Word .docx, or LibreOffice .odt, etc.
Then you can edit the doc in Word or LibreOffice, and then export it to PDF locally which will use the better fonts that you installed locally.

[jnc0614]

Can anyone give an idea of when this issue might be fixed for the Lexend Deca font in Google Docs Fonts?
Depending on what the approximate timeline is, it would help me choose from a few options for completing my project.
Thank you!

[RosaWagner]

Google Fonts is keeping overlapping contours for static fonts instantiated from a variable fonts, so it won't be fixed.

What you are experiencing is a PostScript printer that is not handling this kind of outlines (that are proper to true type fonts). If you plan to print with this kind of machine (which happens quite often with external printing services), it is recommended to use a version with merged contours that you can find here: https://github.com/googlefonts/lexend/tree/main/fonts/deca/ttf. Install it on you machine and use it as described in the previous comment.

You will have this problem with PS Printers with every fonts on GF that is a variable font or that was made from a variable font. If you want to find the version with merged contours, click on the link at the end of the font's description.

[jnc0614]

Thanks very much for this information - it is really helpful.

…

On Thu, Dec 2, 2021 at 3:07 AM Rosalie Wagner ***@***.***> wrote: Google Fonts is keeping overlapping contours for static fonts instantiated from a variable fonts, so it won't be fixed. What you are experiencing is a PostScript printer that is not handling this kind of outlines (that are proper to true type fonts). If you plan to print with this kind of machine (which happens quite often with external printing services), it is recommended to use a version with merged contours that you can find here: https://github.com/googlefonts/lexend/tree/main/fonts/deca/ttf. Install it on you machine and use it as described in the previous comment. You will have this problem with PS Printers with every fonts on GF that is a variable font or that was made from a variable font. If you want to find the version with merged contours, click on the link at the end of the font's description. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#4076 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHBXGXVQHHQINNF3REPMB5TUO5AO7ANCNFSM5IIOEKIA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.