Red Hat Bugzilla – Bug 163231
vertical writing is messed up
Last modified: 2007-11-30 17:11:09 EST
Description of problem:
PostScript file which contains the vertical writing stuff is passed through gs8,
the rendered vertical writing glyphs are all messed up.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.gs -sDEVICE=x11 /usr/share/printconf/tests/test-euc.ps
2.look at the vertical writing
the baseline for the vertical writing isn't correct.
the vertical writing should be rendered correctly.
This is an regression bug.
Created attachment 116741 [details]
Created attachment 116956 [details]
a screenshot on FC4
Created attachment 116957 [details]
a screenshot on devel
Please compare between both screenshots. you will notice that there is two
problems at least. one is, apparently the direction of the grouping symbols are
wrong. it's because gs uses the glyphs of the horizontal writing for the
vertical writing. one is, the baseline of the glyphs are not the center and it
Ick. Not even sure where to start on this one. :-(
davidz: Could this be related to freetype?
I doubt it. as I mentioned at comment #4, there is two problems for the vertical
writing and I suspect gs8 is doing wrong for them.
If these two problems should be filed as the separated bugs, I will.
1. wrong glyph are used. I mean even if CMap for the vertical writing, such as
-V is specified, the glyphs for the horizontal writing is used. Actually the
fonts has the glyphs for the vertical writing and freetype is just rendering it
with given glyph ID. so gs8 must passes the proper glyph ID to freetype.
2. baseline of glyphs are wrong. basically it's different between the horizontal
writing and the vertical writing. but gs8 always calculates it with the
horizontal writing's baseline. this isn't also freetype fault, but gs8 fault.
How is this meant to work? Should GothicBBB-Medium-EUC-H and
GothicBBB-Medium-EUC-V map to different ttf files?
No, same ttf files but different CID.
8.15-0.rc3.7 has some CMaps that had been missing. Does this vertical writing
problem still happen with that version? I can see differences from both
screenshots in the resulting output, but I'm not sure what's right. :-/
Unfortunately it's still there. why it looks different is now Sazanami fonts are
used for default Japanese fonts instead of Kochi.
I'm investigating this problem now BTW.
it seems that CJKV patch for gs-esp 8 has been committed into gs-esp svn at
r165. it may be worth trying to confirm if this bug and Bug #167596 is fixed or
not. just FYI.
------- Additional Comments From firstname.lastname@example.org 2006-06-09 12:42 EST -------
I'm building 8.15.2-5 from r165, so we'll find out.
Please try 8.15.2-6, which contains the change from 164:165. Let me know if
this fixes the problem.
------- Additional Comments From email@example.com 2006-06-13 12:06 EST -------
Please try 8.15.2-6 from rawhide. Does that work any better than it did originally?
Hmm, it looked like the same. will have a look more later.
Created attachment 152767 [details]
a patch to exactly enable CIDFnmap
Attached patch will exactly applies fonts in CIDFnmap even if the same
fontnames are already registered into gs from FAPIcidfmap say.
Thanks! Applied in ghostscript-8.15.4-3.fc7.