On Sun, Mar 18 2018, Daniel Kahn Gillmor wrote:
> https://tools.ietf.org/html/rfc3282 describes a Content-Language:
> header. https://tools.ietf.org/html/rfc8255 describes
> a multipart/multilingual Content-Type.
>
> notmuch currently uses xapian with a hard-coded English stemmer which
> works gr
On Sun 2018-03-18 21:32:35 +0200, Jani Nikula wrote:
> On Sun, 18 Mar 2018, Daniel Kahn Gillmor wrote:
>> * if we know our index expects english, and we have a message part that
>>*is not* english (e.g. Content-Language: es), we could avoid indexing
>>that part.
>
> Why would we do that?
On Sun, 18 Mar 2018, Daniel Kahn Gillmor wrote:
> * if we know our index expects english, and we have a message part that
>*is not* english (e.g. Content-Language: es), we could avoid indexing
>that part.
Why would we do that? Search mostly works just fine for non-English
languages, it's
Daniel Kahn Gillmor writes:
> AIUI, xapian is pretty much committed to being a single-language
> indexer. But i just wanted to point out that it's possible that we
> could be smarter about this in notmuch, and wanted to make a space for
> possible design discussion.
>
More precisely, it uses a
https://tools.ietf.org/html/rfc3282 describes a Content-Language:
header. https://tools.ietf.org/html/rfc8255 describes
a multipart/multilingual Content-Type.
notmuch currently uses xapian with a hard-coded English stemmer which
works great for me as a monolingual American, but limits the
applica