On Sun Feb 21, 2021 at 18:19 CET, Patrick wrote:
> My problem with the TeX code base was that TeX is mainly spaghetti code
> (once untangled) and has many places where one would rather use Go code
> instead of the 'hacks' DEK has used to ensure compatibility (for example the
> ASCII input/output).
My problem with the TeX code base was that TeX is mainly spaghetti code
(once untangled) and has many places where one would rather use Go code
instead of the 'hacks' DEK has used to ensure compatibility (for example
the ASCII input/output). So it is really hard to follow the code.
And from
On Sun Feb 21, 2021 at 17:46 CET, Patrick wrote:
> Hi Sebastien,
>
> that was a manual translation of the web file.
> My plan was to do more than that, ... TeX is such a beast.
yeah... "how hard would it be to translate ~20k lines of C/C++ code (or
6k lines of obfuscated Pascal code) into a set
Hi Sebastien,
that was a manual translation of the web file. My plan was to do more than
that, ... TeX is such a beast.
Patrick
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it,
Hi Patrick,
Nice!
Did you manually translated it or was it done with some tooling?
-s
Original Message
On Feb 21, 2021, 07:43, Patrick < std...@gmail.com> wrote:
Hi Sebastien,
a few years ago I started with dvitype
https://github.com/speedata/gotex
Patrick
Sebastien Binet
Hi Sebastien,
a few years ago I started with dvitype
https://github.com/speedata/gotex
Patrick
Sebastien Binet schrieb am Dienstag, 16. Februar 2021 um 15:23:41 UTC+1:
> hi there,
>
> I'd like to introduce star-tex[1], a (Work In Progress) TeX engine.
>
> it wraps the output of the official
