Re: [css-text] Preventing typographic orphans

On Sun, Jan 4, 2015 at 4:48 PM, Sebastian Zartner <
sebastianzartner@gmail.com> wrote:

> On 5 January 2015 at 00:25, Glenn Adams <glenn@skynav.com> wrote:
> > There are both stylistic and semantic reasons that pertain to last line
> > break and content. It is not one or the other in general. CSS should
> > probably support the necessary properties to effect the stylistic
> > requirements. Whether it should go as far as specifying language specific
> > behavior is doubtful.
>
> Stylistic use cases for influencing the last line break still should
> consider the semantic reasons. While CSS may not define language
> specific behavior, it may at least mention that UAs should consider
> semantic rules for line wrapping.
>

It already does [1]. Sort of. XSL-FO is somewhat more explicit [2][3].

[1] http://dev.w3.org/csswg/css-text-3/#line-breaking
[2] http://www.w3.org/TR/2001/REC-xsl-20011015/slice7.html#language
[3] http://www.w3.org/TR/2001/REC-xsl-20011015/slice7.html#xml:lang


>
> Sebastian
>
> > On Sun, Jan 4, 2015 at 4:06 PM, Sebastian Zartner
> > <sebastianzartner@gmail.com> wrote:
> >>
> >> On 4 January 2015 at 20:19, Jens Oliver Meiert wrote:
> >> >
> >> > > This is awfully hacky and there *really* should be a better way to
> do
> >> > > this.
> >> >
> >> > A quick +1, for this seems *really* like a CSS concern. We should not
> >> > all of a sudden advocate no-break spaces and such for this is
> >> > absolutely not a content issue.
> >> >
> >> > I can’t see a clearer case for something CSS should handle, and I’m
> >> > glad Lea brought it up. And it’d be funny if of all times now we’d get
> >> > all antsy about adding something :|
> >>
> >> The problem here is the grammatically correct wrapping of lines. And
> >> that doesn't sound like something that needs to be controllable via
> >> CSS. Rather the UAs should be in charge of doing the line wrapping
> >> right in regard of the used language.
> >>
> >> Sebastian
> >>
> >
>