DomainKey-Signature: a=rsa-sha1; c=nofws; d=SSpaeth.de; h=from:to:subject
	:date:message-id:mime-version:content-type; q=dns; s=sspaeth.de;
	b=YEu/u/nPXmYfPzla3/gcBXPLf/8V/nj2oXgR2hpDyb+DzBqLc6/G1NmhkmVTM
	90T1R9IFLEpj7rBTIw/uRWVoqBCYOtKL98g/YSArX3ahqNFqAGfOV6HgBlTNdCAq
	XIJ4vm6JpVMb2Igx0ZB+FgH/LT+m7QDAdyeo32+omc01NM=
From: Sebastian Spaeth <Sebastian@SSpaeth.de>
To: Notmuch developer list <notmuch@notmuchmail.org>
Subject: Encodings
User-Agent: Notmuch/0.5-233-gb404931 (http://notmuchmail.org) Emacs/23.2.1
	(x86_64-pc-linux-gnu)
Date: Mon, 11 Jul 2011 16:04:17 +0200
Message-ID: <87zkkkx6am.fsf@SSpaeth.de>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-=";
	micalg=pgp-sha1; protocol="application/pgp-signature"
Precedence: list

--=-=-=

Hi all,
after I was notified about how notmuch's python bindings perform
differently depending on whether we hand it (byte-based) ASCII strings
or unicode, I tried to disentangle what encodings to expect and send it
to. The answer is that things are very implicit. notmuch.h speaks of
strings but never mentions encodings, xapian docs don't mention
encodings but ojwb confirmed that it expects utf-8.

So, can be document what encoding we are expected to pass in the various
APIs and where we can guarantee to actually return UTF-8 encoded
strings? For some of the stuff we read directly from the files, eg
arbitrary headers, we can probably be least sure, but are e.g. the
returned tags always utf-8?

I would love to make the python bindings use unicode() instances in
cases where we can be sure to actually receive utf-8 encoded strings.

Encodings make my brain hurt. Unfortunately one cannot simply ignore
them.

Sebastian

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAk4bAuIACgkQVYX1jMgnoGIIpgCgho4j/M9KGQWPXCbQL3GBf0mJ
hdUAoIBEDWloS3Lfs1lNKau3MuT34apG
=u5cR
-----END PGP SIGNATURE-----
--=-=-=--