Re: [cmis] Text encoding in AtomPub

[Florent Guillaume <fg@nuxeo.com>]

Basically if you don't know the encoding, then it's not text, it's a  
binary.

Florent

On Jul 24, 2009, at 10:52 AM, fmueller@opentext.com wrote:

> Hi,
>
> Here is a question to all the CMIS AtomPub client developers out  
> there:
>
> I got stuck with document creation. In order to comply with AtomPub,  
> text files must not be base64 encoded but enclosed in the <content>  
> tag as plain text. This text must use the same encoding as the Atom  
> XML around it.
> If I pick up a text file from the file system I don't know the  
> encoding of this file and therefore I can't re-encode the text  
> correctly. If the original encoding of the text file and the  
> encoding of the Atom XML don't match by coincidence the document  
> content in the repository will be different from the original  
> content. That is, I can't rely on this method. Since creating  
> documents in two steps (entry first, then adding content) is not  
> supported by all repositories this is not viable option either.
>
> Do I make an error in reasoning or do we have a real issue here?
>
>
> Thanks,
>
> Florian

-- 
Florent Guillaume, Head of R&D, Nuxeo
Open Source, Java EE based, Enterprise Content Management (ECM)
http://www.nuxeo.com   http://www.nuxeo.org   +33 1 40 33 79 87