A KJV-versified text will work now--and I wouldn't hold my breath for
non-KJV-versification to be widely supported in stable releases soon.
That is to say, I wouldn't discourage releasing the more limited text
now and updating when that is possible.
Okay, sounds good. There are notes that co
Greg Hellings wrote:
I've updated BT to compile against SVN (if you pull the SVN of
Bibletime and apply the patch in the patches directory), but seeing as
I didn't have any modules which were built with either extra-canonical
or alternative versification, I've not been able to test if my change
Daniel Owens wrote:
Chris Little wrote:
Daniel Owens wrote:
Can anyone give me some quick pointers on how to use xml2gbs to
compile a module with deuterocanonical material? I have a source file
I itching to try out, and for now I have resorted to deleting the
extra material using a Perl
On Thu, Dec 18, 2008 at 12:13 AM, Daniel Owens wrote:
>
>
> Chris Little wrote:
>>
>>
>> Daniel Owens wrote:
>>>
>>> Can anyone give me some quick pointers on how to use xml2gbs to compile a
>>> module with deuterocanonical material? I have a source file I itching to try
>>> out, and for now I hav
Chris Little wrote:
Daniel Owens wrote:
Can anyone give me some quick pointers on how to use xml2gbs to
compile a module with deuterocanonical material? I have a source file
I itching to try out, and for now I have resorted to deleting the
extra material using a Perl script so I can compil
Daniel Owens wrote:
Can anyone give me some quick pointers on how to use xml2gbs to compile
a module with deuterocanonical material? I have a source file I itching
to try out, and for now I have resorted to deleting the extra material
using a Perl script so I can compile using osis2mod.
1.
DM Smith wrote:
Chris,
I would like to lobby for a separator between the language code and the
field name. I don't much care whether it is a prefix or suffix. While I
understand that you are suggesting that we don't have a deAbbr or
xxAbbr, I could see that it might be added some time in th
Can anyone give me some quick pointers on how to use xml2gbs to compile
a module with deuterocanonical material? I have a source file I itching
to try out, and for now I have resorted to deleting the extra material
using a Perl script so I can compile using osis2mod.
1. Do I need to compile SW
Thanks Peter. More directly for David:
http://crosswire.org/svn/sword/trunk/locales.d/
Peter von Kaehne wrote:
David Haslam wrote:
Where on the CrossWire site might I find well-attested lists of the 66
booknames (or more if we include deuterocanonical works) in many different
languages?
In
A more authoritative online source to proofread from may be this Oxford:
University press, 1850. scholarly edition.
http://name.umdl.umich.edu/AFZ9170.0001.001
Print source: The Holy Bible, containing the Old and New Testaments, with
the Apocryphal books,
Wycliffe, John, d. 1384., Forshall, Josi
David Haslam wrote:
> Where on the CrossWire site might I find well-attested lists of the 66
> booknames (or more if we include deuterocanonical works) in many different
> languages?
>
> In the course of my Go Bible activities, I have collected a fair number of
> such lists in the past 21 months.
Chris Little wrote:
>
>
> Tom Cornell wrote:
>> On Wed, Dec 17, 2008 at 3:04 AM, Chris Little
>> wrote:
>>> My recommendation was actually that the default be the language of the
>>> module (what I have referred to, perhaps somewhat confusingly, as the
>>> localized name). In the absence of that
DM Smith wrote:
For Hebrew, there are 3 codes (there used to be a 4-th of iw. Java uses
this internally.)
heb and he for Hebrew
hbo for Hebrew, Ancient
Ah, excellent. I did not know about hbo. I'm guessing that's a 639-3
addition.
On a related note, there are multiple scripts for some lan
Tom Cornell wrote:
On Wed, Dec 17, 2008 at 3:04 AM, Chris Little wrote:
My recommendation was actually that the default be the language of the
module (what I have referred to, perhaps somewhat confusingly, as the
localized name). In the absence of that, I recommended using the English.
For ol
Where on the CrossWire site might I find well-attested lists of the 66
booknames (or more if we include deuterocanonical works) in many different
languages?
In the course of my Go Bible activities, I have collected a fair number of
such lists in the past 21 months.
It may be something we can use
DM Smith wrote:
> Chris,
>
> I would like to lobby for a separator between the language code and the
> field name. I don't much care whether it is a prefix or suffix. While I
> understand that you are suggesting that we don't have a deAbbr or
> xxAbbr, I could see that it might be added some time
Hi,
On Wed, Dec 17, 2008 at 9:22 PM, DM Smith wrote:
> Chris,
>
> I would like to lobby for a separator between the language code and the
> field name. I don't much care whether it is a prefix or suffix. While I
> understand that you are suggesting that we don't have a deAbbr or xxAbbr, I
> coul
Hi,
On Wed, Dec 17, 2008 at 10:09 PM, Daniel Owens wrote:
> No license flame wars from me--just wanting to help.
Yes, I understand that and thank for the help/info, it is very appreciated.
It was my mistake by putting that note :)
> I understand the GPL
> issues better having reread the license
Tonny,
No license flame wars from me--just wanting to help. I understand the
GPL issues better having reread the license, but I will stay away from
that one. Basically it seems that you're better off releasing Alkitab as
GPL--that way you don't have to contact those nameless authors...
Danie
DM Smith wrote:
>
> On Dec 17, 2008, at 4:04 AM, Peter von Kaehne wrote:
>
>>
>> I think an argument could be had for following scheme combining both
>> proposals into following:
>>
>> [Config_entry]_original
>>
>> [Config_entry] [locale] and ubiquitous installation of a English locale
>> which i
On Dec 17, 2008, at 4:04 AM, Peter von Kaehne wrote:
I think an argument could be had for following scheme combining both
proposals into following:
[Config_entry]_original
[Config_entry] [locale] and ubiquitous installation of a English
locale
which in turn would be returned by the machin
Chris,
I would like to lobby for a separator between the language code and
the field name. I don't much care whether it is a prefix or suffix.
While I understand that you are suggesting that we don't have a deAbbr
or xxAbbr, I could see that it might be added some time in the future
and w
On Dec 17, 2008, at 3:20 AM, Peter von Kaehne wrote:
On the side note: does anyone know who are the copyright owner of
other available locales (chinese zh and zh_CN, and german de) from
BibleDekstop, so I could ask permission to include those on Alkitab
Bible Study.
The German was done orig
Chris,
I wholeheartedly concur. Description should be the actual title of the
work. There are probably are exceptions.
DM
On Dec 17, 2008, at 2:44 AM, Chris Little wrote:
Peter von Kaehne wrote:
Chris Little wrote:
Could you describe how you think all of these values would be used
practi
On Dec 16, 2008, at 9:16 PM, Chris Little wrote:
Peter von Kaehne wrote:
Language:af means little - Africaans would be nicer. How can I get
there?
See http://www.sil.org/iso639-3/download.asp
The official ISO 639-3 to English list is there under Language Names
Index.
I know that GS h
On Wed, Dec 17, 2008 at 3:04 AM, Chris Little wrote:
> My recommendation was actually that the default be the language of the
> module (what I have referred to, perhaps somewhat confusingly, as the
> localized name). In the absence of that, I recommended using the English.
> For old (all existing)
This discussion is repeating some of the earlier discussion about this
same subject. I repeat one point here:
"FinPR" is meaningless to Finnish people. It is customary to reference
the translation with "KR 1938" or something like that. "Pyhä Raamattu
kirkolliskokouksen 1998 käyttöönottaman
Hi,
On Wed, Dec 17, 2008 at 4:09 PM, Peter von Kaehne wrote:
> Daniel Owens wrote:
>> Aren't the translations released under the same license as jsword, which
>> means you don't need to ask permission? I mean, unless the translators
>> made some effort to apply a different license the contributed
Daniel Owens wrote:
> Aren't the translations released under the same license as jsword, which
> means you don't need to ask permission? I mean, unless the translators
> made some effort to apply a different license the contributed
> translation is under the same open source license as the rest of
Chris Little wrote:
> Since new module .confs would have module name information in the
> module's own locale (provided it is available), I don't believe there's
> really a case where the system/user locale would ever be used.
I can see many cases - where someone wants to keep a different
language
Aren't the translations released under the same license as jsword, which
means you don't need to ask permission? I mean, unless the translators
made some effort to apply a different license the contributed
translation is under the same open source license as the rest of the
code, right? Not a l
Chris Little wrote:
Daniel Owens wrote:
- The default should not necessarily be English. This is what Chris is
suggesting. The default display ought to be in the language that the
module developer decides (usually the language of that module, except
in the case of ancient texts, in which case
> On the side note: does anyone know who are the copyright owner of
> other available locales (chinese zh and zh_CN, and german de) from
> BibleDekstop, so I could ask permission to include those on Alkitab
> Bible Study.
The German was done originally by someone else (do not know who) then
compl
Daniel Owens wrote:
- The default should not necessarily be English. This is what Chris is
suggesting. The default display ought to be in the language that the
module developer decides (usually the language of that module, except in
the case of ancient texts, in which case probably English shou
34 matches
Mail list logo
