similar to: Highlight method creates malformed characters.

i have this error when i try to install ferret C:\Documents and Settings\>gem install ferret Need to update 6 gems from http://gems.rubyforge.org ...... complete Building native extensions. This could take a while... ERROR: While executing gem ... (Gem::Installer::ExtensionBuildError) ERROR: Failed to build gem native extension. ruby extconf.rb install ferret creating Makefile nmake

I am trying to use highlight, but I am getting this kind of thing: /usr/local/lib/ruby/gems/1.8/gems/ferret-0.11.4/lib/ferret/index.rb:197:in `highlight'': IO Error occured at <except.c>:93 in xraise (IOError) Error occured in index.c:1222 - lazy_df_get_bytes len = -5, but should be greater than 0 from

Just a quick note for future reference - at least for me, ferret won''t work on Ruby 1.8.4. gem install ferret Successfully installed ferret-0.11.4-mswin32 ruby -v ruby 1.8.4 (2005-12-24) [i386-mswin32] irb irb(main):001:0> require ''ferret'' A windows error message box appears - ruby.exe - Entry Point Not Found The procedure entry point rb_w32_write could not be

Hi - I upgraded to Ferret 0.11.3 from 0.10.13. I used to index 10,000 records in 10 secs. Now it takes 13 minutes. (That''s a factor of ~75x) Did something change in the flush semantics, or something? Thanks! Schnitz -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hey folks, Sorry for cross posting like this but this is an important announcement for all Ferret users. ** Description ** Firstly for those who don''t know, Ferret is a full-text search library which makes adding search to your application a breeze. It''s much faster than MySQL full-text search as well most other search libraries out there. It allows you to do Boolean (+ruby +

Hello list, I wonder if someone has some tips on joining a ferret search with a database. I have a rails project using a postgresql backend and I would like to utilize the superb performance of ferret for fulltext searching. The problem is that I have to joined the result with the database as I have some user access rights to different documents to take into account. Does anyone have

Hello list, As there is still some large file support bugs in the 0.11.4 release I had to download the trunk and apply a patch sent in by kyle http:// ferret.davebalmain.com/trac/ticket/215. The problem is now that the highlighting doesn''t work. Somehow it combines excerpt_length with num_excerpts so if you have and excerpt_length of 50 and num_excerpts of 5 and you get only one

Hi, I noticed a 0.11.3 release and gave it a whirl. I''ve so far not been able to reproduce any segfaults with my ferret_killer[1] script, though I do get some errors. when the searching process is running and I start the indexing process, I immediately get: /usr/lib/ruby/gems/1.8/gems/ferret-0.11.3/lib/ferret/index.rb:692:in `latest?'': File Not Found Error occured at

I''m still having some crashes on my server that don''t seem to happen on my development system. One difference between them is that the server is running in 64bit mode. Are there any issues running ferret on a 64bit system? I''ve seen some old traffic on the subject but all from about 9 months ago. There are some warnings printed out when I install ferret on the

Folks, Since upgrading to ferret 0.11.4 on Mac OS X Tiger, I''ve been running into constant crashes when running my Rails tests. Here''s an example of the output. -- snip -- 1) Error: test_published_blog_can_be_ferreted(BlogTest): Ferret::FileNotFoundError: File Not Found Error occured at <except.c>:117 in xpop_context Error occured in fs_store.c:329 - fs_open_input

Hi Folks, I''ve just released version 0.9.0. This latest version of Ferret is an alpha release. I have removed the old c extension and Ferret is now running on a fully ported C library. This has allowed some huge performance improvements both with regard to memory and CPU usage. There will probably be a few portability issues to start with. It has been developed on Linux so it should

Hi Everyone, I am currently in process of upgrading Ferret 0..9.1 to Ferret 0.10.9 with Ruby 1.8.4 in windows platform. I am trying to use search highlight feature on index_searcher subject = index_searcher.highlight("subject:(blah blah)", 0, :field => :content, :pre_tag = "<span

I have a problem, I use utf all over a rails site, but the search failes to search characters with acccents... I try to debug it, and i had run unit tests for ferret, can those failures cose problems? <pre> /usr/lib/ruby/gems/1.8/gems/ferret-0.11.3/test/ ruby test_all.rb Loading once Loaded suite test_all Started

I''ve successfully installed ferret and acts_as_ferret and have no problem with utf-8 for accented characters. It returns correct results fot e.g. fran?ais. My problem is with non latin characters (Persian indeed). I have tested different locales with no success both on Debian and Mac. Any idea? (ferret 0.11.4, acts_as_ferret 0.4.0, rails 1.1.6) -- Posted via http://www.ruby-forum.com/.

I would like to thank all the people who have contributed to this very fine project. Great work! I''ve encountered some strange results while examining the term frequency of one of my indexed documents. The indexed terms seem to vary for the very same document depending on the presence or absence of completely unrelated operations in the code, so the resulting term frequency changes, too.

Running gem install ferret and selecting 0.11.3 on a Dual Xeon or Dual Opteron 64 bit box running Debian Etch gives the following list of nasty looking warnings, anyone running successfully on 64 bit linux? Building native extensions. This could take a while... fs_store.c: In function ?fso_seek_i?: fs_store.c:238: warning: format ?%lld? expects type ?long long int?, but argument 4 has type

I need to get a set of terms being indexed using Ferret. I used IndexReader.terms and it returns a list of TermEnum nicely. The only problem is that my analyzer includes a stemming filter. So now, the terms I''m getting back are all stemmed. Is there anyway to get the original unstemmed terms back from the index somehow? Thanks. -- Posted via http://www.ruby-forum.com/.

Hi, I''ve adapted my ferret_killer1.rb script to reproduce the segfaults I''m still having in my app with Ferret 0.11.3. ferret_killer1 didn''t reproduce these - I had to add code to retrieve the documents from the index after searching (and fixed the index creation bug Dave spotted). http://johnleach.co.uk/downloads/ruby/ferret/ferret_killer3.rb To use, in one terminal

Hi folks, I''ve working and playing with acts_as_ferret and follow this fantastic tutorial: http://www.railsenvy.com/2007/2/19/acts-as-ferret-tutorial When I try to implement the field storage tip, it crash. So, I try to make it via script/console: 1. I have a simple model called Articles: class Article < ActiveRecord::Base acts_as_ferret :fields =>

Hi folks, This latest release of Ferret has a lot of improvements. There have been substantial improvements to performance. Try it for yourself to see. I won''t be publishing any numbers just yet. I will say though that it''s still about 2-4 times slower than Lucene with the extension installed. There is also some performance improvements in the pure Ruby version if you