Description: When setting the numerals formatting in any numbers field like list numbering, page numbering ... the language set gets back systematically to a same foreign language. For example, if the language is sanskrit (० १ २ ३ ४ ५ ६ ७ ८ ९), libreoffice changes it into farsi when reopening the document. In my installation farsi or persian has never been set anywhere manually as a default language neither it has been used ever. English is set as the default language for western script and Hindi for complex characters. Steps to Reproduce: 1.make a numbered list of items 2.in the "customize" pane of numbering settings, select "१, २, ३, ..." in the list for the field "Number" and click "OK" 3.save and close the document and reopen it. Actual Results: numbers are set to farsi which is the field above "१, २, ३, ...". Farsi is the persian language, its numbers are like this "۱ ۲ ۳". Expected Results: language settings should not be automatically reset. Reproducible: Always User Profile Reset: No OpenGL enabled: Yes Additional Info: nothing
6.2.5 is quite old. Please give a try to last stable LO version 6.4.7 or brand new 7.0.3
(In reply to Julien Nabet from comment #1) > 6.2.5 is quite old. > Please give a try to last stable LO version 6.4.7 or brand new 7.0.3 i tried with LO 6.4.6,, the bug is still there.
[Automated Action] NeedInfo-To-Unconfirmed
I precise that this problem occurs specifically with sanskrit numerals. I tried with nearly all available types of numerals and so far only with sanskrit i'm observing this problem. I even tried after deleting ~/.config/libreoffice. Then in the Options menu "language settings">"languages" "complex text layout must be enabled for sanskrit numerals being available in the "bullets and numbering" customisation settings.
Reproduced. Arch Linux 64-bit Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: a58b9010b38ca43d4b3a2b30fcd6bec28db1b344 CPU threads: 8; OS: Linux 5.13; UI render: default; VCL: kf5 (cairo+xcb) Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded Built on 31 August 2021
Is there any chance that someone solves this problem?
this was reported much later than this one but seems to have caught greater attention: https://bugs.documentfoundation.org/show_bug.cgi?id=141565
*** This bug has been marked as a duplicate of bug 141565 ***