You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here when XTUC is used, it shifted the baseline. This suggests a new page with recommendations for typesetting engines and apps is needed so that they properly expose parametric axes
Thanks for the pointer.
I think the baseline was stable for YTUC, but bull-shifted when YTAS busted out the top of the em.
Base table ignorance + the inability to register y axes are clear indication, to me, that developers are not at all ready for ANY vertical changes to ANY script of ANY design for ANY reason whatsoever, INCLUDING even if it means huge file compression.
On Jul 6, 2020, at 12:18 PM, Dave Crossland <[email protected]> wrote:
Here when XTUC is used, it shifted the baseline. This suggests a new page with recommendations for typesetting engines and apps is needed so that they properly expose parametric axes
https://www.instagram.com/p/CAkbSwnA4s9/?igshid=8omndiwknolj
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Here when XTUC is used, it shifted the baseline. This suggests a new page with recommendations for typesetting engines and apps is needed so that they properly expose parametric axes
https://www.instagram.com/p/CAkbSwnA4s9/?igshid=8omndiwknolj
The text was updated successfully, but these errors were encountered: