#linuxcnc-devel Logs

Nov 05 2021

#linuxcnc-devel Calendar

01:33 AM pere: I notice several manual pages uses non-manual page macros, and even define their own. why is this?
01:45 AM pere: the one I have seen so far are .de TQ (define new macro TQ) and .if.
02:48 AM pere: these macros make translating manual pages using po4a hard.
02:53 AM -!- #linuxcnc-devel mode set to +v by ChanServ
03:08 AM pere: <URL: https://github.com/LinuxCNC/linuxcnc/pull/1356 > is the current status of the translation framework. It handle most documentation files, but throw away the existing translations.
11:12 AM jepler[m]: pere: .TQ is used for the 2nd and following 'hanging tag', after a .TP. .TP introduces undesirable vertical space. However, if it's just too awful to continue to use .TQ, then something else can be done like changing them all to .TP.
11:12 AM * jepler[m] uploaded an image: (20KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/mAKLnshdAgpZMTEDfGqIqqlu/image.png >
11:12 AM jepler[m]: the top one has had its .TQ changed to .TP, causing an extra blank line in the text version
12:05 PM pere: jepler[m]: thanks.
04:05 PM pere: seb_kuzminsky: are you ok with <URL: https://github.com/LinuxCNC/linuxcnc/pull/1327 > now?
04:05 PM pere: smoe asked me to upload to debian when ready, as he is partly offline for a week or so.
04:22 PM seb_kuzminsky: pere: i'm looking at it now - there's a lot to think about in that PR, and it's all squashed into one giant commit, which makes it harder to analyze
04:24 PM seb_kuzminsky: we have guidelines we ask contributors to adhere to (http://linuxcnc.org/docs/2.8/html/code/contributing-to-linuxcnc.html#_effective_use_of_git), but we can't expect everyone to have found that and adhere to it, so i'm just going through what's in the PR slowly
04:42 PM pere: I recommended squashing it, as its commits were mostly for tracking master updates and fixing bugs.
04:43 PM pere: but yeah, it is a complete rewrite of d/rules. :)
04:51 PM seb_kuzminsky: i'm sorry that all the changes in master while 1327 was under development caused so much extra work for smoe and you
04:52 PM seb_kuzminsky: when that happens to me i prefer to use rebase over merge, to avoid having a bunch of confusing commits in the history of the pr, but i get that not everyone likes to use that workflow
04:53 PM pere: I do not mind, but do not know which workflow smoe uses.
04:54 PM pere: seb_kuzminsky: do you have any idea if the po4a change will be accepted or not? unless translators contribute, most/all translations will be most.
04:58 PM seb_kuzminsky: i'm very much in favor of using po4a over the "make a copy and edit the text of the copy" thing we do now
04:58 PM pere: what about the rest of the community?
05:00 PM seb_kuzminsky: i can't speak for anyone else... perhaps an email to emc-developers asking for feedback?
05:01 PM pere: seb_kuzminsky: perhaps best if such request came from someone already known in the project?
05:14 PM pere: seb_kuzminsky: as soon as #1327 is in, I plan to upload to debian.
05:24 PM seb_kuzminsky: sure, i'll send that email
05:26 PM pere: there are tools to generate po files given an english and a translated file, but it need to be done per file and the result need to be controlled by someone who understand the langauge, because it depend on the two files having matching structures.
05:45 PM pere: "po4a-gettextize -f man -m docs/man/man1/axis.1 -l docs/man/es/man1/axis.1" show what that process might look like.
07:06 PM jepler[m]: whatever needs to be merged before uploading to debian, merge away as far as I'm concerned. I don't have the energy to review the specifics but I'm happy to put my confidence in y'all who are working on the software
07:40 PM skunkworks: it is an amazing time for linuxcnc...