Trouble with Japanese (romaji and kanji)

mamster · 03-31-2013, 11:03 PM

Hello, folks. Thanks for answering my question about embedding Japanese fonts over on the EPUB forum. I successfully used glyphIgo to subset the free Hanazono font, and now I'm trying to get my book to render properly on Nook. I'm testing on two Nook devices, my sister's first-gen Nook and my own Nook Simple Touch.

I'm having two problems. I'm guessing neither is solvable, but I want to check and make sure.

1. On the Nook Classic, the characters ō and ū, which are common in romanized Japanese, fail to render, and display as question marks. If I change the font to Helvetica, it renders the ō but not the ū.

2. On the Nook Touch, this problem is solved; the native fonts include those characters. And the kanji render fine with the embedded font, but only if I enable Publisher Defaults. As soon as I turn off Publisher Defaults, the kanji turn into empty boxes.

Question 1: Should I even bother trying to get my document to work on Nook Classic? If so, any ideas? Should I embed the body font using something like Adobe Source Sans?

Question 2: Is it reasonable to ask people to turn on Publisher Defaults if they want to be able to read my book? If so, what's the best way to do that? Have the book open on a page saying "IF YOU HAVE A NOOK..."?

Thanks very much,
Matthew

Mex5150 · 06-27-2013, 12:53 AM

No idea on 1.

For 2, assuming it's rooted, have you tried installing a better font? I could be wrong, but I would imagine turning on the publisher settings forces the reader to use an embedded font rather than the default one which may have non-latin characters missing, where the forced one has the full set.

~Mex

03-31-2013, 11:03 PM	#1
mamster Junior Member Posts: 5 Karma: 10 Join Date: Mar 2013 Device: iPad/iBooks 3	Trouble with Japanese (romaji and kanji) Hello, folks. Thanks for answering my question about embedding Japanese fonts over on the EPUB forum. I successfully used glyphIgo to subset the free Hanazono font, and now I'm trying to get my book to render properly on Nook. I'm testing on two Nook devices, my sister's first-gen Nook and my own Nook Simple Touch. I'm having two problems. I'm guessing neither is solvable, but I want to check and make sure. 1. On the Nook Classic, the characters ō and ū, which are common in romanized Japanese, fail to render, and display as question marks. If I change the font to Helvetica, it renders the ō but not the ū. 2. On the Nook Touch, this problem is solved; the native fonts include those characters. And the kanji render fine with the embedded font, but only if I enable Publisher Defaults. As soon as I turn off Publisher Defaults, the kanji turn into empty boxes. Question 1: Should I even bother trying to get my document to work on Nook Classic? If so, any ideas? Should I embed the body font using something like Adobe Source Sans? Question 2: Is it reasonable to ask people to turn on Publisher Defaults if they want to be able to read my book? If so, what's the best way to do that? Have the book open on a page saying "IF YOU HAVE A NOOK..."? Thanks very much, Matthew

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Best reader for Kanji support: Sony or Kobo	iExilschorsch	General Discussions	2	12-07-2012 07:11 AM
PRS-T1 PRS-T1 Japanese version have japanese-english dic in it?	nukito	Sony Reader	2	06-14-2012 02:37 PM
PRS-350 Use Sony-350 Dictionary to improve reading of Kanji characters?	iExilschorsch	Sony Reader	4	04-04-2011 05:53 AM
Japanes fonts ( Kanji kana)	Butchi	Which one should I buy?	9	12-29-2010 04:34 PM
Hanzi / Kanji Font	ahi	Workshop	6	07-14-2009 08:53 AM

06-27-2013, 12:53 AM	#2
Mex5150 Banned Posts: 23 Karma: 7476 Join Date: Feb 2013 Location: To the left of your body, to the right of your mind, lost in a riddle. Device: Android phone, Nook Touch Simple Glowlight	No idea on 1. For 2, assuming it's rooted, have you tried installing a better font? I could be wrong, but I would imagine turning on the publisher settings forces the reader to use an embedded font rather than the default one which may have non-latin characters missing, where the forced one has the full set. ~Mex

Advert