![]() |
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ツイート
|
1.13 Automatic kind code detective.
If UTF-8 can not display, retry as EUC, SJIS or JIS.
1.12 Support UTF-8.
1.11 Support tooltypes "DEBUGLOG". This is for debug OS4 environment.
1.10 Support tooltypes "GENERATEBITMAP". This is for debug OS4 environment.
1.09 Support tooltypes "FONTNAME". And change font to use from "topaz/16" to "jkff/16".
Installer copy "jkff.font" instead of run fixfonts.
This is solution for install to MorphOS. MorphOS have not fixfonts.
Thanks to HAWK.
1.08 Support "hankaku" FONTX (8 x 16) file.
1.07 Bug fix. If launch from CLI other path, can not read font.
1.06 REVERSEFONT support.
1.05 Support all charactor of Japanese kanji class 1 and 2.
1.04 Replacement font loading process and
relation tooltypes.
1.03 Displayed black box in stead of kanji,
if end of Japanese kanji second class.
Thanks to Ma-ru.
|
2007.02.11 OS4.0 are remove code 0x81 at input event stream. I will try other unicode encoding system. jkffinput003.lha I think unicode in UTF-16BE(Big Endian) have not 0x80-0x8f. Guide of JKFFInput Ver0.03 For note, fllowing function at only window appear. If JKFFInput disappear window, no work. type "h" ==> input "Happy Kanji Life." type "6" ==> input constant Japanese Kanji text with UTF-16BE. type "8" ==> input constant Japanese Kanji text with UTF-8. Please try fllowing steps. 1. Run JKFFInput. 2. (JKFFInput appear window). 3. Run EditPad(OS3.9) 4, Type "6". 5. (EditPad display garbage). 6. Save "test.utf". 7. Quit EditPad. 8. Quit JKFFInput. 9. Run TypeManager. 10. Open "test.utf". 11. Change text type to "Unicode in UTF-16BE". Thank you. |
|
2007.02.10 Thanks, joerg, keisangi. In OS3.9, EditPad(OS3.9) can input kanji with UTF-8. ![]() But NotePad(OS4.0) can't input. UTF-8 have not only 0x00-07f, but also 0x80-0xff. Kanji with UTF-8 have wide range in byte. It use 0x80-0x8f <== Many application are remove this byte. EditPad(OS3.9) keep it. NotePad(OS4.0) remove it. 0x90-0x9f <== 0x9b is CSI(Control Sequence Intoducer) in OS3.9. Is OS4.0 too? 0xa0-0xaf 0xb0-0xbf 0xe0-0xef |
|
2007.02.10 Thanks, TetiSoft, keisangi, Hans, Valiant, Raziel. Update JKFFInput today, jkffinput002.lha. 1. Run EditPad. 2. Please try fllowing 4 keys. type "h" ==> input "Happy " type "k" ==> input "Kanji " type "l" ==> input "Life." type "u" ==> input constant Japanese Kanji text with UTF-8 3. Please write your like word and edit (backspace/delete/return/up/down/left/right/etc...). NOTE: Do not modify Japanese Kanji line. (In OS3.9 EditPad can display kanji step2.) (Please OS4.0 user try fllowing steps.) 4. Save EditPad to "test.utf". 5. Run font display tool (name ?). 6. Load "test.utf". Dose "test.utf" have Japanese Kanji? Can EditPad use Japanese Kanji font? |
|
2007.02.08 I createed simple commodities, jkffinput001.lha. I have basic question. Can OS4.0 accept m68k commodities? If you have OS4.0, please try JKFFInput, report me. This JKFFInput (Ver0.01) only appear window, "CTRL+o" switch disappear. |
|
2007.02.04 Congratulations! I found Japanese Kanji Display for OS4 PPC program. Thanks keisangi. The Amigans website - os4 japanese support Then I drew up plan of port JKFF. --Today(2007.02.04)-- 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) |

