Hi everyone,
I have now addressed the remaining review points and uploaded an updated
package to mentors (`5.0.2-1`).
Changes since the previous upload include:
* moved documentation to `/usr/share/doc/conducteo/`
* moved examples to `/usr/share/doc/conducteo/examples/`
* added `doc-base` integration
* fixed the quickstart guide opening on first launch
* added translation support for the materials database
* removed remaining Windows-specific files from the Debian source
tarball
Regarding other platforms, Windows builds are still supported, but
bundled libraries are no longer included and required dependencies are
now downloaded separately. macOS support existed previously, although I
have not tested it recently due to no longer having access to a Mac.
I also rebuilt and tested the package in a clean Debian environment.
Documentation, examples and localisation now work correctly.
Thank you again for your detailed review and suggestions. If you have
time for another look, I would greatly appreciate it.
Best regards,
Clément
Le 15.05.2026 21:28, Wookey a écrit :
On 2026-05-15 13:55 -0400, The Wanderer wrote:
On 2026-05-15 at 13:36, Wookey wrote:
"DxfHasNoLayer": "DXF file doesn't contain any layer!" ->
"DxfHasNoLayer": "DXF file doesn't contain any layers!"
"DxfHasNoValidPolyline": "DXF file doesn't contain any valid polyline
without self intersec\|
tion!", -> "DxfHasNoValidPolyline": "DXF file doesn't contain any
valid polylines without self intersec\|
tion!",
While not common, this is a usage pattern I've seen before, and may
potentially be considered intentional. The apparent intention as I
parse
it with "any" in a sense along the lines of "even one", so the
singular
could be appropriate, even though it looks awkward for standard
English
usage.
Yes, you are quite right. This one is debatable. 'any valid polyline'
correctly conveys the 'not even one' which is the actual underlying
test, but people (or at least educated native speakers) don't actually
say that, they say 'any valid polylines', so the singular sounds
peculiar.
The same sense might be conveyed while retaining the singular by using
"a" instead?
Yep "DXF file doesn't contain a valid polyline without
self-intersection" works.
Or the whole could be rephrased into something like "No [layer / valid
polyline without self-intersecction] found in DXF file!". That'd be a
bigger and therefore more intrusive change, however.
Speaking of which, however, I think ideally "self-intersection" would
be
a hyphenated phrase.
In fact a better version is "The DXF file doesn't contain a
non-self-intersecting valid polyline"
Or, for easier comprehension: "The DXF file doesn't contain a
(non-self-intersecting) valid polyline"
(i.e. 'without self-intersection' actually sounds quite 'translated'
now I look at it again).
And I agree that a full re-arrange is even better:
"No valid (non-self-intersecting) polyline found in the DXF file!"
('the' is optional, but I prefer it)
The subtleties of even straightforward translation never cease to
fascinate me.
I can post the 141 lines of materials here too if you like and we can
try and collectively work out what they all are.
It ideally needs someone who has done building work in both French and
English and understands the subleties of (construction material) naming
for different types of plaster, stone, brick, concrete, foams, felts
etc. I know quite a lot about contruction materials, but only in
English, so getting an accurate translation is a bit hit-and-miss.
Wookey
