MyBible to USFM/USX issues about biblemulticonverter HOT 2 CLOSED

Thank you for your report.

First, you are using USFM export filter but a .usx file extension, but that was probably just a mistake.

I am not sure what the desired outcome is for you (i.e. how you would expect the program to behave instead). There are obviously situations where Bible formats have features that can not (with acceptable effort) be mapped to other Bible formats, and warnings are there to tell you when this happens to give an indication where you may improve the quality by manually editing the input file, an intermediary Roundtrip file or the output file.

Do you want an option to not show such warnings, or to count/tally them instead of printing them when they are encountered? Or are the warnings unclear and need better wording? Or do the warnings result in a suboptimal output file and you want to suggest how conversion could have been improved here?

For the first warning, WARNING: Raw HTML is not supported: MyBible SQLite format can embed arbitrary HTML inside of footnotes and introduction texts. Your example module includes Facebook links, ordered lists with various CSS, etc. Only a very limited set of tags are converted to actual Bible format features, all the othe tags are stored as "Raw HTML" in the output format. If the destination format also supports Raw HTML, these information can be preserved that way. USFM/USX, on the other hand, does not support any HTML, so it can only export the tags which are supported. Raw HTML Tags will get stripped, but the text content will be preserved. I do not have plans to increase the number of HTML tags that can be converted, so in case there is anything important in the input HTML, I'd suggest to edit either in the source format or in an intermediate Roundtrip format.

The second warning is about a Formatting tag with custom CSS, which has no output mapping for USFM. The tag originally was a <n> tag in MyBible.Zone, and proably it would be a good idea to map it to \add USFM tag here. I will be improving this by matching this to \add, and also add a fuzzy matcher, so that if there was no exact mapping, it would find the italic and make it an \it tag instead. This can also be done manually in the Bible file, or by using the OptimizeFormatting option of StrippedDiffable, e.g.

OptimizeFormatting 'C=font-style: italic; myBibleType=note->F=ITALIC'

To replace all custom formatting with the given CSS by Italic formatting.

In both cases, the resulting file should be usable without any postprocessing, if you can live with the non-optimal tagging.

from biblemulticonverter.

Closing for inactivity. Feel free to reopen in case anything is still open for you.

from biblemulticonverter.