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-inline] should initial-letter-wrap have an auto value? #410

Open
dauwhe opened this issue Aug 16, 2016 · 3 comments
Open

[css-inline] should initial-letter-wrap have an auto value? #410

dauwhe opened this issue Aug 16, 2016 · 3 comments
Labels
css-inline-3 Current Work i18n-tracker Group bringing to attention of Internationalization, or tracked by i18n but not needing response.

Comments

@dauwhe
Copy link
Contributor

dauwhe commented Aug 16, 2016

See issue 13 in the spec. Right now we have

inital-letter-wrap (none | first | all | grid | <length> | <percentage>)

none doesn't do any wrapping, and all wraps every line to be close to the shape of the initial letter. first just wraps the first line, but acts like none if there's a space after the initial letter. This is because you don't want to close up the word space if the para starts like "A screaming comes across the sky."

Should we rename first to auto, and add a first that always applies, whether or not there is a space after the initial letter? I don't immediately see a typographic situation where this would be useful.

@dauwhe dauwhe added the css-inline-3 Current Work label Aug 16, 2016
@frivoal
Copy link
Collaborator

frivoal commented Aug 23, 2016

Unless we expect to get a value that can switch automagically between all and none (and maybe first) at some point in the future and want to reserve auto for that, I agree we can use auto instead of first. As for introducing an non automatic first, we can always do it later, so let's defer that until we get demand / use cases.

@dauwhe dauwhe added i18n-tracker Group bringing to attention of Internationalization, or tracked by i18n but not needing response. Needs i18n feedback labels May 24, 2018
@r12a
Copy link
Contributor

r12a commented Aug 23, 2019

Somehow i missed this request for i18n feedback, but I'm wondering whether there was a particular reason that that label was added to this issue. Nothing is coming to mind that applies here.

I also would have naively expected the auto alternation to be between none and all, rather than none and first.

If auto is used for that alternation, it would generally produce first/all most of the time, since none would only be applied when the para starts with a single-letter word. That somehow seems back-to-front for me.

(Looking at examples, i noted that another approach here is to use none and capitalise the remainder of a word if it is more than one letter long.)

I don't know whether that's of any help.

@fantasai
Copy link
Collaborator

Somehow i missed this request for i18n feedback, but I'm wondering whether there was a particular reason that that label was added to this issue.

@r12a Well, we know the behavior for space-separated languages requires this automatic behavior, where a first line beginning with a space is treated like 'none' and one without is wrapped in similar to 'all' (but subsequent lines are not so wrapped). The question is whether there are languages that would not want this automatic distinction, and would instead prefer to always wrap the first line tightly to its initial letter.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
css-inline-3 Current Work i18n-tracker Group bringing to attention of Internationalization, or tracked by i18n but not needing response.
Projects
None yet
Development

No branches or pull requests

5 participants