Yes - of course! Encoding=UTF-8
It's not primarily a font issue, even though that might be a further annoyance in Xiphos. Having a font without coverage for the Coptic block in question cannot by any stretch of logic account for a search that finds 622,900% of the only 2 true matches. A font can only operate when the results are displayed, not during the search "under the hood". As regards entering the search term in Xiphos, the font in the GUI clearly doesn't support the Coptic block. If however, you copy the word back from the search key field and paste it into BabelPad, it's quite certain that the word was unchanged. The Coptic Bible text displays fine by Xiphos and PocketSword when viewed normally. This thread only relates to the search feature of these front-ends (and any others based on SWORD that use the same Lucene). btw. Would it be true to assume that ticking "fuzzy search" in PocketSword in effect says "goodbye" to Lucene? Best regards, David PS. My updated .conf file is in the attached Zip (if this works herewith). Already submitted to the modules team with a request to update the module to version 1.1.1 Included here FIO. It makes no difference to the matter being pursued. Mostly correcting elementary mistakes that were there from the first release. -- View this message in context: http://sword-dev.350566.n4.nabble.com/Lucene-search-index-and-Coptic-tp4657103p4657115.html Sent from the SWORD Dev mailing list archive at Nabble.com. _______________________________________________ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
