Problem description: Steps to reproduce: 1. export un file from a professional database "navis editions francis lefebvre" 2. the export is made with "doc" termination but it is html format 3. open the file with writer Current behavior: when opening the french letter "é" and the following lettre are replaced by "?" Expected behavior: correct opening with all letters. This issue doesn't exist with release libreoffice 3.4 neither open office, neither word 2003 This issue exists also with word 14 Platform (if different from the browser): Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20100101 Firefox/13.0.1
Created attachment 63474 [details] file which can't be opened correctly
Created attachment 73765 [details] Bug 51430 - screenshot (In reply to comment #0) > Current behavior: > when opening the french letter "é" and the following lettre are replaced by > "?" Confirmed with: LO 4.0.0.2 Build ID: own W7 debug build Windows 7 Professional SP1 64 bit French letter "é" is substituted by "?", some words are garbled, par. 2 is in bold, there are parts of html tags in the text (/STRONG>). Please see attached screenshot. All good in Word 2010.
*** Bug 67610 has been marked as a duplicate of this bug. ***
Created attachment 94566 [details] console logs + bt with symbols On pc Debian x86-64 with master sources updated today, I had a crash during opening. I attached bt + console.
Here a patch for the crash: diff --git a/sw/source/filter/html/swhtml.cxx b/sw/source/filter/html/swhtml.cxx index 3cdcbf3..9f716cd 100644 --- a/sw/source/filter/html/swhtml.cxx +++ b/sw/source/filter/html/swhtml.cxx @@ -2417,6 +2417,8 @@ void SwHTMLParser::AddParSpace() //What I do here, is that I examine the attributes, and if //I find out, that it's CJK/CTL, then I set the paragraph space //to the value set in HTML_CJK_PARSPACE/HTML_CTL_PARSPACE. + if (!pTxtNode->HasHints()) + return; sal_Bool bIsCJK = false; sal_Bool bIsCTL = false; But real fix or just hide the real bug?
Adding self to CC if not already on
This issue is still present in Version: 5.0.1.2 Build ID: 81898c9f5c0d43f3473ba111d7b351050be20261 Locale: es-ES (es_ES) on Windows 7 (64-bit) @Julien, Does your patch fix the problem? if so, could you please summit it to Gerrit?
(In reply to Xisco Faulí from comment #7) > This issue is still present in > > Version: 5.0.1.2 > Build ID: 81898c9f5c0d43f3473ba111d7b351050be20261 > Locale: es-ES (es_ES) > > on Windows 7 (64-bit) > > @Julien, Does your patch fix the problem? if so, could you please summit it > to Gerrit? It dealt just the crash I had. It building right now so perhaps the crash doesn't appear. Anyway, the fix wasn't intended for the initial bug.
Comment on attachment 94566 [details] console logs + bt with symbols On pc Debian x86-64 with master sources updated today, I don't reproduce the crash. However, I still reproduce the pb of the initial description. I noticed several types of logs: :15: parser error : Input is not proper UTF-8, indicate encoding ! Bytes: 0xE9 0x73 0x20 0x2D <title>Portail des abonn�s - Exporter</title> ^ warn:oox.storage:19117:1:oox/source/helper/zipstorage.cxx:66: ZipStorage::ZipStorage exception opening input storage: VisioDocument: version 0 Found xml parser severity error Input is not proper UTF-8, indicate encoding ! Bytes: 0xE9 0x73 0x20 0x2D warn:legacy.osl:19117:1:xmloff/source/core/xmlerror.cxx:181: An error or a warning has occurred during XML import/export! Error-Id: 0x10020002 Flags: 1 WARNING Class: 2 FORMAT Number: 2 Parameters: 0: style:font-name-asian 1: HG Mincho Light J Exception-Message: warn:unotools.config:19117:1:unotools/source/config/configitem.cxx:445: ignoring XHierarchicalNameAccess to /org.openoffice.Office.WriterWeb/Content/Display/ShowContentTips Exception: Display/ShowContentTips warn:legacy.tools:19117:1:svtools/source/svrtf/svparser.cxx:308: there is a conversion error warn:legacy.osl:19117:1:sw/source/core/access/acccontext.cxx:1154: child context should have a size
** 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.1.5 or 5.2.1 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 helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20160920
Dear pcarmouze, 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
Remove the word "Chinese" in summary as I see no Chinese staff anywhere.
Dear pcarmouze, 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