Subject: Re: Unicode Paths
From: Martin Owens <doctormo@gmail.com>
To: Kan-Ru Chen <kanru@kanru.info>
In-Reply-To: <8739fzwxfv.fsf@isil.kanru.info>
References: <1315972539.2201.11.camel@delen> <8739fzwxfv.fsf@isil.kanru.info>
Content-Type: text/plain; charset="UTF-8"
Date: Thu, 15 Sep 2011 12:52:30 -0400
Message-ID: <1316105550.2201.21.camel@delen>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Cc: Notmuch developer list <notmuch@notmuchmail.org>
Precedence: list

It looks like the python variables do include null, my investigations
show that the problem also effects tag names.

The symptoms can be seen when trying to use the python interface and
using unicode tag names or paths. Instead of seeing 'mytag1' we see 'm'
and instead of '/my/path/to/mail' we see '/' thus causing issues were
the db amusingly was trying to write to root.

I'll see if there is a way to remove the nulls from the strings in the
python bindings.

Martin,

On Wed, 2011-09-14 at 12:38 +0800, Kan-Ru Chen wrote:
> I think as long as the path does not contain embedded null character
> then it is safe. Most posix filesystem does not allow null character
> in
> the filename so you cannot use UTF-16 or UTF-32 to encode the unicode
> path.