Bug 96433 - New Tai Lue prevowel character selection
Summary: New Tai Lue prevowel character selection
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
5.0.3.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: needsDevAdvice
Depends on:
Blocks:
 
Reported: 2015-12-12 04:42 UTC by martin_hosken
Modified: 2018-01-29 10:36 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 martin_hosken 2015-12-12 04:42:42 UTC
In Unicode 8, the encoding model for New Tai Lue was changed. This changed prevowels from being stored after the base (as per Indic) to being stored before (as per Thai). This change fixes the character iterators to not select a prevowel and the base before it.

The change is minor and should be applied to 5.0, 5.1 and 5.2. It may be found as change I0103ca0da3a39e48416617aab4372cde8be0bbab.
Comment 1 Aron Budea 2016-05-31 05:14:34 UTC
Asking a dev to set this on track.
Comment 2 Xisco Faulí 2017-06-19 12:16:56 UTC
Where am I supposed to find the change I0103ca0da3a39e48416617aab4372cde8be0bbab ? I get a bad object ID in our repo...
Comment 3 QA Administrators 2018-01-02 10:15:26 UTC Comment hidden (obsolete)
Comment 4 QA Administrators 2018-01-29 10:36:28 UTC
Dear Bug Submitter,

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-20180129