Skip to content
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

[css-font-4] oblique angle for vertical text with text-combine-upright #4818

Open
cconcolato opened this issue Feb 28, 2020 · 2 comments
Open
Labels

Comments

@cconcolato
Copy link

This issue is related to #2983 and #2869

In vertical text, when text-combine-upright is used, the skew should be applied to the combined set of characters and not to individual characters.

@css-meeting-bot
Copy link
Member

The CSS Working Group just discussed [css-font-4] oblique angle for vertical text with text-combine-upright.

The full IRC log of that discussion <dael> Topic: [css-font-4] oblique angle for vertical text with text-combine-upright
<dael> github: https://github.com//issues/4818
<dael> Rossen_: Fairly straightforward explaination. Prop resolution is in case of vertical text layout when we use t-c-u which introduces horizontal text sqeue should be to combined characters
<dael> fantasai: Complication, if you have oblique glyphs they won't go downwards, but to the side. I think a little tricky for that reason. Wanted to bring it for discussion. I think what probably makes sense is we need another property that explicitly does skewing on the line
<dael> fantasai: Not sure which way to do. could be consistent with real itals or fix stuff on line
<dael> Rossen_: Then my prop is continue on GH there. It doesn't sound like what you mentioned was already discussed to point where we can resolve. Behavior is dependent on your prop for skew property I would prefer to have the discussion when ready
<dael> fantasai: Not dependent but needs consider. Main thing is do we want to be consistent with ital or have real and fake ital be different
<dael> Rossen_: Important decision. Hope was in absense of this we could resolve but you bring up a good point. This will introduce a fairly apparent difference which will not have a way for authors to combat it
<dael> Rossen_: If this was the case I propose we wait on resolving until we've resolved skew and how it works
<dael> Rossen_: What do you think fantasai ?
<dael> fantasai: I don't think we're ready to resolve, but doesn't depend on skew. We can go back to issue, but can't just be me talking about it. Bee out there fore a while
<fantasai> s/Bee/Been/
<fantasai> s/fore/for/
<dael> Rossen_: Can I ask you to link the skew issue if it's not linked and we'll bring back when ready for more discussion?

@astearns astearns removed the Agenda+ label Apr 28, 2021
@chrishtr
Copy link
Contributor

I think skew should be applied to the combined set of characters, and in the logical direction (to the side in this case). I don't see a need for a new property.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants