Re: [Freedos-devel] Historical vs. Hysterical Edlin Versions

2022-05-12 Thread Steve Nickolas

On Thu, 12 May 2022, Gregory Pietsch wrote:


FreeDOS Mavens,

I'm thinking of editing Edlin to match historical behavior after downloading 
a 1982 IBM DOS manual and a 1987 Microsoft OS/2 manual I found floating 
around the 'Net. I want to make Edlin still the small program it has always 
been without adding things that would make the executable super-huge, so I 
want to get some feedback from the list before I do anything.




Well, there wouldn't be anything wrong with poking around at the MS-DOS 
2.11 version since it's MIT-licensed now and we legally have the sauce ;)


-uso.


___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel


[Freedos-devel] Historical vs. Hysterical Edlin Versions

2022-05-12 Thread Gregory Pietsch

FreeDOS Mavens,

I'm thinking of editing Edlin to match historical behavior after 
downloading a 1982 IBM DOS manual and a 1987 Microsoft OS/2 manual I 
found floating around the 'Net. I want to make Edlin still the small 
program it has always been without adding things that would make the 
executable super-huge, so I want to get some feedback from the list 
before I do anything. The things I am considering are below:


1. At the beginning of the program, when Edlin reads the file whose
   name is on the command line, the historical thing to do is output
   "End of input file" if the entire input file has been slurped in or
   "New file" if the file does not exist yet. FreeDOS Edlin just runs
   the same code as the T command to slurp the file in and give the
   output of that command, which is the number of lines read.
2. The IBM DOS manual adds "#" as the line number that's one beyond the
   last line. This should be an easy add that doesn't change existing
   behavior.
3. The historical behavior for the Q command is to always verify that
   the user wanted to quit the program with an "Abort edit (Y/N)?" message.
4. Historically, the E command erased any backup copy (i.e. the file
   with the .BAK extension) after writing and before quitting. I don't
   know if I want to emulate this behavior.

I'll probably come up with some more. I am reluctant to add strings to 
Edlin, though, because it would make Jerome's i18n project more hairy. 
Nevertheless, part of the project's goals are to emulate historical 
behavior and eliminate hysterical behavior. There's a lot more there 
that I want to tackle just as soon as I figure it out, but I want to 
tackle the low-hanging fruit first. What do the list-subscribers say?


Gregory
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel


Re: [Freedos-devel] Testing translations

2022-05-12 Thread Daniel D.
On Wed, 11 May 2022 21:41:40 -0400
Jerome Shidel  wrote:

> Possibly. Keyboards and Codepages are vary different things. To which
> program are you referring? The program “could” have hard-coded
> keystrokes (always need Y/N…), maybe a setting in its NLS or use an
> environment variable. 
> 
> :-)
> 
> Jerome

I figured it out. For some reason the translation file (for xcopy in
this case) had some unintentional spaces before the strings. So you had
to type space and then the character you wanted (e.g. at a Y/N prompt)
for it to register. I've fixed it now on xcopy and put up a pull
request. However, I seem to have "broken" the non-UTF8
file(xcopy.no), so unfortunately I think you may have to "regenerate"
it. Special characters are now displayed incorrectly when set to
Norwegian language. It worked before I removed the spaces, maybe I've
accidentally saved it as a UTF-8 file. I'm sorry if that causes any
trouble. 

Daniel


> 
> ___
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-devel



___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel


Re: [Freedos-devel] mKEYB 0.50

2022-05-12 Thread Jim Hall
On Thu, May 12, 2022 at 7:24 AM tom ehlert  wrote:
>[..]
> > Tom: Are you planning to remain the maintainer of mKEYB, or is Davide
> > the new maintainer now? Wanted to check what is your preference.
>
> I'm planning to remain the maintainer, even this means just copying
> Davide's changes over to into 'my' version.
> I'm just busy with other stuff now, but this should soon change.
>
> It doesn't make sense to have 2 different versions of mKEYB.
> expect the same 0.50 version from me soon.
>


Sounds good! I'll watch for your version.


Jim


___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel


Re: [Freedos-devel] mKEYB 0.50

2022-05-12 Thread tom ehlert
Hallo Herr Jim Hall,

am Mittwoch, 11. Mai 2022 um 22:54 schrieben Sie:

> On Wed, May 11, 2022 at 3:51 PM Jim Hall  wrote:
>>
>> FYI that Davide has released mKEYB version 0.50. You can find it here:
>> https://github.com/davidebreso/mkeyb/releases/tag/v0.50
>>
>> The change log is:
>>
>> >Turkish Q and Turkish F layout
>> >better support for AltGr+Shift modifier
>> >less obscure uninstall warning messages
>> >executable compressed with UPX
>>
>>
>> I'm trying to keep watch on Davide's mKEYB, since Tom brought it to
>> our attention, and I am mirroring these releases to the FreeDOS Files
>> Archive at Ibiblio. But to keep from confusing which are Davide's and
>> which are Tom's, I have moved Davide's new versions into a new
>> directory:
>>
>> https://ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/keyb/mkeyb/davide/
>>


> Tom: Are you planning to remain the maintainer of mKEYB, or is Davide
> the new maintainer now? Wanted to check what is your preference.

I'm planning to remain the maintainer, even this means just copying
Davide's changes over to into 'my' version.
I'm just busy with other stuff now, but this should soon change.

It doesn't make sense to have 2 different versions of mKEYB.
expect the same 0.50 version from me soon.

Tom



___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel