#linuxcnc-devel Logs

Jan 13 2022

11:40 AM norias: haha, blamelist
02:12 PM pere: seb_kuzminsky: around?
02:19 PM pere: smoe: btw, do you have any idea who sync weblate with master? I suspect it is done manually?
02:23 PM smoe: pere technically this is https://github.com/LinuxCNC/linuxcnc/commits?author=weblate - but I have no clue whatsover if this is automagically triggered.
02:24 PM pere: smoe: yeah, but I believe someone press 'send changes' in weblate to make it happen.
02:24 PM pere: I am just very happy it seem to happen. :)
02:30 PM smoe: ;) Concerning the glossary, we should look at https://en.wikipedia.org/wiki/G-code - liked it.
02:39 PM pere: smoe: how is it related to the glossary?
02:40 PM smoe: It gives long descriptions for abbreviations occurring in the documentation.
02:41 PM smoe: And while I do not think that the LinuxCNC documentation should be an extended Wiki, we could still think about linking to Wikipedia when we think that something is already said and should not necessarily be repeated.
02:45 PM pere: Right. I guess I have not come across those abbrevations yet.
03:19 PM smoe: Are there opinions on weather debug messages should be translated? For instance there is "ERROR CLASSICLADDER--- Failed to listen socket server...(error=%s)" that may be worthwhile to translate but is not really a but report, more like a "problem report". This likely should be translated. But what about "ERROR CLASSICLADDER--- Failed to create
03:19 PM smoe: thread socket server..." - this should just be reported as it is, I feel.
03:25 PM pere: smoe: no idea, but one way to handle it is to ask users to run with LC_ALL=C when reporting errors.
03:26 PM pere: Another is to include error numbers in the messages for easier identification.
03:32 PM smoe: Not convinced. You need help when you start with everything and that is when you just clicked on the LinuxCNC Icon on the desktop and do not know how to use the terminal, yet.
03:32 PM smoe: Error numbers would be nice, though.
03:51 PM smoe: My changes to Weblate have not yet made it into the archive - this supports your theory this to be manually triggered or via some rare cron job.
04:01 PM pere: it is manually triggered.