Encoding does not apply to "Word Finder"

[GoogleCodeExporter]

#Is this a feature request? If so, describe your feature here:
I change the encoding to Zawgyi-One and when I type in Word Finder I cannot
type in Zawgyi-One sequence. I like to change the typing sequence to
Zawgyi-One in Word Finder?

#What version of WaitZar do you have? What version of Windows?
#  (Click on the WZ icon and choose "Help" to see the version number)
1.7

Original issue reported on code.google.com by thantthetkz on 18 Jun 2009 at 1:59

• Blocking: #131

[GoogleCodeExporter]

Thanks for your bug report; allow me to explain why WZ behaves this way.

1) The encoding that you are talking about is an "output encoding". After you 
type a
word using the "Word Lookup" and hit "Enter", it will be printed in the proper
encoding. (e.g., in Microsoft Word)

2) We are trying to implement a new option, "input encoding", for version 1.8 
or 1.9.
We want to add support for Zawgyi-style input, for Burglish, for Unicode 5.1 
input,
and for Romabama. Currently, the only "input encoding" available is "WaitZar
romanisation", with limited support for "Unicode 5.1" in the help keyboard.

3) We cannot change the keyboard to react to the output encoding, because we do 
not
have a good converter from Win Innwa to Zawgyi-One. Also, it doesn't make 
sense; what
if I want to type IN using a Zawgyi keyboard, but have WaitZar type OUT Padauk
(Unicode)? Our goal with WaitZar is to bring many encodings and input methods
together, not to force them apart.

I have changed the priority to "Low" and the type to "Wishlist". Eventually, 
you will
be able to use the "Word Lookup" in Zawgyi. However, this is not a bug --the 
program
just needs more development time. 

Hope this seems like a good solution to you. Thank you very much for filing 
this bug
report/feature request. :)

Original comment by seth.h...@gmail.com on 18 Jun 2009 at 6:20

• Added labels: Type-Wishlist, Priority-Low
• Removed labels: Type-Defect, Priority-Medium

[GoogleCodeExporter]

I just want to lookup words in zawgyi typing sequence.

Eg. Currently if I want to lookup for "ေျဖ", I have to type in sequence 
like ဖ, ျ ,
ေ. It will be good for those who don't know how to type in 5.1 sequence if we 
can
type in sequence like ေ, ျ , ဖ.

Sorry if there any misunderstood.

Thanks.

Original comment by thantthetkz on 19 Jun 2009 at 2:11

[GoogleCodeExporter]

Yes, thanks for explaining. We hope to add this in the future. So I marked it 
as 
"wishlist". 

Original comment by seth.h...@gmail.com on 19 Jun 2009 at 5:34

[GoogleCodeExporter]

With the new input system, typing in Zawgyi itself is very easy. However, 
looking up
Zawgyi words in romanized mode remains a problem.

I wonder if we can do some magic with the keyboard layouts to allow our virtual
keyboard to work with them. For example:
  1) We intend to load other formats for keyboard layouts. However, we can always
RENDER input properly; just run it through those keyboard engines. 
  2) The issue comes with displaying the keyboard's letters. Perhaps we can allow an
additional "tag" file that says which letter to display (shifted, etc.) on 
which key?

Note, however, that we'd have to add the tricky Ctrl+Shift+whatever 
combinations, AND
find a way to display them properly. Also, if there are custom words like for 
the
kyat ($), then we'd have to allow font rendering for those, too. In other words,
allowing typing in a keyboard layout is actually easy; supporting it with the 
help
keyboard would be tough.

However, there's no reason to be afraid to try! I think we can get a simple 
version
of this (for Zawgyi layout) working for version 1.8

Original comment by seth.h...@gmail.com on 24 Nov 2009 at 3:06

[GoogleCodeExporter]

After adding the infrastructure, I'm confident we can do this. Letter-based 
keyboards
(and the help keyboard) are next on my list.

Original comment by seth.h...@gmail.com on 18 Mar 2010 at 5:47

[GoogleCodeExporter]

Letter-based keyboards work, and the help keyboard works too. They _should_ 
work together, too, but I haven't enabled them for the current demo. That'll be 
next. (That or Romabama). 

Updating the keyboard's virtual letters, however, will take time.

Original comment by seth.h...@gmail.com on 25 Jun 2010 at 8:49

• Changed state: Confirmed

[GoogleCodeExporter]

Perhaps we can "blank out" the keyboard's Burmese letters when not using 
myWin2.1? This way, we can allow users to type in any input encoding for 1.8, 
and add support for guided typing in 1.9.

Original comment by seth.h...@gmail.com on 18 Aug 2010 at 7:07

[GoogleCodeExporter]

Nope, just delaying to 1.9 ---it makes sense to fix everything at once, and 
also standardize Virtual Keys at the same time.

Original comment by seth.h...@gmail.com on 22 Aug 2010 at 4:03