From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.52.236.136 with SMTP id uu8csp77883vdc; Tue, 30 Apr 2013 02:50:17 -0700 (PDT) X-Received: by 10.236.83.173 with SMTP id q33mr4991061yhe.148.1367315416852; Tue, 30 Apr 2013 02:50:16 -0700 (PDT) Return-Path: Received: from rubyforge.org ([50.56.192.79]) by mx.google.com with ESMTP id d47si23707251yhe.30.2013.04.30.02.50.16 for ; Tue, 30 Apr 2013 02:50:16 -0700 (PDT) Received-SPF: pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 50.56.192.79 as permitted sender) client-ip=50.56.192.79; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 50.56.192.79 as permitted sender) smtp.mail=sup-devel-bounces@rubyforge.org; dkim=neutral (bad format) header.i=@gmail.com Received: from localhost.localdomain (localhost [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id E44BB2E0BC; Tue, 30 Apr 2013 09:50:16 +0000 (UTC) X-Greylist: delayed 305 seconds by postgrey-1.31 at rubyforge; Tue, 30 Apr 2013 09:50:05 UTC Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by rubyforge.org (Postfix) with ESMTP id EC7952E068 for ; Tue, 30 Apr 2013 09:50:05 +0000 (UTC) Received: by mail-ob0-f172.google.com with SMTP id v19so269347obq.17 for ; Tue, 30 Apr 2013 02:50:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=ddI3+UL1sYOU17ONvSkDUmuMdtesD+D9qWUS97gAaVs=; b=LMNJk1u85tXpMAWdEoddq76ginFAJtkoz/jPMMUknO8ukKViRfcxWbOJBPVjfBW/Is zALIra1ZBrvpMpRWgAvm6S9voQSMdgFFXhoemN9FwswWbJ9zKQnjF94drRaqOAlJ7mMz eL/A8DHUDA2rsozzWAPF3169usy2Bp6WvpgoCkGb/bzArgLtqq2mgku9Bvs1FLVNrYzF pz3nIPcXfptQpK/R8fBxQA4q9tZADSBK8VP3tDGZF4xnDXo2hSN2oQC9Ze5tFNCjxfVY C9jZB1XyD+MfzVIw7p2mZMkVBLD3QDIdihTeoVR4lfg1Sc2sgCW+d/de89aNSHS9UW6K agWA== MIME-Version: 1.0 X-Received: by 10.60.33.73 with SMTP id p9mr30502883oei.14.1367315096176; Tue, 30 Apr 2013 02:44:56 -0700 (PDT) Received: by 10.182.123.2 with HTTP; Tue, 30 Apr 2013 02:44:56 -0700 (PDT) In-Reply-To: <517E5BD8.6030803@gaute.vetsj.com> References: <1367233230-sup-3593@tesla> <517E5BD8.6030803@gaute.vetsj.com> Date: Tue, 30 Apr 2013 18:44:56 +0900 Message-ID: From: Horacio Sanson To: Sup developer discussion Subject: Re: [sup-devel] sup 0.13 X-BeenThere: sup-devel@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: Sup developer discussion List-Id: Sup developer discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8001386647592959862==" Sender: sup-devel-bounces@rubyforge.org Errors-To: sup-devel-bounces@rubyforge.org --===============8001386647592959862== Content-Type: multipart/alternative; boundary=089e011769cd9a8ee904db90da27 --089e011769cd9a8ee904db90da27 Content-Type: text/plain; charset=ISO-8859-1 Great to see Sup getting back on track again.. I submitted some patches for the Gmail dumper of Heliotrope some time ago but the lack of non alphabet languages (Japanese, Chinese) made it impossible for me to keep using heliotrope/turnesole. The main issue to support Japanese/Chinese with heliotrope was that whistlepig (indexer) lacked the ability to tokenize these languages. Also the half baked UTF-8 support caused several issues with these languages. I would like to help in testing/implementing support for these languages, starting with Japanese, but I would require some guidance. First I would like to know is there is a way to configure the Xapian tokenizer (segmenter) within sup? Please consider that I am new to both sup and to Xapian. Also considering that development of ruby 1.8.x is going to be discontinued on June 2013 I don't find necessary to keep compatibility with it. This would improve UTF-8 support and eliminate the hacks required to support UTF-8 on ruby 1.8.x installations. regards, Horacio On Mon, Apr 29, 2013 at 8:39 PM, Gaute Hope wrote: > > > On 29. april 2013 13:02, Israel Herraiz wrote: > > Excerpts from Hamish D's message of Sun Apr 28 22:32:08 +0200 2013: > >> So the question is, are there any serious bugs that we should fix > >> before releasing 0.13? In particular are there any regressions from > >> 0.12. I'm not aware of any at the moment. > > > > I read the following in the roadmap: > > > > "Release sup-0.13 very soon: will not include maildir support or > > work on Ruby 2." > > > > Does that mean that maildir support will be dropped? Or is it related > > to maildir syncback? Will I be able to read maildirs using Sup 0.13? > > err.. that should have been syncback. maildir support will stay as it is. > > Cheers, Gaute > _______________________________________________ > Sup-devel mailing list > Sup-devel@rubyforge.org > http://rubyforge.org/mailman/listinfo/sup-devel > --089e011769cd9a8ee904db90da27 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Great to see Sup getting back on track again..

I submitted some patches for the Gmail dumper of Heliotrope s= ome time ago but the lack of non alphabet languages (Japanese, Chinese) mad= e it impossible for me to keep using heliotrope/turnesole.

The main issue to support Japanese/Chinese = with heliotrope was that whistlepig (indexer) lacked the ability to tokeniz= e these languages. Also the half baked UTF-8 support caused several issues = with these languages.

I would like to help in testing/implementin= g support for these languages, starting with Japanese, but I would require = some guidance. First I would like to know is there is a way to configure th= e Xapian tokenizer (segmenter) within sup? Please consider that I am new to= both sup and to Xapian.

Also considering that development of ruby 1= .8.x is going to be discontinued on June 2013 I don't find necessary to= keep compatibility with it. This would improve UTF-8 support and eliminate= the hacks required to support UTF-8 on ruby 1.8.x installations.

regards,
Horacio



On Mon, Apr 29, 2013 at 8:39 PM, Gaute Hope <eg@gaute.vetsj.com>= ; wrote:


On 29. april 2013 13:02, Israel Herraiz wrote:
> Excerpts from Hamish D's message of Sun Apr 28 22:32:08 +0200 2013= :
>> So the question is, are there any serious bugs that we should fix<= br> >> before releasing 0.13? In particular are there any regressions fro= m
>> 0.12. I'm not aware of any at the moment.
>
> I read the following in the roadmap:
>
> =A0 "Release sup-0.13 very soon: will not include maildir support= or
> =A0 work on Ruby 2."
>
> Does that mean that maildir support will be dropped? Or is it related<= br> > to maildir syncback? Will I be able to read maildirs using Sup 0.13?
err.. that should have been syncback. maildir support will stay as it= is.

Cheers, Gaute
___________________________________= ____________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel

--089e011769cd9a8ee904db90da27-- --===============8001386647592959862== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel --===============8001386647592959862==--