search

betamaster8 / noto

Automatically exported from code.google.com/p/noto
0 stars 0 forks source link

Japanese font in OTC outputs wrong 骨 glyph in InDesign when language is specified as Japanese #83

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Open InDesign 9.1 on Mac OSX 10.9.3
2. Select language as "Japanese" at Paragraph Style
3. Select Noto Sans CJK Japanese (Japanese OTF in OTC)
4. Type in 骨 (U+9AA8, the bone character)

What is the expected output? What do you see instead?
Expect to get Japanese glyph of the bone character. Instead, I get S. Chinese 
glyph.

Please provide any additional information below.
T. Chinese font and S. Chinese font in OTC give the expected output.
If I use Japanese font in OTC in Illustrator or Fireworks, I get the correct 
Japanese glyph for the bone character.

Original issue reported on code.google.com by xiangye@chromium.org on 18 Jul 2014 at 9:26

Attachments:

GoogleCodeExporter commented 9 years ago 
Tested multilingual OTF and got the same bug. I got the Chinese bone glyph when 
selected multilingual OTF and specified language to be Japanese in Paragraph 
Style.

Original comment by xiangye@chromium.org on 18 Jul 2014 at 9:50

GoogleCodeExporter commented 9 years ago 
verified by roozbeh, the issue in multilingual OTF seems to be InDesign's bug.

Original comment by xiangye@chromium.org on 18 Jul 2014 at 10:13

GoogleCodeExporter commented 9 years ago 
This may be an InDesign bug. The fonts themselves look OK generally.

Original comment by roozbeh@google.com on 18 Jul 2014 at 10:47

GoogleCodeExporter commented 9 years ago 
What comment #2 and #3 meant:  when the fonts were tested with harfbuzz, they 
behaved as expected. So, it's likely to be an InDesign bug.

Original comment by jungs...@google.com on 21 Jul 2014 at 6:18

GoogleCodeExporter commented 9 years ago 
I cannot reproduce this issue in InDesign 10.0 (CC 2014) on OS X 10.9.4. The 
glyph for U+9AA8 (being sure to use U+9AA8, and not U+2EE3) appears as the 
Japanese/Korean form when the Japanese OTC font instance is used, and when the 
text is language-tagged as Japanese, either at the character or paragraph level.

Original comment by ken.lu...@gmail.com on 22 Jul 2014 at 2:17

GoogleCodeExporter commented 9 years ago 
Closing as WontFix, as the fonts look OK.

Original comment by roozbeh@google.com on 22 Jul 2014 at 4:39