Halo, I am just doing the work, getting gmoccapy separated from gscreen. I decided together with Chris to do that, because gmoccapy is meanwhile very special and not any more a typical gscreen custom GUI.
I got all the things running fine, and am am preparing to push to master, but.... Till now I had my icons and locale settings in my own gmoccapy folder. It would be possible to include the locale in share/gmoccapy, but IMHO that is not the correct way to go. IMHO I should maintain the gmoccapy.pot and gmoccapy.po files in src, because they will be changing for quite a while, because gmoccapy is still and will be for a while under development. The question is: Must the files be merged with linuxcnc.po (mo) IMHO no, I go much more far and say it should not!! I will try to explain: gmoccapy.po contains 438 translated lines , what mean 100 % linuxcnc.po contains 3008 lines , but only 46 % have been translated! gscreen would contain about 300 lines, none translated. Please ask someone to translate a GUI like gscreen (Like I would like to do for Chris). At this state of development I must go through 3008 lines and look with one goes for gcreen. You can imagine, that I will not be very willing to do that. Please imagine we split the linuxcnc.po ugly monster file in parts like: motion_control command halshow ngcgui gscreen .... .... .... I only mentioned some of the involved files. Please ask a friend of you to translate a small file, with only 100 lines, I am sure it is much easier to convince him to get involved in linuxcnc as translator with this question instead of asking him to walk through a file with more than 3000 lines. To begin that way, I would like to copy my gmoccapy.mo file (yes, I made already the mo file) with the Submakefile directly to /share/locale/de/LC_MESSAGES/ and the Spanish and Serbian translations to the corresponding folders. I know that would began a new way to handle the locale in linuxcnc, but I am convinced we only get advantages. I also see that there would be some work, to split the actual po-monster in its parts. From my side I do not see any reason, why not to handle separate locale files for different GUI, but may be I do not see any reason so I would like to point that out for discussion. Again my arguments in one state: - gmoccapy is still and will be for quite a while under development, so the files do change very often - If I merge the gmoccapy.po files with the po files from src/po , it is nearly impossible to find out what entries are mine and what are from others. Just take a look in one file, i.e. de.po and you will see, that there are a lot of files mixed in that file and it is not possible to sort them by the source file, so witch one I will need to translate. - IMHO it is the wrong way to mess translations from different files in one big file, how to maintain that in a correct way? We should better go the way to split this monster up and have different translation files for the different source files. I feel the solution would be to copy the gmoccapy.mo files directly from my source folder to the corresponding locale folder: like: cp src/emc/usr_intf/gmoccapy/locale/de/LC_MESSAGES/gmoccapy.mo share//locale/de/LC_MESSAGES/gmoccapy.mo cp src/emc/usr_intf/gmoccapy/locale/es/LC_MESSAGES/gmoccapy.mo share//locale/es/LC_MESSAGES/gmoccapy.mo cp src/emc/usr_intf/gmoccapy/locale/rs/LC_MESSAGES/gmoccapy.mo share//locale/rs/LC_MESSAGES/gmoccapy.mo This will not mess anything around and will be the beginning of a clearer locale structure. Norbert ------------------------------------------------------------------------------ Android apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1 Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview and more. Get your Android app in front of a whole new audience. Start now. http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
