If schwa + combining grave is input, then that is what is stored in the text string in the PDF, which means that the text can be selected, copied, and pasted into other environments and stands a reasonably good chance of being correctly displayed in other fonts as ə̀ rather than as ə`.
If schwa + combining grave is input, then that is what is stored in the text string in the PDF, which means that the text can be selected, copied, and pasted into other environments and stands a reasonably good chance of being correctly displayed in other fonts as ə̀ rather than as ə`.
Since my client is ony interested in a very narrow user base, I think I'd rather opt for making it easier for them to input rather than worrying about how it will render in another font which will likely never happen
Who can say. Going back to input, if the schwa + combining grave is how the ccmp feature is written, can my client simply select the precomposed glyph via the character/glyph palette and still be compliant?
@Denis Moyogo Jacquerye I tried you suggested ccmp code. It worked the same way my previous attempt did, but with the added bonus of aligning the base glyph with the precomposed glyph in the glyph palette. Thank you.
Comments
I have tested schwa gravecomb by schwagravecomb, and it properly decomposes when changed to other fonts