Hello! 27.10.2016, 11:32, "Alexander Ilin" :27.10.2016, 01:53, "John Benediktsson" :does it work to just use binary and then do ``>string``? Sorry, let me redo my last message. Well, it sort of works, but the result is not what I would expect, knowing that
27.10.2016, 01:53, "John Benediktsson" :does it work to just use binary and then do ``>string``? Sorry, let me redo my last message. Well, it sort of works, but the result is not what I would expect, knowing that Factor works with Unicode, and Unicode does contain all the
27.10.2016, 01:53, "John Benediktsson" :does it work to just use binary and then do ``>string``? Well, it sort of works, but the result in what I would expect, knowing that Factor works with Unicode, and Unicode does contain all the pseudographics.
27.10.2016, 03:14, "Jim Mack" :Are you talking about the characters that used to be used in character based windows apps? LIke on this page from 179-218 or so? https://en.wikipedia.org/wiki/Code_page_437 Yes, that's exactly what I'm talking about. ---=---Александр
Are you talking about the characters that used to be used in character
based windows apps? LIke on this page from 179-218 or so?
https://en.wikipedia.org/wiki/Code_page_437
On Wed, Oct 26, 2016 at 3:52 PM, John Benediktsson wrote:
> does it work to just use binary and then
does it work to just use binary and then do ``>string``?
On Wed, Oct 26, 2016 at 2:55 PM, Alexander Ilin wrote:
> Hello!
>
> I'd like to parse some log-files created by an old-style DOS program.
> They contain pseudographics characters for drawing frames and tables.
>
Hello! I'd like to parse some log-files created by an old-style DOS program.They contain pseudographics characters for drawing frames and tables.Technically, that's not ASCII, but a superset with all 8 bits used.Do we have an 8-bit encoding that would support that? I took a look at the