Created attachment 123331 [details] the xml file which contains some sayings of prophet mohammad and his progeny peace be upon them which is persian translation. hi every one. i have a valuable document which contains persian translations of some sayings and narrations of prophet mohammad and his progeny peace be upon them. the file is in xml format. when i try to open it with libreoffice, the persian parts of my documents are completely unreadible and are not displayed in persian characters! no matter if i open libreoffice writer, in the file menu i select open, press control+o to activate the open menu. or when the file is selected, right click on it and in the open with submenu, select libreoffice writer. libreoffice does not recognize the encoding and even does not ask to which encoding should it use to open this file properly! as a result, the persian parts of my document, is completely unreadible! i tested this in open office. when i selected file, right click on it and in the open with submenu choosed open office writer, open office asked me about encoding, font and language and finally could open my file properly! steps to reproduce: 1/ right click in the document which i attached. 2/ from open with which is submenu, select libreoffice writer and open the document. 3/ do the same for open office and compare the result. current behaviour: libreoffice does not recognize the encoding of persian parts, cant show it properly and even does not ask for choosing encoding. expected behaviour: libreoffice recognizes the persian encoding, or at least ask me about what encoding should it use. in open office: if i select open in the file menu or press control+o and open this file i get the error: general input output error. when i right click on my file, (by the way, i use the application key and select open with which is submenu) and select open office writer for openning my file, open office asks about encoding, font and language, and finally shows the file properly. i tested many versions of libreoffice and the result was the same. this bug is critical for me. thanks and i request devine mercy and blessings for you.
TESTING with Ubuntu 14.04 64bit + LO 5.2.0.0.alpha0+ (2016-02-24_23:58:47) (In reply to zahra from comment #0) > Document: attachment 123331 [details] > ... > when i try to open it with libreoffice, the persian parts of my documents > are completely unreadible and are not displayed in persian characters! > ... > steps to reproduce: > 1/ right click in the document which i attached. > 2/ from open with which is submenu, select libreoffice writer and open the > document. I'll use the alternate steps ("in the file menu i select open, press control+o to activate the open menu.") > ... > current behaviour: libreoffice does not recognize the encoding of persian > parts, cant show it properly and even does not ask for choosing encoding. > expected behaviour: libreoffice recognizes the persian encoding, or at least > ask me about what encoding should it use. I'm not sure which sections of the document are Persian/supposed to render as Persian. zahra: Please attach a couple of screenshots showing 1) How you expect the document to render (or at least the text) 2) How LibreOffice is rendering the document Please feel free to crop the screenshots, add some (thin) red circles around important parts, etc. Anything that helps us to focus-in on the specific problem makes triage go much more quickly! Bonus: If you can demonstrate the problem with a 1- or 2-page document, that really helps. Simple, simple examples are our favorite! Status -> NEEDINFO
hi. as i mentioned libreoffice does not recognize the encoding and even does not ask me which encoding should it use for openning this xml file! by the way, forgive me to forgot to mention that the encoding of this document is UTF8 compare it with open office as i mentioned. open wich is submenu and select the open office writer in the submenu. then select the encoding utf_8 and open it. you can observe the result and the difference. thanks for your attention.
(In reply to Robinson Tryon (qubit) from comment #1) > I'm not sure which sections of the document are Persian/supposed to render > as Persian. Everything between two open and close tags e.g. <Hadis>?? ???? ?????? ???? ?? ?????? ?? ???? ????? ????? ? ??? ?????? ?? ??????? ? ?? ?? ??? ??????.</Hadis> You can open the xml file with any browser to check (tested with IE11 and Firefox ESR 38.6.1 under Win 10 x64) > zahra: Please attach a couple of screenshots showing > 1) How you expect the document to render (or at least the text) > 2) How LibreOffice is rendering the document Zahra is blind so she can not work with images. The attached file is a good example. I believe this is Docbook format. Opening with Docbook option selected results in a blank page. I believe this is indeed a bug in the Docbook filter.
** 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.2.5 or 5.3.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 helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170306
Dear zahra, 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
Problem still occurs on LibreOffice 6.2.8 and 6.3.3
Dear zahra, 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
If I open it in Writer as text, I see the XML source. By default, it is all set to the font Liberation Mono. In this font, most characters appear to be rendered, but some are not, they are represented as squares (you can see these between the <Source> tags in the first few entries). If I then proceed to change the font to Arial, all characters are rendered. I would close as WFM, but this bug was reported against Windows specifically, and I am using Mac OS. Version: 7.4.0.0.alpha0+ / LibreOffice Community Build ID: e9332dcdc8f2ea268d1b17c73d43a8834cf75365 CPU threads: 10; OS: Mac OS X 12.0.1; UI render: Skia/Metal; VCL: osx Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded
Created attachment 187572 [details] PDF showing how the text is rendered in LibreOffice 7.6 Zahra, could you try with a newer version of LibreOffice? Working well for me with 7.6. This is how I see when opening your file with LibreOffice Version: 7.6.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: b76a3bdc996f275f9d615b32d6ab89d533a7505c CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded