Revision history [back]

Many frequently used characters cannot be typed individually. For inputting one of those characters one needs to type a word containing this character and than delete other part of the word, as for the characters not appearing in the stock word database (e.g. characters mainly used for contact names) . This is rather inconvenient and makes the input method unusable for everyday life.

A general solution would be https://together.jolla.com/question/1495/provide-table-based-input-method-engine-framework/. But since this input method is shipped with the device, it should be fixed rather than staying at the current state.

Many frequently used characters cannot be typed individually. For inputting one of those characters one needs to type a word containing this character and than delete other part of the word, as for the characters not appearing in the stock word database (e.g. characters mainly used for contact names) . This is rather inconvenient and makes the input method unusable for everyday life.

A general solution would be https://together.jolla.com/question/1495/provide-table-based-input-method-engine-framework/. But since this input method is shipped with the device, it should be fixed rather than staying at the current state.

Many frequently used characters cannot be typed individually. For inputting one of those characters one needs to type a word containing this character and than delete other part of the word, as for the characters not appearing in the stock word database (e.g. characters mainly used for contact names) . This is rather inconvenient and makes the input method unusable for everyday life.

A general solution would be https://together.jolla.com/question/1495/provide-table-based-input-method-engine-framework/. But since this input method is shipped with the device, it should be fixed rather than staying at the current state.

Update: It seems that there is a maximum of 20 candidates showing up in the 'word-prediction-list'. Could there be any method to expand the length of that list? Or is it possible to implement a grid view like in Meego Harmattan?

Many frequently used characters cannot be typed individually. For inputting one of those characters one needs to type a word containing this character and than delete other part of the word, as for the characters not appearing in the stock word database (e.g. characters mainly used for contact names) . This is rather inconvenient and makes the input method unusable for everyday life.

A general solution would be https://together.jolla.com/question/1495/provide-table-based-input-method-engine-framework/. But since this input method is shipped with the device, it should be fixed rather than staying at the current state.

Update: It seems that there is a maximum of 20 candidates showing up Fixed in the 'word-prediction-list'. Could there be any method to expand the length of that list? Or is it possible to implement a grid view like in Meego Harmattan?1.0.7.16, great job!

Many frequently used characters cannot be typed individually. For inputting one of those characters one needs to type a word containing this character and than delete other part of the word, as for the characters not appearing in the stock word database (e.g. characters mainly used for contact names) . This is rather inconvenient and makes the input method unusable for everyday life.

A general solution would be https://together.jolla.com/question/1495/provide-table-based-input-method-engine-framework/. But since this input method is shipped with the device, it should be fixed rather than staying at the current state.

Update: Fixed in 1.0.7.16, great job!

Many frequently used characters cannot be typed individually. For inputting one of those characters one needs to type a word containing this character and than delete other part of the word, as for the characters not appearing in the stock word database (e.g. characters mainly used for contact names) . This is rather inconvenient and makes the input method unusable for everyday life.

A general solution would be https://together.jolla.com/question/1495/provide-table-based-input-method-engine-framework/. But since this input method is shipped with the device, it should be fixed rather than staying at the current state.

Update:

Update: Fixed in 1.0.7.16, great job!job!

After the 1.0.7.16 release, the stock pinyin input method is fully working with all the candidates selectable. However, the character set provided by the IMs (including pinyin, handwriting and stroke) is not complete so that some chars cannot be typed. The charset (GB2312) is rather old and do not contain many recently popularized chars or some chars mainly used for people's names. It would be better to provide IMs with the UTF8 set which agrees with the system as well.

Many frequently used characters cannot be typed individually. For inputting one of those characters one needs to type a word containing this character and than delete other part of the word, as for the characters not appearing in the stock word database (e.g. characters mainly used for contact names) . This is rather inconvenient and makes the input method unusable for everyday life.

A general solution would be https://together.jolla.com/question/1495/provide-table-based-input-method-engine-framework/. But since this input method is shipped with the device, it should be fixed rather than staying at the current state.

Update: Fixed in 1.0.7.16, great job!

After the 1.0.7.16 release, the stock pinyin input method is fully working with all the candidates selectable. However, the character set provided by the IMs (including pinyin, handwriting and stroke) is not complete so that some chars cannot be typed. The charset (GB2312) is rather old and do does not contain many recently popularized chars or some chars mainly used for people's names. It would be better to provide IMs with the UTF8 set which agrees with the system as well.