Bug 92399 - Always ignore diacritics for Tibetan in search
Summary: Always ignore diacritics for Tibetan in search
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Linguistic (show other bugs)
Version:
(earliest affected)
4.4.4.1 rc
Hardware: x86-64 (AMD64) All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: China-Minority-Scripts Diacritics CTL
  Show dependency treegraph
 
Reported: 2015-06-28 09:59 UTC by Elie Roux
Modified: 2024-08-04 18:30 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
very simple example showing the problem (8.33 KB, application/vnd.oasis.opendocument.text)
2015-06-28 09:59 UTC, Elie Roux
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Elie Roux 2015-06-28 09:59:17 UTC
Created attachment 116884 [details]
very simple example showing the problem

This is certainly a bug quite simple to fix, but it makes Tibetan almost unuseable in LO. The search field seems to search only the first tibetan letter of what's inside it, and finds many false results.

As an example, open the attached file (created with LO 4.4.4.1-beta from Debian/sid. It contains just "ས་ས་ མྲ་ སྲ་". Then open the search bar (Ctrl+F) and paste "སྲ" without the quotes. Click on an arrow, LibreOffice highlights the first "ས་" which it obviously shouldn't.
Comment 1 Elie Roux 2015-06-30 10:33:51 UTC
Changed component to "linguistics". ས་ and སྲ start by the same collation element (ས་) according to http://cgit.freedesktop.org/libreoffice/core/tree/i18npool/source/collator/data/dz_charset.txt , maybe that's the problem? This would be a bug anyway.
Comment 2 Buovjaga 2015-07-02 13:31:39 UTC
Reproduced.

Font download: https://collab.itc.virginia.edu/wiki/tibetan-script/Tibetan%20Machine%20Uni.html

Win 7 Pro 64-bit, Version: 4.4.4.3
Build ID: 2c39ebcf046445232b798108aa8a7e7d89552ea8
Locale: fi_FI

Version: 5.1.0.0.alpha1+ (x64)
Build ID: 3a6ec53eeeec71312f5ea890689f9c2ee79c2aac
TinderBox: Win-x86_64@62-TDF, Branch:MASTER, Time: 2015-07-01_02:24:40
Locale: fi-FI (fi_FI)
Comment 3 Buovjaga 2015-09-02 12:37:02 UTC
Version: (earliest affected)
Comment 4 Elie Roux 2015-09-02 12:55:57 UTC
Beluga, I've just reproduced it with 5.0.1.2, why did you change it back to 4.4.4.1-rc? Was the bug fixed for you?
Comment 5 Buovjaga 2015-09-02 13:02:25 UTC
Please read the version field: Version: (earliest affected)
Reverted change again.
Comment 6 Elie Roux 2015-09-02 13:04:24 UTC
Ok thanx!
Comment 7 Elie Roux 2016-08-15 18:20:35 UTC
With latest master, the bug disappears by unchecking the "Ignore diacritics CTL" in the "Other options" of the search dialogue...

As diacritics should always be ignored in Tibetan (as these are real letters, not optional signs), is there a way to make a by-language setting?
Comment 8 QA Administrators 2017-09-01 11:20:53 UTC Comment hidden (obsolete)
Comment 9 QA Administrators 2020-08-18 05:17:56 UTC Comment hidden (obsolete)
Comment 10 Elie Roux 2020-08-18 06:50:56 UTC
still present in 6.1.5.2
Comment 11 Kevin Suo 2020-11-23 15:54:57 UTC
I do not reproduce this bug behaviour in version 7.1 beta1 and 6.4.7. When search སྲ, Writer hilights the last char, which should be what you expect. Could you confirm?

I set this to NEEDINFO. Please set back to NEW if you still reproduce this with newer version (at least 6.4.7 or 7.0 release).
Comment 12 QA Administrators 2021-05-23 04:20:35 UTC Comment hidden (obsolete)
Comment 13 QA Administrators 2021-06-23 03:49:21 UTC
Dear Elie Roux,

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