@TetiSoft

Quote:

Well one of your excuse I believe, because you know UTF-8 will need to be extended system wide, and you know it big job to add it.

It?s not like can?t convert UTF-8 back to 8bit using the codepage before sending it over the serial port.

Quote:

Again I don?t se how this is relevant, SSH and other shells can be supported, simply char conversions from UTF-8.

@joerg

Quote:

UTF8 is not magic, it?s easy detectable because of the way it encoded, you can check if?s valid format or not, if not is ASCII, for storage it only required a zero terminated text string, but problem is program requires ASCII (8 bit) and need to read attributes from UTF-8 supported gadget class, the you can?t do that whit existing TAGS, there for explicit UTF-8 support tags most be added.

UTF8 support can be extended one class at time.

@TetiSoft

SetFont CHARSET ISO-8859-7

Should not be nursery, when you have files form different countries they should use there correct symbol.

If I have downloaded a file from Sweden or Finland or some other country, it should use original symbols in its file name, not the symbols from CHARSET I?m currently using.

I was saying the con-handler, need?s UTF-8 support ?<ESC>[? should be the same as CSI

If you convert ?????? to UTF-8 you and insert this current shell, the ASCII values be interpret ESC code sequences this happens, the problem whit con-handler is that it expects ASCII code, and therefore assumes the ?????? encoded symbols are ESC codes.

In order to clean this up, ESC codes most be in UTF8 format.

When it comes to input.handler and data coming from there most be converted using a CHARSET for example ISO-8859-7 the result should be UTF-8 before it written to terminal.

symbol="ESC [" should be the format used for new applications, CSI should be rendered obsolete or only used when older programs expects that format.

@LiveForIt

Or else a deeper integration most be done where the ESC code sequences becomes embedded in side UTF-8, but then the shell system most be completely updated.

@Billsey

Web archive maybe

@spotUP

I think it?s better to use UTF-7 because UTF-8 conflicts whit ESC code sequences in AmigaDOS.

UTF-7 can maybe be added as patch to AmigaOS, to display text, but you most have some kind way to type the text as well, that?s is the biggest problem.

@Raziel

My CPU is on its way down there, should be out of my county now..

@evilrich

Looks like dynamic linked .so files there, nice work.

@magic

Install Linux while you wait.

GCC + SDL = Games

@Chris

That screenshot does not tell, if it works ok or not?

@tonyw

Try installing it under E-UAE, then copy it over to OS4, and use Snoopy to detect any problems.

@wizzard_o

Welcome hope you enjoy this useful forum.

@spotUP

If like to you can ask Antique for it..

@Crumb

I did not know any one where working on it,

This version is Reaction based, and uses Picasso?96 display code,
It?s based on changes for MorphOS, that is again based on AmigaOS3.x, it was easier to do it that way because of memory address emulation, the window mode is upgraded form black and white to 24bit Picasso?96 bitmap, but it not optimized so runs slowly on Antique (600 Mhz) computer, should work fine on 800Mhz computer whit out any frame skip.

* Fixed the device emulation (CDROM support) code it was broken.
* Fixed NSD64 support fixed.
* Fixed the program exit code, it was broken,
* Fixed the makefile script it was not tuned for AmigaOS,

For Mac address space, I?m using virtualized memory to avid memory fragmentation problems.

* AHI support not tested.
* Ethernet support might be broken, not properly tested.
* Reaction GUI incomplete; it does not refresh correctly and you can't add disk images.

I can not continue working on it, because my AmigaOne-XE stopped working, and I most send it for repair.

Antique has a copy of the source code so it should be safe.

@Rogue

Quote:

I guess we will know what that is when the time is right.

@ikir

Well Done ACube!

@abalaban

I don?t know any thing about TCL, so don?t know, but the port TCL library ended up standard Amiga library or some thing else?

@abalaban

Well probably where unable to generate a valid library structure?

There some tools for that in the SDK have a look?

@Rogue

Quote:

Well that depends on the configure script, if you can?t even get this running then its not where likely you are going to be able to port anything, at least that my experience, (maybe its easier using a cross compile..).

@Rogue

Yes but source code to that game probably is not free.