Created attachment 102892 [details] Concordance file with the question mark instead of some characters. Problem description: Concordance file not support all characters. Current behavior: Put a question mark in place of other than ASCII characters. Expected behavior: To support all Unicode characters. Operating System: Windows 7 Version: 4.2.5.2 release
hi, I see this when opening the file in LO 4.2.5.2 and 4.4 master under Win7x64: test;;;;0;0 ?i;;;;0;0 ?inem?;;;;0;0 cândva;;;;0;0 lua?i;;;;0;0 I have no experience with .sdi files... which software should be used to correctly view them?
I think it's a mistake in saving files sdi.
I tested on OS X and sdi file saves fine. If you want to test you can create an index apfabetic and to add a concordance file to add words with different unicode characters.
The file should look like this: test;;;;0;0 și;;;;0;0 ținemă;;;;0;0 cândva;;;;0;0 luați;;;;0;0
ok, please post a screenshot of that .sdi file opened in another software which renders text correctly. regarding this bug, are we dealing with a FILESAVE or rather a FILEOPEN issue?
It is a FILESAVE problem. I have no better program to see the file that it can not because it's misspelled.
TESING with LO 4.3.2.2 + Ubuntu 14.04 (In reply to comment #6) > It is a FILESAVE problem. I have no better program to see the file that it > can not because it's misspelled. Okay, I think I'm now understanding the issue. The attached .sdi file is not Unicode-encoded: $file test.sdi test.sdi: ISO-8859 text, with CRLF line terminators (possible) Repro Steps: - Open LibreOffice Writer (on Windows) - Create a Concordance file as described in the Help files [1] - That includes: - Insert -> Indexes and Tables -> Indexes and Tables -> Index/Table - In the Type box, select "Alphabetical Index". - In the Options area, select the Concordance file check box. - Click the File button, and then choose New - Create a new file, copying-in high-unicode words like și, ținemă, cândva, and luați - Click 'OK'/save the concordance file RESULT: For me, everything worked, and the names appear as expected. The file is unicode: $ file new-sdi-file.sdi new-sdi-file.sdi: UTF-8 Unicode text We'll need someone on Windows who can confirm the behavior you describe. Because this bug is now better-understood, removing needAdvice tag. [1] https://help.libreoffice.org/Writer/Edit_Concordance_File
Confirmed on Windows 7 on master and 3.3.0 using qubit's steps. Version: 4.4.0.0.alpha0+ Build ID: 0a32edcdc2bda75a7536ce7f88c91cbc56e7afb1 TinderBox: Win-x86@39, Branch:master, Time: 2014-09-24_00:45:04 File is encoded in ascii and this was its contents. ?i;?inem?;cândva;lua?i;0;0
** 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.6 or 5.2.3 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-20161108
*** Bug 108910 has been marked as a duplicate of this bug. ***
** 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
The language the reporter is using is romanian. My language is also romanian, so it is easy for me to test this. What I have discovered: I saved the file the reporter attached in description. And to insert there one diacritics from romanian language. And I get the message from the text editor: "We could NOT save the file using Vestic coding (ISO-8859-15). The document contains one or more characters that can not pe coded. Choose another coding from below". After I choose "Romana ISO-8859-16" (meaning romanian language) everything worked perfect.
Now, in order to see if it is our bug, or is a problem by defining ISO I will try to generate a .sdi file from the Writer: 1. Open a new file, Insert Table of Contents - Alphabetical index - Concordance file - New 2. After that I inserted into the .sdi file some romanian characters and they were saved and well rendered in the Index (see the screenshot) For Emilian: please retest this bug with the steps from this comment above (steps 1+2).
Created attachment 164940 [details] working ok
Could be a problem with encoding on Windows See this bug: https://bugs.documentfoundation.org/show_bug.cgi?id=108910
Dear Emilian, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear Emilian, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp