search

notofonts / hebrew

Noto Hebrew
SIL Open Font License 1.1
2 stars 1 forks source link

Noto Hebrew Fonts are not displayed #7

Closed GPodkolzin closed 1 year ago

GPodkolzin commented 5 years ago

Title

Noto Hebrew Fonts are not displayed in Word

Font

NotoSerifHebrew-Regular.ttf

NotoSerifHebrew-Regular.zip

Where the font came from, and when

Site: https://noto-website-2.storage.googleapis.com/pkgs/NotoSansHebrew-hinted.zip Date: 2019-04-10

Font Version

Version 2.000;GOOG;notosource:20170915:90ef993387c0; ttfautohint (v1.7)

Application name and version

Word 2007

Issue

  1. Choose a Noto Hebrew font in Word menu
  2. The text is not displayed in that font and remains in the default font (e.g. Arial)
  3. The font must change to the Noto Hebrew font but it does not
  4. The font is displayed in Word's Symbol dialogue Noto Serif Hebrew Issue
  5. Word behaves as if Noto Serif Hebrew font did not contain Hebrew characters. Here is a screenshot of what it looks like when I've chosen Noto Serif Hebrew. Noto Serif Hebrew Issue 2
YisroelTech commented 4 years ago

The same issue happening with the later version of Word (Word 2019), as well as Microsoft PowerPoint.

The funny thing is that it actually works without issue in Microsoft Excel and Microsft Publisher.

Maybe related (but certainly not the same issue, because that one started in Word 2013 and was fixed with Windows 10 Version 1703): https://word.uservoice.com/forums/304924-word-for-windows-desktop-application/suggestions/15604398-add-backward-compatibility-for-unicode-fonts-with

kosmynkab commented 3 years ago

Not sure what could be the source of the issue - tested all three (Rashi, Serif and Sans) in version 16.50 on Mac OS 11.3.1 and they all work with the files I generated. I was not able to use any non-precomposed characters though - that might be problem with Word itself, as other Hebrew fonts behave similarly.

To be tested again after pushing files.

simoncozens commented 1 year ago

The problem may well be that the hinted/unhinted fonts don't contain "enough" characters for Office to support. Please try with the full builds instead.