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 there it is still only possible to read / write 8bit TFM/DVI. So a more modern approach would be to translate LuaTeX or PDFTeX, but this aint easy either. Patrick Sebastien Binet schrieb am Sonntag, 21. Februar 2021 um 18:15:25 UTC+1: > 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 of nicely structured Go > packages" ? :) > > my initial strategy to have something working in a mixture of Go and > C/C++ (I am in the middle of getting rid of the C++ part), is OK to get > some PDFs out of the gate, but I think I need to invest in the tooling > to do the automatic web->Go translation. (either web->Pascal->Go or > web->C->Go.) > tex.web doesn't change too much nor too often, but 3.141592653 was just > "released" after I had started my C/C++->Go migration (bummer), so it > does happen. > > -s > > -- 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, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/ed9682d1-f1f6-4eec-9cb3-b5ad78e44586n%40googlegroups.com.
