Re: [nvda-translations] Korean input: some concerns and problems

Hi,
I might have seen it - could you give us the subscription address so I can
forward this to the Korean forum? Thanks.
Cheers,
Joseph

-----Original Message-----
From: nvda-translations-bounce@xxxxxxxxxxxxx
[mailto:nvda-translations-bounce@xxxxxxxxxxxxx] On Behalf Of Mesar Hameed
Sent: Sunday, July 08, 2012 3:15 PM
To: nvda-translations@xxxxxxxxxxxxx
Subject: Re: [nvda-translations] Korean input: some concerns and problems

Hi Joseph,

I dont know if you saw this or not, but Mick has just recently set up a list
where these issues will be discussed.
It would be great if you can give him feedback on that list, since he is
currently working on adding input method support for asian languages.

Best wishes,
Mesar

--
Date: Fri, 29 Jun 2012 21:32:05 +1000
From: Michael Curran <mick@xxxxxxxxxxxx>
To: NVDA screen reader development <nvda-dev@xxxxxxxxxxxxxxxxxx>
Subject: [NVDA-dev] A new NVDA dev list for Asian character input

Hi all,

Today I created a new email list for people interested in contributing to
NVDA's support for Asian character input, which I am currently working on in
the inputMethods branch.

Info on the list or to join, go to:
http://lists.nvaccess.org/listinfo/nvda-dev-asia

The goal with this work is to allow users to efficiently enter asian
characters (specifically Chinese and Japanese) using NVDA, which includes
reading of candidate characters, and navigation of the composition string.
This also includes better announcement of input method switching.

I would like to thank both the TDTB in Taiwan and the HKBU in Hong Kong for
funding this particular project.

Thanks
Mick
On Sun 08/07/12,14:49, Joseph Lee wrote:
> Hi folks,
> Korean beta testing is going well - people report that the interface 
> is usable. However, the Korean forum members raised some concerns with 
> input processing and processing of Hanja (Chinese characters in Korean):
> Issue: when typing in Korean, input announcement by character doesn't 
> work, although announcing input by words and command keys works as 
> expected. I think this is the matter of editing character descriptions
file.
> Concern: Hanja processing in Korean should be implemented Korean uses 
> about
> 1800 regular Chinese characters, and including variant symbols, the 
> number of Hanja characters becomes over 25000. Also, there were some 
> suggestions to include Korean as one of the input methods branch 
> mostly because of special character inputs required (Korean uses 
> non-Latin script) and because of special uses of Chinese character 
> keyboard input (on Korean keyboards, the right CTRL key usually acts as
Hanja input toggle).
> Thanks for your considerations.
> Cheers,
> Joseph
> 
> 
> 



Other related posts: