Source Code Control (git)

[John Cowan]

You'd only need Ucode if you were writing a client; a server doesn't have
to display anything.  And Unicode only grows by adding new characters:
existing ones never get removed and most of their properties don't change
either, so keeping up actually isn't that hard.


On Sun, Feb 14, 2021 at 9:15 PM Katarina Eriksson <gmym at coopdot.com> wrote:

> Stephane Bortzmeyer <stephane at sources.org> wrote:
>
>> On Sun, Feb 14, 2021 at 07:48:53AM +0000,
>>  Jonathan Lane <jon at dorsal.tk> wrote
>>  a message of 38 lines which said:
>>
>> > Personally, I can't wait for some crazy bastard to write a Gemini
>> > server in Motorola 68000 assembly for the Amiga.
>>
>> TLS will certainly create interesting challenges. (Unicode, too.)
>>
>
> AmiSSL[1] has full compatibility with the latest OpenSSL, requires 68020
> or higher and AmigaOS 3 or higher. The crypto itself would still take a
> long time.
>
> There also exist a unicode library called Ucode[2]. But since I discovered
> it when writing this email, I don't know if it's usable for such a project.
> Keeping up with the new Unicode versions is a project of itself.
>
> While on the Amiga programming topic, I've been spending one or two hours
> every Saturday evening (just a few weeks in a row) teaching myself Amiga E.
>
> Inspired by Amiga E's 32 bit chars and AmiSSL for Amiga E[3], I've started
> to write a gemtext parser (ASCII only at first, then Latin1 characters in
> UTF-8) in the hope I can add enough features to eventually call it a gemini
> client.
>
> I wouldn't attempt doing it in M68k assembly, though.
>
> [1] http://aminet.net/package/util/libs/AmiSSL-4.7
>
> [2] http://aminet.net/package/text/show/Ucode
>
> [3] http://aminet.net/package/dev/e/AmiSSL_in_E
>
> --
> Katarina . o O (we might have strayed a bit from the topic)
>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailing-list-archive.gemi.dev/www/attachments/20210214/acc57c61/attachment.htm>