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 en
So what flavour of regex does diatheke actually use under Linux?
Why is it that the *dot metacharacter* is not recognized?
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/diatheke-search-type-regex-and-the-dot-tp4656879p4656889.html
Sent from the SWORD Dev mailing
Created http://tracker.crosswire.org/browse/MODTOOLS-101
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/diatheke-search-type-regex-and-the-dot-tp4656879p4656890.html
Sent from the SWORD Dev mailing list archive at Nabble.com.
_
Why not make this a permanent URL in addition to the original one?
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/CrossWire-Bug-Tracker-upgrade-tp4656681p4656891.html
Sent from the SWORD Dev mailing list archive at Nabble.com.
One of the *diatheke* output filter options is *-o r* for Arabic Shaping.
There seems to be no corresponding *GlobalOptionFilter* defined in our wiki
page for .conf files.
https://crosswire.org/wiki/DevTools:conf_Files#Elements_required_for_proper_rendering
Is there something missing that merely
To print on the Linux console diatheke output from Arabic script texts
both the options shaping and bidi are required.
They do work and are not vapourware.
Peter
On Fri, 2017-03-03 at 06:41 -0800, David Haslam wrote:
> One of the *diatheke* output filter options is *-o r* for Arabic
> Shaping.
Thanks Peter,
Are both these diatheke options necessary only in Linux ?
What would happen if a Windows user specified/omitted them ?
Does shaping apply for all the languages that use Arabic/Persian script?
Do any languages such as Pashto or Dari have any letters that shaping
doesn't yet fully su
I have just added a new section in the wiki page:
https://crosswire.org/wiki/Frontends:Diatheke#Diatheke_option_filters
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/Arabic-shaping-tp4656892p4656895.html
Sent from the SWORD Dev mailing list archive at Nabble.com
An old thread from 2012 but something new to ponder for this module.
If anyone fancies a project in *text development*, now that Unicode 9.0
includes a new block for *uppercase Cherokee letters*, rewriting the source
text for the Cherokee NT and making use of the new letters would be an
interestin
Probably will in some form or another.
-- DM
> On Mar 3, 2017, at 9:37 AM, David Haslam wrote:
>
> Why not make this a permanent URL in addition to the original one?
>
> David
>
>
>
> --
> View this message in context:
> http://sword-dev.350566.n4.nabble.com/CrossWire-Bug-Tracker-upgrade
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 dea
SWORD supports compiling with a variety of regex engines-- typically GNU
regex on most linux system. We include 'internal regex' copy of this,
as well. We also will compile against the C++ standard regex engine
including the language spec. Each handles unicode characters different.
. is cer
12 matches
Mail list logo
