Archive of RubyForge sup-devel mailing list
 help / color / mirror / Atom feed
From: Horacio Sanson <hsanson@gmail.com>
To: Sup developer discussion <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] sup 0.13
Date: Tue, 30 Apr 2013 18:44:56 +0900	[thread overview]
Message-ID: <CAHWBo_aKjp__dkjuJ-tYHpKJuv2G=k_jxTWMo0QyyUtvxZbGXA@mail.gmail.com> (raw)
In-Reply-To: <517E5BD8.6030803@gaute.vetsj.com>


[-- Attachment #1.1: Type: text/plain, Size: 1962 bytes --]

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 <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
> >> 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
>

[-- Attachment #1.2: Type: text/html, Size: 2809 bytes --]

[-- Attachment #2: Type: text/plain, Size: 143 bytes --]

_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel

  reply	other threads:[~2013-04-30  9:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-28 20:32 Hamish D
2013-04-28 20:54 ` Gaute Hope
2013-04-29 11:02 ` Israel Herraiz
2013-04-29 11:39   ` Gaute Hope
2013-04-30  9:44     ` Horacio Sanson [this message]
2013-05-02  8:17       ` Gaute Hope
2013-05-09  1:39         ` Horacio Sanson
2013-05-20  7:24           ` Gaute Hope
2013-05-07 11:54 ` [sup-devel] sup 0.13 - please test Gaute Hope
2013-05-13  7:46   ` Gaute Hope
2013-05-13 23:15     ` Matthieu Rakotojaona

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAHWBo_aKjp__dkjuJ-tYHpKJuv2G=k_jxTWMo0QyyUtvxZbGXA@mail.gmail.com' \
    --to=hsanson@gmail.com \
    --cc=sup-devel@rubyforge.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox