Load dxf then Save As plt is empty

[KenR60]

Hello All,  Have never done this before so I'm stuck.  I have a *dxf file when I open it in Inscape all looks Good, then I Save As a *plt file so that my Laser Cutting Software can read it but when it tries to open the *plt file nothing happens. I use *plt files all the time but they have never came from a *dxf file before.  I have attached the *.dxf file

[brynn]

DXF to PLT?  I'm thinking there probably is no realistic conversion happening there.  Inkscape can probably only convert SVG to PLT (or images made with Inkscape). 

Try saving the DXF as SVG first.  Then check the image to make sure that did not cause any negative effects.  Then go ahead and save as PLT

[Moini]

Inkscape automatically converts everything it loads to SVG. It cannot directly 'edit' other file formats, but always does a conversion when saving as a non-SVG file format, as far as I understand. Additional saves should not be necessary.

[brynn]

Ok, so if what Moini says is true, then there must be something in the DXF file which isn't being converted properly.

Unfortunately, I can't seem to open DXF files.  Or rather, when I open with Inkscape, they are always blank.  Hopefully someone else can have a look.

Off-Topic: show

This is off-off topic!  Moini, I'm thinking this FAQ needs to be updated:  https://inkscape.org/en/learn/faq/#what-formats-can-inkscape-importexport.  It either needs to say something like "Inkscape can open or import a wide variety of vector formats", or list all the ones in the Open dialog.  What do you think?  I'm not asking you to do it, of course.  Just want to make sure I'm not off base, if I do it.

[Moini]

Btw., the Inkscape open dialog only says it can open version 13 of the dxf file format. Might need a conversion between formats first. I think I once used LibreCad for that, but I don't remember the details.

As for the FAQ, I think listing them all is a bit too much, I get 55 (more or less) different formats. Still, I think the most important ones should be listed, as they are now. Perhaps add something like 'and more'? That's also very future-proof...

[brynn]

I did just stumble on the reason I can't open DXF files (need to install something extra).  If I have time later, I'll look into it further.

Where did the DXF file come from?  If you downloaded it, you could look at the site where you downloaded, and find out if you could get an SVG download instead.  Maybe it would convert better?  But if not, at least we could have a look and find out why.

Or someone else who already can open DXF files might come along still....

(Thanks for your comments on FAQ Moini.)

[Ronnie Moore]

brynn, you mentioned you may has stumbled across why you cannot open or import a dxf file, can you share that solution? I upgraded the the latest version Inkscape 0.92.2 (5c3e80d, 2017-08-06) and am no longer able to import dxf files.
Thanks

[brynn]

   Oohh      I didn't write it down, and now I'm not sure.

I think I had noticed this FAQ:  https://inkscape.org/en/learn/faq/#how-install-uniconvertor-windows  It does not specifically say DXF.  But it does mention PLT.  And since both of them are AutoCAD formats, I thought it would be worth a try.

I haven't tried it yet.  I'll keep my fingers crossed for you though.  Let us know if it works, and we can update the FAQ.

[Ronnie Moore]

Brynn

I followed the instructions and installed the extension and still receieve the error message when trying to import or open a DXF file.

This is the error:
"ERROR:root:code for hash md5 was not found.
Traceback (most recent call last):
  File "C:\Program Files\Inkscape\python\Lib/hashlib.py", line 147, in <module>
    globals()[__func_name] = __get_hash(__func_name)
  File "C:\Program Files\Inkscape\python\Lib/hashlib.py", line 97, in __get_builtin_constructor
    raise ValueError('unsupported hash type ' + name)
ValueError: unsupported hash type md5
ERROR:root:code for hash sha1 was not found.
Traceback (most recent call last):
  File "C:\Program Files\Inkscape\python\Lib/hashlib.py", line 147, in <module>
    globals()[__func_name] = __get_hash(__func_name)
  File "C:\Program Files\Inkscape\python\Lib/hashlib.py", line 97, in __get_builtin_constructor
    raise ValueError('unsupported hash type ' + name)
ValueError: unsupported hash type sha1
ERROR:root:code for hash sha224 was not found.
Traceback (most recent call last):
  File "C:\Program Files\Inkscape\python\Lib/hashlib.py", line 147, in <module>
    globals()[__func_name] = __get_hash(__func_name)
  File "C:\Program Files\Inkscape\python\Lib/hashlib.py", line 97, in __get_builtin_constructor
    raise ValueError('unsupported hash type ' + name)
ValueError: unsupported hash type sha224
ERROR:root:code for hash sha256 was not found.
Traceback (most recent call last):
  File "C:\Program Files\Inkscape\python\Lib/hashlib.py", line 147, in <module>
    globals()[__func_name] = __get_hash(__func_name)
  File "C:\Program Files\Inkscape\python\Lib/hashlib.py", line 97, in __get_builtin_constructor
    raise ValueError('unsupported hash type ' + name)
ValueError: unsupported hash type sha256
ERROR:root:code for hash sha384 was not found.
Traceback (most recent call last):
  File "C:\Program Files\Inkscape\python\Lib/hashlib.py", line 147, in <module>
    globals()[__func_name] = __get_hash(__func_name)
  File "C:\Program Files\Inkscape\python\Lib/hashlib.py", line 97, in __get_builtin_constructor
    raise ValueError('unsupported hash type ' + name)
ValueError: unsupported hash type sha384
ERROR:root:code for hash sha512 was not found.
Traceback (most recent call last):
  File "C:\Program Files\Inkscape\python\Lib/hashlib.py", line 147, in <module>
    globals()[__func_name] = __get_hash(__func_name)
  File "C:\Program Files\Inkscape\python\Lib/hashlib.py", line 97, in __get_builtin_constructor
    raise ValueError('unsupported hash type ' + name)
ValueError: unsupported hash type sha512
The fantastic lxml wrapper for libxml2 is required by inkex.py and therefore this extension.Please download and install the latest version from http://cheeseshop.python.org/pypi/lxml/, or install it through your package manager by a command like: sudo apt-get install python-lxml

Technical details:
No module named lxml"

[brynn]

Oh gosh!  Your problem, which started out borderline over my head, is almost completely over my head now.  If anyone else can help, please feel free to jump in!

The first thing I would do, is double-check everything about the UniConverter installation (proper file was downloaded, installed in the right place, if possible confirm installation was successful, etc).

Here's (at least one) bug report on that (not so) fantastic lxml wrapper issue:  https://bugs.launchpad.net/inkscape/+bug/450927/  It's another python-related problem.  Comment #15 contains a possible workaround for Windows (which did work for someone else in a different topic).

Do you have enough technical understanding to follow that bug report?  If not, we'll probably need someone to explain.  I can trip and stumble through it, but there are gaps in my understanding.

[Moini]

(It appears to be the same problem as the last 5 or six times this came up, Brynn)

- first: you do not need to install uniconvertor. It comes with Inkscape 0.92.2 for Windows. Uninstall it if you have added it to your system. It could possibly make things worse, if it's an incompatible version.

- second: what you need to do now, is please uninstall your current Inkscape version completely, then install Inkscape 0.92.2 again. With Python.
Don't update Inkscape on Windows, at least not from Inkscape 0.91 to Inkscape 0.92. If you do, this is going to mess up your Inkscape Python installation. It needs removal, then installation of new version.

After that, you should not get those lxml errors anymore.

Download link: https://inkscape.org/en/release/0.92.2/windows/

[brynn]

(It appears to be the same problem as the last 5 or six times this came up, Brynn)

I'm afraid I don't know what 5 or 6 times you're referring to, Moini.  As far as I understand, the problem which Ronnie Moore is having, is not being able to open DXF files.  (probably should split this out from the op, since it seems to be a separate problem?)  This is the first time I've heard this problem. 

It looks like the fantastic lxml problem only came up after installing Uniconverter -- unless the traceback error was received from the start, but only reported after installing Uniconverter.   I have seen the fantasic lxml problem many times.  But since I don't understand it, I don't usually try to answer it - thus, my plea for assistance. 

Also, I thought I made it clear that I wasn't sure if installing Uniconverter would help with DXF problem.

Don't update Inkscape on Windows, at least not from Inkscape 0.91 to Inkscape 0.92.

I also don't know what you mean about "updating" Inkscape.  As far as I know, there is no update.  You can only uninstall the old version (if on Windows, you're replacing an msi or exe version) and install the new one.  (If you're "installing" a 7z package, you don't need to uninstall the msi or exe versions.) 

As far as I understand, the inability to open DXF files started after Ronnie Moore installed 0.92.2.  So possibly, only uninstalling the new Uniconverter would be necessary?  But again much of this is just beyond my understanding.

[Moini]

Update as in install the next version over the previous. As far as I know, Inkscape will then ask you if you want to update, if it can detect a previous version. But that process is broken.

The lxml error is due to Inkscape's Python install messed up after an update, in the current cases on Windows with 0.92 after people installed the new version. Many extensions need lxml, so it's the same error message for different extensions (and the problem the users report depends on which extension they needed to use).

[brynn]

Update as in install the next version over the previous. As far as I know, Inkscape will then ask you if you want to update, if it can detect a previous version. But that process is broken.

Oh, I wasn't aware of that!  I don't remember seeing it, but for 0.92.2, I used the 7z package.  Maybe it doesn't apply to the 7z?  Or maybe I just didn't notice.  Hhm, no I don't see anything like that for the 7z.

No, this is the first time I've heard any of this.  After investigating, I think I had seen the comment about updating on the download page for Windows (https://inkscape.org/en/release/0.92.2/windows/64-bit/) and meant to ask about it, but since I was getting the 7z package, I guess it slipped my mind.  I think that page needs some more detail in the explanation.  I don't think a non-tech type of user will understand it.

And I guess if you don't remember which installer you used previously, you have to avoid that update option.  I wonder what happens if you try it?  Would Inkscape catch it and stop the installation?

What is the benefit of using this update feature?  I don't consider installing Inkscape takes so much time that a user would be concerned about shortening it.  It must have some significant benefit, or else why was it added?

If the update feature is broken, shouldn't that be on the download page, in bold, and perhaps red text? (I don't have access to that page, so can't propose changes there - guess I'd need to post to the mailing list?)  I assume it was only discovered after release?  But it sounds serious enough that we should notify people before they start the installation.  Or if nothing else, an FAQ about 0.92.2/windows/lxml error?

Edit
This is off topic, but I noticed this on the main download page (of the website)

"Documentation
    Fix link for FAQ entry on DPI change"

If a simple edit is needed for the FAQ page, I could do it.  Just someone needs to tell me what it is.