Description: I use Writer to create both pdfs for imprints and epubs. My current LO is 5.3.7 and I'm testing 6.2.0.0.alpha1 (x64). Since there's no option to export to pdf with trim marks and color bars, I created a pdf with them on another program from a page with a logo on it. I covered the logo with a white square before saving this and importing as bit map on page style. LO 5 correctly imported it without the logo showing, but it wasn't so with LO 6.2, which also made the lines fuzzy. Regarding the epub export, I am using Writer2Latex 1.6 extension (writer2html) in LO 5 and the LO6 default epub export filter. Neither of them created a cover for the book even though I selected an image in the LO 6.2 filter menu. LO 6.2 epub export filter only allows to select either new file at header or page break when it should be able to let you chose whether one or both and at which header level even if it's not adding additional options as W2L does. LO 6.2 epub filter didn't export chapter numbers, which W2L handled correctly. LO 6.2 epub filter added and F in front of the footnote number and added a line between notes, which make it look pretty weird on ADE. And LO 6.2 is not exporting style formating correctly, creating a lot of garbage code in the epub instead of a clean export. I'm copying the output from LO 6.2 epub export filter <p class="para0"><span class="span0">Rom</span><span class="span0">a</span><span class="span0">. </span><span class="span0">(41158 palabras)</span></p> <p class="para1"> </p> <p class="para1"><span class="span1">Nuestros lectores </span><span class="span1">desearán</span><span class="span1"> —al menos esa es nuestra esperanza</span><span class="span1">—</span><span class="span1"> </span><span class="span1">posponer</span><span class="span1"> por unos instantes la explicación que va a tener lugar entre P</span><span class="span1">è</span><span class="span1">trus y Regin</span><span class="span1">e</span><span class="span1">, a fin de seguir </span><span class="span1">en su</span><span class="span1"> peregrina</span><span class="span1">ción a</span><span class="span1"> uno de los héroes de esta historia, héroe abandonado </span><span class="span1">durante mucho</span><span class="span1"> tiempo y </span><span class="span1">en el</span><span class="span1"> que nos parece que </span><span class="span1">querían</span><span class="span1"> inter</span><span class="span1">e</span><span class="span1">s</span><span class="span1">arse</span><span class="span1">. </span></p> Compare the same lines from W2L export <h1 id="toc0"><span class="SectionNumber">CAPÍTULO I </span>Roma. (41158 palabras)</h1> <p class="Standard" lang="fr-FR" xml:lang="fr-FR"> </p> <p class="Standard">Nuestros lectores desearán —al menos esa es nuestra esperanza— posponer por unos instantes la explicación que va a tener lugar entre Pètrus y Regine, a fin de seguir en su peregrinación a uno de los héroes de esta historia, héroe abandonado durante mucho tiempo y en el que nos parece que querían interesarse. </p> You can see that LO epub export filter is not exporting language information, which is used by epub readers to show the right dictionary for the words. Actual Results: Messy epub Fuzzy lines in bitmap Expected Results: Output should have been at least as good as in previous LO for both things: 1. Handling of pdf imports as bitmaps keeping quality 2. epub filter should have been worked from the best existing filter around (Writer2Latex's writer2html) to add up to it. 3. If the software had done trim/crop marks and color bars, I shouldn't have needed another program to create the bitmap. Reproducible: Always User Profile Reset: No Additional Info:
Created attachment 146672 [details] Printscreens from epub and doc
Mark/Miklos: thought you might be interested in this one since it concerns epub part.
FWIW, the output from a document with text copied as plain text and then formatted is cleaner than the output from a working texts with deletions, additions and so on. See example below: Exported with LO 6.2 export as epub. <p class="para8"><span class="span8">Alas de sangre</span></p> <p class="para1"><span class="span7"> </span><span class="span7">Elías Saavedra</span></p> <p class="para9"><span class="span4">Una ira interior luchaba por salir sin que pudiera controlarla y él estaba dispuesto a hacer cualquier cosa con tal de hallar qué era lo que la originaba. Una sensación de rabia que no alcanzaba a comprender y que le reconcomía por dentro.</span></p> <p class="para0"><span class="span4">Branadel había llegado hasta la ciudad Exported with Writer2html (Writer2Latex) <h1 dir="ltr" id="toc1"><a id="RefHeadingToc3066392408007"></a>Alas de sangre</h1> <p class="Autor" dir="ltr"> Elías Saavedra</p> <p class="Primerparrafo" dir="ltr">Una ira interior luchaba por salir sin que pudiera controlarla y él estaba dispuesto a hacer cualquier cosa con tal de hallar qué era lo que la originaba. Una sensación de rabia que no alcanzaba a comprender y que le reconcomía por dentro.</p> <p class="Standard" dir="ltr">Branadel había llegado hasta la ciudad Please, note that class names in the second case have been inherited from parent document while they've been assigned by export filter, even for headers. Versión: 6.2.0.0.alpha1 (x64) Id. de compilación: ff46ad24d1d3cbcea45895520483ed1fd4ff488b Subprocs. CPU: 2; SO: Windows 10.0; Repres. IU: predet.; VCL: win; Configuración regional: es-ES (es_ES); Calc: threaded
Hello Lbartolome. A new major release of LibreOffice is available since this bug was reported. Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Import of pdf as bitmap in page style is now correct on version 6.3 and transparencies are not showing. epub output is as messy as before and not keeping styles. Heading is exporting as <p> +span class instead of <h> and spans are not being closed when changing class or closing tag (h, p...) increasing file size up to 10%. Copying and pasting as text and restyling before exporting is a workaround to get rid of the extra spans, but not viable with texts with hundreds of notes additional to the regular italics and headings. <p class="para3"><span class="span2">En el cual el autor descorre el telón del teatro en que va a representarse su drama.</span></p> <p class="para2"> </p> <p class="para2"><span class="span1">Si el lector quiere emprender conmigo una peregrinación hacia los días de mi juventud y retroceder a la mitad del curso de mi </span><span class="span1">vida</span><span class="span1">, haremos alto al principio del año de gracia de 1827 y diremos a las generaciones que datan de esta época lo que era París, física y moralmente considerado, en los </span><span class="span1">últimos</span><span class="span1"> años de la Restauración.</span></p> <p class="para2"><span class="span1">Empezaremos por el aspecto físico de la moderna Babilonia. De Este al Oeste, pasando por el Sur, París en 1827 era poco </span><span class="span1">mas</span><span class="span1"> ó menos lo que es en 1854. El París de la ribera izquierda es naturalmente estacionario y tiende mas bien a despoblarse que a poblarse; al contrario de la </span><span class="span1">civilización</span><span class="span1"> </span><span class="span1">que</span><span class="span1"> camina de Oriente </span><span class="span1">a</span><span class="span1"> Occidente, París, esta </span><span class="span1">capital</span><span class="span1"> del mundo civilizado, marcha del Sur al Norte: Montrouge invade </span><span class="span1">a </span><span class="span1">Mont</span><span class="span1">m</span><span class="span1">artre.</span></p>
Created attachment 160875 [details] Example ODT with headings Export to EPUB and unzip. section0001.xhtml has <p class="para0"><span class="span0">Heading 1</span></p><p class="para1"><span class="span1">Heading 2</span></p><p class="para2"><span class="span2">Heading 3</span></p> lbartolome: please do not mix several issues into a single report. This will now deal with the headings. If you are still worried about other issues, please create new reports for them. Arch Linux 64-bit Version: 7.0.0.0.alpha1+ Build ID: bdc8cd060dca8a97ef7970d1c0ab30694930beea CPU threads: 8; OS: Linux 5.6; UI render: default; VCL: kf5; Locale: en-US (fi_FI.UTF-8); UI: en-US Calc: threaded Built on 14 May 2020
Reproducible in LO 7.2 alpha1 as described in Comment 6 Version: 7.2.0.0.alpha1+ / LibreOffice Community Build ID: b1c0734ffe0f395757b6e0cea7830d820231afeb CPU threads: 8; OS: Linux 4.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2021-05-18_03:16:20 Calc: threaded
Dear lbartolome, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug