Hi Uwe, On Wed, Jul 13, 2011 at 09:04:47AM +0200, Uwe Kleine-K?nig wrote: > > But as Carl sais, we cannot guarantee that a tag is utf8 encoded anyway. > I think it would be right to enforce that tags are utf-8 encoded. > Otherwise the users get strange results if they change their locale.
I agree that it would be very nice indeed if it was safe to assume all tags are utf-8. But i also see that it's a bit of an effort to ensure this as all UI's would have to explicitly recode stuff that isn't utf-8. It seems to be a conciously made design decision to allow other encodings for tags, which is up for discussion f course. All I'm saying is that the bindings should conform. And if it's not safe to assume utf-8 here, we shouldn't decode as such. I'm unsure what happens in all the new get_part() parts of the api. If there, all mimepart-text is also returned as utf-8, it would only be consistant to bend tag encodings to utf-8 also. But I doubt thats the case. Can anyone clarify this? /Patrick -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: <http://notmuchmail.org/pipermail/notmuch/attachments/20110713/2c748d5a/attachment.pgp>