Archive of RubyForge sup-devel mailing list
 help / color / mirror / Atom feed
From: William Morgan <wmorgan-sup@masanjin.net>
To: sup-devel@rubyforge.org
Subject: [sup-devel]  [Heliotrope] search for cyrillic terms does not work
Date: Fri, 24 Feb 2012 22:42:57 -0800	[thread overview]
Message-ID: <1330152007-turnsole-69593@terminus-est> (raw)
In-Reply-To: <20120224054318.8144.49786@localhost>

Excerpts from Serge Z's message of 2012-02-23 21:43:18 -0800:
> Can you please suppose why that could happen or offer a simple
> workaround?  This issue is the only one which stops me from migrating
> to Heliotrope/Turnsole.

I'll have to look into it. Super-ascii search was definitely working at
some point, so I'm not sure why there was a regression. You can help by
trying to see whether the problem is in whistlepig or in heliotrope,
e.g. by adding and querying Cyrillic documents in a whistlepig index of
your own construction.

-- 
William <wmorgan@masanjin.net>
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel


  reply	other threads:[~2012-02-25  6:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-24  5:43 Serge Z
2012-02-25  6:42 ` William Morgan [this message]
2012-02-29 10:44   ` Serge Z
2012-03-05 22:57     ` William Morgan

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=1330152007-turnsole-69593@terminus-est \
    --to=wmorgan-sup@masanjin.net \
    --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