#linuxcnc-devel Logs
Mar 26 2022
#linuxcnc-devel Calendar
05:11 AM -!- #linuxcnc-devel mode set to +v by ChanServ
05:22 AM pere: in docs/src/ladder/classic-ladder.adoc, what is the purpose of the string "[show sequential program]" in line 709?
05:26 AM silopolis[m]: Can't tell.
05:29 AM silopolis[m]: Just asked Phil Thimpson...
09:22 AM silopolis[m]: <pere> "in docs/src/ladder/classic-..." <- Just a different style of plc programming. Instead of inputs and outputs going left to right, you have a list of sequences from top to bottom
09:23 AM silopolis[m]: It's called grafcet or sfc
09:23 AM pere: what does that has to do with asciidoc?
09:24 AM pere: asciidoc go gracy when the string show up at the start of the line in translated docs, and I did not really understand its purpose in the paragraph it is in. still do not, I must admit. did you understand it?
09:25 AM silopolis[m]: Ah sorry misunderstood
09:26 AM pere: This is the paragraph: "This is the SEQUENTIAL editor window Starting from the top left image:
09:26 AM pere: Selector arrow , Eraser Ordinary step , Initial (Starting) step
09:26 AM pere: Transition , Step and Transition Transition Link-Downside , Transition
09:26 AM pere: Link-Upside Pass-through Link-Downside , Pass-through Link-Upside Jump
09:26 AM pere: Link Comment Box [show sequential program]"
09:26 AM pere: I am beginning to suspect my po4a build rules are correct, and the problem is in the adoc files themselves, exposed when their formatting change in the translated docs.
09:42 AM silopolis[m]: If po4a has enough syntax awareness and strict checking, that could well be the case
09:45 AM silopolis[m]: But indeed very unclear why this string is into square braces
09:47 AM silopolis[m]: But I've had other hard times while migrating fr with (not so) special caracters at the beginning of lines
10:37 AM pere: silopolis[m]: any clue what is going wrong in <URL: https://github.com/LinuxCNC/linuxcnc/runs/5703799275?check_suite_focus=true >? Got the doc building test working (ie building html pages), but the pdf build still fail on github. works on my bullseye machine.
12:40 PM silopolis[m]: pere: looks like it starts to break on png convertion https://github.com/LinuxCNC/linuxcnc/runs/5703799275?check_suite_focus=true#step:4:18325
12:40 PM silopolis[m]: but have no clue of the meaning of "Failed to get connection" (https://github.com/LinuxCNC/linuxcnc/runs/5703799275?check_suite_focus=true#step:4:18336) when calling inkscape 🤔
12:43 PM silopolis[m]: pere: image path 'images/inside-comp.png' should most probably be 'gcode/images/inside-comp.png' somewhere in gcode directory
12:43 PM silopolis[m]: https://github.com/LinuxCNC/linuxcnc/runs/5703799275?check_suite_focus=true#step:4:18716
12:45 PM silopolis[m]: pere: then it seems like there are many characters encoding errors starting at https://github.com/LinuxCNC/linuxcnc/runs/5703799275?check_suite_focus=true#step:4:18989
12:48 PM silopolis[m]: pere: on a second read, these are all "Package inputenc Error[s]", whereas https://github.com/LinuxCNC/linuxcnc/runs/5703799275?check_suite_focus=true#step:4:18980 reports "no support found for inputenc"
01:11 PM pere: silopolis[m]: any idea how these could happen? Is the build working for you? Ie ./debian/configure; debuild?
01:11 PM silopolis[m]: pere: which refers to https://ctan.org/pkg/inputenc Latex package
01:12 PM pere: I do know the latex inputenc package, but have no idea how it could go wrong with autogenerated latex from docbook output...
01:12 PM pere: seem to me like the generated files are not utf-8 on github, but they are utf-8 on my machine.
01:18 PM silopolis[m]: 😲
03:04 PM linuxcnc-build: build #1856 of 1660.rip-buster-python3 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1660.rip-buster-python3/builds/1856 blamelist: Hans Unzner <hansunzner@gmail.com>
03:05 PM linuxcnc-build: build #2257 of 1640.rip-buster-rtpreempt-amd64 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1640.rip-buster-rtpreempt-amd64/builds/2257 blamelist: Hans Unzner <hansunzner@gmail.com>
03:13 PM linuxcnc-build: build #2015 of 1650.rip-buster-rtpreempt-rpi4 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1650.rip-buster-rtpreempt-rpi4/builds/2015 blamelist: Hans Unzner <hansunzner@gmail.com>
03:13 PM linuxcnc-build: build #8656 of 0000.checkin is complete: Failure [4failed] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/8656 blamelist: Hans Unzner <hansunzner@gmail.com>
03:30 PM linuxcnc-build: build #1857 of 1660.rip-buster-python3 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1660.rip-buster-python3/builds/1857 blamelist: Hans Unzner <hansunzner@gmail.com>
03:30 PM linuxcnc-build: build #2258 of 1640.rip-buster-rtpreempt-amd64 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1640.rip-buster-rtpreempt-amd64/builds/2258 blamelist: Hans Unzner <hansunzner@gmail.com>
03:40 PM linuxcnc-build: build #2016 of 1650.rip-buster-rtpreempt-rpi4 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1650.rip-buster-rtpreempt-rpi4/builds/2016 blamelist: Hans Unzner <hansunzner@gmail.com>
03:40 PM linuxcnc-build: build #8657 of 0000.checkin is complete: Failure [4failed] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/8657 blamelist: Hans Unzner <hansunzner@gmail.com>