[notmuch] [PATCH] json_quote_str should handle non-ASCII characters

2010-04-13 Thread Carl Worth
On Thu, 04 Mar 2010 11:40:03 +0100, Gregor Hoffleit wrote: > The current code in json_quote_str() only accepts strict printable ASCII > code points (i.e. 32-127), all other code points are dropped from the > JSON output. > > This patch accepts code points 32-255. Thanks, Gregor! I've pushed

[notmuch] [PATCH] json_quote_str should handle non-ASCII characters

2010-03-04 Thread Gregor Hoffleit
* Sebastian Spaeth [Do M?r 04 14:57:27 +0100 2010] > On 2010-03-04, Sebastian Spaeth wrote: > > The current code in json_quote_str() only accepts strict printable ASCII > > code points (i.e. 32-127), all other code points are dropped from the > > JSON output. > > That would explain why my web

[notmuch] [PATCH] json_quote_str should handle non-ASCII characters

2010-03-04 Thread Sebastian Spaeth
On 2010-03-04, Sebastian Spaeth wrote: > The current code in json_quote_str() only accepts strict printable ASCII > code points (i.e. 32-127), all other code points are dropped from the > JSON output. That would explain why my web interface does not display any umlaut symbols. Nice finding,

[notmuch] [PATCH] json_quote_str should handle non-ASCII characters

2010-03-04 Thread Gregor Hoffleit
The current code in json_quote_str() only accepts strict printable ASCII code points (i.e. 32-127), all other code points are dropped from the JSON output. This patch accepts code points 32-255. json_quote_str() should handle non-ASCII characters. --- json.c |4 ++-- 1 files changed, 2

Re: [notmuch] [PATCH] json_quote_str should handle non-ASCII characters

2010-03-04 Thread Gregor Hoffleit
* Sebastian Spaeth sebast...@sspaeth.de [Do Mär 04 14:57:27 +0100 2010] On 2010-03-04, Sebastian Spaeth wrote: The current code in json_quote_str() only accepts strict printable ASCII code points (i.e. 32-127), all other code points are dropped from the JSON output. That would explain