Behold the Table Driven Text Service, Part 2 (Three ways to convert!)

by Michael S. Kaplan, published on 2008/01/23 07:16 -08:00, original URI: http://blogs.msdn.com/michkap/archive/2008/01/23/7179692.aspx


Prior posts in the series:

That previous post introduced the MSDN_TableTextService_Simple.txt text file (right click on it and sve it somewhere if you want to use it).

And it showed one conversion technique.

So now I thought I'd cover all three techniques, and explain them a bit further....

The three types are known as Simple Conversion, Incremental Conversion, and Explicit Conversion. Each of them is described below:

Simple Conversion:

Inputted composition character shows in the small window which called "Reading Window". The Candidate Window is shown by press the conversion key (the "Space" key) which list items that match the inputted composition character.

This is what was previously shown in Part 1.

Incremental Conversion:

Inputted composition character shows in the small window which called "Reading Window". The Candidate Window is shown immediately when the user inputs a composition character. List items should match inputted composition character, and also “Incremental Conversion” shows list items for result of wild card search by inputted composition character.

Here is a nice sample, named MSDN_TableTextServiceIncremental.txt (right click and save it to your machine).

This sample profile has below conversion table;

[Text]
"1" = "Ⅰ"
"1" = "ⅰ"
"1" = "①"
"10" = "Ⅹ"
"10" = "ⅹ"
"10" = "⑩"
"11" = "Ⅺ"
"11" = "ⅺ"
"11" = "⑪"
"12" = "Ⅻ"
"12" = "ⅻ"
"12" = "⑫"

When we input "1" as a composition character, then "Incremental Conversion" shows list items for match as "1" and also shows list items match as "11" and "12" because there are result of wild card search as "1*". After listed item 4, the items are result of a wild card search. According to a wild card search, candidate list items should show combination string where the left side is a match as the inputted composition character, and right side is next expected composition character for wild card search character.

Explicit Conversion:

Inputted composition character shows up in the small window which called the "Reading Window". The Candidate Window is shown immediately when the user inputs a composition character. However, Explicit Conversion doesn’t process for wild card search.

The Look and feel of "Explicit Conversion" is similar to that of Simple Conversion, though as the above indicates it also has some behavior more like Implicit Coversion.

To be honest, these three different methods are similar enough between each other that the small behavior differences will sometmes seem like bugs to users who actually find themselves trying to use more than one of them!

Here is a nice sample, named MSDN_TableTextService_Explicit.txt (right click and save it to your machine).

When we input "1" as a composition character, then "Explicit Conversion" shows list items for match "1" only.

Now, to look at the differences between these three files as far as settings go, it is all in the [Configuration] section, which contains one of the following entries:

EXPLICIT:
ShowExplicitCandidateImmediately=1

INCREMENTAL:
ShowIncrementalCandidateImmediately=1

SIMPLE:
None of the above

Now as I said, the similarities can lead to more confusion thn you might imagine, and in general it is best to try to intuitively use the input method and see if it works the way you thought it would. I'll talk more about this later....

Coming up: what keystrokes do what, both built-in and definable.

 

This post brought to you by(U+2461, aka CIRCLED DIGIT TWO)


# Jan Kučera on Wednesday, January 30, 2008 7:51 AM:

Hello, this is really cool stuff!

Okay, I would like to ask, is there any way how to not disturb the typing? I mean, if I write "12", to just press space and have the "12" written? Like the reading window to be a little bit useless, to type its content directly and only offer candidates in case you want to change typed "12" to anything else...

I hope the question is understandable a bit.. :-)

Jan

# Ken Aarts on Tuesday, April 15, 2008 12:55 PM:

Do you, or anyone, have a pointer to documentation on moving the reading window?  I am writing a partially IME aware application, which displays the composition strings, but I haven't found the API to direct the Reading Window to near my caret.

Thanks,

Ken


referenced by

2008/10/21 Behond the Table Driven Text Service, Part 14 (Don't expect too much from numbers)

2008/07/25 Behold the Table Driven Text Service, Part 13 (Sinhalification proclamation!)

2008/06/30 Behold the Table Driven Text Service, Part 12 (The knights who say நீ, redux, #2)

2008/06/21 Back to Sri Lanka (conceptually)

2008/02/25 Behold the Table Driven Text Service, Part 11 (The knights who say நீ, redux, #1)

2008/02/15 Behold the Table Driven Text Service, Part 10 ("Even Jove nods," Atlas shrugged, "so we'll convert their old files, now.")

2008/02/12 Behold the Table Driven Text Service, Part 9 (Will you be content if I tell you how some content can be defined?)

2008/02/11 Behold the Table Driven Text Service, Part 8 (Configuration 'junk in the trunk', part 2)

2008/01/30 Behold the Table Driven Text Service, Part 7 (Configuration 'junk in the trunk', part 1)

2008/01/29 Behold the Table Driven Text Service, Part 6 (it is sufficient to be iconic, aka DaYi, DaYi Aynu!)

2008/01/28 Behold the Table Driven Text Service, Part 5 (All about the language, baby!)

2008/01/25 Behold the Table Driven Text Service, Part 4 (Specifying when to modify, if not how)

2008/01/24 Behold the Table Driven Text Service, Part 3 (Where do keystrokes come in?)

go to newer or older post, or back to index or month or day