Fosstodon

Felix Palmen :freebsd: :c64:You might think rendering <a href="https://mastodon.bsd.cafe/tags/MSDOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#MSDOS</a> <a href="https://mastodon.bsd.cafe/tags/ANSIart" class="mention hashtag" rel="nofollow noopener" target="_blank">#ANSIart</a> on a modern <a href="https://mastodon.bsd.cafe/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows</a> is just fine because it still supports the old codepages, including <a href="https://mastodon.bsd.cafe/tags/cp437" class="mention hashtag" rel="nofollow noopener" target="_blank">#cp437</a>. Well, sort of.Some escape sequences are interpreted differently than ANSI.SYS did. In the worst case, you'll just see garbage. Most files are "sane" enough though, but even then, the default colors are "just wrong"...<a href="https://mastodon.bsd.cafe/tags/dos2ansi" class="mention hashtag" rel="nofollow noopener" target="_blank">#dos2ansi</a> takes advantage of the 256color support available since Windows 10 to mimic the original <a href="https://mastodon.bsd.cafe/tags/VGA" class="mention hashtag" rel="nofollow noopener" target="_blank">#VGA</a> palette. It also renders to a virtual canvas first, exactly emulating ANSI.SYS, and then uses a safe subset of ANSI for actual output. And it can read and display <a href="https://mastodon.bsd.cafe/tags/SAUCE" class="mention hashtag" rel="nofollow noopener" target="_blank">#SAUCE</a> metadata. 😎Of course it also works on <a href="https://mastodon.bsd.cafe/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a>, <a href="https://mastodon.bsd.cafe/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeBSD</a>, etc.<a href="https://zirias.github.io/dos2ansi/" rel="nofollow noopener" translate="no" target="_blank">https://zirias.github.io/dos2ansi/</a>

Felix Palmen :freebsd: :c64:Also quite recent: <a href="https://mastodon.bsd.cafe/tags/dos2ansi" class="mention hashtag" rel="nofollow noopener" target="_blank">#dos2ansi</a>. This is a very versatile converter for <a href="https://mastodon.bsd.cafe/tags/MSDOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#MSDOS</a> <a href="https://mastodon.bsd.cafe/tags/ansiart" class="mention hashtag" rel="nofollow noopener" target="_blank">#ansiart</a> (and other "text") files to a format using <a href="https://mastodon.bsd.cafe/tags/Unicode" class="mention hashtag" rel="nofollow noopener" target="_blank">#Unicode</a> and only standard <a href="https://mastodon.bsd.cafe/tags/ANSI" class="mention hashtag" rel="nofollow noopener" target="_blank">#ANSI</a> <a href="https://mastodon.bsd.cafe/tags/SGR" class="mention hashtag" rel="nofollow noopener" target="_blank">#SGR</a> escape sequences, so, suitable for today's terminals like <a href="https://mastodon.bsd.cafe/tags/xterm" class="mention hashtag" rel="nofollow noopener" target="_blank">#xterm</a>. It includes an ansiart viewer which is "just" a shellscript, leveraging dos2ansi, xterm, less and some nice original <a href="https://mastodon.bsd.cafe/tags/IBM" class="mention hashtag" rel="nofollow noopener" target="_blank">#IBM</a> fonts to do its job. So, maybe something for the <a href="https://mastodon.bsd.cafe/tags/retrocomputing" class="mention hashtag" rel="nofollow noopener" target="_blank">#retrocomputing</a> fans.<a href="https://github.com/Zirias/dos2ansi" rel="nofollow noopener" translate="no" target="_blank">https://github.com/Zirias/dos2ansi</a>Docs (manpages) are here: <a href="https://zirias.github.io/dos2ansi/" rel="nofollow noopener" translate="no" target="_blank">https://zirias.github.io/dos2ansi/</a>As there was *some* interest, a <a href="https://mastodon.bsd.cafe/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeBSD</a> port is available: <a href="https://www.freshports.org/converters/dos2ansi" rel="nofollow noopener" translate="no" target="_blank">https://www.freshports.org/converters/dos2ansi</a>

Felix Palmen 📯<a href="https://fosstodon.org/@dani" class="u-url mention" rel="nofollow noopener" target="_blank">@dani</a> Haha 😎 I'm running a (heavily configured) <a href="https://techhub.social/tags/fvwm3" class="mention hashtag" rel="nofollow noopener" target="_blank">#fvwm3</a> here. This screenshot was just for demonstration that <a href="https://techhub.social/tags/dos2ansi" class="mention hashtag" rel="nofollow noopener" target="_blank">#dos2ansi</a> and <a href="https://techhub.social/tags/showansi" class="mention hashtag" rel="nofollow noopener" target="_blank">#showansi</a> don't depend on any configuration, so this was a completely unconfigured X session in <a href="https://techhub.social/tags/Xephyr" class="mention hashtag" rel="nofollow noopener" target="_blank">#Xephyr</a>, which by default runs <a href="https://techhub.social/tags/twm" class="mention hashtag" rel="nofollow noopener" target="_blank">#twm</a>.You can even see the test mode in <a href="https://techhub.social/tags/xterm" class="mention hashtag" rel="nofollow noopener" target="_blank">#xterm</a> can only use 8 colors (because this is what the default xterm <a href="https://techhub.social/tags/terminfo" class="mention hashtag" rel="nofollow noopener" target="_blank">#terminfo</a> entry announces), still the <a href="https://techhub.social/tags/xterm" class="mention hashtag" rel="nofollow noopener" target="_blank">#xterm</a> windows launched by <a href="https://techhub.social/tags/showansi" class="mention hashtag" rel="nofollow noopener" target="_blank">#showansi</a> have full color support, they explicitly set the terminal name to "xterm-256colors".

Felix Palmen 📯Not having added anything to <a href="https://techhub.social/tags/dos2ansi" class="mention hashtag" rel="nofollow noopener" target="_blank">#dos2ansi</a> for a while now, I'd say v2.0 is the "final" version for now. I initially wanted that for v1.0, and it's amazing how many weird files, edge cases, and also ideas for improvements you can discover for something that "simple" 🙈 I have ideas for future development, like provide the core functionalities as a shared library, like add some config file for dos2ansi itself as well (instead of just for <a href="https://techhub.social/tags/showansi" class="mention hashtag" rel="nofollow noopener" target="_blank">#showansi</a>), maybe even more ... but all of that can wait, it's IMHO "complete" as it is.A <a href="https://techhub.social/tags/Debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#Debian</a> package is attached to the release on github, and a <a href="https://techhub.social/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeBSD</a> port is added ... anyone wants to help make it available in more repositories? 😎 Would be most helpful if the fonts it uses by default are packaged as well and can be set as dependencies ... <a href="https://repology.org/project/dos2ansi/versions" rel="nofollow noopener" translate="no" target="_blank">https://repology.org/project/dos2ansi/versions</a><a href="https://techhub.social/tags/retrocomputing" class="mention hashtag" rel="nofollow noopener" target="_blank">#retrocomputing</a> <a href="https://techhub.social/tags/ansiart" class="mention hashtag" rel="nofollow noopener" target="_blank">#ansiart</a> <a href="https://techhub.social/tags/msdos" class="mention hashtag" rel="nofollow noopener" target="_blank">#msdos</a>

Felix Palmen 📯I just pushed an official <a href="https://techhub.social/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeBSD</a> port of <a href="https://techhub.social/tags/dos2ansi" class="mention hashtag" rel="nofollow noopener" target="_blank">#dos2ansi</a> 😉 <a href="http://www.freshports.org/converters/dos2ansi" rel="nofollow noopener" translate="no" target="_blank">http://www.freshports.org/converters/dos2ansi</a>

Felix Palmen 📯And now, the full docs for <a href="https://techhub.social/tags/dos2ansi" class="mention hashtag" rel="nofollow noopener" target="_blank">#dos2ansi</a> v2.0 are available online as well: <a href="https://zirias.github.io/dos2ansi" rel="nofollow noopener" translate="no" target="_blank">https://zirias.github.io/dos2ansi</a>IMHO manpages are an awesome documentation format. And with a little bit of "responsive" <a href="https://techhub.social/tags/CSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#CSS</a>, they're well usable on a mobile as well -- I wished the typical "online man" sites would do something like that 😉

Felix Palmen 📯Released: <a href="https://techhub.social/tags/dos2ansi" class="mention hashtag" rel="nofollow noopener" target="_blank">#dos2ansi</a> v2.0 <a href="https://github.com/Zirias/dos2ansi/releases/tag/v2.0" rel="nofollow noopener" translate="no" target="_blank">https://github.com/Zirias/dos2ansi/releases/tag/v2.0</a>The real "visible change" is documentation. <a href="https://techhub.social/tags/showansi" class="mention hashtag" rel="nofollow noopener" target="_blank">#showansi</a> now got a manpage as well, and the one for <a href="https://techhub.social/tags/dos2ansi" class="mention hashtag" rel="nofollow noopener" target="_blank">#dos2ansi</a> improved a lot. Also better build instructions and some updates/corrections in the README. With these docs, you can hopefully make it do exactly what you want 😉Also, the build system (my own homebrewn <a href="https://techhub.social/tags/GNU" class="mention hashtag" rel="nofollow noopener" target="_blank">#GNU</a> <a href="https://techhub.social/tags/make" class="mention hashtag" rel="nofollow noopener" target="_blank">#make</a> framework) got lots of improvements and fixes. <a href="https://github.com/Zirias/zimk/" rel="nofollow noopener" translate="no" target="_blank">https://github.com/Zirias/zimk/</a><a href="https://techhub.social/tags/ANSIart" class="mention hashtag" rel="nofollow noopener" target="_blank">#ANSIart</a> <a href="https://techhub.social/tags/MSDOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#MSDOS</a> <a href="https://techhub.social/tags/retrocomputing" class="mention hashtag" rel="nofollow noopener" target="_blank">#retrocomputing</a>

Felix Palmen 📯I'm planning to create a release <a href="https://techhub.social/tags/dos2ansi" class="mention hashtag" rel="nofollow noopener" target="_blank">#dos2ansi</a> v2.0 soon, which will have more or less the feature set of v1.8, but with complete and helpful documentation for everything. Main work left to do for that is to add more text to the manpages 😉At least, the tool I wrote for generating docs now has everything I'll need for that!<a href="https://github.com/Zirias/mkclidoc" rel="nofollow noopener" translate="no" target="_blank">https://github.com/Zirias/mkclidoc</a>

Felix Palmen 📯And now, my little documentation generation tool can also produce manpages in <a href="https://techhub.social/tags/HTML" class="mention hashtag" rel="nofollow noopener" target="_blank">#HTML</a> format (this will be useful for the <a href="https://techhub.social/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows</a> version of <a href="https://techhub.social/tags/dos2ansi" class="mention hashtag" rel="nofollow noopener" target="_blank">#dos2ansi</a>) 😎 Using simple/minimal semantic markup, the "manpage style" is entirely left to <a href="https://techhub.social/tags/CSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#CSS</a>Screenshots: - Desktop unstyled - Desktop bright mode - Desktop dark mode - Mobile dark mode

Felix Palmen 📯Now working on adding a manpage for <a href="https://techhub.social/tags/showansi" class="mention hashtag" rel="nofollow noopener" target="_blank">#showansi</a> as well. I noticed I need to add features to my "mkclidoc" tool in order to get something meaningful here ...First step, added support for cross-references 😎 -- next thing needed will be documenting related files...Next <a href="https://techhub.social/tags/dos2ansi" class="mention hashtag" rel="nofollow noopener" target="_blank">#dos2ansi</a> release will probably just be nice and complete documentation!

Felix Palmen 📯Here's a quick demo how the new documentation generation in <a href="https://techhub.social/tags/dos2ansi" class="mention hashtag" rel="nofollow noopener" target="_blank">#dos2ansi</a> works 😎 <a href="https://github.com/Zirias/mkclidoc" rel="nofollow noopener" translate="no" target="_blank">https://github.com/Zirias/mkclidoc</a>Screenshots: - Input format (on github) - help (-h) output (on <a href="https://techhub.social/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows</a>) - manpage (on <a href="https://techhub.social/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeBSD</a>)Might make sense to add some <a href="https://techhub.social/tags/HTML" class="mention hashtag" rel="nofollow noopener" target="_blank">#HTML</a> output as well, e.g. for the Windows binary package... 🤔

Felix Palmen 📯<a href="https://techhub.social/tags/dos2ansi" class="mention hashtag" rel="nofollow noopener" target="_blank">#dos2ansi</a> v1.8 released! <a href="https://github.com/Zirias/dos2ansi/releases/tag/v1.8" rel="nofollow noopener" translate="no" target="_blank">https://github.com/Zirias/dos2ansi/releases/tag/v1.8</a>There's some major rework inside adding support for seekable streams, which was necessary to implement the logic detecting <a href="https://techhub.social/tags/SAUCE" class="mention hashtag" rel="nofollow noopener" target="_blank">#SAUCE</a> even when the preceding DOS EOF character is missing.Quite some improvements to the <a href="https://techhub.social/tags/showansi" class="mention hashtag" rel="nofollow noopener" target="_blank">#showansi</a> script as well, now comes with "fontsets" (explained in the comments in these and the config file) 😎 Plus added a manpage. Wanted a single source of truth (shared with the help output) and didn't find a good tool for that, so I quickly came up with my own: <a href="https://github.com/Zirias/mkclidoc" rel="nofollow noopener" translate="no" target="_blank">https://github.com/Zirias/mkclidoc</a> It's bundled with dos2ansi now. Can produce man in both classic troff and BSD mandoc. The default choice is based on `uname` for now, tested on <a href="https://techhub.social/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeBSD</a> and <a href="https://techhub.social/tags/Debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#Debian</a>.<a href="https://techhub.social/tags/ANSIart" class="mention hashtag" rel="nofollow noopener" target="_blank">#ANSIart</a> <a href="https://techhub.social/tags/MSDOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#MSDOS</a> <a href="https://techhub.social/tags/retrocomputing" class="mention hashtag" rel="nofollow noopener" target="_blank">#retrocomputing</a>

Felix Palmen 📯I just released <a href="https://techhub.social/tags/dos2ansi" class="mention hashtag" rel="nofollow noopener" target="_blank">#dos2ansi</a> v1.7, which includes one final bugfix: Quoted output of <a href="https://techhub.social/tags/SAUCE" class="mention hashtag" rel="nofollow noopener" target="_blank">#SAUCE</a> metadata should use proper "shell-style" quoting, so it can be directly consumed by <a href="https://techhub.social/tags/showansi" class="mention hashtag" rel="nofollow noopener" target="_blank">#showansi</a>, which it does now. Plus <a href="https://techhub.social/tags/showansi" class="mention hashtag" rel="nofollow noopener" target="_blank">#showansi</a> got a (tiny) bit of optimization.<a href="https://github.com/Zirias/dos2ansi/releases/tag/v1.7" rel="nofollow noopener" translate="no" target="_blank">https://github.com/Zirias/dos2ansi/releases/tag/v1.7</a>Well, just after releasing, I found more stuff to tackle. No, not new bugs at least.But more weirdly broken ANSIart files. Example: <a href="https://16colo.rs/pack/root0297/FU-B%26B.ANS" rel="nofollow noopener" translate="no" target="_blank">https://16colo.rs/pack/root0297/FU-B%26B.ANS</a>This one *has* SAUCE metadata, but it's not properly "hidden" behind a DOS EOF character (0x1a), which means even 'type' on a real DOS machine will output the SAUCE gibberish below the pic 🙈 So, there *might* be a v1.8 adding more heuristics to detect and parse more broken SAUCE ... 😂 <a href="https://techhub.social/tags/MSDOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#MSDOS</a> <a href="https://techhub.social/tags/ANSIart" class="mention hashtag" rel="nofollow noopener" target="_blank">#ANSIart</a> <a href="https://techhub.social/tags/retrocomputing" class="mention hashtag" rel="nofollow noopener" target="_blank">#retrocomputing</a>

Felix Palmen 📯Yet another revision, <a href="https://techhub.social/tags/dos2ansi" class="mention hashtag" rel="nofollow noopener" target="_blank">#dos2ansi</a> v1.6.3 <a href="https://github.com/Zirias/dos2ansi/releases/tag/v1.6.3" rel="nofollow noopener" translate="no" target="_blank">https://github.com/Zirias/dos2ansi/releases/tag/v1.6.3</a>--- brings yet another subtle bugfix in <a href="https://techhub.social/tags/showansi" class="mention hashtag" rel="nofollow noopener" target="_blank">#showansi</a>: To set the title with an escape sequence, it uses "printf %b" with its \-notation for control characters, so literal backslashes in the title must be escaped as well 🙈 Apart from that, added nice "portability bikeshed":- Removed the dependency on 'sed' again, quoting/escaping strings for 'eval' *can* be done in pure <a href="https://techhub.social/tags/POSIX" class="mention hashtag" rel="nofollow noopener" target="_blank">#POSIX</a> <a href="https://techhub.social/tags/shell" class="mention hashtag" rel="nofollow noopener" target="_blank">#shell</a> script.- Added proper detection of the POSIX shell to my <a href="https://techhub.social/tags/zimk" class="mention hashtag" rel="nofollow noopener" target="_blank">#zimk</a> build system, along with variables to override the choice. Used that to generate the shebang for <a href="https://techhub.social/tags/dos2ansi" class="mention hashtag" rel="nofollow noopener" target="_blank">#dos2ansi</a>. Really an awesome way to write /bin/sh without writing /bin/sh 😂 (rumors say there *are* POSIX systems with the compliant shell in a different path ...)Screenshot: Yet another file with "weird" title from <a href="https://techhub.social/tags/SAUCE" class="mention hashtag" rel="nofollow noopener" target="_blank">#SAUCE</a><a href="https://techhub.social/tags/ANSIart" class="mention hashtag" rel="nofollow noopener" target="_blank">#ANSIart</a> <a href="https://techhub.social/tags/MSDOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#MSDOS</a> <a href="https://techhub.social/tags/retrocomupting" class="mention hashtag" rel="nofollow noopener" target="_blank">#retrocomupting</a>

Felix Palmen 📯And now there's even <a href="https://techhub.social/tags/dos2ansi" class="mention hashtag" rel="nofollow noopener" target="_blank">#dos2ansi</a> v1.6.2: <a href="https://github.com/Zirias/dos2ansi/releases/tag/v1.6.2" rel="nofollow noopener" translate="no" target="_blank">https://github.com/Zirias/dos2ansi/releases/tag/v1.6.2</a>The good thing is: The issues I'm fixing here are getting more and more obscure 😂First I noticed <a href="https://techhub.social/tags/xterm" class="mention hashtag" rel="nofollow noopener" target="_blank">#xterm</a> doesn't accept all <a href="https://techhub.social/tags/utf8" class="mention hashtag" rel="nofollow noopener" target="_blank">#utf8</a> for its '-title' option, no matter what. But it *does* support the escape sequence to set a title, so, why not use this instead.Having added support for that (and also optionally for setting the window size using an escape sequence), I had a look at quoting again. Indeed, <a href="https://techhub.social/tags/showansi" class="mention hashtag" rel="nofollow noopener" target="_blank">#showansi</a> failed for e.g. file names containing <a href="https://techhub.social/tags/shell" class="mention hashtag" rel="nofollow noopener" target="_blank">#shell</a> special characters.Therefore added a *safe* quote function. The downside is, it requires <a href="https://techhub.social/tags/sed" class="mention hashtag" rel="nofollow noopener" target="_blank">#sed</a> now. Well ....Screenshot shows both improvements, I picked a "maximum weird" file name and used a file that has an 'ö' in its title 🥳 -- in the showansi debugging output, you can see the quoting in action 🤯 <a href="https://techhub.social/tags/MSDOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#MSDOS</a> <a href="https://techhub.social/tags/ANSIart" class="mention hashtag" rel="nofollow noopener" target="_blank">#ANSIart</a> <a href="https://techhub.social/tags/retrocomupting" class="mention hashtag" rel="nofollow noopener" target="_blank">#retrocomupting</a>

Felix Palmen 📯<a href="https://techhub.social/tags/dos2ansi" class="mention hashtag" rel="nofollow noopener" target="_blank">#dos2ansi</a> v1.6.1 (a pure bugfix/service release): <a href="https://github.com/Zirias/dos2ansi/releases/tag/v1.6.1" rel="nofollow noopener" translate="no" target="_blank">https://github.com/Zirias/dos2ansi/releases/tag/v1.6.1</a>* Fix possible crash (🙈) when querying for font or codepage on a file with a non-text <a href="https://techhub.social/tags/SAUCE" class="mention hashtag" rel="nofollow noopener" target="_blank">#SAUCE</a> type. * Try to parse something meaningful even out of partially broken SAUCE dataYep, the possible crash was the reason to create a release even for a pretty "small" bugfix. 🙄 Chances are nobody would have noticed though, the SAUCE *display* was not affected, only the machine-readable query (-q).Screenshot: The "offending" file. It even had literal ",1" written in the month field of the SAUCE date, but obviously meaning January here 😂<a href="https://techhub.social/tags/MSDOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#MSDOS</a> <a href="https://techhub.social/tags/ANSIart" class="mention hashtag" rel="nofollow noopener" target="_blank">#ANSIart</a> <a href="https://techhub.social/tags/retrocomputing" class="mention hashtag" rel="nofollow noopener" target="_blank">#retrocomputing</a>

Felix Palmen 📯Meanwhile:* Added a <a href="https://techhub.social/tags/Debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#Debian</a> (amd64) package to <a href="https://techhub.social/tags/dos2ansi" class="mention hashtag" rel="nofollow noopener" target="_blank">#dos2ansi</a> v1.6 release (on Github) * Updated the <a href="https://techhub.social/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeBSD</a> port here: <a href="https://people.freebsd.org/~zirias/patches/0001-converters-dos2ansi-Add-new-port.patch" rel="nofollow noopener" translate="no" target="_blank">https://people.freebsd.org/~zirias/patches/0001-converters-dos2ansi-Add-new-port.patch</a> * There's of course still the <a href="https://techhub.social/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows</a> binary attached to the releaseMight push the FreeBSD port to official ports later ....Screenshot: Random <a href="https://techhub.social/tags/showansi" class="mention hashtag" rel="nofollow noopener" target="_blank">#showansi</a> rendering ... 🙈 <a href="https://techhub.social/tags/MSDOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#MSDOS</a> <a href="https://techhub.social/tags/ANSIart" class="mention hashtag" rel="nofollow noopener" target="_blank">#ANSIart</a> <a href="https://techhub.social/tags/retrocomputing" class="mention hashtag" rel="nofollow noopener" target="_blank">#retrocomputing</a>

Felix Palmen 📯Just noticed the <a href="https://techhub.social/tags/showansi" class="mention hashtag" rel="nofollow noopener" target="_blank">#showansi</a> script from <a href="https://techhub.social/tags/dos2ansi" class="mention hashtag" rel="nofollow noopener" target="_blank">#dos2ansi</a> is now "smarter" than the renderer on 16colo.rs 😂 When there's no (<a href="https://techhub.social/tags/SAUCE" class="mention hashtag" rel="nofollow noopener" target="_blank">#SAUCE</a>) metadata indicating the font to use, but the canvas after rendering turns out to be exactly 80x50 or 80x43, it just *guesses* that's most likely the VGA50 or EGA43 mode and picks that font 😉 (Of course, this "smartness" can be disabled with the "-S" flag)Compare to this: <a href="https://16colo.rs/pack/avpack16/frg-ans2.ans" rel="nofollow noopener" translate="no" target="_blank">https://16colo.rs/pack/avpack16/frg-ans2.ans</a><a href="https://techhub.social/tags/ANSIart" class="mention hashtag" rel="nofollow noopener" target="_blank">#ANSIart</a> <a href="https://techhub.social/tags/MSDOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#MSDOS</a> <a href="https://techhub.social/tags/retrocomputing" class="mention hashtag" rel="nofollow noopener" target="_blank">#retrocomputing</a>

Felix Palmen 📯<a href="https://techhub.social/tags/dos2ansi" class="mention hashtag" rel="nofollow noopener" target="_blank">#dos2ansi</a> v1.6: <a href="https://github.com/Zirias/dos2ansi/releases/tag/v1.6" rel="nofollow noopener" translate="no" target="_blank">https://github.com/Zirias/dos2ansi/releases/tag/v1.6</a>* Fix cursor movement again, it never wraps or scrolls. * Many smaller improvements to the <a href="https://techhub.social/tags/showansi" class="mention hashtag" rel="nofollow noopener" target="_blank">#showansi</a> script * Add an example configuration using scalable fonts from <a href="https://int10h.org/oldschool-pc-fonts/" rel="nofollow noopener" translate="no" target="_blank">https://int10h.org/oldschool-pc-fonts/</a> instead of the default bitmap fontsScalable fonts are a tradeoff here. You get freely configurable sizes and correction of aspect ratio. You lose pixel-perfect (perfectly sharp) display. You can't have both, unfortunately.Screenshot shows scalable fonts 😉 <a href="https://techhub.social/tags/MSDOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#MSDOS</a> <a href="https://techhub.social/tags/ANSIart" class="mention hashtag" rel="nofollow noopener" target="_blank">#ANSIart</a> <a href="https://techhub.social/tags/retrocomputing" class="mention hashtag" rel="nofollow noopener" target="_blank">#retrocomputing</a>

Felix Palmen 📯There was still room for improvement ....From "just needs a little <a href="https://techhub.social/tags/script" class="mention hashtag" rel="nofollow noopener" target="_blank">#script</a> to turn <a href="https://techhub.social/tags/dos2ansi" class="mention hashtag" rel="nofollow noopener" target="_blank">#dos2ansi</a> in a nice ANSIart viewer" to a ~400-lines "monster" in 8 days ... 😂 It *should* work well with any <a href="https://techhub.social/tags/POSIX" class="mention hashtag" rel="nofollow noopener" target="_blank">#POSIX</a> <a href="https://techhub.social/tags/shell" class="mention hashtag" rel="nofollow noopener" target="_blank">#shell</a>. I hope so. 🙈 <a href="https://github.com/Zirias/dos2ansi/blob/master/src/bin/dos2ansi/showansi.in" rel="nofollow noopener" translate="no" target="_blank">https://github.com/Zirias/dos2ansi/blob/master/src/bin/dos2ansi/showansi.in</a>

Recent searches

Search options

Administered by:

Server stats:

#dos2ansi