Hello, Thank you Jerome for your reply.
> Jerome Shidel <jer...@shidel.net> şunları yazdı (18 May 2020 15:17): > > But, that is mostly just normal management headaches. To fix that, a common repository with all strings’ files would be an ideal intermediary solution. Each package maintainer would upload their strings, and translators could update as necessary. And it should be the translator’s responsibility to make sure that before a release all translations are updated. > > Occasionally, individuals have sent me translations for packages other than > the ones I develop. With no good place to send them at present, > I just started to funnel all translations into a new Github project at > https://github.com/shidel/fd-nls I have updated a couple of translations, and opened a PR for them. > The best solution, is to send translations to the actual developer of the > individual project the translation was created. I tend to disagree. AFAIS, it is really hard to find all the maintainers, and chase them to update their version. Instead, maintaining them at the FDOS organisation (each project would have their own maintainer and only the maintainer would have the permission to edit) would contribute to a steady development. This would really help the FDOS release managers to update the latest strings before a major release. Regarding the remaining translations, I still have fdpkg, fc, tee, md5sum, password and htmlhelp to update. I searched on the internet for the source files, but most ibiblio links are dead and some of the source files have conflicting message file contents/outdated. I would really appreciate help regarding these files. On the main Github org; edlin, find, sort have pending PRs for the translations as well. Thank you, Emir _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
