[css3-fonts] Font Matching: Minor Comments

http://dev.w3.org/csswg/css-fonts/#char-handling-issues

   # The procedure above is always performed on text runs
   # containing Unicode characters, documents using legacy
   # encodings are assumed to have been transcoded before
   # matching fonts.

s/The procedure above/CSS font matching/
s/,/:/

   # Layout engines often convert base character plus
   # combining character sequences into precomposed
   # characters if they exist.

This is an interesting statement, but not clear what is
wanted from UAs here. Is this allowed or disallowed?
Would prefer a "may" or "must not" here.

   # The font matching algorithm outlined here supports
   # both ways and fonts can generally support either
   # but variations can occur.

Too many conjunctions. Insert a comma before "but", and
I'll let it slide. ;)

   # If a given character is a Private-Use Area Unicode
   # codepoint and none of the fonts in the fontlist
   # contain a glyph for that codepoint

I don't think "fontlist" is a valid term here... Did
you mean "none of the matched faces"?

*** Substantive issue ***

Also, do we want to exclude generic faces from being
matched here? They're have the same issues as system
fallback in that you can't predict what the PUA will
return.

*** ~~~~~~~~~~~~~~~~~ ***

   # In general, the fonts for a given family

s/for/within/

   # Optimizations of this process are allowed provided
   # that an implementation behaves as if the algorithm
   # had been followed exactly. Matching occurs in a
   # well-defined order to insure that the results are
   # as consistent as possible across user agents, given
   # an identical set of available fonts and rendering
   # technology.

I'd push this paragraph up all the way to the end of
the top-level subsection, "5 Font Matching Algorithm",
right after the first paragraph "The algorithm below
... glyph for that character." It's a general statement
applicable to the whole section, and not really a
"Character handling issue".

http://dev.w3.org/csswg/css-fonts/#font-matching-changes

Add a statement to the top of "5.5 Font matching changes"
   <p><em>This section is non-normative.</em></p>

http://dev.w3.org/csswg/css-fonts/#font-matching-examples

I don't really understand why this example is under
font matching? Seems like it's showing off :lang()
more than anything...

   # This selects any element that has the given language -
   # Japanese or Traditional Chinese - and uses the
   # appropriate font.

s/ - /&nbsp;&mdash; /g;

~fantasai

Received on Wednesday, 22 May 2013 07:59:59 UTC