Date: prev next · Thread: first prev next last
2013 Archives by date, by thread · List index


On Fri, Jul 19, 2013 at 1:30 AM, Nathan Wells <sungkhum@gmail.com> wrote:
Thanks Norbert,

2) I am not sure what makes something qualify for backport, but if this is
needed, is there anything I need to do?

Excuse me in advance if my ignorance of the Khmer language make my
question irrelevant or meaningless, but:
It seems to me that before, we did not handle word-break _at all_...
and with icu we do, but it is not 'perfect'.
So the situation went from 'not supported at all' to 'supported but
with corner case mis-handled.
I then assume that _some_ user of the existing version would be
unhappy of loosing completely a functionality if that felt that worked
'well-enough' for them... and _they_ would file a regression bug if we
rollback that change ?
At a proper version boundary, one could argue that it is necessary...
but it is very harded to argue for that kind of changes between 4.0.n
and 4.0.(n+1), since these dot release are meant to be 'safe' for
user, as in very unlikely to do random behavior changes on you...

Then again, this is a very locale-specific problem, that I admittedly
does not understand much about... so my objections to back-porting it
are mild and should be ignored by dev that knows better :-)... but
that is also why, also it would be technically trivial to revert it...
I'd rather not do it myself.

Norbert

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.