<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:braunmax@yahoo.com" title="braunmax@yahoo.com">braunmax@yahoo.com</a>
</span> changed
<a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - Editing: RTL character string causes (left to right) numerics to flip order to also be RTL"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=69109">bug 69109</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>RESOLVED
</td>
<td>REOPENED
</td>
</tr>
<tr>
<td style="text-align:right;">Resolution</td>
<td>NOTABUG
</td>
<td>---
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - Editing: RTL character string causes (left to right) numerics to flip order to also be RTL"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=69109#c11">Comment # 11</a>
on <a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - Editing: RTL character string causes (left to right) numerics to flip order to also be RTL"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=69109">bug 69109</a>
from <span class="vcard"><a class="email" href="mailto:braunmax@yahoo.com" title="braunmax@yahoo.com">braunmax@yahoo.com</a>
</span></b>
<pre>Dear Khaled Hosny,
Thank you for giving attention to this bug, which I highly appreciate.
I unfortunately need to add the following, which may allow the status to be
changed back to an active bug:
(i) All editing is done with an LTR keyboard (English (US) keyboard, English
(UK) as prime language). The only secondary keyboard is the English (UK)
keyboard. I have set no secondary keyboard and CTL enabling changes little of
this behaviour, in fact. Some value is obtained by Insert->RTL (or LTR) code.
(ii) Even worse than the simple form of the bug I have registered is the effect
that if spaces between the numerals are removed, except for a space placed as
thousand marker between 123 and 456 the behaviour on deleting the "I" is even
more inconsistent, and the number changes to 456 123.... the meaning thus
changes due to the flip. This cannot be anything but a bug.
(iii) The call to limit the correction/fix to "standard" of unicode is a
divergence, with this argument notepad would be the only editor, ascii or
ebcdic code our only character lists.
(iv) The conflation of what is expected of a WYSIWIG editor, and the properties
of a character set is unhelpful. With a pointer device like a mouse, one
expects an insertion point to be transparently placeable, and with the LTR
keyboard one expects to be able to insert or delete a character as needed,
without changing the visual rendition of other characters which are already
present. WYSIWIG editors DO insert formatting codes and overrides
transparently, and must do so. A hex level editor of course is something
different, as one had in the "code view" of wordperfect. The only final
limitation is open document text format type 1.2.
(v) One cannot rely on the keyboard choice only to affect behaviour either,
what about Japanese, which functions both LTR horizontally, and Vertically
downwards, left to right wrapping, often uses arabaic numerals etc.
(vi) The left and right pointer keys, and the backspace and forward delete keys
should not switch around in a single keyboard [alternate keyboards specific to
a language may be different]- the danger is that a single character in a
complex string or paragraph may not then be reachable and deletable... I can
also produce even that faulty behaviour.
Thus - not only does this bug (which affects all RTL/LTR/CTL algorithms) open a
can of worms (as you have warned) - it has opened a veritable plague of
parasites. And a solution may be found as we progress further in language and
character flexibility... as perhaps LO 6.1 may induce.
For now this bug should remain as needing attention, and potentially be
elevated to a higher priority. It is either an implementation flaw, or violates
a design assumption, in both cases a bug.
I hope this reply does gain your support.
Regards,
Max</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>