Hello Kusanagi-san,
On 5/15/13 6:03 AM, Kusanagi Kouichi wrote:
On 2013-05-10 09:23:17 -0500, Aric Stewart wrote:
Hi there,
I know I am a year late to the party here but I am digging deep into tategaki for a few Japanese programs that are having serious rendering issues and I believe that this patch is incorrect.
Can you explain the problem? How do I reproduce it? I know that tategaki has a minor issue, but it's not serious. Does reverting commit fecb1d8b6f81c2bfff7116e80380b1d4f7b7befc ("gdi32: GetGlyphIndices doesn't substitute glyph.") help?
Just reverting the changes to GetGlyphIndices causes your original tests to fail. so I will have to investigate why and try to correct that. Did you have a specific test case that required this change?
I am attaching the test patch that proves it to me. Kusanagi-san, we should try to make sure that this does not break what it was that you where trying to fix with your original patch.
Your test passed here.
-aric
I also thought that tategaki was mostly working, but I started to investigate and have found quite a number of serious issues.
I have attached my test program as well as png screen shots from win7 and wine to illustrate the issues I am trying to solve. Most interesting to me are the rotated glyph origin problem as well as the fact that @fonts rotate many of the characters by 90 degrees.
I have some work in progress that is fixing the origin, the incorrect GSUB substitution when using glyph indices and also the rotation.
I am finding the logic on how windows decides which glyphs get the 90 degree rotation and which do not very hard to figure out. Do you have any understanding on how that works?
thanks! -aric
