| ----------------------------------------
gopherproxy.sh fixed (mostly)
February 06th, 2024
----------------------------------------
I thought I'd post an update on my last phlog entry from 13 Dec 2013...
Better late than never I suppose... The aforementioned gopherproxy.sh
script was fixed the next day after I discovered it had stopped working.
It now uses lynx instead of squid, and seems to actually be working
better than squid did! For instance, squid often choked badly on multi-
byte UTF-8 characters; lynx does not suffer at all from this issue.
For now the biggest issue I see does revolve around unicode characters
though: There simply is no single monospace font famiy that can display
all unicode characters... The consequence of this is that whan a gopher
item contains characters from multiple radically different unicode
blocks (e.g. basic latin and braille patterns, *OR* basic latin and
unified Han) the browser or OS is sourcing a different font for the
blocks that the embedded font in my stylesheet does not support... For
actual readable text it's probably not a problem, though it could be a
little ugly. For text art, however, it totally breaks it because when
multiple fonts are sourced, the glyphs from each given font are never
the same size.
In related news, as-of yesterday, gopherproxy.sh partially converts ANSI
escape sequences into CSS colors... Usually I don't add features unless
it is something that lynx supports, but I also use Lagrange, and it
supports them, so why the hell not? Besides, lynx -source can be piped
into ansi2html and then back into lynx to deal with any ANSI nonsense...
---------------------------------------- |