Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of tom@thomas-harding.name
 designates 88.170.168.121 as permitted sender)
Message-ID: <4AA278C8.40302@thomas-harding.name>
Date: Sat, 05 Sep 2009 16:42:16 +0200
From: Thomas Harding <tom@thomas-harding.name>
User-Agent: Mozilla-Thunderbird 2.0.0.22 (X11/20090706)
MIME-Version: 1.0
To: user@couchdb.apache.org
Subject: Re: [HALF-SOLVED] Re: how to handle attachments with couchdb-lucene?
References: <4AA1C2BA.1070008@thomas-harding.name>
	 <39BB2977-3502-4E68-A2DE-DF3EE04C43DA@gmail.com>
	 <46aeb24f0909050232p5893bbc9k14845ae9e163c674@mail.gmail.com>
	 <4AA242A8.1070306@thomas-harding.name>
 <46aeb24f0909050510u7509903dmc3620a1b06f00020@mail.gmail.com>
In-Reply-To: <46aeb24f0909050510u7509903dmc3620a1b06f00020@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Thanks for your response.

So, for text/plain guessed as application/octet-stream I suppose the problem
comes from couchdb itself, as:
"tom@blackberry:~/couchdb-lucene$ file test
test: UTF-8 Unicode text".

On the other hand, for "text/x-patch" and "text/whatether",
Metadata.CONTENT_TYPE
could be filled in tika calls with "text/plain" via a matching table.

'Just an idea... :)

Robert Newson wrote:
> couchdb-lucene uses the content-type stored in couchdb when parsing
> attachments. couchdb-lucene then uses Apache Tika to parse the
> attachments, and it is there that support for new MIME types should be
> requested.
>
> A list of currently supported MIME types is available at;
>
> http://github.com/rnewson/couchdb-lucene
>
> B.
>