matt...@matthew-desktop:~$ diatheke -t latin -b ChiUns -f osis -k 1 Sam 1:5
I Samuel 1:5: ￩w savlm="x-Strongs: H05414"￫gěi ￩/w￫ ￩w
savlm="x-Strongs: H02584"￫hā ná ￩/w￫ ￩w savlm="x-Strongs:
H04490|x-Strongs: H0639|x-Strongs: H0259"￫de què shì shuāng fēn ￩/w￫
￩w savlm="x-Strongs: H0157"￫, yīn wèi t
Module: ChiUns 2.1
Transliteration: Latin
ICU 3.4.1
diatheke -t latin -b ChiUns -f osis -k 1 Sam 1:5
I Samuel 1:5: gěi hā ná de què shì shuāng fēn , yīn wèi tā
ài hā ná . wú nài yé hé huá bù shǐ hā ná shēng yù
.
Two problems here in this particular (this is not isolated to this one,
eithe
On May 3, 2009, at 5:46 PM, Chris Little wrote:
In general, I'm planning for the addition of versification systems
to progress slowly and conservatively. So I've recommended to Troy
that we release 1.6.0 with the current set (KJV(A), NRSV(A)
supersets, Leningrad, & MT).
The main reason f
Troy,
It still isn't working. I've had a brief look through the code but
don't see anything obvious. If you can't find something I'll build a
debug version of sword and try to do some more looking, but it will be
a couple of days. I think it should be easy enough to replicate by
simply setting SWO
Troy,
I believe I missed the [Install] part of it. I'll try that and let you know.
Matthew
On Sun, May 3, 2009 at 9:11 PM, Troy A. Griffitts wrote:
> Dear Matthew,
>
> Does the entire contents your sword.conf file look like this:
>
> [Install]
> LocalePath=./
>
> sword.conf exists in your worki
Dear Matthew,
Does the entire contents your sword.conf file look like this:
[Install]
LocalePath=./
sword.conf exists in your working directory on Windows (same location as
you .exe, I believe, unless you specify using a magic .pif file or some
such) and you have a locales.d/ folder also in y
Peter von Kaehne wrote:
Chris Little wrote:
Does that all sound reasonable?
In principle, yes and particularly wrt the conservative approach you
suggest. It would be easy to go overboard with enthusiasm and then
create a mess which will be impossible to clear up.
But wrt the protestant Russia
Chris Little wrote:
> Does that all sound reasonable?
In principle, yes and particularly wrt the conservative approach you
suggest. It would be easy to go overboard with enthusiasm and then
create a mess which will be impossible to clear up.
But wrt the protestant Russian Synodal versification -
In general, I'm planning for the addition of versification systems to
progress slowly and conservatively. So I've recommended to Troy that we
release 1.6.0 with the current set (KJV(A), NRSV(A) supersets,
Leningrad, & MT).
The main reason for this is that a v11n definition must remain stable
Bible translations for Central Asia generally follow the same versification
scheme as the Russian Synodal Translation (RST), as is exemplified in the
SWORD based Holy Bible program (MK) developed for the Institute of Bible
Translation (IBT) for Russia/CIS. Moreover, most Slavic language
translatio
10 matches
Mail list logo
