Quote:
Originally Posted by Quoth
Do the PDFs embed the required fonts? Otherwise you don't know what it should look like  |
Those are the PDFs generated years ago, and then I have the actual DOC(X)s (this is how I know all the font information + have all the correct underlying unicode characters).
But there's two parallel issues here:
1. Fonts: Since I can't use any of those 4 proprietary fonts, I'm going to
have to rely on different fonts in the ebook.
On the proofing side of things, it's hard to tell if this is simple font differences (like a difference between Serif/Sans-Serif fonts)... or if stripping those fonts can cause the displayed text to now be wrong.
Side Note: It looks like
"Source Han Sans" may be another potential font candidate.
2. HTML Language: There are actual language variations (different swashes and swooshes).
For example, this single character:
返 (U+8FD4)
in different languages, has at least 5 different representations:
https://en.wikipedia.org/wiki/File:S...Difference.svg
In ebooks, this would require proper lang markup:
Code:
<span lang="zh-Hans">返</span> (Simplified Chinese)
<span lang="zh-Hant">返</span> (Traditional Chinese)
<span lang="zh-HK">返</span> (Traditional Chinese - Hong Kong)
<span lang="ja">返</span> (Japanese)
<span lang="ko">返</span> (Korean)
All are the same Unicode character, but should display differently (like the above SVG).
I mean, to me, the few sample images I posted in #1
look similar, but I don't know, because it all looks Chinese to me
.
Side Note: My best guess currently, is that I can change anything that was in:
PMingLiU -> lang="zh-Hant" (Traditional Chinese)
SimSun -> lang="zh-Hans" (Simplified Chinese)
MS Gothic + MS Mincho -> lang="ja" (Japanese)
then substitute in a thoroughly vetted Asian font (like Source Han Sans). But then comes actual device support... has anyone meticulously tested this stuff across devices?