Re: specification for Mozilla's SVG in OpenType proposal

On Wed, Feb 6, 2013 at 5:31 PM, Cameron McCormack <cam@mcc.id.au> wrote:

> From my POV I'm not sure how important it is to have glyphchar="", as
> glyphid="" does the job just as well, and since you're creating the whole
> font you of course know the cmap and the purpose of each glyph, so I don't
> think it is a burden to have to specify each glyph's contents by ID.  roc:
> does glyphchar="" buy you much convenience?


I think it does buy you some convenience if you're adding SVG glyphs to an
existing font. However, it's not essential and dropping it would not be a
catastrophe.

Rob
-- 
Wrfhf pnyyrq gurz gbtrgure naq fnvq, “Lbh xabj gung gur ehyref bs gur
Tragvyrf ybeq vg bire gurz, naq gurve uvtu bssvpvnyf rkrepvfr nhgubevgl
bire gurz. Abg fb jvgu lbh. Vafgrnq, jubrire jnagf gb orpbzr terng nzbat
lbh zhfg or lbhe freinag, naq jubrire jnagf gb or svefg zhfg or lbhe fynir
— whfg nf gur Fba bs Zna qvq abg pbzr gb or freirq, ohg gb freir, naq gb
tvir uvf yvsr nf n enafbz sbe znal.” [Znggurj 20:25-28]

Received on Wednesday, 6 February 2013 11:33:47 UTC