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

On 2017-03-02, 18:51 GMT, Greg Hellings wrote: > 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? Are we really sure CP850 is really

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

On 2017-03-02, 16:14 GMT, David Haslam wrote: > S:\>xiphos\diatheke -b KJV -s regex -k Æneas > Verses containing "ãneas"-- none (KJV) > > It changes the non-ASCII characters to something else entirely! > > Such a diatheke command works OK in Linux, or so I'm told. That’s the crazy state of dual

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

This wchar in Windows is UTF-16. https://msdn.microsoft.com/en-us/library/windows/desktop/ff381407(v=vs.85).aspx Manfred > Am 02.03.2017 um 19:51 schrieb Greg Hellings : > > My only thought is that Windows doesn't use UTF-8 internally (it uses > UTF-16), while Sword

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

Thanks, Greg. That's the best explanation that I've seen so far. 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-tp4656866p4656880.html Sent from the SWORD Dev mailing list archive

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

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 wrote: >

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

On Thu, Mar 2, 2017 at 11:50 AM, Karl Kleinpaste wrote: > On 03/02/2017 12:17 PM, David Haslam wrote: > > I am assuming that when Karl bundles these with Xiphos, he just uses what's > available and most recent in our SVN. > > I don't build/bundle them. They're whatever Greg

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

Exactly how they get compiled is beyond my pay grade. Even the jargon in your reply is outside my ken. ;>) 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-tp4656866p4656877.html

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

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

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

On 03/02/2017 12:17 PM, David Haslam wrote: > I am assuming that when Karl bundles these with Xiphos, he just uses what's > available and most recent in our SVN. I don't build/bundle them. They're whatever Greg built into the MinGW Sword RPM. The Windows build script just includes them in the

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

The only reason I'm using the Sword utilities bundled with Xiphos is because they happen to be a more recent version than what I can find in the ftpmirror on our server. The former has diatheke version 4.7 and the latter diatheke version 4.6 I am assuming that when Karl bundles these with

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

Thanks Karl. I suppose Linux also succeeds when the *en dash* is properly used with any of the "hyphenated" names such as: Abel–beth–maachah Under Windows CMD, diatheke changes these to U+00FB LATIN SMALL LETTER U WITH CIRCUMFLEX. S:\>xiphos\diatheke -b KJV -s phrase -k Abel–beth–maachah

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

On Thu, Mar 2, 2017 at 10:27 AM, David Haslam wrote: > Hi Greg, > > Windows 7 x64 using ordinary cmd.exe as the command shell. > > Do you think I'd get better results if I called diatheke.exe from inside a > cygwin shell ? > I think that I don't like to think about

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

On Thu, Mar 2, 2017 at 10:29 AM, Karl Kleinpaste wrote: > On 03/02/2017 11:14 AM, David Haslam wrote: > > Such a diatheke command works OK in Linux, or so I'm told. > > $ diatheke -b KJV -s regex -k Æneas > Entries containing "Æneas"-- none (KJV) > $ diatheke -b KJV -s

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

Hi Greg, Windows 7 x64 using ordinary cmd.exe as the command shell. Do you think I'd get better results if I called diatheke.exe from inside a cygwin shell ? btw. I've never used Windows PowerShell. I even had to look it up in https://en.wikipedia.org/wiki/PowerShell How come this only came to

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

On 03/02/2017 11:14 AM, David Haslam wrote: > Such a diatheke command works OK in Linux, or so I'm told. $ diatheke -b KJV -s regex -k Æneas Entries containing "Æneas"-- none (KJV) $ diatheke -b KJV -s lucene -k Æneas Entries containing "Æneas"-- Acts 9:34Acts 9:33 ; -- 2 matches total (KJV) $

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

Don't use Windows? But in all seriousness, is this in CMD or PowerShell? What version of Windows is this? You very possibly could be running into a limitation of the operating system. --Greg On Thu, Mar 2, 2017 at 10:14 AM, David Haslam wrote: > This simply doesn't work

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

This simply doesn't work inside the Windows command line shell. S:\>xiphos\diatheke -b KJV -s regex -k Æneas Verses containing "ãneas"-- none (KJV) It changes the non-ASCII characters to something else entirely! Such a diatheke command works OK in Linux, or so I'm told. Is there a solution?