[jsword-devel] Chinese and Chinese Simplified

Matthew Patenaude mnglfiddle at gmail.com
Sat Aug 24 12:48:31 MST 2013


Chris,

I like that idea. It is definitely true that, while conversion between
simplified and complex characters usually does an OK job, it often makes
mistakes that would cause difficulty in search applications.

Matthew Patenaude


On Sat, Aug 24, 2013 at 6:28 AM, Chris Burrell <chris at burrell.me.uk> wrote:

> Hi
>
> Just wondering - do we want to allow Chinese to be searchable regardless
> of whether it is traditional or simplified.
>
> There is a small library (https://code.google.com/p/java-zhconverter/)
> which does the conversion. My understanding is that traditional to
> simplified is unique, and simplified to traditional is not always unique
> (although the library I think only gives you one option).
>
> My thought is that for chinese versions, we add the simplified/traditional
> options in the same field of the index so that we can prevent user errors
> (I've found myself raising a bug against Simplified Chinese not working,
> but it was because I had a traditional Chinese version selected.). We would
> never display these mappings, just use them to return results..
>
> Just a thought.
> Chris
>
>
> _______________________________________________
> jsword-devel mailing list
> jsword-devel at crosswire.org
> http://www.crosswire.org/mailman/listinfo/jsword-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.crosswire.org/pipermail/jsword-devel/attachments/20130824/912b3823/attachment.html>


More information about the jsword-devel mailing list