Bug 48754 - Hebrew Numbering doesn't work
Summary: Hebrew Numbering doesn't work
Status: RESOLVED DUPLICATE of bug 48043
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.5.2 release
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-16 00:56 UTC by r0bertchik
Modified: 2012-10-26 00:35 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Attachments
native numbering test document (10.56 KB, application/vnd.oasis.opendocument.text)
2012-10-25 23:20 UTC, Lior Kaplan 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description r0bertchik 2012-04-16 00:56:59 UTC 
In the past when I have used OpenOffice, when I selected "Native Numbering", as long as my time/date format was set to use Hebrew, OO would allow me to use correct hebrew consecutive numbering, such that after the letter "י" instead of receiving "כ" as you would using normal "Hebrew" numbering, I would get "יא".

I am using the latest distro of Ubuntu x86 with an English interface. I noticed the change after I upgraded my distro from which the previous one used OO.

I also spoke to Lior about this.
Comment 1 Lior Kaplan 2012-10-25 23:20:52 UTC 
Created attachment 69096 [details]
native numbering test document

When setting the locale to Hebrew (through the command line or in LibO language options), I would get native numbering in Hebrew like you wanted.

Just changing the LC_TIME variable doesn't help (LibO 3.6.3.1 on debian unstable 64bit), and the native numbering are in English. I used "export LC_TIME=he_IL.UTF-8".
Comment 2 Lior Kaplan 2012-10-26 00:17:26 UTC 
I meant LC_NUMERIC=he_IL.UTF-8

In any case, of this is a regression we need to know if which version it worked. I've tested 3.5.3 and no change....
Comment 3 Lior Kaplan 2012-10-26 00:35:15 UTC 

*** This bug has been marked as a duplicate of bug 48043 ***