Jump to content

Please read the Forum Rules before posting.

Photo
- - - - -

Format for creating a dictionary


  • Please log in to reply
38 replies to this topic

#31 Josh Bond

Josh Bond

    Administrator

  • Administrators
  • PipPipPipPipPip
  • 2,882 posts
  • LocationGallatin, TN
Offline

Posted 02 April 2012 - 11:06 PM

Josh & Brent,
Let me join in the chorus here too. RTF code and what to put in and what not to put in is all new to me as well. But what I like about it is that its exciting stuff because it makes me have to learn it in order to be able to achieve the desired result I want.

Now, here is the beaut stuff, the way that e-Sword reads rtf in all its views (windows) and editors is exactly as what Microsoft has put out, and there is no difference. So what you see in the database files of the rtf specifications that needs to be displayed in e-Sword is exactly the same that is used in MS Word 2007 (


For Topics, yes.

For commentaries, dictionaries, devotionals, etc with no RTF header--no, there are differences in the way it's rendered in other RTF viewers and editors. e-Sword wraps these modules with its own RTF header. Therefore, the RTF content we write for these modules types (or T4 writes in most cases), must be compliant with the header e-Sword adds.

For example, what does /f1 mean in Microsoft Word? It means whatever font 1 is set to in the header. In an e-Sword commentary, dictionary, Bible, etc (with no header), \f1 can only mean one thing--the Greek font set the user in e-Sword (which by default is Titus Cyberbit Basic). It could mean hundreds of things in other RTF viewers. Just one example--there's many others.

#32 BH.

BH.

    Utility Developer

  • Contributors
  • PipPipPipPipPip
  • 1,206 posts
  • LocationCalifornia
Offline

Posted 02 April 2012 - 11:11 PM

For Topics, yes.

For commentaries, dictionaries, devotionals, etc with no RTF header--no, there are differences in the way it's rendered in other RTF viewers and editors. e-Sword wraps these modules with its own RTF header. Therefore, the RTF content we write for these modules types (or T4 writes in most cases), must be compliant with the header e-Sword adds.

For example, what does /f1 mean in Microsoft Word? It means whatever font 1 is set to in the header. In an e-Sword commentary, dictionary, Bible, etc (with no header), \f1 can only mean one thing--the Greek font set the user in e-Sword (which by default is Titus Cyberbit Basic). It could mean hundreds of things in other RTF viewers. Just one example--there's many others.

Josh - you said it better that I did....

#33 APsit190

APsit190

    e-Sword Tools Developer

  • Members (T)
  • PipPipPipPipPip
  • 1,943 posts
  • LocationThe Land of the Long White Cloud
Offline

Posted 03 April 2012 - 08:52 PM

<p>

</p>
<p><br />
For Topics, yes.<br />
<br />
For commentaries, dictionaries, devotionals, etc with no RTF header--<em>no, </em>there <u>are</u> differences in the way it&#39;s rendered in other RTF viewers and editors. e-Sword wraps these modules with its own RTF header. Therefore, the RTF content we write for these modules types (or T4 writes in most cases), must be compliant with the header e-Sword adds.<br />
<br />
For example, what does /f1 mean in Microsoft Word? It means whatever font 1 is set to in the header. In an e-Sword commentary, dictionary, Bible, etc (with no header), \f1 can only mean one thing--the Greek font set the user in e-Sword (which by default is Titus Cyberbit Basic). It could mean hundreds of things in other RTF viewers. Just one example--there&#39;s <em>many </em>others.</p>
<p><br />

</p>
<p> </p>
<p>Hi Josh,</p>
<p>In a bblx (SQLite) database file in respect to the languages that e-Sword can handle, in the Details Table, in the Font Record of the Database, the font for the Bible is set. It is this that e-Sword actually reads. So when you see . . .</p>
<ul>
<li>DEFAULT this is the English Font</li>
<li>GREEK</li>
<li>HEBREW</li>
<li>CHINESE</li>
</ul>
<p>and etc, these are the reserved rtf words by Microsoft which e-Sword uses. But what the Font face is used for the language, then that&#39;s a different story. I think (better ask Rick Meyers to be more certain) this is programmably done.</p>
<p> </p>
<p>So; both Hebrew and Greek uses TITUS Cyberbit Basic, and from memory TITUS Cyberbit Basic is \f2 (I think). Now, it really doesn&#39;t matter if \f2 (or whatever it is) that is used to identify the font, because it is that font which has been chosen to read the rtf reserved words for HEBREW and GREEK . All that matters, irrespective of reserved words is that it matches the font that has been chosen for it.</p>
<p> </p>
<p>For example, the Default font for e-Sword right across all its resources/modules is Georgia for English text. It doesn&#39;t matter if its a Bible, Commentary, Dictionary Topic Note, Study Note, or what ever. The reserved rtf word DEFAULT reads it. I changed the default font to Times New Roman right across e-Sword, and the rtf reserved word reads that because its English that its reading. And its that is what matters.</p>
<p> </p>
<p>I had a good play around with the Fonts in e-Sword, and I know that, I to have say, Times New Roman to read Hebrew, it actually looks crap, so it pays to leave the font set at its default. But for English Text it doesn&#39;t matter so much.</p>
<p> </p>
<p>Now getting to your rtf headers, These are the same that Microsoft has put out, there are no differences irrespective of the resource type. bblx modules uses the same rtf code and headers as topic note modules. After all, rtf is rtf any-which-way you want to cut it. Only where differences lie are the versions of rtf code. e-Sword 10x uses rtf version 1.9.1 right across the board. As for he headers themselves, you only have what you want in the viewer. Topic, Study, and Journal Notes would have a few more than the Bible, Commentary, Dictionary and etc viewers. Outside of that, everything else is the same.</p>
<p> </p>
<p>Blessings,</p>
<div>Autograph.png </div>


#34 Josh Bond

Josh Bond

    Administrator

  • Administrators
  • PipPipPipPipPip
  • 2,882 posts
  • LocationGallatin, TN
Offline

Posted 03 April 2012 - 09:14 PM

Hey man, just so we don't propagate bad information here:

1) BBLX files do not use the same headers as Topic files. BBLX cannot have headers at all in 10.x. e-Sword wraps Bibles with a default header. e-Sword does not wrap Topics with a default header. Topics have their own header.

2) e-Sword uses the font's specified in Options/Fonts for cmtx, bblx, dctx, etc with no header. Titus Cyberbit Basic is the default font for Greek or Hebrew, but that can be changed in Options/Fonts. Cmtx, bblx, and dctx with no header make no reference to Titus Cyberbit Basic directly. The rtf only references \f0, \f1, etc (see #3 below).

3) e-Sword does not use the font's specified in Options/Fonts for Topics or study Notes. So the default font (usually Georgia unless the user changed it) does not and is not used as the display font for Topics and Study Notes. Topics and Study notes have their own header, which means they use whatever font the module maker specified.

4) Jonathon posted a nice summary of font designations. \f0 is default English. \f1 is Greek, \f2 is Hebrew (etc). It is absolutely important that text be prefaced with the right font designation. If you have greek text with a \f0 designation, it will display with the default font (usually Georgia unless the user changes in Options/Fonts) instead of the Greek font (usually Titus Cyberbit Basic unless the user changes in Options/Fonts).

You're getting Topics and Study Notes, which have headers, confused with cmtx, bblx, and dctx, which were not designed to have headers.

#35 lbynet

lbynet

    New to Bible Support

  • Veterans
  • Pip
  • 1 posts
Offline

Posted 19 April 2012 - 09:03 AM

Hello, I am  new to this dictionary module project.  I need guidance as to how to produce my first module dictionary.  I do not know how to begin, but I am open to learn.  I would like to know how to start from scratch.  I have been working on a dictionary and I am anxious to added to e-sword.    I need to know what is the format and how to read it as well.  I have all dictionary in an excell format, what is the layout that I need to follow. Your help is most appreciated.  thank you.

#36 patchworkid

patchworkid

    Resource Builder

  • Members (T)
  • PipPipPipPipPip
  • 1,544 posts
  • LocationOld England
Offline

Posted 19 April 2012 - 09:53 AM

hi please read carefully

http://www.biblesupp...-tool-tip-tool/


thanks
Merismos the Scriptures with Patchworkid's Study Bible Set<p>http://www.biblesupp...tudy-bible-set/, MySword -http://www.biblesupp...tudy-bible-set/

#37 Josh Bond

Josh Bond

    Administrator

  • Administrators
  • PipPipPipPipPip
  • 2,882 posts
  • LocationGallatin, TN
Offline

Posted 19 April 2012 - 11:34 AM

Hello, I am new to this dictionary module project. I need guidance as to how to produce my first module dictionary. I do not know how to begin, but I am open to learn. I would like to know how to start from scratch. I have been working on a dictionary and I am anxious to added to e-sword. I need to know what is the format and how to read it as well. I have all dictionary in an excell format, what is the layout that I need to follow. Your help is most appreciated. thank you.


I would recommend using my ToolTIp NT Guide: http://www.biblesupp...revision-21712/

Chapter 3 has step-by-step instructions for creating a dictionary module. Making a simple dictionary with one entry takes less than a minute.

#38 jimb.writer

jimb.writer

    New to Bible Support

  • Members
  • Pip
  • 4 posts
Offline

Posted 19 September 2014 - 09:21 PM

Speaking of Dictionaris, How do we go about placing a Concise Encyclopedic Bible Dictionary IN CHINESE, as a resource for Non-English speakers?



#39 journey

journey

    Resource Builder

  • Members (T)
  • PipPipPipPipPip
  • 637 posts
  • LocationOklahoma
Offline

Posted 19 September 2014 - 10:16 PM

Speaking of Dictionaris, How do we go about placing a Concise Encyclopedic Bible Dictionary IN CHINESE, as a resource for Non-English speakers?

 

I assume it would be a long and difficult process.

 

1.  Start by selecting a dictionary to use that is out of copyright and otherwise legal to use. You certainly wouldn't want to do a lot of work and find out the dictionary you chose can't be used.

 

2.  Obviously, find someone who can translate your selected dictionary into Chinese. There might be some translation type programs that would speed this process, but you would still need a translator to proof-read, etc.

 

3.  Find someone who can work with your finished Chinese translation to the extent that they can make an e-Sword dictionary module. I can only assume they would have to be able to speak and write Chinese fluently.

 

4.  Distribute your finished module here and/or elsewhere.


Philippians 4:6-7 (KJV)
6 Be careful for nothing; but in every thing by prayer and supplication with thanksgiving let your requests be made known unto God. 7 And the peace of God, which passeth all understanding, shall keep your hearts and minds through Christ Jesus.

 





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users




Similar Topics



Latest Blogs