Daniel Kahn Gillmor <d...@fifthhorseman.net> writes:

> (sorry for the late reply to this thread)
>
> On Thu 2019-02-21 15:11:48 -0400, David Bremner wrote:
>> to be unique case-insensitively, so I decided to convert them to lower
>> case on input. This turns out to be "fun", if we try to handle things
>> other than ASCII.  So one option is to just insist prefixes are ASCII.
>>

> I have no problem with asserting that all character strings in the
> notmuch database are UTF-8.  That's just the only sane thing to do in
> 2019.  But if we build any feature into notmuch that makes assumptions
> or requirements about upper-casing, lower-casing, or collating strings,
> and that feature interacts between the currently-running locale and
> whatever locale was used to store data in the the database in the past,
> and those locales can differ, we may be inflicting some subtle pain on
> users.

I eventually settled on 4b9c03efc, which will probably do strange thing
to people who define non-ascii prefix names in non-utf8 locales. I'm OK
atm with just saying that is unsupported.

d
_______________________________________________
notmuch mailing list
notmuch@notmuchmail.org
https://notmuchmail.org/mailman/listinfo/notmuch

Reply via email to