Find content
Male
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.
