Couzzo / hackerskeyboard

Automatically exported from code.google.com/p/hackerskeyboard
0 stars 0 forks source link

Feature Request: Invalid Character Sequence checking (Thai) #166

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Background/Justification:

Keyboard input methods for some languages, in particular those with a complex 
layout such as Thai, usually have built-in rules for detecting invalid 
character sequences and alert the user (eg. audible or visual feedback) if such 
a condition occurs. This is standard behaviour for Thai keyboards on all major 
OS'es and mobile devices. Alternative Android keyboards such as CN Thai and 
TSwipe also have this feature.

Would it be possible to also this feature to Hacker's Keyboard?

References/Further information:

- Thai Input and Output Methods.pdf (attached)
Defines the sequence checking rules. Note: this document is old so references 
the TIS-620 (8 bit) character set extension to ASCII. The modern equivalent in 
Unicode is the block starting at 0x0E00 and is a one-for-one mapping of TIS-620.

- libthai project (http://linux.thai.net/projects/libthai)
Contains a C implementation, commonly used in Linux projects.

- icu-project.org
C and Java implementations
Description: 
http://userguide.icu-project.org/collation/concepts#TOC-Thai-Lao-reordering

Original issue reported on code.google.com by hmm...@gmail.com on 18 Jan 2012 at 10:09

Attachments:

GoogleCodeExporter commented 9 years ago
I haven't looked into this yet. If I'm understanding it right, a library like 
this would help with finding word breaks too? See issue 72 for the problems it 
currently has with Thai word completion.

I'm afraid this type of complex and language-specific change will need to wait 
- I currently have quite a lot of things on my TODO list and limited time to 
work on them, so unless someone can collaborate and provide easy-to-integrate 
changes to implement this I probably won't get to this in the near future.

Original comment by Klaus.We...@gmail.com on 26 Jan 2012 at 9:03