Hi Thraex, I agree with you. A RC5 would also be helpful for me to see if everything works correct. With some of NLS files at Github I have absolutely no idea why it should make sense to translate them at all. So I will not translate them for the moment. From my side there is a more basic problem: As I see it as a user, FreeDOS is finished for estimated 60 percent. I will try to explain it below. But I think it should work stable enough for a new RC5 - and maybe a 1.3 when this RC5 is out. Okay, lets start with the question why it is finished for 60 %:
As I am not sure if I will have time for the next meeting, here some ideas. I do not say that it should already be implemented in the next version, but I think it should be done some day to come to an end with a complete FreeDOS. I know it is problematic to find programmers, but when the following things are done step by step it will work very fine some day. a) external commands: Some of them have a text in the readme file: "still to do", "known bugs" "roadmap" etc. These commands should be checked and all these things fixed (if necessary, otherwise text should be removed) b) a lot of (external) commands support no NLS. This should be added to get a unique system. I know that this is a lot of work, but it makes sense in my eyes. c) fixing the bugs reported on the FD Bug Tracker at Sourceforge - independent which priority is actually set. d) (html)help still does not work correct; AMB is a nice feature but it does not directly work with htm-files, so it may become a problem some day. And there is a basic update available on Jeromes github site. e) scandisk 0.5 - a fine tool, but it never worked. Only the GUI exists. Would be nice to have it some day. f) support for FAT32 and lfn for all commands, g) with some compilers / whatever it is VERY VERY hard to write an NLS file. Especial when there are variables within the text as each language has a different grammatic. You have to look three times what is text and what is no text to translate. Would it be possible to avoid such compilers? h) at https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/backup/ there are two htm files that describe backup/restore. One of them is written by Ralf Quint, a member of the FD group. (hi Ralf, Warsteiner is not the best german beer). Till today I only saw this htm file but no binary. Is this binary available? Can it be added? i) NLS support: Is there anybody who can tell me if all DOS commands support [J(a)|Nein] or [O(ui)|N(on)] etc. instead of [Y(es)|N(o)]? If not, they should do it. As a translator you never know what to do. This is only a collection of ideas that shall help to get FreeDOS to a "final" version. Willi @ Thomas Muller: Is this text format ok? Sent: Tuesday, July 27, 2021 at 12:49 PM From: "thraex" <thr...@numericable.fr> To: freedos-devel@lists.sourceforge.net Subject: Re: [Freedos-devel] What are the blocking bugs/issues for FreeDOS 1.3? On 26.07.2021 01:29, Jim Hall wrote: > And: With the updates we have, are we ready to release this as > "FreeDOS 1.3" or do we need a "FreeDOS 1.4 RC5"? As a translator and somewhat a tester, IMHO a RC5 would be necessary. For example, when one chooses the French or Turkish (and possibly other) keyboard layouts on the installer, after the installation this is not taken into account (bug 282 & bug 306). FreeCOM wasn't using some of the translations in RC4, so there was no easy way to check if they were OK (see <https://github.com/FDOS/freecom/issues/24>). I stupidly left French translations of diskcopy, fdnpkg, md5sum and mem in UTF-8 (no idea how I managed this, sorry) -- this will be fixed when Jerome has time to take care of <https://github.com/shidel/fd-nls/issues/26[https://github.com/shidel/fd-nls/issues/26]>. Fritz Mueller also brought to my attention some mistakes in Blocek translations (keyboard shortcut & charset issues) that I need to fix (and Blocek 1.62 would need to be packaged to replace 1.4 if Laaca doesn't finish and release 1.7 in time for FreeDOS 1.3). Obviously none of these are showstoppers but as compiling this stuff is beyond my abilities, I'd love to be able to check it with a new RC and make final adjustments if necessary to avoid giving a bad overall impression to newbies like me. _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel[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
