OnLineBible export issues #51
Comments
{See comment in 47} |
{See comment in 47} |
|
I am getting a flood of the following warnings: For convenience, I have included information about the verse where this Cross Reference was found at the end of each warning. By the way, it would be more convenient if the BibleMultiConverter did it. Some cross references look like they are invalid, but many references are correct. Why they are replaced with plain text? Is it possible to make them also appear as hypertext links? |
To understand this correctly, it is not required to replace newlines by
The documentation you linked (I don't find the link right now) says that cross references have to be either |
I have not shown an example. This is my big oversight. I hope that after the example, everything will be clear. I'll take Ge 3:13 as an example. There are several NewLineCodes Everything in one line. What I suggested is this: Now a four-line verse. Each line starts with a NewLineCode
Yes you are right. The help I gave the link does not contain all the necessary examples. I will have to supplement myself. In the warning list, almost all of the verse range references look correct. Except when verse 999 is indicated. Instead of 999, find the last verse in this chapter. For example, instead of
This displays all the verses from 1 Kings 17:1 to 2 Kings 2:25 or from john 21:1 to Acts 2:11. |
|
Thank you, that indeed clarifies it. So put a newline before every newline marker, but leave the newline marker intact. About finding the last verse: Do you know if the versification mapping is also applied to imported cross references? In other words, if KJV versification is ignored and the last verse of Ex 7 is verse 29, yet the KJV has only 25 verses there, should |
How briefly and clearly this thought can be expressed in English. I see that you have understood me correctly now.
Yes, I know that well. The program does not remap cross references in importing Verse Note. This feature could be expanded in the future. I believe that the information contained in the xxx.RMP file is sufficient for such a remapping.
With that said, there is no need to perform any conversions. But my question is, how do you know that |
|
In verse Ge 10:2 the reference is created as follows: |
A few decades ago I used to program in Delphi 5 too (and Visual Basic 6). However, with the advent of Windows XP it became obvious that Delphi 5 took some design decisions that made it hard or even impossible to write modern user interfaces. That was the point when I switched over to C# and Java.
It is not. Asking a
I do not think I will implement this one. This is again some case where the limited support for references in USX would create a feature in OnLineBible exporter that is hard to get right for other imports and all cases. Probably you can get something similar by postprocessing the files with some regular expressions (as you know that all the references will have this format). And as you said, the reference works fine in OnLineBible anyway. |
- Collapse consecutive whitespace (again) after moving text before footnotes - Add newline character before every `\&` occurrence - Do not move dashes over footnotes, replace en dash by em dash before doing so - Allow cross references to multiple chapters; limit last verse number by versification See #51.
|
I believe all the issues have been fixed. |
|
In the Online Bible there are different types of hypertext linking commands. In the following table is shown the difference between two of them.
In the last column I show how this type of link looks in MyBible. When converting from MyBible to Online Bible the first type of link converts well and the second not. I hope that the table itself in its comprehensive way shows in which way it should be converted. In case clarification is required then I will demonstrate by way of discussion. |
|
Михаил, my converter does not try to implement every feature that two or more Bible formats are supporting, it rather focuses on the common ones (Scripture, Strongs, headlines, footnotes, emphasis, simple cross references). In MyBible, |
Why do you write that the module does not support converting commentary modules? I created two modules: МакАрт-к.SQLite3 and МакАрт-к.commentaries.SQLite3. I launched a utility: As a result I get the result I need. All the footnotes which are in the МакАрт-к.commentaries.SQLite3 module are successfully converted. The For example: Now
Instead, it is necessary that in both cases the transformation took place like this:
You must agree that in this case there is also definitely not the support of a special kind of link but, at the same time the quality of conversion is noticeably better. |
I should have written that the conversion of standalone commnetaries is not supported. Your commentaries.SQLite3 file which has Commentary modules, which contain (at most) one entry for a verse, and are separate from Bible modules (can be scrolled alongside any bible) are supported by many Bible programes, but not by BibleMultiConverter. This is a hobby project I do in my spare time. Therefore, nobody has a (human) right to decide on what I have to spend it on. And I'd rather spend the time in improving conversion of the existing features to more Bible formats (like this whole issue started) than adding even more features which I would then have to add not only for MyBibleZone and OnLineBible, but for all formats that support it (or users of e.g. Logos will rightfully complain that they also want commentary links converted to their format).
Like every other "unsupported" link type, e.g. hyperlink to website or to MyBible's feature pages. When you convert to a roundtrip format (e.g.
This is the wrong attitude. As I wrote, there is no (human) right to create any issues here and GitHub has the tools to block people from commenting on my projects if required. And since the project is open source, you can always give it a try and implement it yourself or pay someone to do so. Pull Requests for new features are welcome, but when you add a new feature, please try to implement it equally well for all Bible formats that support it, if you want me to include it. In your private fork, you can of course implement it as you like (e.g. only for MyBible to OnLineBible, or only when the character set is cyrillic, etc).
This probably depends on the module. What if the text looks like? Will you then want to replace "the next chapter" by "Mt 21:1"?
Debatable. The original module author chose a text for his link, so replacing that text with a canonical verse reference must not necessarily be better. |
|
The bold is saved when converted but the italic isn’t. In the next table is shown in which way the italic should transform in the inner format using the Online Bible.
|
|
As per #47 (comment) and 4f1613a, this is already implemented, except for when the italics appears inside a headline or footnote. If it does not work, please share an example where italics outside of a headline and footnote are not converted. Should the exceptions be removed again? |
The problem just applies namely to the footnote. It has to do with the fact that I didn’t consider one feature of the behavior of Online Bible. Online Bible in the footnotes uses italic only till the code appears |
|
There is the option IncludeStrongs, which allows the Strong's numbers to be placed but there is no option which allows morphology codes to be placed. At present, the morphology codes are accessible in many Greek texts, for example: TR 1550 - Textus Receptus Text and 1881 Westcott Hort Greek Text. Morphology codes in these modules fit in the footnotes "{..........}". |
|
This is not different to other grammar information, like for example Louw-Nida or Lemma, which may be present in the module but have no special syntax in OnLineBible. The StrippedDiffable module provides an option to move such information into footnotes. When you export the result to OnLineBible (or, in fact any format that supports footnotes) they appear as footnotes like you want them. In 87b9a6d I greatly increased the options to decide which kind of information you want to copy to footnotes. So you can just copy Morphology tags to footnotes, but keep Strongs and everything else where it was. Or you can copy both Morphology and Louw-Nida to footnotes, but format Morphology in bold and Louw-Nida in underlined. Or add prefix "Louw-Nida:" to every Louw-Nida footnote. |
If such a option can be done for the StrippedDiffable format then that means that such a option can be done for the OnLineBible format as well. I don’t understand how I can use the result I received in the StrippedDiffable format? if my goal is to convert it to OnLineBible. |
I just don't have the time and resources to add every obscure option that is useful for 1% or less of bibles to all the more than 50 export formats supported by this converter. If anybody supplies patches, I'm glad to review and merge, but as long as nobody has that unlimited time, you have to use the options that are already available.
The Diffable format and its variants have the property that converting from X to Diffable and then Diffable to Y loses no information, when compared with direct conversion. So, for example you can do To convert AFV from MySword to OnLineBible while having all morphology tags in footnotes and Strongs numbers in OnLineBible's native format. |
|
#51 (comment) I made two commands: As a result I received two identical files. I need to copy it in the footnotes and at the same time the Strongs number and Morphological code. May I do that? |
|
I assume you need the morphology.rawtag attribute as the morphology does not follow RMAC or WIVU? This results in morphology not being stored in morphology tags but in extra attributes of type mybiblezone:rawtag:m. (Even if I had added support for exporting morphology to OnLineBible, it would not have been worked, as there are no morphology tags in the converted bible anyway). But I got you covered there, too. In that case, you can use Hope this helps. |
|
#51 (comment) It creates an impression that I don’t know all the possibilities which are in the tool. I want to learn to use the following option: For example: I want the Strongs number to look like this: Can I do something similar to this? |
|
For example: RMAC CONJ assuming the destination format supports bold and italic in footnotes. Fo get something like you desire, I would use custom prefixes like Strongs+Strong: Morph+Morph: and then use regular expressions or similar to replace |
|
Very good explanation. Now everything is understandable. Here is one more problem which, in my opinion, needs a solution. Element “
Modifier 1 is taken into account and modifier 2 is not. For example: This word after the conversion in the OnLineBible format turns into the following: but should be like this: and with the report the change b7644bf is like this: because here the newline is absent. |
|
When there are some bibles who use |
That which you are talking about in MyBible corresponds with tag And so we can boldly talk about the mistake in conversion which is conditioned with the incorrect perception of the |
|
It is indeed a good idea to sometimes look at the latest version of the specification :-) |
When copying Strong's numbers into the footnotes for the New Testament the numbers in the footnotes begin with |
|
@Michahel, thanks for the report. In fact, the issue is not as simple as you thought. When opening the module in MyBible.Zone, the numbers correctly link to the Hebrew Dictionary. In fact, Strong's numbers in MyBibleZone format can contain prefix letters (and some even use X and Y to denote numbers for words that did not exist in the original KJV and therefore have no Strong numbers). But, when numbers have no prefix, a bible can declare in its INFO table what prefix to use:
Only if this is unspecified and the numbers do not have prefixes themselves, it should fall back to use H in OT and G in NT. This logic was broken, I will push a fix later today to correct this import mistake. If you convert again, you will see H as the prefix and export to OnLineBible should work as you expect it. |
|
Pushed in 3bbdf13. |
I am converting USX to OnLineBible Format. The command I am running is
C:\PROGS\BibleMultiConverter>java -Dparatext.allowrefsoutsidefootnotes=true -jar BibleMultiConverter.jar USX N:\Bibles\CARS\Text OnLineBible R:\_CARS.Exp IgnoreKJVWhen trying to check in the Online Bible, I am getting a list of the following errors:
The two spaces before the footnote were found to be the source of the problem. Those.
Text[Space][Space]{Footnote} Textit is unacceptable. It should be like this:Text[Space]{Footnote} Text.Here you can download my dump file to trace it yourself: dump.zip
The text was updated successfully, but these errors were encountered: