yolio2003 / noto Goto Github PK

Google not font is really awesome. Please add the iconic font there too.

Thanks

A hindi user reports "lack of support for jihvAmUlIya and upadmAnIya" - see 
attached screenshot

What steps will reproduce the problem?
1.Click on Mongolia - no Mongolian script listed
2.Cick on PR China - Mongolian script listed

What is the expected output? What do you see instead?
Mongolian script is used in Mongolian republic


What version of the product are you using? On what operating system?
Web version.

Please provide any additional information below.
Please add Mongolian Script to the Mongolian script list.

Japanese sample text (via translation of "Universal Declaration of Human 
Rights" Article 1) has a tiny typo (or mistranslation).

fixed file (on my personal clone) : 
https://code.google.com/r/x2357handle-notofonts/source/browse/sample_texts/ja-Jp
an.txt

diff with latest : 
https://code.google.com/r/x2357handle-notofonts/source/diff?spec=svnd75a8ec2fce5
21c6d23f4f3c27c8df310ffc2187&r=d75a8ec2fce521c6d23f4f3c27c8df310ffc2187&format=s
ide&path=/sample_texts/ja-Jpan.txt

c.f.

  Translation by OHCHR :
  http://www.ohchr.org/EN/UDHR/Pages/Language.aspx?LangID=jpn
  Translation by Ministry of Foreign Affairs of Japan :
  http://www.mofa.go.jp/mofaj/gaiko/udhr/1b_001.html

Lacking letter "と" is almost no problem as Japanese, although above 
translation examples has such text, so I added.

I noticed this typo by noto fonts preview page,
  http://www.google.com/get/noto/#/family/noto-sans-jpan
I think this preview images also needs to be fixed.

The Regional Indicator S (U+1F1F8) is higher than other letters of the alphabet 
in the Color Emoji font.

When I install unhinted Noto Sans Khmer and NotoSansKhmerUI on a mac, it shows 
up in the Fontbook listing as NotoSans instead of Noto Sans Khmer (UI). 

This needs to be fixed.

What steps will reproduce the problem?
1. Install Noto Sans Cham at 
https://code.google.com/p/noto/source/browse/trunk/fonts/individual/unhinted/Not
oSansCham-Regular.ttf
2. Try to view the font in Windows' font setting at Control Panel > Fonts
3. Try to use the font in various programs


What is the expected output? What do you see instead?
I expect Noto Sans Cham is seen and can be used in all programs like other Noto 
Sans fonts. Instead, this font is not shown in the font list. Some programs can 
use the font while some cannot.

Examples of affected programs:
Windows font setting, Windows Notepad, Firefox (Nightly), Adobe Photoshop 
extended CS6 64bit.

Examples of unaffected programs:
Internet Explorer 11, Google Chrome 35, BabelMap 7.0.0.0, LibreOffice 4.2.4.2.


What version of the product are you using? On what operating system?
Noto Sans Cham r253 and r237.
Windows 8.1 64bit with update. All updates installed. English interface.


Please provide any additional information below.
Explantion of attached screenshot Noto Sans Cham.PNG-
Top right corner: Noto Sans Cham is installed on the system
Lower right corner: The font does not appear in Windows font list
Top left corner: IE shows the font while Photoshop does not
Lower right corner: additional font settings in Windows

Explanation of attached screenshot Noto Sans Cham_2.PNG-
Side by side comparison of the font usage in Firefox(left) and Chrome(right) 
with the same CSS setting.
Code2000, another font I have with Cham block support, is uninstalled before 
testing so Chrome is not showing other fonts.

It may be a FreeType bug, a chrome bug, or a font issue.

But I basically get a capital gamma when I display the character as 15px in 
Chrome at 100% zoom.

Behdad, since you probably have a setup similar to mine, would you take a quick 
look to see if you can reproduce?

Install the font from 
https://code.google.com/p/noto/source/browse/fonts/individual/unhinted/NotoSansS
ymbols-Regular.ttf

Here's the snippet for Chrome: data:text/html;charset=utf-8,<span 
style="font-size: 15px;">&#x1f1eb;</span>

Attaching a screenshot.

FreeType version 17.1.11
Chrome version 36.0.1985.103 beta

While the dot accents for characters such as U+0121 and U+022F seem to be 
aligned with the dot of the 'i' character in sans, in serif they are not. Text 
where characters with a dot accent are next to an i, such as in the Maltese 
word "niġi", looks bad.

The font has non-existing Malayalam glyphs(Glyphs with dot under consonants) or 
rarely used glyphs(Glyphs with U+0D62 MALAYALAM VOWEL SIGN VOCALIC L)

http://thottingal.in/blog/2014/03/22/spurious-glyphs-in-notosansmalayalam/

Akan is by far the largest ethno-linguistic grouping in Ghana and is also found 
in Ivory Coast.
The akan alphabet has the following letters that are not in noto font (and 
akan, fantse, twi do not appear in the supported languages). 

Missing letters:
1. One that looks like a '3' rotated 180 degrees (so a variation of the letter 
'e').
2. One that looks like a 'c' rotated 180 degrees (so a variation of the letter 
'o' but with an open end).

What steps will reproduce the problem?
1. ഉകാരം ഇൻഡിസൈനിൽ ശരിയായി 
കാണിക്കുന്നില്ല.
2. മറ്റു മലയാളം ഫോണ്ടുകൾക്ക് 
കുഴപ്പമില്ല. 
3.

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?


Please provide any additional information below.

Some Khmer fonts have ZWSP while others have ZWJ, ZWNJ. Still others have 
U+250C but most Khmer fonts do not U+250C (dotted circle). 

All fonts should have U+250C to represent a stand-alone combining mark. 

According to the following references, ZWJ, ZWNJ and ZWSP have to be present in 
Khmer fonts in addition to U+250C. 

http://www.microsoft.com/typography/otfntdev/khmerot/shaping.htm
http://goo.gl/RrNS7  (It's a SIL document in PDF)

It shows it as its final form when it should be in initial form.

The character is important for Urdu.

What steps will reproduce the problem?
1.Typing in Telugu make the baseline higher compared to English or hindi 
2.The same happens for kannada too
3.

What is the expected output? What do you see instead?
The base line of Telugu and kannada are supposed to be in line with English and 
hindi in order to use punctuations, but it appears to be higher. 


What version of the product are you using? On what operating system?
KitKat 4.4.2 on nexus 4 


Please provide any additional information below.
I happen to notice that there are regular/bold and regularUI/boldUI fonts and 
it's supposed to use the UI version for contacts and Lockscreen etc and the 
regular type for messaging and text display a cross the device, but what I 
found was it is using the UI variant everywhere. When I replaced the UI version 
with the normal version the Telugu text was being displayed on the same 
baseline as English in messages etc but the bottom part is being chopped off in 
Lockscreen or contacts etc. Please resolve this issue soon. 

1. ulUnicodeRange has bogus bits set. That is. the bits for uncovered Unicode 
ranges are set. 

2. Noto Serif Khmer Regular has usWeight set to 300 (light) instead of 400 
(regular/normal). 

reference : 

http://www.microsoft.com/typography/otspec/os2.htm#wtc

For those of us who want to hack on these fonts, can you add a "how to build" 
section in the documentation ?

What steps will reproduce the problem?
1. click on Portugal language dot 
2. you'll see Portuguese/Galician

What is the expected output? What do you see instead?

It should be Portuguese/Mirandese


Please provide any additional information below.

http://en.wikipedia.org/wiki/Mirandese_language

Noto font is great idea and currently has very good fonts but for Arabic, IMO 
Arabic Naskh and Kufic fonts (which no doubt are very good Arabic styles fonts) 
are not good enough font face for supporting all Arabic derivatives because 
they are somehow classical Arabic style fonts (but this font as far as I know 
is meant for supporting all scripts equally and neutrally somehow).

http://scripts.sil.org/Lateef and http://scripts.sil.org/Scheherazade perhaps 
are good "sample" of fonts for a neutral Arabic style sans font should be like.

Of-course this is not a bug but just a suggestion or enhancement.

The word "嘅" (U+5605) is composed by a phonetic component "既" with a 
radical "口" (the mouth), i.e. 嘅 = 口 + 既.

Similar words are 溉, 概 and 慨, where 溉 = 氵+ 既 , 概 = 木 + 既, and 
慨 = 忄 + 既.

There are at least 3 common writing forms for 既. They are represented as 
U+65E2(既), U+65E3(旣) and U+FA42(既) in Unicode. Among these three, the 
first one "既" is the most common. So it makes sense to see 溉 composed by 
氵 + 既, 概 composed by 木 + 既, and so on.

Historically "嘅" is a variant of "慨" (U+6168, 忄 + 既). Nowadays, "嘅" 
is widely used by the Cantonese community with a different meaning (it is used 
as a possessive or final particle).

Therefore, the writing form of "既" in "嘅" should be consistent with the 
other words with the same phonetic component.

However, in Nato CJK, it is composed by 口 + 旣 (U+65E3), which makes its 
form inconsistent with the other words.

Attached is the sample of two fonts: One is Nato, another is MHeiHK-Medium from 
Monotype Hong Kong.

Thank you!

What steps will reproduce the problem?
1. Install Noto Sans T Chinese fonts to ~/.fonts/
2. exec fc-list 'Noto Sans T Chinese' family style weight

What is the expected output? What do you see instead?

Noto Sans T Chinese DemiLight should have a different weight with Regular but

Noto Sans T Chinese,Noto Sans T Chinese Regular:style=Regular:weight=80
Noto Sans T Chinese,Noto Sans T Chinese Black:style=Black,Bold:weight=210
Noto Sans T Chinese,Noto Sans T Chinese Thin:style=Thin,Regular:weight=0
Noto Sans T Chinese,Noto Sans T Chinese 
DemiLight:style=DemiLight,Regular:weight=80
Noto Sans T Chinese,Noto Sans T Chinese Bold:style=Bold:weight=200
Noto Sans T Chinese,Noto Sans T Chinese Medium:style=Medium,Regular:weight=100
Noto Sans T Chinese,Noto Sans T Chinese Light:style=Light,Regular:weight=50

In fontconfig the font weight between Regular and Light should Book=75

Also using GtkFontChooser which uses Pango, there is no DemiLight or Book but 
two Medium.

According to the Unicode data file ScriptExtensions.txt, the following 10 
characters are used in Kaithi, but are not included in the font:

A830..A835 # [6] NORTH INDIC FRACTION ONE QUARTER..NORTH INDIC FRACTION THREE 
SIXTEENTHS
A836..A837 # [2] NORTH INDIC QUARTER MARK..NORTH INDIC PLACEHOLDER MARK
A838 # NORTH INDIC RUPEE MARK
A839 # NORTH INDIC QUANTITY MARK

The data file is at:
http://www.unicode.org/Public/UNIDATA/ScriptExtensions.txt

The same is said in the text of the Kaithi block:
"To indicate fractions and unit marks, Kaithi makes use of the numbers encoded 
in the Common Indic Number Forms block, U+A830..A839."
(Unicode 6.0, section 10.7, page 337 = Unicode 6.2, page 347)

It seems that the unhinted version of NotoSansKhmer-Bold.ttf, available at 
https://code.google.com/p/noto/source/browse/trunk/fonts/individual/unhinted/Not
oSansKhmer-Bold.ttf still has a couple of hints. The following five glyphs have 
hints:

uni17D1
uni17D2
uni17D3
uni17D9
uni17DA

Hello, I am font designer from Georgia, liked very much, that you made font for 
our region, especially for GEORGIA. I would like to work with you on next 
fonts. I have practice on working with big companies, as Dalton Maag, Paratype 
and The Northern Block. 

Thank you very much! And Good Luck!

[email protected] 

Several of the spacing modifier letters in Noto Sans Version 1.04 have zero 
width, whereas they should be normally spaced. (See Unicode range with 
descriptions at http://www.unicode.org/charts/PDF/U02B0.pdf.)

For example, IPA [miːn] displays incorrectly, since the triangular colon sign 
ː is crushed between the i and n.

正體(繁體)中文所用的寫法，個人認為大有問題。從圖例顯示
，寫法是向台灣敎育部靠攏。然而，使用正體中文的地區有��
�多，如香港、澳門和海外華僑等，其他地區並不以台灣寫法�
��尚。此外，即使在台灣，過去舊日的書刊出版，乃至今天的
報章，主要使用的也不是敎育部寫法。大家主要使用的，是��
�去傳統字書裏的正體寫法，有人稱作「舊字形」，日本朋友�
��叫「康熙字典體」——不是指某款遭濫用的字型，而是指參
照同文書局原版的《康熙字典》每字字頭之寫法。這種寫法��
�一來有充份字理，二來在字型美學上也較美觀。至於台灣敎�
��部寫法，則以楷書寫法，來強行扭曲明體、黑體等印版字型
，既缺乏字理，也不夠美觀，已有不少人詬病。在下由衷感��
�　Adobe的貢獻，但極望　Adobe能把正體中文的字型，改回眞正
正統的《康熙字典》寫法（即「舊字形」），而不是台灣以��
�寫楷書扭曲黑體的寫法。不勝銘感！

我不反對有台灣人想用台灣敎育部的寫法，但最最最最低限��
�，也應還其他Tradition 
Chinese使用者，使用眞正Tradition寫法的空間，分拆開「Taiwan」�
��「Tradition」兩體。而不是強迫其他正體使用者依從台灣那種
以楷扭曲黑的寫法。

The zip/tar archives available in the Downloads section only include Noto*.ttf; 
the Arimo, Tinos and Cousine fonts are still only downloadable as individual 
TTF files from the Wiki (or by downloading the entire Subversion repository). 
It seems like it would be a good idea to have a separate archive file generated 
for these three font families.

Don't call font._buildReverseGlyphOrderDict().  It automatically rebuilds that 
when needed.  See:

https://github.com/behdad/fonttools/blob/master/Lib/fontTools/ttLib/__init__.py#
L561

What steps will reproduce the problem?
1.Open Noto Sans Hebrew 
2. Look at U+0592 (Hebrew accent segol)
3.

What is the expected output? What do you see instead? The three dots should be 
arranged with one on top and two centered below. Instead, there two on top with 
one centered below.


What version of the product are you using? On what operating system?
noto-d7adb9162b40 on Windows 7

Please provide any additional information below.

The concerns are best described by the article linked below:


https://medium.com/@eteraz/the-death-of-the-urdu-script-9ce935435d90

No glyph available for the Ghana Cedi Currency: ₵
Please add this so Noto can be used on Ghana websites!

Hi,

Is it possible to include the characters of all the languages in a single ttf 
file?
For example, if I use NotoSans-Regular.ttf I am able to print characters for 
Bulgarian, Czech, Danish, Dutch, Finnish, French, German, Estonian, Greek, 
Hungarian, Icelandic, Macedonian, Russian, Polish, Portuguese, Vietnamese and 
Turkish. But not for Arabic, Hindi, Bengali, Japanese, Mandarin, Hebrew and 
Catonese.

I can use only a single ttf file.

Regards

What steps will reproduce the problem?
1. Trying to use letter u̯ (lowercase u with inverted breve below), it's not 
placed below, rather to the lower right.
2.
3.

What is the expected output? What do you see instead?
Now I can't get it to appear below, as intended.


What version of the product are you using? On what operating system?

Latest version of Noto Serif, it's the same on Noto Sans. I use Windows 8, and 
it's present both when I "test" the font on Fontsquirrel, and in 
InDesign/Google Chrome etc.
Further on, it's the same on my Android Phone, and at my Mac at work.

Please provide any additional information below.

http://graphemica.com/032F (believe this is relevant)

http://www.univie.ac.at/lexlep/wiki/u%CC%AF
http://www.utexas.edu/cola/centers/lrc/ielex/U/P0745.html

The two other links is about use of the letter in Proto-Indo-European.

The following fonts have extra cmap subtables, with platform IDs of 0 or 1. 
These cmap subtables should be removed:

hinted/NotoSansLao-Bold.ttx
hinted/NotoSerifKhmer-Regular.ttx
hinted/NotoSerifKhmer-Bold.ttx
hinted/NotoSansLao-Regular.ttx
hinted/NotoSansLaoUI-Regular.ttx

What steps will reproduce the problem?
Noto Serif Italic does not contain the Serbian and Macedonian glyphs for the 
italic letters.

Please see the attached screenshot.
— column 1 regular
— column 2 italic russian
— column 3 italic macedonian and serbian

Additionally the ѓ italic is missing as well.


Please have a look at the following wikipedia articles for a more in-depth 
explanation on how to prepare a solution.

http://en.wikipedia.org/wiki/Macedonian_Cyrillic
http://en.wikipedia.org/wiki/Serbian_Cyrillic_alphabet

Amazing from this — keep up the great job!
Thanks guys (bow)

NotoSansMalayalam does not follow the file name convention. 

NotoSansMalayalam.ttf should be NotoSansMalayalam-Regular.ttf
NotoSansMalayalamUI.ttf should be NotoSansMalayalamUI-Regular.ttf

1. Remove the ligature 'श्व' (SHA VIRAMA VA - 0936 094D 0935) - 
attachment 1. So that, that ligature would be as in attachment 2.

Reasoning: Nepali does not use the former; Hindi and Marathi is ok with the 
second one.


2. Fix the white seen at the junction of the half form for 'ञ्ज' (NYA 
VIRAMA JA - 091E 094D 091C) - attachment 3.


Other deep conjuncts considered were:
ञ्ज (NYA VIRAMA JA - 091E 094D 091C)
ङ्ग (NGA VIRAMA GA - U+0919 U+094D 0917)

Even though Nepali uses these sequences for nasalization, it does not use deep 
conjunct. Hindi and Marathi are using respective Anuswara based forms for 
nasalization. So these sequences are rare in Hindi and Marathi. So the decision 
is not to go for these deep conjuncts.

What steps will reproduce the problem?
1. Type / View the character ஶ்ரீ (U+0BB8 U+0BCD U+0BB0 U+0BC0)
2. Type / View the character sequence ஸ்ரீ (U+0BB6 U+0BCD U+0BB0 U+0BC0)

What is the expected output? What do you see instead?
1. For 1, the expected output is a single glyph (shritamil ஶ்ரீ). 
Actual output is seperate glyphs of shaprehalftamil (ஶ்) and raiivowelsign 
(ரீ)  (ஶ் ரீ without a space in middle)

2. For 2, the expected output is seperate glyphs of saprehalftamil (ஸ்)  
(ரீ) (ஸ் ரீ without a space in middle). Actual output is a single 
glyph (shritamil ஶ்ரீ)

What version of the product are you using? On what operating system?
Noto Sans Tamil 1.03 on Android Kitkat, Ubuntu.

Please provide any additional information below.

Complex glyph SRI was changed from U+0BB8 U+0BCD U+0BB0 U+0BC0 to U+0BB6 U+0BCD 
U+0BB0 U+0BC0 in Unicode 4.1.[1] NotoSansTamil (like many other fonts) are 
still using the older definition for the complex glyph. Apple / iOS are using 
updated fonts and as a result, text written in old format (and rendered as 
single shri glyph in NotoSansTamil font) will be rendered as seperate glyphs 
and viceverse. This defeats the purpose of interoperability that Unicode gives.

Suggested Fix :-
The ligature subtable for shritamil glyph currently has
saprehalftamil ratamil(ர) iivowelsigntamil(ீ)
satamil(ஸ) viramatamil(்) ratamil(ர) iivowelsigntamil(ீ)

It should be replaced with 

shaprehalftamil ratamil(ர) iivowelsigntamil(ீ)
shatamil(ஶ) viramatamil(்) ratamil(ர) iivowelsigntamil(ீ)

This change will be in line with latest unicode standard.

See also https://bugzilla.redhat.com/show_bug.cgi?id=1078661 similar bug for 
Lohit-Tamil font.

[1] http://www.unicode.org/L2/L2005/05129-tamil-named.txt

Listed below are spurious tables (in that they're NOT necessary for 
'run-time'). 

* Khmer/Hinted/NotoSansKhmer-Regular : TSI[0-3,5]
* Khmer/Hinted/NotoSerifKhmer* : morx  : Hinted fonts do not need morx

* Khmer/Unhinted/*Sans*  : TSI[P,S,V] 
* Lao/Hinted 
    NotoSansLao-{Regular,Bold} : TSIV
    NotoSansUILao-Regular : TSIV
    All fonts : morx 
* Lao/Unhinted
    All fonts : TSI{V,P,S,D}

All fonts have FFTM table : 28 bytes
Some fonts have Pfed table : ~100 bytes

I removed TSI[P,S,V] successfully with VOLT and they work on Windows. (when I 
used ttx to remove them, they didn't work on Windows). 

However, TSI[0-3,5] tables are problematic. They're not VOLT tables and 
removing them with ttx led them not to work properly on Windows. 

Noto Emoji monochrome font is missing from the public Noto website.

The current Noto Serif lacks MARK and MKMK feature, and is not convinent to 
type IPA.

I found one immediate minor bug. The sequence 0CB0 + 0CCD + 0CB0 is rendered 
wrongly. I have attached the screenshot depicting the wrong and correct display 
forms. 

Thanks and regards,
Pavanaja

The Kaithi font is mistakenly defining ASCII digits instead of the Devanagari 
digits.

According to Unicode 6.2, section 10.7, page 347,

"The digits in Kaithi are considered to be stylistic variants of those used in 
Devanagari. Hence the Devanagari digits located at U+0966..096F should be 
employed."

But the font instead employs the ASCII digits, at U+0030 to U+0039.

The cmap in the font should be change to point from the Devanagari digits to 
the glyphs, not the ASCII digits.

Two characters used in the Lisu script are located outside of the Lisu Unicode 
range. They have been ommitted in the Noto Lisu font.

This is the Unicode description of the two characters:

“Other Modifier Letters.

Nasalised vowels are denoted by a nasalization mark following the vowel. This 
word-forming character is not encoded separately in the Lisu script, but is 
represented by U+02BC modifier letter apostrophe, which has the requisite shape 
and properties (General_Category=Lm) and is used in similar contexts.

A glide based on the vowel A, pronounced as [ɑ] without an initial glottal 
stop (and normally bearing a 31 low falling pitch), is written after a verbal 
form to mark various aspects. This word-forming modifier letters is represented 
by U+02CD modifier letter low macron. In a Lisu font, this modifier letter 
should be rendered on the baseline, to harmonize with the position of the tone 
letters.”

Source: http://www.unicode.org/versions/Unicode6.2.0/ch13.pdf#page=27.

You have supported Urdu in the form of the Arabic Nashq script which is not the 
correct way to do it.

There is a writeup on this by Ali Eteraz (Twitter:@eteraz) here - 
https://medium.com/@eteraz/the-death-of-the-urdu-script-9ce935435d90

Examples of Nastaliq fonts: http://urdu.ca/1 (direct link: 
http://urdu.ca/UrduFonts.zip) or  http://www.urdujahan.com/font.html. 

The modifier arrowheads (U+02C2..02C5), used in phonetics to note place of 
articulation, are oversized and vertically too low in NotoSans and NotoSerif. 
They are almost indistinguishable from greater-than and less-than sign.

They should be at a superscript like position, and smaller.

Compare, for example, with SIL fonts Andika, Charis, Doulos, Gentium.

It appears that Cousine may not be supporting Latin combining marks properly. 
The following combination doesn't work correctly on ChromeOS for example: c̓

Android version: 4.4.2 (KitKat)
Device Model: Nexus 7 (2013)

Malayalam conjunct യ്വ (U0d2f + U0d4d + U0d35) is not rendering properly 
in my android tablet. There are words using this conjunct in Malayalam. See 
these search results:

https://www.google.com/search?q=ചെയ്വാൻ
https://www.google.com/search?q=ചെയ്വിൻ

The rendering could be as displayed in this picture (see the red arrow mark):
http://imgur.com/xemgPhN
The above image is taken from Malayalam bible known as Sathyavedapusthakam.

Malayalam conjunct ഴ്വ (U0d34 + U0d4d + U0d35) is also not rendering 
properly.

There are words using this conjunct in Malayalam. See these search results:
https://www.google.com/search?q=താഴ്വര
https://www.google.com/search?q=വാഴ്വ്

This issue has been reported to Android project earlier:
http://code.google.com/p/android/issues/detail?id=67430

First of all, a big thanks to your team for the hard work on developing the CJK 
font family. After reading the news I installed the fonts on my PC in no time. 
However after some use I spot an issue - the full-width comma "，" is somewhat 
offsetted.

As you can see from the attached image, the full-width comma is higher than 
those of the other glyphs. This is the most obviously in the smallest weight. 
It is less obvious in the black variant, but when you compare it with the 
full-width comma "。" it is still higher. This also happens in vertical 
writings.

I only tried the Traditional Chinese typeface, so I am not sure if it is a 
common issue across all fonts.

The value of the fsType bits in the OS/2 table of all/most of the fonts is 
mistakenly set to 0x0008, but should be set to zero.

Here's what 0x0008 means: "[...] the font may be embedded but must only be 
installed *temporarily* on other systems [...]".

Here's what zero means: "Fonts with this setting indicate that they may be 
embedded and permanently installed on the remote system by an application. The 
user of the remote system acquires the identical rights, obligations and 
licenses for that font as the original purchaser of the font [...]".