On the "Edit Index" dialog the show be an option to select the delimiter character. Currently only commas are available. Or change the import so it supports ":" as reported here https://ask.libreoffice.org/en/question/77273/opening-rtf-with-index-inclusing-subkeys-fails/
Jim, your comment is clear to me, but I'm not sure how to combine it with your bug summary. Do you have a problem with RTF-Import? If this is the case, please attach that RTF-file and give some informations how to reproduce the bug with the provided file. Thanks. => NEEDINFO
Created attachment 161002 [details] RTF file with index entries Attached with index entries. Forget the part of my bug report about changing the delimiter. If you open this file with Word or OpenOffice you'll see the correct format of the index.
[Automated Action] NeedInfo-To-Unconfirmed
Created attachment 164888 [details] PDF exported from MSO 2013
(In reply to Jim from comment #2) > Created attachment 161002 [details] > RTF file with index entries > > Attached with index entries. > Forget the part of my bug report about changing the delimiter. > If you open this file with Word or OpenOffice you'll see the correct format > of the index. Jim: can you point to some very, very specific thing that we should be looking at here? I don't immediately spot any incorrectness.
(In reply to Buovjaga from comment #4) > Created attachment 164888 [details] > PDF exported from MSO 2013 Ok Attached are two file 1) Adam Dell.RTF 2) Adam Dell.PDF I read the RTF file into MS Word 2019 and created the PDF file. Look closely on page 7 at the index. Try to product the same looking index in LibreOffice from the RTF file. Please let me know if you understand
Created attachment 164902 [details] PDF file attached PDF result from MS Word
Created attachment 164903 [details] RTF file RTF file attached
Ok thanks. Adjusting summary. Arch Linux 64-bit Version: 7.1.0.0.alpha0+ Build ID: d784e711c102f204552c3c816636da01b1085f61 CPU threads: 8; OS: Linux 5.8; UI render: default; VCL: kf5 Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded Built on 29 August 2020
Style looks the same in 3.3.0, but the numbering was incorrect temporarily in 4.4.7. I might bibisect it later just to get some idea of related code paths.
(In reply to Buovjaga from comment #11) > Style looks the same in 3.3.0, but the numbering was incorrect temporarily > in 4.4.7. I might bibisect it later just to get some idea of related code > paths. First change, in win32-5.2 (numbering still not correct): https://git.libreoffice.org/core/commit/93faf178195ca974747849879266783884ae27c5 tdf#87034 RTF import: fix multiple superscripts after footnote ... The numbering became correct with (bibisected with win32-6.0): https://git.libreoffice.org/core/commit/756b2431f0006a01affa7c92c2dede2b11166001 tdf#108949 rtf writerfilter: apply char properties to footnote
Created attachment 177948 [details] The example file in Word and Writer master Seems like there is "Superscript" direct formatting applied to the numbers, which is not supported in Writer: you can simply not highlight and format those endnote numbers. Version: 7.4.0.0.alpha0+ (x64) / LibreOffice Community Build ID: eb69767d7c1bb8e6e780fd9503f08c9d7f5ecb45 CPU threads: 13; OS: Windows 10.0 Build 19042; UI render: default; VCL: win Locale: hu-HU (hu_HU); UI: en-US Calc: threaded
The bug I reported has nothing to do with end notes. It's the index format.
Dear Jim, 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
Bug still exists. About information attached
Created attachment 192346 [details] About LibreOffice As requested about information attached
(In reply to Jim from comment #17) > Created attachment 192346 [details] > About LibreOffice > > As requested about information attached Note for the future: the button next to "Version information" copies the text into your clipboard, so you can paste it anywhere as pure text.