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.
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.
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?
(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.
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team Sun, 11 Sep 2016 21:43:24 +0200
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