Re: [Openexr-devel] Re: Help implementing Imf::Ostream

[Chris Cox]

Or that your seek function isn’t correct, or the file isn’t being flushed, etc.


On 2/11/10 5:34 PM, "Koraxen" <address@hidden> wrote:

> To confirm:
>
> Assuming I start with an std::string containing UTF-8 encoded data. I then call c_str() on the std::string to get raw chars, and pass them into the API. Is this the correct procedure? 
>
> I tried this and and nothing gets written to any path with Unicode chars :(
>
> On the other hand, if I go through Imf::IOstream, an EXR file DOES get written to the Unicode path. However, the file's contents are somehow corrupt because they can't be opened in EXR viewers. This suggests that my write() function isn't complete? I am not sure?
>
> void MyOStream::write(const char c[], int n)
> {
>     m_OutStream->write(c,n);
> }
>
> Thanks!
>
>
> On Thu, Feb 11, 2010 at 3:20 PM, Lutz Latta <address@hidden> wrote:
> > > The bigger question is:
> > >
> > > *** How can you write EXR files to paths that have Unicode characters? ***
> >
> > This was discussed on the list a while back (search the archives), and it was agreed to use UTF-8 encoded char* strings when passing Unicode file names into the API. Since this discussion was a while ago, this is probably how it's implemented in the current OpenEXR version. I haven't checked in a while.
> >
> > Hope this helps,
> >    Lutz