by Michael S. Kaplan, published on 2008/02/15 09:31 -05:00, original URI: http://blogs.msdn.com/b/michkap/archive/2008/02/15/7713553.aspx
Prior posts in the series:
Last time, I explained a bit about what this one would be about -- it is a pure IME blog posting, so if IMEs do not interest you then you can skip on and wait for the next part....
My exact words were:
Next time I'll look at how to convert from some on the old style IMEs if you have been using them in the past...
I will now explain what the hell I was talking about. :-)
You see, in prior versions of Windows, Microsoft provided for Traditional and Simplified Chinese users the dotIME which was similar to the Table Driven TIP in terms pf lots of its functionality, though it was based more directly on the old IMM (Input Method Manager) based IMEs.
In addition, end users could be create there own dotIME by providing a "dictionary" text file and then running one of the conversion tools (named ImeGen.exe and UImeTool.exe).
Now this text fule format, while very useful for its time, was not the format that the new Table Driven Tet Service IMEs use. Just a slightly different direction, one that is not being carried forward into Vista and beyond. Mea culpa, etc. -- this new format, maybe it will last longer!
Therefore with Vista, those tools (ImeGen.exe and UImeTool.exe) are no longer supported, but Microsoft wanted to provide a way so that a customer could provide the text file nd it would convert the dictionary to the Table Driven TIP dictionary format....
The syntax to make the conversion happen (all on one line)
RunDll32.exe "%ProgramFiles%\Windows NT\TableTextService\TableTextService.dll" DictionaryGenerator [options] <output text file name>
Note that special, case-sensitive DictionaryGenerator keyword.
And the options are as follows:
Specify input text file format
<format> Traditional | Simplified | HongKong
-section:<name>:<input text file name>
Specify input text file name for each particular section
This option could be specify one or more of the following:
<name> SettingFile | KeyStroke | Radical | Text | Phrase | Symbol
<input text file name> Specify input text file name
Specify code page value for convert text file to Unicode if input text file(s) are in some other code page. Note that there is only one setting to be used by all files.
<output text file name>
Specify output text file name
Now this converter will only work from the text file, not the binary format file that the older tools (ImeGen.exe and UImeTool.exe) generated.
But if you have the text files this converter will reportedly save you some trouble. :-)
This post brought to you by ⑩ (U+2469, aka CIRCLED NUMBER TEN)
# John Cowan on 15 Feb 2008 1:53 PM:
What is it with you guys and obsoleting your tools all the time? I have lots of spiffy new tools, but my old tools work just as they did in 1969, and often even better (faster, more Unicode, etc.)
# Michael S. Kaplan on 15 Feb 2008 2:19 PM:
I cannot answer definitively for another team, but I suspect it has to do with the fact that the actual teams involved were different, living and working on different continents -- it makes starting over much easier to contemplate.
But I don't really know for sure. I prefer to not abandon stuff, personally, though I am sometimes overruled....
2008/06/21 Back to Sri Lanka (conceptually)
go to newer or older post, or back to index or month or day