Hi! > ...write code to support it. We could use a compatible > Backup/Restore that is under the GNU GPL or a similar > free-for-everyone license. The FreeCOM project has been idle for a > long time, and needs a maintainer to update it. There have been > various requests for the kernel that need fixing.
Not to forget free FDISK, which has several bugs which all relate to the same few areas of code... The maintainer was going to look into it again, but he certainly can use some help... As for FreeCOM command.com and kernel: You can try to contact blairdude at gmail... who maintained FreeCOM, but he is not online that often. Still worth a try, as he may have more up to date versions compared to what is in the SVN repository. For the kernel, please contact the kernel mailing list and/or me if you want to help... :-). > 2. The Freemacs editor needs updating. Interesting :-). Aitor also plans to update our EDIT, but I have not heard about his project recently... > 3. Again, look at the FreeDOS Software List, and find a utility that > hasn't yet been converted to support internationalization through the > Kitten (or Cats) library, and provide the patches necessary to support For this category, I recommend looking at the ratio between size of the binary, number of strings and number of users. If you have only few strings and the tool is small, you may not want to double its size by adding multi language support in particular if there are few users or the tool is simple. Of course that is only my personal opinion :-). For tools written in Assembly language, you typically do the i18n as a compile time step: Cutemouse can be compiled in several languages and new Runtime has several languages in 1 binary. Last but not least there are points beyond 3.: Fritz Mueller can use some proof reading for his HTMLHELP update. This means checking whether the help describes DOS correctly and is written in correct English and German. The help can be used from the DOS prompt (local copy) and via a web browser. Also our Bugzilla gives a good overview about which tools have how many relevant open bugs, but it is also good to re-test things to see whether the bugs actually still do exist in current versions of our stuff. Finally, to be able to make a FreeDOS 1.1 CDROM at all, the FDUPDATE project needs help. This means that for all apps which got updated after 1.0, we need two ZIPs in the right directory structure so it can be installed by unzipping it into the fdos directory. FDUPDATE, FDPKG and the installer also support some extra things like install triggers in special batch files in the zip and dependency info in text files in the zip, but those are often optional/trivial. You can find some updated stuff and a list of almost all to be updated things online: already updated packages: http://mateusz.viste.free.fr/fdupdate/ list of versions: http://www.freedos.org/freedos/software/ some updated packages: http://rugxulo.googlepages.com/ other version/url list: http://rugxulo.googlepages.com/fdpkgnew.txt Everybody is welcome to help with any of the mentioned :-). Thanks :-) Eric ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
