[sword-devel] In Windows command shell, diatheke search is restricted to ASCII for the query key!

[Greg Hellings]

My only thought is that Windows doesn't use UTF-8 internally (it uses
UTF-16), while Sword assumes and demands UTF-8. Perhaps diatheke just
blindly consumes its input as UTF-8, and goes along its merry way?

--Greg

On Thu, Mar 2, 2017 at 11:48 AM, David Haslam <dfhmch at googlemail.com> wrote:

> Greg,
>
> It was worth a test inside cygwin and the result was also a fail:
>
> $ xiphos/diatheke -b KJV -s regex -k Æneas
> Verses containing "ãneas"-- none (KJV)
>
> I tried it with this too, and that fare no better:
>
> $ utils/diatheke -b KJV -s phrase -k Æneas
> Verses containing "ãneas"-- none (KJV)
>
> That's my link to where the utils from our ftpmirror had been downloaded.
>
> Is it even worth installing PowerShell ?
>
> I'm beginning to think that diatheke.exe was never designed to cope with
> non-ASCII searches.
>
>
> David
>
>
>
>
> --
> View this message in context: http://sword-dev.350566.n4.
> nabble.com/In-Windows-command-shell-diatheke-search-is-
> restricted-to-ASCII-for-the-query-key-tp4656866p4656876.html
> Sent from the SWORD Dev mailing list archive at Nabble.com.
>
> _______________________________________________
> sword-devel mailing list: sword-devel at crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.crosswire.org/pipermail/sword-devel/attachments/20170302/794dda1e/attachment.html>