Hello Brendan,

Accept utf8! It's in the ACES container spec afaik.

Take care,

Lars Borg
408 536 2723<tel:4085362723> (tel),408 391 9479<tel:4083919479> (cell) 
[email protected]<mailto:[email protected]>


-----Original message-----
From: Brendan Bolles <[email protected]>
To: "[email protected]" <[email protected]>
Sent: Tue, Nov 13, 2012 21:36:12 GMT+00:00
Subject: [Openexr-devel] UTF-8

In OpenEXR 2.0, how about coming up with a formal position as to whether 
channel names and string attributes are considered UTF-8?

If we want to do as little as possible, I think it'd be good to at least 
include something in the docs like "use UTF-8 at your own risk" or maybe take a 
tougher stance like "all text in OpenEXR files should be ASCII".  I want to 
know if I should expect UTF-8 or can just ignore it.  Right now I'm sure some 
writers are storing UTF-8 and some readers are treating it as ASCII.


Also, maybe a new "encodedStringAttribute" should be added where the encoding 
is stored?  Would people use such a thing?


Brendan


_______________________________________________
Openexr-devel mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/openexr-devel
_______________________________________________
Openexr-devel mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/openexr-devel

Reply via email to