Re: Unified draft of SVG-in-OT

So you're suggesting that it's OK for a single glyph to be able to draw ANYWHERE on the page/canvas?!?!    Sorry, but that's "crazy talk" (<grin/>).

I recall a conversation with a colleague 25 years ago where we had a similar argument.

Bottom line: "It's my window and you can't draw on it".

Leonard

From: Robert O'Callahan <robert@ocallahan.org<mailto:robert@ocallahan.org>>
Reply-To: "robert@ocallahan.org<mailto:robert@ocallahan.org>" <robert@ocallahan.org<mailto:robert@ocallahan.org>>
Date: Friday, July 26, 2013 11:07 AM
To: Leonard Rosenthol <lrosenth@adobe.com<mailto:lrosenth@adobe.com>>
Cc: Nikos Andronikos <nikos.andronikos@cisra.canon.com.au<mailto:nikos.andronikos@cisra.canon.com.au>>, "public-svgopentype@w3.org<mailto:public-svgopentype@w3.org>" <public-svgopentype@w3.org<mailto:public-svgopentype@w3.org>>
Subject: Re: Unified draft of SVG-in-OT

On Sat, Jul 27, 2013 at 1:11 AM, Leonard Rosenthol <lrosenth@adobe.com<mailto:lrosenth@adobe.com>> wrote:
Can we agree that for static glyphs that they should be clipped – OR at least that the box needs to be pre-defined somewhere?

No :-)

HOWEVER, there are a myriad of use cases for these glyphs where these glyphs are rendered OUTSIDE of a web context.  Whether it is an OS platform (Windows, iOS, etc.), a non-web-based file format (Word, iWork, PDF, etc.), or print – these glyphs will need to be rendered by SVG into a separate context and then "copied back" into the primary context.  That requires knowing the size & shape of the destination – at least to do it optimally.

Your SVG renderer can compute the ink bounding box for you.

Rob
--
Jtehsauts  tshaei dS,o n" Wohfy  Mdaon  yhoaus  eanuttehrotraiitny  eovni le atrhtohu gthot sf oirng iyvoeu rs ihnesa.r"t sS?o  Whhei csha iids  teoa stiheer :p atroa lsyazye,d  'mYaonu,r  "sGients  uapr,e  tfaokreg iyvoeunr, 'm aotr  atnod  sgaoy ,h o'mGee.t"  uTph eann dt hwea lmka'n?  gBoutt  uIp  waanndt  wyeonut  thoo mken.o w