- From: 張俊芝 via GitHub <sysbot+gh@w3.org>
- Date: Tue, 05 Feb 2019 08:26:46 +0000
- To: public-css-archive@w3.org
> > So from your replies, there are one common reason for not adding support for this: implementation difficulty. > > No, it's the combination of lack of usecase (and proof of usecase) and implementation difficulty. If something has strong usecase, and it's not terribly complicated to implement, browsers may still try to do that. `writing-mode` itself is complicated enough, but it does have strong usecases, which is why it got added and implemented. However, an imaginary usecase is unlikely to be able to justify a complicated implementation. > That's what I meant, it's **one** of the common reasons. > > I think the implementation difficulty is primarily due to lack of support of such typography in low-level graphics layer, such as GDK/GTK. I am not sure, but I am interested in looking into this issue in the further. > > I don't think so. I believe the main problem is from calculating various metrics like text position and baseline in layout. There are way too many possible combinations of features can affect text layout. They all need to be taken into consideration when implementing. > Thanks you for the suggestion @upsuper . I meant I am not sure whether typography is native supported by GTK itself, or an uper layer based on GTK. I don't know much about graphics layer programming, would like to look into it, just saying. -- GitHub Notification of comment by Zhang-Junzhi Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3608#issuecomment-460551470 using your GitHub account
Received on Tuesday, 5 February 2019 08:26:48 UTC