Re: [css-ui] text-overflow and text-orientation: upright

> On 20 Apr 2015, at 09:59, Xidorn Quan <quanxunzhen@gmail.com> wrote:
> 
> On Mon, Apr 20, 2015 at 6:13 PM, John Daggett <jdaggett@mozilla.com> wrote:
> 
> 
> Xidorn Quan wrote:
> 
> > The spec says that U+2026 should be used for rendering ellipsis,
> > however, it seems to be a bit unfortunate when it is used with vertical
> > text and text-orientation is upright.
> > 
> > It causes something like
> > 
> > a
> > b
> > c
> > …
> > 
> > instead of
> > 
> > a
> > b
> > c
> > ⋮
> > 
> > Not sure what's the best way to resolve this issue. Probably the spec
> > could state that, U+FE19 should be used in that specific case.
> 
> The solution is to use a font that supports vertical text:
> 
>   p { font-family: Hiragino Kaku Gothic ProN, Meiryo; }
> 
> This will do want you want for this case because the 'vert' feature is
> always applied to upright vertical textruns. Making this work for fonts
> lacking support for vertical layout (vertical metrics, vertical
> substitutions) is out of scope for user agents I think.
> 
> That's fair. I thought text-orientation: upright; would suppress any vertical transform, but it seems I was wrong.
> 
> Given that it's a font issue, I agree that we don't need to change the spec.

As I said, fonts can fix the problems, but fonts that do are not in
common use by western authors.

I agree that western vertical upright text is not very common, so
the need isn't particularly pressing, but it is generally a good
idea to allow UAs to do better if they want to, so I stand by my
proposal of changing this sentence:

  Implementations may substitute a more language/script-appropriate
  ellipsis character, or three dots "..." if the ellipsis character
  is unavailable.

into this:

  Implementations may substitute a more language, script, or writing-mode
  appropriate ellipsis character, or three dots "..." if the ellipsis character
  is unavailable. 

 - Florian

Received on Wednesday, 22 April 2015 09:31:16 UTC