Re: [Freedos-devel] CHAR: echo ascii characters

Thanks! I'll copy these into a wiki page, so we can have them for reference in one spot. I'll do that this weekend. Jim On Fri, Jul 30, 2021, 8:26 PM wrote: > For a fairly comprehensive* list I ran across this site, it lists code > pages and the first version of DOS seen > > https://www.aivos

Re: [Freedos-devel] CHAR: echo ascii characters

For a fairly comprehensive* list I ran across this site, it lists code pages and the first version of DOS seen https://www.aivosto.com/articles/charsets-codepages-dos.html * where by comprehensive I mean just DOS based code pages, not including the many additional ones available in other OSes suc

Re: [Freedos-devel] CHAR: echo ascii characters

> 248 is the degree symbol on every codepage referenced in the MS-DOS 5> manual > on my bookshelf: 437 (English), 850 (Multilingual - Latin I), > 852 (Slavic - Latin II), 860 (Portugal), 863 (Canadian-French), 865 > (Nordic) It would take me a while to research again, but I identified > several

Re: [Freedos-devel] CHAR: echo ascii characters

Just for referance Alt-248 works on Dosemu2, but of course depending on your window manager it could be eaten before Dosemu2 sees it. ___ Freedos-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedo

Re: [Freedos-devel] CHAR: echo ascii characters

On Fri, Jul 30, 2021 at 5:20 PM Bret Johnson wrote: [..] > First of all, you say that this is intended to put ASCII codes into > a file, but it just writes them to the screen. You indicate the > user was asking how to inject them into a file. The most obvious > way I can see to do that (though c

Re: [Freedos-devel] CHAR: echo ascii characters

Jim: A couple of questions & comments on this. First of all, you say that this is intended to put ASCII codes into a file, but it just writes them to the screen. You indicate the user was asking how to inject them into a file. The most obvious way I can see to do that (though certainly not the

[Freedos-devel] CHAR: echo ascii characters

Someone had emailed me to ask how to get a list of extended ASCII characters into a file on FreeDOS (the Alt key trick doesn't seem to work under a virtual machine). So I wrote a program to help them to do that. Because this is a simple program, I've released it into the public domain. I've also p

Re: [Freedos-devel] Devel-Philosophy [was: blocking bugs/issues for FreeDOS 1.3]

On 7/29/2021 5:17 PM, Jim Hall wrote: But for a modern DOS that needs to support different languages by different users in different countries, I think language catalogs (the "Kitten" method) provide the best solution. Well, the problem is that this can increase the size of a lot of executabl

Re: [Freedos-devel] PRTSCR.DOC

We're getting off topic here, but it's worth having a discussion anyway. > in that case you should translate the documentation first to something> people might read. people might read 4 or 6 pages. 60+ pages is simply> insane and exactly nobody will read beyond page 3. Well, I think all I can

Re: [Freedos-devel] Devel-Philosophy [was: blocking bugs/issues for FreeDOS 1.3]

Hi, > On Jul 30, 2021, at 8:12 AM, thraex wrote: First, thanks again for your translation work. :-) > On 30.07.2021 13:31, Jerome Shidel wrote: > >> As a reminder… >> >> If you want to contribute new or updated translations, please >> visit https://github.com/shidel/fd-nls >>

Re: [Freedos-devel] Devel-Philosophy [was: blocking bugs/issues for FreeDOS 1.3]

On Fri, Jul 30, 2021, 8:46 AM wrote: > I am going to issue a pull request for the FreeCom changes, just haven't > had a chance yet as I need to make sure I don't screw up codepages in the > process. The changes are updating an email address and url and adding an > additional % so mostly direct fi

Re: [Freedos-devel] Devel-Philosophy [was: blocking bugs/issues for FreeDOS 1.3]

I am going to issue a pull request for the FreeCom changes, just haven't had a chance yet as I need to make sure I don't screw up codepages in the process. The changes are updating an email address and url and adding an additional % so mostly direct find and replace changes. Jeremy On Fri, Jul 30

Re: [Freedos-devel] Devel-Philosophy [was: blocking bugs/issues for FreeDOS 1.3]

On 30.07.2021 13:31, Jerome Shidel wrote: > As a reminder…  > > If you want to contribute new or updated translations, please > visit https://github.com/shidel/fd-nls >  and be sure and check out > the https://github.com/shidel/fd-nls/blob/master/report.txt > <

Re: [Freedos-devel] Devel-Philosophy [was: blocking bugs/issues for FreeDOS 1.3]

Hi, > On Jul 29, 2021, at 8:17 PM, Jim Hall wrote: > > On Wed, Jul 28, 2021 at 7:15 AM Eric Auer wrote: >> >> COUNTRY=... and COUNTRY.SYS are not undocumented, but your >> choice of words hints at another idea: Do you suggest to >> introduce a TSR to handle string and key translations, to >> b