create UTF-8 keymaps in memory, this would break nearly every existing shell/console/terminal/KingCON/whatever.
Yes will break KingCon, but so did SnoopDOS. Console/Shell? will need UTF8 support anyway.
Terminal / whatever? is the problem really.
What you need is legacy API and new style API, so programs that don?t know of UTF-8 don?t notice it.
Quote:
do you volunteer to create new shells/ consoles/con-handlers etc which can handle ESC[ or UTF-8 escape sequences
Yes, development is a hobby for me not a job, so I even do it for fun, even add the KingCon scrollbar.
I need the source-code of the OS4 con-handler.
con-handler is the wrong place to put UTF-8 support into. This would have to be done in the place that actually deals with putting control sequences, and sequences of characters on the screen, and that's console.device, not con-handler. Similarly, while con-handler would be the right place to add a scroll bar or two to a window, the task of updating the window's contents in response to scroller operations would be for console.device and not con-handler.
Yes, KingCon and just about every other console handler there ever was did these tasks all on its own and ignored the console.device's part. This was mainly because you couldn't change console.device. But it still makes for bad architecture. Small recap: graphics.library renders text on the screen; console.device transforms control sequences into text rendering operations; con-handler transforms file I/O operations for console.device to use them.
You should consider taking up this offer; that's less work for you and the rest of the OS4 dev team.
Olsen has an account on this site. He maintains both the con-handler and the technical part of giving access to OS4 sources.
All true, but I'm not the guy who hands out access permits for the operating system source code.
The situation being what it is, it would be great to have more developers contributing to the operating system, but with great enthusiasm comes the need to sign great non-disclosure agreements.
I don't know what the procedure is. In the past there was a path from the beta test group to becoming an OS4 developer, and something similar did exist for the professional Amiga software developers.
con-handler is the wrong place to put UTF-8 support into. This would have to be done in the place that actually deals with putting control sequences, and sequences of characters on the screen, and that's console.device, not con-handler.
I'm not asking for UTF-8 support, all what is needed as first step would be ASCII support. The current con-handler e.g. refuses to accept a control sequence for "Cursor up" when its ASCII (with <ESC>[ instead of <CSI>).
Yes, a valid ASCII escape sequence is also a valid UTF-8 escape sequence, that would be a bonus.
News feed
OS4 Feedback forum
OS4Depot Feedback forum
AmiCygnix forum
ABC shell forum
AmiKit forum
Cinnamon Writer forum
CodeBench forum
Digital Universe forum
Dopus 5 forum
E-UAE forum
Gnash forum
Ibrowse forum
JAmiga forum
Odyssey forum
OWB forum
Qt forum
SmartFileSystem forum
Timberwolf forum
TouchDevice forum
TuneNet forum
Unsatisfactory Software forum
Donate
