Bug 161928 - idx formatting/indexing
Summary: idx formatting/indexing
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Linguistic (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All All
: medium trivial
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-07-06 11:17 UTC by Robert
Modified: 2025-12-26 03:11 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Robert 2024-07-06 11:17:08 UTC
first
I understand that the dat and idx are not meant to be user modified; 
and good performance, or reduced overhead of these files and how they are indexed should take precedence.

But, while looking at the idx, I realized that the index was by character, which is not easy to determine without some tools

indexing by line isn't much better, but it might be easier to modify the index.
Comment 1 Buovjaga 2024-08-29 06:29:12 UTC
Do you have performance measurements that show benefits of changing this? I asked about this in the dev chat and idx handling has never shown up in any perf profiles.
Comment 2 QA Administrators 2025-11-25 15:17:02 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2025-12-26 03:11:37 UTC
Dear Robert,

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