Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (athena.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
MIME-Version: 1.0
In-Reply-To: 
 <CAGHTdUXZPixuQDnRg_NMqbop=KcY0XJwi7vy9AgA59kNMVnJPw@mail.gmail.com>
References: 
 <CAAOi-OEt_Dmf0gctg+wYrGTvcxmenFJh_OVoZ_yeZweeJ6ZVXw@mail.gmail.com>
 <CAHdjipLPj2W5-95_g4RfvwrCBf__c=RispBc4u2YXB+i6GsLAQ@mail.gmail.com>
 <CAAOi-OGZnDbSoda6VbWfU3qEjqJchr-8mWYBrEm3DS_Y8gnS+w@mail.gmail.com>
 <CAHdjipLTmhPbhH7WjofUpLS8ubZL-E26qDY8QnWPgvAcAujQkg@mail.gmail.com>
 <CAAOi-OF8YpN=9Gb-vN5XbWkmruKMX2ZyJwWULz68xD6Wk0guRw@mail.gmail.com>
 <CAHdjipKe7EcSJW5zs=26Kc3TQ+oXnH=OJL75g2oYy490Tsz9xA@mail.gmail.com>
 <CAGHTdUXZPixuQDnRg_NMqbop=KcY0XJwi7vy9AgA59kNMVnJPw@mail.gmail.com>
From: Daniel Gonzalez <gonvaled@gonvaled.com>
Date: Fri, 3 Jan 2014 17:33:06 +0100
Message-ID: 
 <CAAOi-OFzhQ=0R3cj_8EKkp4SLgs7xRogLJrTiB8hbGNeO4vmGg@mail.gmail.com>
Subject: Re: Specify attachment encoding for couchdb
To: user@couchdb.apache.org
Content-Type: multipart/alternative; boundary=047d7b2e4d58cd67f004ef1378ed

--047d7b2e4d58cd67f004ef1378ed
Content-Type: text/plain; charset=ISO-8859-7
Content-Transfer-Encoding: quoted-printable

Great! That is exactly what I was looking for!

Thanks!


On Fri, Jan 3, 2014 at 5:08 PM, Nick North <north.n@gmail.com> wrote:

> Cunning :-)
>
>
> On 3 January 2014 15:48, Alexander Shorin <kxepal@gmail.com> wrote:
>
> > Erhm..just replace:
> >
> > > db.put_attachment(doc, content, content_type=3D'text/plain')
> >
> > with
> >
> > > db.put_attachment(doc, content,
> content_type=3D'text/plain;charset=3Dutf-8')
> >
> > And CouchDB will remember it:
> >
> > $ http HEAD http://localhost:5984/b/testing/test
> > HTTP/1.1 200 OK
> > Accept-Ranges: none
> > Cache-Control: must-revalidate
> > Content-Encoding: gzip
> > Content-Length: 102
> > Content-MD5: 7y85tiUeF/UX9kqpKAzQEw=3D=3D
> > Content-Type: text/plain; charset=3Dutf-8
> > Date: Fri, 03 Jan 2014 14:14:27 GMT
> > ETag: "7y85tiUeF/UX9kqpKAzQEw=3D=3D"
> > Server: CouchDB/1.6.0+build.0bf1856 (Erlang OTP/R16B01)
> >
> > it will also available in attachments stub info. So before decoding,
> > just read content-type value, get att's encoding and decode it
> > according it.
> >
> > --
> > ,,,^..^,,,
> >
> >
> > On Fri, Jan 3, 2014 at 7:43 PM, Daniel Gonzalez <gonvaled@gonvaled.com>
> > wrote:
> > > No, what I mean is "how can I keep track of the encoding used for eac=
h
> of
> > > the attachments, so that I can decode then correctly whenever I want
> to"
> > >
> > >
> > > On Fri, Jan 3, 2014 at 4:23 PM, Alexander Shorin <kxepal@gmail.com>
> > wrote:
> > >
> > >> Not sure if I follow your idea. You mean, that how you can set such
> > >> charset info for existed attachments? In this case you have to
> > >> reupload them.
> > >> --
> > >> ,,,^..^,,,
> > >>
> > >>
> > >> On Fri, Jan 3, 2014 at 6:40 PM, Daniel Gonzalez <
> gonvaled@gonvaled.com>
> > >> wrote:
> > >> > Thanks but, how do you set that on a per-attachment basis in a
> couchdb
> > >> > document? If this is not supported, I guess I will have to add a
> > mapping
> > >> > "attachments-encoding" to the document where I can associate each
> > >> > attachment with its encoding. Any comments on this?
> > >> >
> > >> >
> > >> > On Fri, Jan 3, 2014 at 3:18 PM, Alexander Shorin <kxepal@gmail.com=
>
> > >> wrote:
> > >> >
> > >> >> You can set MIME type as text/plain;charset=3Dutf-8 to help brows=
ers
> > >> >> detect the correct content encoding.
> > >> >> See http://tools.ietf.org/html/rfc2068#section-3.4 for more info
> > >> >> --
> > >> >> ,,,^..^,,,
> > >> >>
> > >> >>
> > >> >> On Fri, Jan 3, 2014 at 5:52 PM, Daniel Gonzalez <
> > gonvaled@gonvaled.com>
> > >> >> wrote:
> > >> >> > Hi,
> > >> >> >
> > >> >> > I have the following test script:
> > >> >> >
> > >> >> > # -*- coding: utf-8 -*-
> > >> >> >
> > >> >> > import os
> > >> >> > import couchdb
> > >> >> >
> > >> >> > GREEK =3D u'=C1=C2=C3=C4 =C5=C6=C7=C8 =C9=CA=CB=CC =CD=CE=CF=D0=
 =D1=D3=D4=D5 =D6=D7=D8=D9 =E1=E2=E3=E4 =E5=E6=E7=E8 =E9=EA=EB=EC =ED=EE=EF=
=F0 =F1=F2=F4=F5
> > =F6=F7=F8=F9'
> > >> >> >
> > >> >> > # Prepare a unicode file, encoded using ENCODING
> > >> >> > ENCODING =3D 'utf-8'
> > >> >> > filename =3D '/tmp/test'
> > >> >> > open(filename, 'w').write(GREEK.encode(ENCODING))
> > >> >> >
> > >> >> > # Create an empty document
> > >> >> > server =3D couchdb.Server()
> > >> >> > db =3D server['cdb-tests']
> > >> >> > doc_id =3D 'testing'
> > >> >> > doc =3D { }
> > >> >> > db[doc_id] =3D doc
> > >> >> >
> > >> >> > # Attach the file to the document
> > >> >> > content =3D open(filename, 'rb') # Open the file for reading
> > >> >> > db.put_attachment(doc, content, content_type=3D'text/plain')
> > >> >> >
> > >> >> > As you can see, the file is utf-8 encoded, but when I attach th=
at
> > >> file to
> > >> >> > couchdb, I have no way to specify this encoding. Thus, requesti=
ng
> > the
> > >> >> > attachment at http://localhost:5984/cdb-tests/testing/testretur=
ns
> > >> the
> > >> >> > following Response Headers:
> > >> >> >
> > >> >> > HTTP/1.1 200 OK
> > >> >> > Server: CouchDB/1.2.0 (Erlang OTP/R15B01)
> > >> >> > ETag: "7y85tiUeF/UX9kqpKAzQEw=3D=3D"
> > >> >> > Date: Fri, 03 Jan 2014 13:43:36 GMT
> > >> >> > Content-Type: text/plain
> > >> >> > Content-MD5: 7y85tiUeF/UX9kqpKAzQEw=3D=3D
> > >> >> > Content-Length: 102
> > >> >> > Content-Encoding: gzip
> > >> >> > Cache-Control: must-revalidate
> > >> >> > Accept-Ranges: none
> > >> >> >
> > >> >> > Seeing the attachment with a browser shows complete gibberish.
> How
> > >> can I
> > >> >> > store the encoding for couchdb attachments?
> > >> >> >
> > >> >> > Thanks and regards,
> > >> >> >
> > >> >> > Daniel
> > >> >> >
> > >> >> > PD: SO reference link:
> http://stackoverflow.com/q/20905157/647991
> > >> >>
> > >>
> >
>

--047d7b2e4d58cd67f004ef1378ed--