Foreign Characters

Quote:

No, I meant what the heck is the line I quoted supposed to mean?

I suspected typos at first, but I see you romanize almost the same:

EigoNoKeeBoodoHaMuzukashiNiHaiChattaNaiDeShouNe (only you have Chata instead of Chatta in kana)

"KeeBoodo" (38 googlits) should be "KiiBoodo" (over five million reported by Google), I know, but "MuzukashiNi" isn't Japanese. (Muzukashiku would be, but not even that would make sense with HaiChattaNai. Everything before and after HaiChatta(Nai) makes sense, so you obviously know some Japanese, which is great.
日本語の勉強になおなおがんばって下さいよ!

@kilaueabart

はい、少し日本語分かります。
前に日本の鳥取県鳥取市すんでましたでも。。。
その時間あいだに結婚しあります、その結婚は今止まった。

Yes, I understand a little bit of the Japanese Language.
Before I lived in Tottori City, Tottori Prefecture, Japan

During that time I was married but that is now ended.

[edit]
as for my use of Japanese... I was CamelCasing based on
Word / Particle and Modifier points...

Ni for に and De for で along with
~Shitai for ～したい as examples...

[/edit]

@nbache

That is correct, dead-keys are immediate pre-processing
for the next key only and exit change of state after the
subsequent entry...

@all

I can not however deal with dead-keys for Hiragana, Katakana
and Kanji input over and above normal English input.

as any "Japanese Windows" or Linux system is fully capable
of multiple language input which is the proper target
for the Perception IME.

Basically *any* input will be handled with Perception IME
being the layer inserted for language specific rules.

the "default" rules will be "raw" or English input with the
existing "deadkey" triggers for umlauts and similar input.

However for Arabic/Japanese/Chinese and other languages that
need an extended set of rules to be input properly...

That is where Perception IME will make itself available with
a common perception.library which the normal language libs
that are the "nihongo.language" and "mandarim.language"
libraries (these are coded, not data based) will insert
the IME into the normal Intuition level processing.

I will be using the list of locale "Preferred Languages" to
decide which IME modules will be immediately accessible
from the controlling commodity and perception.library


Beyond that any IME preferences will be "per-language"
and I have not decided where to store them yet.

I will not be adding them as a general Preferences Editor.
as they will only be limited to the controlling CX tool.

The "nihongo.language"(Japanese) library will only bind
to the Perception IME library when it is present
along with launching the CX tool also being optional.

the following rules of behaviour will apply...

"default English Input layout", Recognition of the 4 added
Japanese only jp106 keys.

there will be a toggle between English and Japanese modes,
with the "Japanese" state being further expanded for
Hiragana / Katakana / Double-Wide-English / Kanji-Menu

Each Hiragana is 1-3 Letters to type, Katakana is another
symbol set repeating the same input options.
Double-Wide is a UTF8 encoding option for 16bit/symbol
input and Kanji mode can have an indefinite depth tree
for selecting what Kanji are "typed" based on a whole
string selection process.

typing "kanji" on any other Japanese IME will give the
following options...
Hiragana=かんじ
Katakana=カンジ
Kanji= 1:漢字 2:莞爾 3:完治 4:寛治　5:感じ 6:...

Using the exact same data entry of [kanji] followed by
pressing space twice with a number or enter key to select
from the displayed menu of choices
(the Windows IME gave 14 built-in dictionary options)

so a definite example that simple dead-keys will not suffice
to handle this kind of input (do you want to enter triple
dead-key combos to select each character in the word then
needing to know a triple dead-key number entry to select
which variation with a possibility of getting it wrong?)

Trying to input IME level material using dead-keys only
would be like trying to drive a car or a semi-trailer rig
after the medical removal of the drivers eyes and no
prior training...

the Perception IME will have to fill this glaring gap
and I am considering how to handle other options as well.