Insert Header Here

-------Original Message-------

I'm sorry I didn't get to the message on sword-support sooner, but I'd 
really appreciate if all new modules were just sent to me.  I apologize 
for seeming like such a control-freak, but there are a lot of factors that 
go into a release that most people don't realize.  There are also a lot of 
standard practices that I'm trying to implement that people seem not to 
notice, but I will try to document them soon.

In general, if anyone wants to send us a new module, they can send it to
my email address or post it online and send me the URL.  Feel free to 
respond to sword-support messages with this information if I haven't seen 
or noticed it.  I also only want source documents (in vpl, imp, thml, or 
osis format) and will compile the module myself.  This protects us from 
the possibility that there are bugs in the module creation tools or the 
version of swordlib that they're built against which might affect the 
content.

I will rename this Bible as "RusVZh" and re-upload once I have compressed 
the text and fixed a couple little problems with the .conf file.

--Chris

On Fri, 21 Mar 2003, Christian Renz wrote:

I have uploadedd Victor's new Russian NT module with Strong's #s. The
module name is "rntvzh".

Victor, I removed the category specification from the module's config
file, as the Install Manager calls this category "Biblical Texts", not
"Bibles" (like you wrote).

I just copied the files into ~ftp/pub/sword/raw and updated
mods.d.tar.gz. Is there anything else I need to do? (Sorry, it's been
a while since I did this).

Greetings,
   Christian

_______________________________________________
sword-devel mailing list
sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel

-- 

Будьте благословенны в Нем,
Виктор Журомский,
Директор Украинского Общества Благодати
_____________________________________________________________
Посетите наши сайты
www.solomonet.org             Grace Fellowship International (en)       
www.gracefellowshipintl.com   Grace Fellowship International (en)
www.inthebeloved.com          Украинское Общество Благодати (ru)
www.christ4you.org            Христианский Информационный Портал (ru)

аСДЭРЕ АКЮЦНЯКНБЕММШ Б мЕЛ,
бХЙРНП фСПНЛЯЙХИ,
дХПЕЙРНП сЙПЮХМЯЙНЦН нАЫЕЯРБЮ аКЮЦНДЮРХ
_____________________________________________________________
оНЯЕРХРЕ МЮЬХ ЯЮИРШ
www.solomonet.org             Grace Fellowship International (en)       
www.gracefellowshipintl.com   Grace Fellowship International (en)
www.inthebeloved.com          сЙПЮХМЯЙНЕ нАЫЕЯРБН аКЮЦНДЮРХ (ru)
www.christ4you.org            уПХЯРХЮМЯЙХИ хМТНПЛЮЖХНММШИ оНПРЮК (ru)

On Mon, 24 Mar 2003, Victor Zhuromsky wrote:

Dear Chris,
could you please, explain to me what tags of ThML to use for making 
Greek-Russian Lexicon module with (1) Strong's numbers, (2) inside 
cross-references, (3) Scripture references and (4) font selection for 
Greek and Hebrew selections.

I would actually recommend using OSIS.  At the moment, it is unsupported 
by Sword, but this will be quickly remedied (as soon as someone un-breaks 
BibleCS).  Once it is, all modules will be converted to OSIS format.  So I 
will answer your questions in terms of both ThML and OSIS:

For ThML: (all documented at http://www.ccel.org/ThML/)
(1) <sync type="Strongs" value="G42" /> marks Strong's Greek lemma 42.
(2) The URI format for ThML is described at 
http://www.ccel.org/ThML/ccel-URI.htm but we do not currently support this 
(and never will).  You may use <a [name|id]="..."> and <a href="..."> 
pairs to link within a single entry, and it will work in those front-ends 
that use HTML for rendering, but you cannot link to other entries and it 
will not work in the Windows front-end.
(3) <scripRef passage="John 3:16">John 3:16</scripRef>  Anything that 
Sword can parse may go into the passage attribute.
(4) Font selection is heavily discouraged and (I hope) not supported.  
Everything should be encoded as UTF-8 and the front-end should be left to 
determine how to assign fonts.  Theoretically, you could use the HTML 
<font> tag.

For OSIS: (documented at http://www.bibletechnologies.net/OSISTools.dsp)
(1) <w lemma="x-Strong:G42">some Greek word</w> achieves the same thing as 
the above <sync> tag in ThML.
(2) Mark targets with osisID attributes and mark <reference> tags with the 
same osisRef value.
(3) <reference osisRef="Bible:John.3.16">John 3:16</reference> achieves 
thesame thing as the above <scripRef> tag, but the value of osisRef must 
be a valid osisRef and the reference itself must follow the book name 
abbreviations described here: 
http://www.bibletechnologieswg.org/osis/specs/BibleBookNames.html .
(4) Discouraged and not possible.  OSIS is entirely semantic, not 
presentational.

--Chris

_______________________________________________
sword-devel mailing list
sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel

On Tue, 25 Mar 2003, Victor Zhuromsky wrote:

Tanks for explanations, but it is really discauraging that I don't have 
such freedom with Sword engine as I would do with amy HTML browser or 
original ThML interpreter, because I use completely different fonts for 
both Greek and Hebrew, that are not to be encoded to UTF-8. The fonts 
are taken from Bible Works project and are bwgrkl.ttf and bwhebb.ttf. If 
I don't apply these fonts, all the greek and hebrew words would be 
without accents, etc.

These are copyrighted fonts that may not be distributed with our text, so 
they are inappropriate for a Sword module.  Furthermore, they are not 
Unicode fonts, so they make it difficult to support other platforms or 
searching in a unified manner.  Even Bibleworks is moving to Unicode for 
their next release.  There is no issue with displaying accents in Unicode, 
you simply need to convert the encoding correctly.  There are a few 
converters specifically for Bibleworks fonts that you can find on the web.

Anyway, I will try making the module in ThML because it is free, but 
OSIS is a commercial language and is not good for use in GNU project. 
That is my opinion.

OSIS is NOT a "commercial language" and I don't have any idea where you 
got that impression.  OSIS is an open standard developed by the ABS, the 
SBL, CrossWire and many others (including people from CCEL).  It is being 
developed in the open.  ThML, on the other hand, is controlled exclusively 
by CCEL (not that this is a reason to not use it).  OSIS is CLEARLY more 
in line with the goals of a GNU project than any other standard for 
marking up Bibles & Bible-related texts.

If you insist on using ThML, you may, but ALL modules WILL be converted to 
OSIS at some time in the future.

One more question. How should i mark my Strong's numbers that they are 
targets in my lexicon, for other bible texts to point to it?

make an IMP file of the following format:

$$$G1
<def>....</def>
$$$G2
<def>....</def>

etc.

G for Greek, H for Hebrew.

They will somewhat confuse the current version of Sword, but in the next 
release, we will be moving to Strong's numbers preceded by a G or H in 
order to remove confusion and come into line with standard practices.

The IMP file itself does not need to be valid ThML, just the parts that 
follow a line beginning with "$$$".

--Chris

_______________________________________________
sword-devel mailing list
sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel

Insert Header Here

Insert Header Here

Insert Header Here

Insert Header Here

Insert Header Here

Insert Header Here

Insert Header Here

Insert Header Here

Chapter 1

Chapter 1

Chapter 1