Unicode Paths

2011-09-16 Thread Sebastian Spaeth
On Thu, 15 Sep 2011 13:52:12 -0400, Austin Clements wrote: > On Tue, Sep 13, 2011 at 11:55 PM, Martin Owens wrote: > > Hello Again, > > > > I notice in the lib code notmuch_database_open(), > > notmuch_database_create() these functions use const char *path for the > > directory path input. Is thi

Re: Unicode Paths

2011-09-16 Thread Sebastian Spaeth
On Thu, 15 Sep 2011 13:52:12 -0400, Austin Clements wrote: > On Tue, Sep 13, 2011 at 11:55 PM, Martin Owens wrote: > > Hello Again, > > > > I notice in the lib code notmuch_database_open(), > > notmuch_database_create() these functions use const char *path for the > > directory path input. Is thi

Unicode Paths

2011-09-15 Thread Austin Clements
On Tue, Sep 13, 2011 at 11:55 PM, Martin Owens wrote: > Hello Again, > > I notice in the lib code notmuch_database_open(), > notmuch_database_create() these functions use const char *path for the > directory path input. Is this unicode safe? > > The python bindings (and ctype docs) seem to suggest

Unicode Paths

2011-09-15 Thread Martin Owens
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

Re: Unicode Paths

2011-09-15 Thread Austin Clements
On Tue, Sep 13, 2011 at 11:55 PM, Martin Owens wrote: > Hello Again, > > I notice in the lib code notmuch_database_open(), > notmuch_database_create() these functions use const char *path for the > directory path input. Is this unicode safe? > > The python bindings (and ctype docs) seem to suggest

Re: Unicode Paths

2011-09-15 Thread Martin Owens
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

Unicode Paths

2011-09-14 Thread Kan-Ru Chen
Martin Owens writes: > Hello Again, > > I notice in the lib code notmuch_database_open(), > notmuch_database_create() these functions use const char *path for the > directory path input. Is this unicode safe? > > The python bindings (and ctype docs) seem to suggest using something > called 'wchar

Unicode Paths

2011-09-13 Thread Martin Owens
Hello Again, I notice in the lib code notmuch_database_open(), notmuch_database_create() these functions use const char *path for the directory path input. Is this unicode safe? The python bindings (and ctype docs) seem to suggest using something called 'wchar_t *' for accepting unicode but that'

Re: Unicode Paths

2011-09-13 Thread Kan-Ru Chen
Martin Owens writes: > Hello Again, > > I notice in the lib code notmuch_database_open(), > notmuch_database_create() these functions use const char *path for the > directory path input. Is this unicode safe? > > The python bindings (and ctype docs) seem to suggest using something > called 'wchar

Unicode Paths

2011-09-13 Thread Martin Owens
Hello Again, I notice in the lib code notmuch_database_open(), notmuch_database_create() these functions use const char *path for the directory path input. Is this unicode safe? The python bindings (and ctype docs) seem to suggest using something called 'wchar_t *' for accepting unicode but that'