<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - There is a string display error with numbers above 10 about All Korean Numeric text and Japanese Modern Numeric text"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=130140#c9">Comment # 9</a>
on <a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - There is a string display error with numbers above 10 about All Korean Numeric text and Japanese Modern Numeric text"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=130140">bug 130140</a>
from <span class="vcard"><a class="email" href="mailto:naruoga@gmail.com" title="Naruhiko Ogasawara <naruoga@gmail.com>"> <span class="fn">Naruhiko Ogasawara</span></a>
</span></b>
<pre>@DaeHyun Sung -san, let me confirm, you mean this is an import issue from XLSX
file?
At least in Japanese, LibO unable to recognize Excel's format sub-modifier (I'm
not sure this is the right word, though), such as "[DBNum1]Standard" or
[DBNum1]0". We have to choose which option should be assumed.
In Japanese Excel,
Arabic: 1 10 11
[DBNum1]Standard: 一 十 十一
[DBNum1]0: 一 一〇 一一
LibO always choose [DBNum1] to [NatNum1], which has:
[NatNum1]:一 一〇 一一
or we can say LibO always assumes "[DBNum1]0" with some historical reason I
guess), this is currently design decision.
But you expect "一 十 十一", which is from "[DBNum1]Standard".
Do you want to claim to change this behavior?
NOTE: Now Excel can select "漢数字" as the number format, which always use
"[DBNum1]Standard", so the current design seems incompatible with Excel. At
least in Japanese, it is a considerable option to change it.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>