Open postiffm opened 7 years ago
Is it possible that the problem with the font size (120pt instead of 12pt) have a link with the stylesheet.xml? I deleted all the .0, in it but it seems to change nothing? (ex: 13.0, I wrote 13).
I do not yet know why this is happening. However, I do know this. Export an odt file from Bibledit-desktop, move it into a new temp directory, and then unzip it. Edit styles.xml so that 13,0 = 13, and 12,0 = 12, etc. I use some macros in my text editor to do that quickly, because there are several hundred occurrences. Then, do zip -r new.odt *. This will repack the ODT file so you can open it in LibreOffice. It will have much better font sizes. I will send you the example that I created.
I've learned more about this bug. Changing the stylesheet will not help. There is either a bug in how we generate the font sizes (13,0) or there is a bug in how LibreOffice processes the file and ignores the comma, thus making the font size 130 instead of 13. I have submitted a bug report at LibreOffice to see what they say, and will let you know. There may be a work-around we can do, but I have to ponder it before making the change.
Hello Matthew, I saw your text, yes it is already almost good, but there is no right margin, the chapter number is out of the text. Really the export tool of Teus (Bibledit) is perfect!! Today I will only use this one. I think if it is possible to import his code this will be the best solution (maybe he can help??) Yesterday I receive a text on Bambara exported with Paratext, and I was proud to see how Bibledit (Teus) export really better!! My hope is to use only Bibledit-Desktop, but for this I need an export tool that does the job right. I also think it's our chance to surpass Paratext, if the quality of the export is still as I saw it... If you need an exemple of the Teus export I can send it.
Our messages crossed!
Please send me the correct (Teus exported) .odt file. You can send to my email instead of through here.
I send you Ruth, if you need something more long, no problem. You can see also the header with the page number and the book name and chapter. 10_Ruth_standard.odt.zip
Here's a little insight:
The comma is generated by printing library as it observes the French locale.
"Which is wrong. It must not write values with localized separators to XML. See xmlschema-2 that defines period ('.' full stop) as decimal indicator."
The above comment is from a LibreOffice developer. So something has gone wrong in how the xml is written...it is not supposed to use comma as a decimal separator. Instead, it should always use a period.
Try it now. Commit e723ad3..4b3811c should fix your problem. Let me know how you like the format of the output, and whether we can close this issue.
Congratulations!! Thanks a lot, it works well. Ok now for the output, it's not difficult I hope it at least as well as that of Teus :) That means, header with page number, and bible book name following with the chapter number (for this he uses the hidden style (See this issue report). embedded the chapter number as a drop cap to the text. And no-break space between the verse number and the text (Teus proposed 3 possibility during export) See this issue. I noticed also a minor problem during export with the markers: va fp ili1 ili2 tc1 tc2 and tr. But now I can report more about it, because the most important is done :)
I can add in the odt output the titles (section header...) are in the text body category, it should be in the title category.
Currently we can't change the police size of the note text style. Should be nice to do it directly in BB-D.
I can add in the odt output the titles (section header...) are in the text body category, it should be in the title category.
My idea was to use the browser tool of LO. But maybe it is not necessary, Teus used the hidden style with the book name and chapter, this is also useful to browser the file.
This might solve some problems that bibledit-desktop export-to-opendocument has experienced.