104 replies to this topic

[ForbesWilson]

Hi Rob,

Thanks for the help, I think you were right, the pc dropped the connection. I managed to convert both files, and have copied them to my phone, however if I look at the commentary on John 1:1, this is what is displayed " \pard\sb192\sa96\b\fs23 THE WORD (jn 1:1-18)", and the esv bible gives a whole lot of stuff I cannot copy, so I don't know what I have done wrong. I would be happy to send you the files if that would help.

Regards,

Forbes

Edited by ForbesWilson, 17 March 2013 - 07:04 AM.

[Atheist Rob]

The files will likely be larger than the limit for e-mail, so send me a mail (bibsup at hamal.nl) and I will give you some credentials where you can upload the files to. Please do grant me some patience, it's a crazy busy time at the moment, but I'll try to help where I can.

 

Regards,

Rob

[Obot]

Guys,

 

I am a complete newbie both to Mysword and all the techie stories about getting ESV bible to Mysword on my new Honeycomb 4.1.2 Samsung Galaxy Grand. I desperately need the ESV bible on Mysword. IN A VERY SIMPLE AND STRAIGHT FORWARD IDIOT'S GUIDE, how do I get ESV bible on Mysword. I am running Windows 7 laptop 32bits.

 

Very anxious for a timely help.

 

Thanks

Obot. 

[Atheist Rob]

I am a complete newbie both to Mysword and all the techie stories about getting ESV bible to Mysword on my new Honeycomb 4.1.2 Samsung Galaxy Grand. I desperately need the ESV bible on Mysword. IN A VERY SIMPLE AND STRAIGHT FORWARD IDIOT'S GUIDE, how do I get ESV bible on Mysword. I am running Windows 7 laptop 32bits.

 

I created a blog entry that I can reference in other situations as well. I hope is newbie-friendly enough ;-)

 

http://www.biblesupp...ipt-on-windows/

 

Regards,

Rob

[Jonathan Mitchell]

In our attempts to convert the Jonathan Mitchell for MySword we ran into a few issues.  I am hoping you can address them:

1.  My study bible relies heavily on bold and plain text to make verses more readable.  It appears your scripts will only do bold or plain text but not a mix of both?  (My ESword bible is here if you need to see how heavily I rely on bold and plain text)

2.  We ran into a problem with curly braces with the compiled MySword module.  Since RTF (I use LibreOffice 4.1) puts a \ before every curly brace (open and closing) this creates an issue in the text once compiled into MySword.  Is there a way around this?  

Thanks so much for your efforts on this project!

 

Jonathan Mitchell

[Atheist Rob]

In our attempts to convert the Jonathan Mitchell for MySword we ran into a few issues.  I am hoping you can address them:

1.  My study bible relies heavily on bold and plain text to make verses more readable.  It appears your scripts will only do bold or plain text but not a mix of both?  (My ESword bible is here if you need to see how heavily I rely on bold and plain text)

2.  We ran into a problem with curly braces with the compiled MySword module.  Since RTF (I use LibreOffice 4.1) puts a \ before every curly brace (open and closing) this creates an issue in the text once compiled into MySword.  Is there a way around this?  

Thanks so much for your efforts on this project!

 

Jonathan Mitchell

Hi Jonathan,

 

I am currently on a course in Sweden so I can't look at it yet. As soon as I have time (which will be one and a half weeks from now) I will look at it. Can you please provide me a link to the e-Sword text?

 

Regards,

Rob

[Jonathan Mitchell]

Hi Jonathan,

 

I am currently on a course in Sweden so I can't look at it yet. As soon as I have time (which will be one and a half weeks from now) I will look at it. Can you please provide me a link to the e-Sword text?

 

Regards,

Rob

 

 

Thank you for your attention to this matter!  I assume you want the .bblx file and not the rtf.   You might find the communication helpful that I got from MySword on the issues they fixed to have the MySword version look exactly like the ESword version:  

Hi,
 

I just used the E-Sword version as its RTF is more simplified than the original RTF you sent in the simple conversion tool.

The following are the RTF commands considered:

1. \b and \b0
2. \i and \i0
3. \endash and \emdash
4. \ldblquote and \rdblquote
5. \lquote and \rquote
6. \line
7. \{ and \}

The rest were just removed.
 

Also, verse references were converted to cross-reference links but I only have common abbreviations so some might not be picked up. E.g. Mat 1:23. But since most of these are OT references and the Bible is NT only, you will still need to select a different translation for that (unless the Deluxe split view is used where the other pane is a Bible with OT).
 

Attached is the migrated module. Please check. When all is fine, you can give me appropriate text for comments/description (you will see in Menu->About->About Module all about the module), publisher info, copyright info, etc. so that we can place them in the details.
 

Regards,
 

MySword Team

 

http://www.biblesupp...-new-testament/

[Atheist Rob]

Hi Jonathan,
 

Thank you for your attention to this matter!  I assume you want the .bblx file and not the rtf.   You might find the communication helpful that I got from MySword on the issues they fixed to have the MySword version look exactly like the ESword version:

Yes, my script expects a SQLite database file and will convert the text verse by verse.
 

I just used the E-Sword version as its RTF is more simplified than the original RTF you sent in the simple conversion tool.

The following are the RTF commands considered:

• 
  
• \b and \b0
• \i and \i0
• \endash and \emdash
• \ldblquote and \rdblquote
• \lquote and \rquote
• \line
• \{ and \}

The rest were just removed.

 

Ouch, we have an issue here. My script cannot handle "\tag ... \tag0" RTF tags. The script parses the RTF tags recursively and with this form of tagging it is impossible for me to know if "\tag0" is the end of a earlier tag or just a new one. My script expects RTF tags in the form of "{\tag ... }". If you only used start and stop tags for bold and italic, AND you did not use the curly brace form of tagging, it should be easy enough to replace every "\i0" by "}" and every "\i" by "{\i" (and the same for "\b0" and "\b") and feed the result to my script.
I can easily handle "\endash" and the like, that should not be a problem. Regarding the "\{", I thought that was a literal curly brace? How should it be handled? As a grouping tag or as a literal curly brace?
 
Regards,
Rob

[Jonathan Mitchell]

Hi Jonathan,
 

Yes, my script expects a SQLite database file and will convert the text verse by verse.
 

Ouch, we have an issue here. My script cannot handle "\tag ... \tag0" RTF tags. The script parses the RTF tags recursively and with this form of tagging it is impossible for me to know if "\tag0" is the end of a earlier tag or just a new one. My script expects RTF tags in the form of "{\tag ... }". If you only used start and stop tags for bold and italic, AND you did not use the curly brace form of tagging, it should be easy enough to replace every "\i0" by "}" and every "\i" by "{\i" (and the same for "\b0" and "\b") and feed the result to my script.
I can easily handle "\endash" and the like, that should not be a problem. Regarding the "\{", I thought that was a literal curly brace? How should it be handled? As a grouping tag or as a literal curly brace?
 
Regards,
Rob

 

Well, let me be clear, I have no idea what the folks at MySword did but I was told that the steps he needed to take to insure proper formatting given I made heavy use of bolding and curly braces was not the kind of thing that could be compiled and handed out as a means of making MySword modules.  There is no question your tool works but I don't fully understand the complexities.  I use Libreoffice 4.1 to make the RTF and Tooltip to compile the .bblx file.  I do recall something being said when the folks at MySword saw formatting irregularities about limitations in tags used by Tooltip and I know there are flavors to RTF.  I use curly braces as literals because, many times, when drilling down through possible translations of the Greek I find it necessary to use brackets, commas and curly braces.  I was curious if, during the editing pipeline, something could be done on my editing end so that I could still use your scripts to compile without the issues I encountered this time.

[Alleinx]

Well, it works, although the module on which I tested this tool happened to be encrypted and it produced a file recognizable by mysword, but with unreadable characters. So in order not to try converting various modules (in each case it takes quite a long time) my question is how is it possible to find out more quickly whether a module is encrypted or not? Is there any simple method to determine that?