Active Topics
-
The N900 is now 15 years old! (9)
to Nokia N900 by Arno_11 - 2 hrs, 47 mins ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 5 days, 15 hrs ago - more...
amandalam |
2010-07-20
, 17:38
|
|
Posts: 85 |
Thanked: 383 times |
Joined on Jan 2010
@ Hong Kong
|
#21
|
Originally Posted by cheve
丿丨乛丨一丨乛一一乛丨
|
|
2010-07-20
, 21:18
|
|
Posts: 362 |
Thanked: 143 times |
Joined on Mar 2008
|
#22
|
Originally Posted by amandalam
thank you very much...I transposed the 4th and 5th stroke in my failed attempts.
丿丨乛丨一丨乛一一乛丨
|
|
2010-08-13
, 00:37
|
|
Posts: 85 |
Thanked: 383 times |
Joined on Jan 2010
@ Hong Kong
|
#23
|
Version 0.3 is now released. Introduced "Strokes Enquiry" feature that allows you to enquire and copy the strokes of any particular Chinese character, plus various other fixes.
See #1 for more details.
See #1 for more details.
|
|
2010-10-28
, 02:24
|
|
Posts: 13 |
Thanked: 8 times |
Joined on Oct 2010
@ Australia
|
#24
|
This is a great ap amanda!
It is nice to have the English keyboard, particularly for those of us who have lost the on-screen keyboard after installing penpower.
Along the English line...
1. Can predictive English text be added? (to accompany the predictive Chinese)
2. The English keyboard has some 'features' which reduce the potential size of the letter keys...
a. There are two backspace keys
b. The apostrophe, and perhaps the comma and full-stop, could all be on the bottom row, using some of the 'space' bar. I notice that the 'shift' key doesn't do anything to the symbols. Perhaps the 'Enter' key can be spanned across two rows, if that helps the arrangement.
c. In landscape mode, the English keyboard does not need a blue bar at the top of the screen. Unless it is used for predictive text
Otherwise, 'Stroke Order' is great as it is!
It is nice to have the English keyboard, particularly for those of us who have lost the on-screen keyboard after installing penpower.
Along the English line...
1. Can predictive English text be added? (to accompany the predictive Chinese)
2. The English keyboard has some 'features' which reduce the potential size of the letter keys...
a. There are two backspace keys
b. The apostrophe, and perhaps the comma and full-stop, could all be on the bottom row, using some of the 'space' bar. I notice that the 'shift' key doesn't do anything to the symbols. Perhaps the 'Enter' key can be spanned across two rows, if that helps the arrangement.
c. In landscape mode, the English keyboard does not need a blue bar at the top of the screen. Unless it is used for predictive text
Otherwise, 'Stroke Order' is great as it is!
|
|
2010-10-28
, 02:53
|
|
Posts: 85 |
Thanked: 383 times |
Joined on Jan 2010
@ Hong Kong
|
#25
|
Originally Posted by vkelim
Thanks for your suggestions! I am very happy that someone actually uses it!
This is a great ap amanda!
It is nice to have the English keyboard, particularly for those of us who have lost the on-screen keyboard after installing penpower.
Along the English line...
1. Can predictive English text be added? (to accompany the predictive Chinese)
2. The English keyboard has some 'features' which reduce the potential size of the letter keys...
a. There are two backspace keys
b. The apostrophe, and perhaps the comma and full-stop, could all be on the bottom row, using some of the 'space' bar. I notice that the 'shift' key doesn't do anything to the symbols. Perhaps the 'Enter' key can be spanned across two rows, if that helps the arrangement.
c. In landscape mode, the English keyboard does not need a blue bar at the top of the screen. Unless it is used for predictive text
Otherwise, 'Stroke Order' is great as it is!
I do intentionally keep two backspace keys --- the top one is for Chinese characters that I don't want to put extra code just to hide it when the English keyboard is shown; and there is one in the English keyboard because it would be much more natural to use it.
The position of apostrophe, comma and full-stop is referring to the PC keyboard layout, which I think most people would get used to it quickly. But as a trade-off of this, the English keys become a little bit smaller...
Introducing predictive phrases for English would mean another library to prepare and maintain, and it would only make sense if I implement this like the T9-way (i.e. lookup the phrases by checking the characters as you type, instead of just taking the first character and gives you its associated phrases)...this would take some time for technical research.
Unfortunately I'm quite busy on other personal stuffs these days though; but I'll see if I can incorporate some of your suggestions (e.g. the blue bar one) in the next versions.
|
|
2010-11-02
, 19:26
|
|
Posts: 1 |
Thanked: 1 time |
Joined on Oct 2010
|
#26
|
Originally Posted by cheve
i intially also had problems with some characters, until i realized that (i will represent stroke glyphs in "ascii art") -, stroke is also used for reverse stroke '-, and is therefore used for strokes, which look like \,, \_ or <.
is there document somewhere for nokia implementation of stroke order to form word? the stroke order you show for '好' is different from what I could recall if I were to write the word with pen and paper.
so e.g. 厶 is written as -, + \
Last edited by mykhal; 2010-11-02 at 19:28. Reason: added another stroke
| The Following User Says Thank You to mykhal For This Useful Post: | ||
 |
|
2010-12-11
, 03:22
|
|
Posts: 191 |
Thanked: 46 times |
Joined on Jun 2010
@ NanJing China
|
#27
|
some update will come ?
hope it wil not be long since I won't finsih mine before 201103
hope it wil not be long since I won't finsih mine before 201103
|
|
2010-12-29
, 11:18
|
|
Posts: 13 |
Thanked: 8 times |
Joined on Oct 2010
@ Australia
|
#29
|
Thanks for the update! with the slightly larger keys on the on-screen keyboard, my finger can now grow a little fatter!
|
|
2011-02-25
, 07:20
|
|
Posts: 17 |
Thanked: 2 times |
Joined on Feb 2011
|
#30
|
Is it possible to use this in place of mscim (which doesn't have the symbols virtual keyboard and doesn't work in Qt apps)?
Also, I find this input method slower in normal use than pinyin input even though Chinese is my native language. It's good for finding characters I don't know how to pronounce though.
Also, I find this input method slower in normal use than pinyin input even though Chinese is my native language. It's good for finding characters I don't know how to pronounce though.