Am 21.01.2009 um 05:29 schrieb Chris Little:
ICU is not a requirement for using UTF-8 modules; rather than use
ICU, most frontends (certainly BPBible, GnomeSword, BibleTime and I
think MacSword as well) have defined their own string manager code
(generally using the platform - qt, glib or
Brother Robert Sandrock OSB, the author of T'Nach,
http://www.koenigsmuenster.de/rsk/install.jar
a German freely distributable Bible study programme has kindly allowed
us to import his extensive dictionaries (Greek, Hebrew and Latin) into
CrossWire. These dictionaries have been created by
On Sun, Jan 18, 2009 at 9:23 PM, Chris Little chris...@crosswire.org wrote:
Peter von Kaehne wrote:
If this understanding is correct could we either move them in bulk into
the main repository or- in my view vastly preferable - create a vendor
repository for Wycliffe and move them there?
If
As a side issue of the other debate - how can I achieve NFC for a text I
am working on via commandline utilities?
All I can find in ICU documentation is about programming methods
available, but I have seen no command line utilities.
Peter
___
Daniel Glassey wrote:
On Sun, Jan 18, 2009 at 9:23 PM, Chris Little chris...@crosswire.org wrote:
Peter von Kaehne wrote:
If this understanding is correct could we either move them in bulk into
the main repository or- in my view vastly preferable - create a vendor
repository for Wycliffe
Peter von Kaehne wrote:
As a side issue of the other debate - how can I achieve NFC for a text I
am working on via commandline utilities?
All I can find in ICU documentation is about programming methods
available, but I have seen no command line utilities.
Peter
You can use perl to do it,
glib appears to have a good selection of basic Unicode handling functions.
However, I don't see any reference made to UCA or CLDR. I'm sure they're
implementing the normalization algorithms correctly, but if they aren't
specifically using UCA and CLDR for collation, collation won't be
Peter von Kaehne wrote:
As a side issue of the other debate - how can I achieve NFC for a text I
am working on via commandline utilities?
All I can find in ICU documentation is about programming methods
available, but I have seen no command line utilities.
DM's suggestion of using the Perl
Matthew Talbert wrote:
My bias against ICU is that I have never been able to successfully
compile against it, either on Windows or Linux. That has been quite a
while ago, so I should try again. Also, I believe for a while, ICU
wasn't included in many distros (this is just based off of comments
On Wed, Jan 21, 2009 at 2:05 PM, Peter von Kaehne ref...@gmx.net wrote:
Matthew Talbert wrote:
My bias against ICU is that I have never been able to successfully
compile against it, either on Windows or Linux. That has been quite a
while ago, so I should try again. Also, I believe for a
Have a look at iconv and uconv. One come pretty standard on most UNIX systems
and the other comes with ICU. I can never remember which is which.
-original message-
Subject: [sword-devel] Normalising on the commandline
From: Peter von Kaehne ref...@gmx.net
Date: 21/01/2009 7:59 am
As a side
Chris Little wrote:
uconv -f utf-8 -t utf-8 -x NFC -o output input
Thanks a lot!
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above
Peter von Kaehne wrote:
Chris Little wrote:
uconv -f utf-8 -t utf-8 -x NFC -o output input
Thanks a lot!
Unfortunately learned in the process that my problems with search are
not caused by lack of normalisation, but by inconsistent encoding -
there are three different Arabic/Farsi Unicode
13 matches
Mail list logo
