Bug 96861

Summary: "Enable natural sort" is not defined clearly enough in the Bulgarian help
Product: LibreOffice Reporter: kivi <kiv>
Component: CalcAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED INSUFFICIENTDATA    
Severity: normal CC: ilmari.lauhakangas
Priority: medium    
Version: 4.4.7.2 release   
Hardware: All   
OS: All   
Whiteboard:
Crash report or crash signature: Regression By:

Description kivi 2016-01-02 15:20:37 UTC
In the Bulgarian help for Natural sort is stated as follows:
"
Разрешаване на естествено сортиране
Естественото сортиране е алгоритъм, който подрежда текстове, завършващи с числа, според стойността на числовия елемент, вместо по обикновения азбучен ред. Например, да предположим, че имате поредица от стойности от рода на A1, A2, A3, A4, A5, A6, …, A19, A20, A21. Когато ги поставите в област от клетки и стартирате сортирането, ще получите A1, A11, A12, A13, …, A19, A2, A20, A21, A3, A4, A5, …, A9. Този резултат е предсказуем за хората, запознати с вътрешния механизъм на сортирането, но за повечето потребители е странен, ако не и неудобен. Ако е включено естественото сортиране, стойностите като тези от примера се подреждат „правилно“, което означава по-удобна работа със сортирането като цяло.
"
Last sentence in free translation says: If it will be switched on, the valuses as in the example will be ordered "correctly".

It is not clear what to expect as ordered correctly.

My kind suggestion is possibly to change this last sentence and show example what to expect. Some thing like  A1, A2, A3, A4, A5, A6, …, A19, A20, A21 if my understood of Natural sort is correct.
Comment 1 Buovjaga 2016-01-04 11:55:05 UTC
I think you should contact the Bulgarian translators: https://wiki.documentfoundation.org/Local_Mailing_Lists#Bulgarian

Setting to NEEDINFO while waiting for the translators' reaction.
Comment 2 kivi 2016-01-04 16:49:33 UTC
OK
I will try to connect them directly.

But where to sent my suggestion?
Your link does not help me. I see there some group resources only.
Probably announce@bg.libreoffice.org is not applicable, and users@bg.libreoffice.org also.
I am expecting discuss@bg.libreoffice.org also is not a perfect match. 

This is why I decided to make my suggestion as a bug report.

May be it will be better to cancel this bug report, because now I feel it is not so important to bother a bunch of people with it?
Comment 3 Buovjaga 2016-01-04 18:24:27 UTC
(In reply to Krasimir Ivanov from comment #2)
> OK
> I will try to connect them directly.
> 
> But where to sent my suggestion?
> Your link does not help me. I see there some group resources only.
> Probably announce@bg.libreoffice.org is not applicable, and
> users@bg.libreoffice.org also.
> I am expecting discuss@bg.libreoffice.org also is not a perfect match. 
> 
> This is why I decided to make my suggestion as a bug report.
> 
> May be it will be better to cancel this bug report, because now I feel it is
> not so important to bother a bunch of people with it?

I think the "discuss" mailing list would be perfectly fine. After you reach them, you can close this report.
Comment 4 Xisco Faulí 2016-09-11 21:27:54 UTC Comment hidden (obsolete)
Comment 5 Xisco Faulí 2016-10-10 11:13:39 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-20161010