On 12/14/2013 11:14 AM, Greg Hellings wrote:
Since the release of 1.7.0 there have been 3 commits to master:
1) Normalizing licenses and properties, all are differences in comments
2) Kostya's update to a locale
3) A patch "Don't generate linebreaks for , which
comes from USFM //.
Are all three
Printers at that time did a number of things that would be surprising to
us today. Also, things like spellings were not as officially fixed as
they are now. That means that being "faithful to the text", and/or
translators, is not as clear of an objective, with texts that old, as it
is with some
Since the release of 1.7.0 there have been 3 commits to master:
1) Normalizing licenses and properties, all are differences in comments
2) Kostya's update to a locale
3) A patch "Don't generate linebreaks for , which
comes from USFM //.
Are all three of these safe for me to pull into the 1-7-x ma
On 2013-12-14 11:07, DM Smith wrote:
The information is in the wiki (www.crosswire.org/wiki). There's a
links on the home page to pretty much everything that you need to
know. You can also find a transcription of Gen 1 for the 1611 KJV.
Nicely done.
Regarding the effort, go for it. I've ofte
Jeffrey,
There are no GUI tools. Personally, I find that a sometimes GUI makes it harder
not easier. The command line is really easy, but some break out in cold sweat
thinking about it. I find that the command line for osis2mod is incredibly
easy. But I avoid GUI interfaces if I can. But the mo
Check out our wiki, it has all info you would ever need
Sent from my HTC
- Reply message -
From: "Israel"
To:
Subject: [sword-devel] KJV 1611
Date: Sat, Dec 14, 2013 16:01
Sorry for the misinformation. I had thought someone had said there were
no GUI tools, so making a module was not
Sorry for the misinformation. I had thought someone had said there were
no GUI tools, so making a module was not as simple as it could be.
Please forgive my ignorance. I didn't realize it could be done so
easily, do you have links to the info on how to do it, so I can be
better informed and not
I see little relevance to the proposed project, but if you're going to
spend money on a KJV history, get the current, authoritative one:
http://www.amazon.com/Textual-History-King-James-Bible/dp/0521771005/
If you want to read the book David links to, I'd rather recommend
checking it out for fr
Hi Jeffrey,
There is literally no possibility that any characters in the 1611 KJV
have not already been encoded in Unicode. Don't concern yourself with
fonts at all. You don't need to make your own font. And we will not
distribute fonts with modules. Your only concern in this area is
encoding
The character thorn can be found in the Latin-1 Supplement block of
Unicode: Þ
I would suggest investigating the Latin Extended blocks. There are many
fonts that support them. You may find exactly the characters you are
looking for.
You could also check with the Medieval Unicode Font Initiat
Before even contemplating starting such a project, it is advisable to become
acquainted with the detailed textual history of the Authorised Version.
Suggest obtain this book by F H A Scrivener.
*The Authorized Version of the English Bible (1611): Its Subsequent Reprints
and Modern Representatives
11 matches
Mail list logo
