@keisangi

Thanks for test and report.
Please open test.utf with NotePad and change font.
I think workbench preferences can change it too.
And JKFFInput display other font?

I will program JKFFInput with 2 weeks.
Please waitting for Step1(JKFFInput for OS3.9).

@keisangi

I update JKFFInput.
Please try text type "Unicode in UTF-16BE".

EditPad(OS3.9) do not input 0x81 in OS4.0.
I think OS4.0 are remove 0x81 at input stream.

UTF-16BE have not 0x81, I think.

# OS3.9 do not remove 0x81.
# Who update OS4.0 program for remove 0x81? ;)

@keisangi

Thank you for many test.

TypeManager have gadget "text type".
Please tell me, text type items.

EditPad(OS3.9) in OS3.9 work it.
Please try this steps.
1. Run JKFFInput
2. Run EditPad(OS3.9)
3. type "u"
4. (EditPad display garbege)
5. Save "test.utf"
6. Quit EditPad
7. Quit JKFFInput
8. Run TypeManager
9. Open "test.utf"
10. Change text type to "Unicode in UTF-8"

@(to all)

Update JKFFInput. Please look my page.
http://www.phoenix-c.or.jp/~olfa/jkff/index.html

OS4 dose not need JKFFDisp.
Because OS4 can display kanji already.

OS display / input
OS3.9 JKFFDisp / JKFFInput
OS4.0 (inside OS) / JKFFInput

@Valiant

Sorry for no guide my page.
JKFFInput Ver0.01 work only appear/disappear window.
Is JKFFInput work appear/disappear?
Please try key combination "ctrl + o".

I programming JKFFInput now.

@keisangi

JKFFDisp(m68k) is patch to font table on m68k world.
PPC program not use this table,
then JKFFDisp not work.

JKFFInput(m68k) is one of commodities,
and convert input event on commodities stream (future).

If OS4.0 have only one stream for commodities,
and if OS4.0 accept m68k commodities,
then m68k commodities chain to PPC commodities stream.

@keisangi

Sorry for no progress report.
Because I have many minutes(30-60) for create english statement.
Please watch current state.
http://www.phoenix-c.or.jp/~olfa/jkff/index.html

I think not need PPC version, if OS4.0 accept m68k commodities.

@Hans

Thank you for tell me about OS4 SDK.
I downloaded two archives.

Please wait finish Step1 with about 1 month.

@keisangi

I can't read japanese part of #16.
Because AWebII(m68k) handle only single byte,
it can't handle double byte (example "さ").
I drew up plan of port JKFF.
--Today--
JKFF(OS3.9/m68k)
1. Patch font table
2. Patch to function Text
3. Insert input handler (input.device)
4. Handle code SJIS/EUC/JIS
JKFFDisp(OS3.9/m68k)
1. One of commodities
2. Patch to font table
3. Ptach to function Text
4. Handle code SJIS/EUC/JIS/UTF
--Step1--
Create JKFFInput(OS3.9/m68k)(SAS/C)
1. One of commodities
2. Insert CxObject (commodities network)
3. Handle code UTF
4. (Not patch to font table)
5. (Not patch to function Text)
--Step2--
Port JKFFInput(OS4/PPC)(gcc)
(I wish "Same source code, each compile".)
--Goal--
OS3.9 JKFFDisp/JKFFInput(m68k)
OS4 JKFFInput(PPC)

I will start "Step1".
Long long ago, I bought "Amiga SDK for Linux" CD.
I can use it for develop Step2?

@keisangi

I found your screenshot on OS4, congratulations!

Function of JKFF is convert
"RAW keycode" => "kanji(SJIS/EUC) code".
If support OS4, it must convert
"RAW keycode" => "UTF-8 code".

I have some question. Do OS4 have input stream?
On OS3.9, JKFF insert input handler to input.device
with command IND_ADDHANDLER.