[svgwg] Issue: Clarify SVG Integration spec re expectations for SVG in OpenType (#145) marked as SVG Native

dirkschulze has just labeled an issue for https://github.com/w3c/svgwg as "SVG Native":

== Clarify SVG Integration spec re expectations for SVG in OpenType ==
[Email from Sairus Patel](https://lists.w3.org/Archives/Public/www-svg/2016May/0003.html):

I’d like to request the following changes to the [SVG Integration document](https://www.w3.org/TR/svg-integration/). This has come up in the context of the current revision to the OpenType-SVG specification. Please let me know if there is another process by which to move this along:
1. In sec 2 > font document, change:
   
   > must use the secure animated processing mode.
   
   to:
   
   > must use the secure animated or secure static processing mode.
   
   Reason: As stated in OT-SVG, it is valid for a font-engine _not_ to support animation. Thus either mode above should be allowed.
2. In sec 2, font document, replace:
   
   > This referencing mode is intended to used by the OpenType specification for processing documents from the "SVG" table.
   
   by:
   
   > The OpenType specification uses this referencing mode for processing documents from the ‘SVG ’ table. OpenType has a facility whereby color palette variables are provided in the above user agent style sheet as well; see https://www.microsoft.com/typography/otspec/svg.htm.
3. Since it’s been addressed above, delete:
   
   > Issue 4: Should the CSS Variables that map the palette colors into the document be defined here too? It probably makes sense to keep that in the OpenType specification.
   
   Reason: It makes sense to have OT be the single place the color palette variables facility is defined in. It probably makes sense for OT to be the sole place the UA style sheet in ‘font document’ (sec 2) is defined in as well, though that isn’t part of this proposal.
4. Sec 3.1 External References says:
   
   > Issue 5: This is all too handwavy. And we perhaps shouldn't try to make an exhaustive list. This needs to be defined in terms of Fetch, probably. And the URL Standard for comparing the URLs.
   
   I’d like to request that the document resolve this issue. I’ve heard concern from implementors about this “handwavy”ness.


See https://github.com/w3c/svgwg/issues/145

Received on Tuesday, 21 May 2019 19:11:23 UTC