Re: Clarification of some aspect of opentype SVG spec

On Sat, Jan 30, 2016 at 7:17 AM, Hin-Tak Leung <htl10@users.sourceforge.net>
wrote:

> - encoding: I added support to UTF16/UTF32 both endian and utf8. But I
> imagine one day somebody will want random favorite encodings of theirs for
> their XML, just because it isn't disallowed. Can something be said about
> that? Actually supporting UTF32 already seems overkill, since presumably
> most want to optimize for data size, so utf8 would be the best choice.
>

We should require that the SVG be UTF8 only.

Rob
-- 
lbir ye,ea yer.tnietoehr  rdn rdsme,anea lurpr  edna e hnysnenh hhe uresyf
toD
selthor  stor  edna  siewaoeodm  or v sstvr  esBa  kbvted,t
rdsme,aoreseoouoto
o l euetiuruewFa  kbn e hnystoivateweh uresyf tulsa rehr  rdm  or rnea
lurpr
.a war hsrer holsa rodvted,t  nenh hneireseoouot.tniesiewaoeivatewt sstvr
esn

Received on Friday, 29 January 2016 19:33:17 UTC