-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for Inkscape 1.0 #24
Comments
That's a good question... There is a page in the Inkscape wiki providing instructions to update extensions. It looks like a few changes might be necessary but nothing fundamental. |
@ianwilliamson I drafted a PR to update this extension for Inkscape 1.0 on macOS and it works again (at least on my system). You can give it a try. Note that the location of the extension folder changed in 1.0 and is now in |
Thanks @seignovert, your PR looks good to me and I'd be happy to merge. Let me know when you feel it's ready. |
I'm glad to see this being worked on. I just upgraded from Fedora30 to Fedora31. The latter ships with inkscape-1.0 beta. I tried downgrading inkscape to version 0.92.4, but your wonderful extension does not work, even with this older inkscape. Could you let me know when you might have an updated version of LaTeX Text extension that would work with inkscape-1.0 beta? It would be extremely useful for a long piece I'm working on. Thanks so much. |
Sorry @pscott33, I cannot give any relaiable estimate when I have time to get back to this. |
I'm using @seignovert fork with inkscape 1.0 (4035a4fb49, 2020-05-01) on an Arch linux box (python 3.8.3) and it works fine. |
With the release of the Inkscape 1.0 beta I wanted to start a discussion on what would be required for making this extension work with the new standalone OS X application. Also, are there fundamental changes introduced in 1.0 that require updates to this extension? I'm guessing yes?
So far, the 1.0 experience on OS X seems to be very smooth. It would be great to have this extremely useful extension available as well.
The text was updated successfully, but these errors were encountered: