[Fedora-i18n-bugs] [Bug 435880] [si_LK] ibus-gtk requires surrounding-text support for si-wijesekera.mim

bugzilla at redhat.com bugzilla at redhat.com
Mon Aug 23 10:03:23 UTC 2010


Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=435880

fujiwara <tfujiwar at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
               Flag|needinfo?                   |

--- Comment #51 from fujiwara <tfujiwar at redhat.com> 2010-08-23 06:03:22 EDT ---
Thanks for the comments.

(In reply to comment #49)
> BTW, in modern Sinhala, words are also separated by a space. The problem is
> once the buffer has been committed and a user goes to edit a syllable. e.g. a
> syllable "koo" might need to be changed to "kee" and should require only two
> backspaces and al-lakuna key presses. But without surrounding text support you
> need 4 backspaces followed by 3 more key presses. The worst case scenario is if
> the user does the logical set of steps (2 backspaces and 1 al-lakuna) it will
> result in an encoding error.

In preedit, I would expect not to use any backspace keys if you need to change
"koo" to "kee". I feel it would be one space and enter key.
It would be great if you could explain why it's important to support the
already committed text since I don't identify the usage to the actual
hand-writing.

In the preedit mode, I mean preedit buffer would be similar to the writing
mode. Once the text is committed in preedit mode, using backspace keys on
computer could be similar to using an eraser on paper.
So if you try to modify the already committed text in surrounding mode, it
would be similar to using an eraser on paper to me.

(In reply to comment #50)
> If you use such input methods with preedit, you may need to behave differently
> to change the same string, depending on whether it has already been committed
> or not.  This is an confusing situation.

The previous suggestion means to support the previous chars belonged to a word
without supporting already committed text.
It would be great if you could explain why it's important to support the
already committed text since I don't identify the usage to the actual
hand-writing.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


More information about the i18n-bugs mailing list