Hey Andy, Thank you for yours answers
Le dim. 22 nov. 2020 à 18:11, andy pugh <bodge...@gmail.com> a écrit : > I moved the docs into a sub-directory. > Let's say that's a start ;-) I have done some work to enable multilingual documentation in .comp > files, and translated manually-written manpages (should) be > automatically handled. > I seem to have forgotten to merge the multilingual halcompile changes. > > https://github.com/LinuxCNC/linuxcnc/commit/5dc2ef3ce76942a66d2b39d6e2542cb8ea51253c That's a nice step forward for sure ! Nevertheless, after diving into this yesterday and tonight, I think that being able to use tools such as OmegaT, POedit and Crowdin ( https://support.crowdin.com/translation-process-overview/, playing at setting this up to see how that really [could] work: https://crowdin.com/project/linuxcnc) would really help translators work and maybe build a team for this task... To better benefit these, it seems preferable that l10n strings be stored in dedicated files rather than embedded in source files. So could be that adding gettext support to comps could be more better suited... Sorry, I don't understand what you mean about man pages :/ > - Should the mixed language hierarchy be kept or should language specific > > subdirectories/hierarchies be built ? Too new to this to grasp the > > pros/cons of each organisation. > > Possibly an issue to worry about later? > ... well, at first sight, it seems that tools mentioned above all tend to like the one directory per language organization, like we already have for man pages. _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
