Bug 30379 - LibreCAD 2.2.0rc3 : Followup Report
Summary: LibreCAD 2.2.0rc3 : Followup Report
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 8
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-05-05 02:08 CEST by John L. ten Wolde
Modified: 2022-05-05 04:53 CEST (History)
1 user (show)

See Also:
Source RPM: librecad-2.2.0-0.rc3.1.mga8.src.rpm
CVE:
Status comment:


Attachments

Description John L. ten Wolde 2022-05-05 02:08:10 CEST
Hi everyone.  I'm continuing on from bug 29996 as requested by Dave Hodgins, but it turns out that neither of my two remaining concerns are actually issues so this report is purely informational.  No further action is required as there are NO BUGS HERE!

(1)  The first of my two concerns was that LibreCAD's packages weren't being pulled in together all at once for correct installation.  Well, I don't know how it happened, but when the packages made the transition from the Testing repo into Core Updates that issue seems to have resolved itself.  Uninstall one component and all of LibreCAD's components, plus libdxfrw go with it.  Try to (re)install just one component and they all get selected for download.  It's all back to the way I've grown to expect.  Bravo!

(2)  My second concern had to do with the missing WenQuanYi Zen Hei font file wqy-unicode.lff.  This file provides CJK character support for East Asian scripts (by which I mean characters for text labels, dimension values, etc. *within* a drawing; *not* for the UI widgets etc.).  Well, that file is still missing, and though I consider this a valid issue for any user who needs that text, my upstream investigations led me to this head-scratcher:

    https://librecad.readthedocs.io/en/latest/appx/fonts.html

That's a list of all the fonts meant to be included in the new 2.2.x branch.  Being an alphabetically sorted list, wqy-unicode.lff should appear at the very bottom, but it's missing there too.  This suggests to me that upstream has *intentionally* dropped support for it.  I could find no mention or explanation anywhere of why they've decided to leave their East Asian users out in the cold this way.

...


Anyway, I don't think I can be considered a LibreCAD "power-user" by any means, but over the last week-and-a-half I've given it a pretty thorough shakedown with a fairly complicated multi-layered project.  For the most part it's functional, but as it's an RC, there certainly *are* a few (upstream) issues with it.  Most notably (and annoyingly) there's a problem with text rotation.  In LibreCAD all angles are assigned in degrees.  Rotate some text and its degrees get saved to file correctly, but reload that same drawing and the degrees get converted to radians that are then *interpreted* as if they were degrees (so for example, text rotated to 90° gets magically shifted to 1.57079°).  I'm betting this conversion anomaly crept has somewhere into the new libdxfrw.  Whoops!

So yeah, I'll take these new issues upstream, and as it stands, there's presently nothing further for our side to do regarding LibreCAD.  You can be sure, however, that when these problems get resolved and/or the next stable release drops, I'll pop back in with an update request.  Until then all that's left for me to type here is my THANK YOU to Nicolas Salguero, David Walser, and everyone else involved in straightening out bug 29720 and bug 29996! :-)



P.S.:  How do you CC a few people in a report like this so they actually get to see it before it's closed?
Comment 1 Dave Hodgins 2022-05-05 04:53:41 CEST
You can add a comment to bug 29720 or bug 29996, without reopening the bug.
The new comment will get sent to everyone already in that bug's cc list.

Closing as invalid for obvious reasons. :-)

Resolution: (none) => INVALID
CC: (none) => davidwhodgins
Status: NEW => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.