-
Notifications
You must be signed in to change notification settings - Fork 620
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Strange behavior with ccmp lookup & marks #121
Comments
Right. We have found that this is the behavior that Uniscribe exposes, at least in the Arabic shaper, so we have implemented it that way. I understand it might not be desirable... |
Or does Windows expose a different behavior in your testing? |
Behdad, thank you for the explanation. |
Thanks. I'll test and reconsider. |
I think this mostly serves to illustrate the fact that it's a bad idea to use the digraph characters in general, at least in conjunction with combining marks. Given a digraph <xy> followed by a combining accent such as <acute>, it's unclear in principle whether the accent is expected to appear on the first component of the digraph, on the second component, centered over the digraph as a whole, or perhaps even duplicated and rendered on both components. (FWIW, I suspect the latter would be the most appropriate thing to do in Dutch if presented with the text sequence <U+0133, U+0301>, for example: it's wrong to write either iȷ́ or íj, the correct presentation is íȷ́ .... which is i-acute j-acute, in case it doesn't render well for you. But this isn't up to an engine like harfbuzz; if anything, it'd be up to the 'locl' feature to decide which rendering to implement.) |
I agrees that this case is very marginal and the digraphs are a silliness. |
I double checked that Uniscribe does the same. Closing as such. |
Hello.
It is not very important but I am curious to understand ...
In this minimal font the latin dz digraph is transform to a d followed by a z using a ccmp lookup.
Applying an accent to the digraph then it moves it to the first letter ignoring (for GPOS mark) the separation done by the ccmp lookup.
http:pecita.eu/ccmpDigraph/ccmpDigraph.tar.bz2
The text was updated successfully, but these errors were encountered: