In N'ko, we have our own digits. Here are the n'ko digits : ߀ ߁ ߂ ߃ ߄ ߅ ߆ ߇ ߈ ߉ Is it posible to replace the latin digits by the above n'ko digits ? I know that fix that might be complicated because of "%d", "%f".... This efature is not only for n'ko. Eastern-arabic and Hindi numerals are not supported. PS : don't forget that n'ko is a RTL language, then to write the number one hundred twenty three (123), we write "321" with n'ko digits.
Marking as NEW - valid enhancement request (see bug 64331 for N'ko locale details).
I can't find a way to install a N'ko font in LibreOffice. So, I am not able to check this bug. Could you, Kairaba, explain how you installed a N'ko font, please? Thanks
Dear Kairaba, 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 INSUFFICIENTDATA 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 MassPing-NeedInfo-Ping
Dear Kairaba, 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