-
Notifications
You must be signed in to change notification settings - Fork 5
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
problems with Spacing Modifier Letters and Combining Diacritical Marks #13
Comments
hmm... if it's not too much trouble, could you add those minimal verifiable complete examples to this bug (ideally, one per comment)? That'll make it easier to check and track for me. |
|
(2) Based on this question:
|
(3) Based on this question:
|
(4) Based on this question:
|
thanks! I'll try to see what's going on with this hopefully today |
Any updates on this? Ulrike Fischer added a comment to the stackexchange question that suggests both a place to look regarding the issue and a point that suggests that the desired behaviour may be hard to define in the first place. |
I've unfortunately not had any time to look at this yet, and might not get to it for at least another few days =( |
Understood. I'll keep an eye out for whatever you find when you're able to. |
I am having similar issues with using combining marks in DevanagariExtended and VedicExtensions range with devanagari and other Indian script fonts which do not have these characters. Some of the approaches above show the combining mark separately - with dotted circle. The only approach that has worked correctly is when the combining mark is surrounded by uccoff and uccon - eg. ठ\uccoff{\fontspec{Siddhanta}᳚}\uccon Siddhanta font supports these combining marks not available in other fonts - http://svayambhava.blogspot.in/p/siddhanta-devanagariunicode-open-type.html |
I just posted this question on the LaTeX stackexchange before finding the
ucharclasses
repo. Am I right that the issue I encountered is a bug or limitation, or am I doing something wrong?The text was updated successfully, but these errors were encountered: