Re: [nvda-translations] Please suggest
- From: Takuya Nishimoto <nishimotz@xxxxxxxxx>
- To: nvda-translations@xxxxxxxxxxxxx
- Date: Tue, 4 Sep 2012 10:54:12 +0900
Hello,
1.
Regarding "{number} {word}" message, Japanese translation of this
should be "{word}", i.e. the number should not be announced.
This is because people who cannot see the display only use arrow keys
and enter key to select the candidate of Japanese language.
I understand it is not good solution for people who sometimes want to
use Japanese and sometimes Chinese.
Other than message translation, its behavior should be configured
depending on languages.
2.
Regarding Joseph's comment, I agree that the announcement of input
composition should be different depending on the input method
currently used.
For example, automatic candidate report is enabled by default,
however, it should not be enabled for some cases including all of
Japanese input methods.
--
Takuya Nishimoto
2012/9/4 Joseph Lee <joseph.lee22590@xxxxxxxxx>:
> Hi,
> 1. Language layout: I think you can leave them as is, as speech would say,
> "input language (layout)". For example, if you're using English (United
> States) layout, it'll say, "English (United States layout).
> 2. Number word: this is used when viewing candidates or interpretation
> suggestions for a letter in Asian languages. For example, in Korean, the
> word "soo" (pronounced like "sue") has several interpretations; in some
> contexts, "soo" could mean "water," at other times it means "number". These
> suggestions are presented in a list format, called "candidates list", with
> each interpretations being given a numeric label. So, to use our example
> word, the window (and speech output) would look like:
> User puts the cursor on the word "soo" (it is spelled differently in
> Korean). Then the user presses a key to bring up suggested interpretations
> with the following text on it:
> {number} {word}
> 1. "soo" as in "water"
> 2. "soo" as in "number"
> Here, numbers would be number text, while the word would be the actual word
> and the interpretations.
> As for Korean translation, I'm looking for Korean words for "candidate",
> "composition, "native input", "alphanumeric input" and others originating
> from input methods branch. And we cannot simply translate "native input' as
> Korean nor "alphanumeric input' as English," respectively because:
> 1. Even in alphanumeric input, there are variations on this, and there are
> languages which uses alphanumeric input but doesn't use English layout.
> 2. Native input usually means the default keyboard layout used in a given
> language or country, and there are situations when people would use three or
> more language layouts or the language version of NvDA and installed keyboard
> layout would be different.
> A possible solution could be to separate po files into main messages and
> input switching group. But this could add complexity; another method would
> be bunch of if/else/case statements so that different IME/TSF (input
> methods) would provide different messages, thus helping the translators in
> the future and to prepare for situations explained above.
> Cheers,
> Joseph
>
> -----Original Message-----
> From: nvda-translations-bounce@xxxxxxxxxxxxx
> [mailto:nvda-translations-bounce@xxxxxxxxxxxxx] On Behalf Of DINAKAR T.D.
> Sent: Monday, September 03, 2012 7:50 AM
> To: NVDA TRANSLATION LIST
> Subject: [nvda-translations] Please suggest
>
> Hi Team,
>
> What words can be added to the following strings to make their function
> clear? Can you please suggest?
>
> 1. {language} - {layout}
> 2. {number} {word}
>
> Thanks,
>
>
> DINAKAR
>
>
>
Other related posts:
