Created attachment 91523 [details] police ean13 créée par grandzébu Problem description: Bonjour, Sur la version 4.1.4.2 de librooffice, apparait un bug lors de l'export pdf de la police code Ean13 (crée par grandzébu, http://grandzebu.net/informatique/codbar-en/ean13.htm). Jusqu'à présent, j'utilisais une ancienne version d'openoffice (3.1.0) et l'export pdf fonctionnait parfaitement pour cette police. Steps to reproduce: 1. taper un texte du type 9HSMHKA*acfjij+ (en respectant la casse). C'est un nombre de 12 chiffres encodé pour créer un gendcod 2. utiliser sur ce texte la police code Ean13 3. exporter en pdf Current behavior: avec une ancienne version d'openoffice, le code-barre (ou gencod) était bien retranscrit Expected behavior: Avec la dernière version de libreoffice, le code-barre est écrasé par l'exportation en pdf. (A savoir le phénomène se produit de la même manière sur Apache open office) cordialement, Jennifer Operating System: Windows 7 Version: 4.1.4.2 release
Hi Jennifer, English language is required here. Can you do it? Thanks, Jacques
Hi Sophie, would you like to translate this bug report for us? :-)
Quick translation: " Hi, On 4.1.4.2 LO version, there's a bug which appears during PDF export of the font "Code EAN13" (which has been created by grandzébu, http://grandzebu.net/informatique/codbar-en/ean13.htm). Until now, I used a former version of OpenOffice (3.1.0) and the PDF export perfectly worked for this font. Steps to reproduce: 1. Type a text like 9HSMHKA*acfjij+ (respect the letter case), it's a number of 12 characters specifically forged to create an EAN (European Article Numbering) code (Translator's note: "GENCODE" was the name of a French organism to manage EAN codes in France) 2. Apply the font "Code EAN13" on this text 3. Export to PDF (translator's note: I've fixed the confusion between current and expected behaviour) Current behavior: With last LO version, the barcode is "crushed" (removed?) by PDF export. (This also occurs in Apache OpenOffice) Expected behavior: "With an old OpenOffice version, the barcode (or gencod) was well exported" (translator's note: Should export ok) Regards. "
Jenifer: pour information, les bugs doivent être déclarés en anglais. (translation: for your information, bugs must be declared in English)
Created attachment 91558 [details] export with 4.1.4.2 On pc Debian x86-64 with LO Debian package 4.1.4.2, I don't reproduce this. The test file export seems ok. (sur Debian x86-64 avec le paquet LibreOffice 4.1.4.2 de Debian, je n'ai pas reproduit le problème. Le fichier d'export de test semble correct).
Created attachment 91560 [details] test with LO 4.1.4.2 on Windows I attached the result of a PDF export on Windows, the barcode is indeed crushed. (J'a joint le résultat d'un export PDF sur Windows, le code barre est effectivement écrasé).
So the problem is confirmed. Michael: any idea who may help here?
Merci Julien pour ta traduction. Je ne savais pas que je devais rapporter le bug en anglais mais tu l'as traduit bien mieux que je ne l'aurais fait! Envoyé depuis mon appareil mobile Samsung -------- Message d'origine -------- De : bugzilla-daemon@freedesktop.org Date :06/01/2014 21:27 (GMT+01:00) A : dinali@free.fr Objet : [Bug 73306] PDF: problème de transcription d'une police par l'export PDF Comment # 5 on bug 73306 from Julien Nabet Jenifer: pour information, les bugs doivent être déclarés en anglais. (translation: for your information, bugs must be declared in English) You are receiving this mail because: You reported the bug.
Created attachment 91614 [details] test on mac I attached a pdf made on Mac OS 10.7.5 with LO 4.1.4 It's quite small (but it was small too on Writer even after having selected font size 16) but not crushed
Hello If it helps I confirm reproduce the problem on windows xp already with version LibreOffice 3.5.0rc1 Version ID : b6c8ba5-8c0b455-0b5e650-d7f0dd3-b100c87 (I have not tested with an older version) I confirm it is ok with OOo 3.2.1 Regards Pierre-Yves
Pierre-Yves: Thank you for your feedback, I update version accordingly. (BTW, about my Windows test, it was with Win7 64)
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.0.5 or 5.1.0) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2016-02-21
Hmm; looks like a font-embedding issue - that's a very odd font, and we would need it in the PDF; did we change the defaults there somewhen ? Either way - unclear why I'm CC'd here =)
** Please read this message in its entirety before responding ** 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
This exports fine on Windows now Version: 6.3.3.2 (x64) Build ID: a64200df03143b798afd1ec74a12ab50359878ed CPU threads: 2; OS: Windows 10.0; UI render: default; VCL: win; Locale: en-US (en_US); UI-Language: en-US Calc: threaded