#Long-term feature request
WaitZar isn't a font conversion program; it's a typing system. However, it
_does_ have support for a great many conversions, and its use of Unicode as a
"pivot-encoding" allows stranger conversions (Win Innwa -> Ayar) to be reliable
without anyone actually developing that _specific_ conversion.
Moreover, 1.9 will add some form of scripting support, so we can allow
encodings to define some kind of "auto-detect" script. This script (can be
written in Javascript and) can return "highly likely (this encoding)",
"possibly" or "definitely not". If no script is present, always return
"possibly". So, if the user highlights some text in a program, we can guess as
to its encoding.
Given that, it shouldn't be too hard to add a "Convert In-Place" option, via a
hotkey or a (temporary) right-click context menu item, or something similar.
Then, we can list all "possibly" encodings, with the "likely" ones at the top,
and the "not" ones hidden ("see more..."). We can also show the sample text
rendered in each encoding, which will be accurate, since we're just using
Microsoft's font APIs. This will make converting old text a LOT easier.
The reason I'd consider this, when in the past I would not, is that WaitZar is
supposed to be a useful input tool. So if people have it in their system tray,
why not put it to good use? That way, they won't have to look for their
conversion program, find out it's out-of-date, download the latest one, etc.,
etc., every time they want to change a simple string.
So... maybe for 1.9? It could be fun~
Original issue reported on code.google.com by seth.h...@gmail.com on 20 Jun 2010 at 2:12
Original issue reported on code.google.com by
seth.h...@gmail.comon 20 Jun 2010 at 2:12