[mpeg-OTspec] AHG Kick-off and new draft to review

Sairus Patel sppatel at adobe.com
Wed Nov 26 22:00:48 CET 2014


I think that mention of "hard-coded" colors in the CPAL section was the confusing part. [ The reason for putting it there was to distinguish it from COLR's use of the CPAL table: with COLR, the CPAL table contains all the font-specified colors used by multicolor glyphs, whereas with SVG, the SVG table can contain "hard-coded" colors separate from CPAL. ]

Here is the proposed wording:

#### In Sec 5.7.11 CPAL > subsection: 'SVG ' and 'CPAL'
## REMOVE the sentence:

"The SVG glyph descriptions are able to express their own explicit or "hard-coded" colors as well; these do not vary by palette selection."

## REPLACE the sentence:
"See the SVG table's specification for more details."

WITH the following, as a new paragraph:

"The SVG glyph descriptions are able to express their own explicit or "hard-coded" colors as well. These are not related to color variables and thus do not vary by palette selection. See the SVG table's specification for more details."

#### In Sec 5.5.2 [SVG Table] Color Palettes:
## ADD the following as a NEW paragraph to the end of the section:

Note that the SVG glyph descriptions are able to express their own explicit or "hard-coded" colors as well. These are not related to color variables and thus do not vary by palette selection. For example, a font designer may want the teardrop on a crying emoji always to be blue (this is "hard-coded") but the rest of the emoji regulated by color variables, with the skin of the face having a default value of the classic "smiley face" yellow (default both in the SVG glyph description itself - see the var(--color0, yellow) example below - and in the default color palette).

Sairus

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.aau.at/pipermail/mpeg-otspec/attachments/20141126/d8aff7cf/attachment.html>


More information about the mpeg-otspec mailing list