- Inkscape Translators - Inkscape Mailman

Inkscape 1.4.4 is out!
by Maren Hachmann 06 May '26

06 May '26

Inkscape 1.4.4 ============== Inkscape 1.4.4 is now available for all three supported operating systems (Linux, macOS, Windows)! You can download it from: https://inkscape.org/release/inkscape-1.4.4 BUGFIX and MAINTENANCE RELEASE ------------------------------ Inkscape 1.4.4 is be a bugfix and maintenance release, which brings you 20 crash fixes, more than 25 bug fixes and performance improvements, a couple small new features, and comes with almost 20 updated translations. The most important fixes and changes in this release are: * 20 crash fixes, among them for three nasty bugs where Inkscape wouldn't even start * almost 20 other bug fixes * 6 changes that improve performance * a new palette * a new button for rotating stars and polygons into their 'neutral' or 'upright' position * 27 updated interface translations * 15 updated documentation translations * installation files for Windows on Arm See the release notes for more information (also about known issues): https://inkscape.org/doc/release_notes/1.4.4/Inkscape_1.4.4.html Like its predecessor, it is also a bridge release in the sense that it can be used to convert the planned Inkscape 1.5 multipage file format to the pre-1.5 multipage format. Versions lower than Inkscape 1.4.3 will not be able to interpret pages created in Inkscape versions 1.5 and upwards. Opening a document in Inkscape 1.4.3 and saving it will convert it to the current ('old') page format (MR #7608). Background: While the 'old' format of pages in Inkscape is a custom addition that only works in Inkscape, the new format will make use of the svg:view element, which is standardized and can work in other SVG viewers, too. Find more information about this in MR #7525. Report Bugs ----------- Please report all bugs you find in our Inbox bug tracker on GitLab! https://inkscape.org/report ----------------------------- Join an Inkscape project team ----------------------------- Inkscape is always happy to welcome new contributors in various areas: code, docs, translation, UX, bug triaging, or even outreach! The main ways to get involved are listed on https://inkscape.org/contribute/ and you can get in touch with us on https://chat.inkscape.org/ Thanks to everyone involved in this release! -- The Inkscape team

1 0

Inkscape 1.4.4 release candidate available for testing!
by Maren Hachmann 25 Apr '26

25 Apr '26

Inkscape 1.4.4 Release Candidate ================================ Inkscape 1.4.4rc is now available for testing for all three supported operating systems (Linux, macOS, Windows)! For the first time, we also provide packages for Windows on Arm. Being a pre-release, this version is not intended for production use, but to help us smooth out any issues that should not show up in the actual release which is due in less than 2 weeks from now. You can download it from: https://inkscape.org/release/inkscape-1.4.4rc BUGFIX and MAINTENANCE RELEASE ------------------------------ Inkscape 1.4.4 will be a maintenance and bugfix release, which brings you 20 crash fixes, more than 25 bug fixes and performance improvements, a couple small new features, and will come with more than 25 updated translations. See the release notes draft for more information: https://wiki.inkscape.org/wiki/Release_notes/1.4.4 Like the previous version, Inkscape 1.4.4 will also be a 'bridge release' in the sense that it can be used to convert the planned Inkscape 1.5 multipage file format to the pre-1.5 multipage format. Versions lower than Inkscape 1.4.3 will not be able to interpret pages created in Inkscape versions 1.5 and upwards. Opening a document in Inkscape 1.4.3 and saving it will convert it to the current ('old') page format. Background: While the 'old' format of pages in Inkscape is a custom addition that only works in Inkscape, the new format will make use of the svg:view element, which is standardized and can work in other SVG viewers, too. Find more information about this in MR #7525. KNOWN ISSUES ____________ * On macOS, if Inkscape has been started from the command line, extensions will not work (both in the graphical user interface as well as when only using the Inkscape commandline). Many import / export file formats provided by Python extensions are also affected. This is a security feature added in 1.4.3 for official macOS .dmg files, which fixes CVE-2025-15523. Learn more about it in our bug tracker at https://gitlab.com/inkscape/inkscape/-/work_items/6047 * On Wayland (display server), depending upon the Gtk version your system uses, a crash may occur when moving a docked tab, or closing a floating dialog. Trying to undock a dialog may result in the wrong dialog being undocked (https://gitlab.com/inkscape/inkscape/-/issues/6013). Report Bugs ----------- Use at your own risk, and please report all bugs you find in our Inbox bug tracker on GitLab! https://inkscape.org/report ----------------------------- Join an Inkscape project team ----------------------------- Inkscape is always happy to welcome new contributors in various areas: code, docs, translation, UX, bug triaging, or even outreach! The main ways to get involved are listed on https://inkscape.org/contribute/ and you can get in touch with us on https://chat.inkscape.org/ Thanks to everyone involved in this pre-release! -- The Inkscape team

1 0

Translate for the upcoming Inkscape 1.4.4 until April 31!
by Maren Hachmann 17 Apr '26

17 Apr '26

Hi everyone! Inkscape 1.4.4 will be a maintenance and bug fix release. We plan to do a release candidate on April 22, and a release on May 6. Inkscape 1.4.4 is in string freeze now, that means that the translatable contents for the main program is not going to change until the release from now on. The translation submission deadline is April 31, at 23:23:59 UTC. -------------------------- Translations made after that time will likely not be a part of Inkscape 1.4.4. There are only a handful changed/new strings, so if your translation is already up-to-date, there's almost nothing to do! https://translate.inkscape.org/projects/inkscape/1-4-x/inkscape/ ---------------------------------------------------------------- On a side note, the project is currently discussing about the adoption of an AI policy here: https://gitlab.com/inkscape/inkscape-board/-/issues/5 The current direction is leaning to banning the use of LLMs, to encourage learning and reduce skill erosion (and because of ethical, quality, and environmental concerns). If you *do* use AI to help you (as there is currently no ban), please make sure to check (and if necessary, adjust) each and every single string that you submit. We have already had the experience of LLMs producing garbage and that being submitted, and it took a lot of re-working. We would much prefer if the Inkscape UI translation came from your own brains! --------------------------------------------------------------- On another side note, I've started to work on updating our translation instructions here: https://gitlab.com/inkscape/inkscape-docs/contributors-guide/-/merge_reques… - when it's ready, you're going to be able to find all info related to translations in our Contributors' Guide: https://inkscape.gitlab.io/inkscape-docs/contributors-guide/. -------------------------------------------------------------- When you have questions about a specific string and how it is used in Inkscape, please ask in the chat: https://chat.inkscape.org/channel/team_translation Thanks all! And happy translating! Maren

1 0

Dutch translation of "STROKE"
by catherine 12 Apr '26

12 Apr '26

Hello, I'm completely new to writing messages to mailinglists, but I'm not new to inkscape, have been using it for almost 10 years. Hope this message is the correct way to get in touch. I'd like to contribute to, or request, a rectification of the current Dutch translation. -*-*-*- Especially for the translation of STROKE, as in "Fill and *Stroke".* It's currently translated as "Vulling en *Streek*", instead if the previous "Vulling en *Lijn*". The word "*streek*" does exist in Dutch, and it has multiple meanings, but that of a line is not common. https://translate.google.nl/?sl=auto&tl=en&text=streek&op=translate https://www.woorden.org/woord/Streek At first I thought it was a typo, because the Dutch word "*streep*" does also exist and can be used for indicating a line, a dash. https://translate.google.nl/?sl=auto&tl=en&text=streep%0A&op=translate https://www.woorden.org/woord/Streep In Belgium, I volunteer as a coach for teaching young, Dutch speaking children (8 years +) how to design for the lasercutter, using Inkscape. Due to this context, this current Dutch translation bothers me (I always prefer English versions for personal use). Being forced to use "Streek", "Streekkleur", "Streekstijl" with young children, feels very uncomfortable. It's like I am learning them incorrect Dutch. So, if you agree with me that "*Streek*" should be replaced, I would rather go back to the previous "*Lijn*", instead of changing it to "*Streep*". Looking forward to your feedback. Also if you disagree! Kind regards, Catherine (Belgium)

2 1

Spanish translation
by Daisy 24 Mar '26

24 Mar '26

Hello, My name is Daisy Gonzalez, and I’m based in New York City. I’m fluent in both English and Spanish, with family roots in Colombia. I enjoy Inkscape and genuinely love working with the tool. I’m especially interested in contributing through Spanish translation, as I have experience in technical writing and translation work. If Spanish translation efforts are already well supported, I would be happy to explore other ways to contribute. My background includes UX/UI with Front-end Development skills, social media strategy, and communications, along with over five years of freelance graphic design experience. I’d love the opportunity to support Inkscape in any way that’s helpful. Looking forward to hearing from you, Kindly, Daisy *Daisy Gonzalez* daisy.gu07(a)gmail.com 917-359-6377 LinkedIn <https://www.linkedin.com/in/daisyg19> | Calendly <https://calendly.com/daisy-gu07>

4 3

New Turkish translator
by Kaya Zeren 25 Feb '26

25 Feb '26

Hi Community, I've been translating and maintaining Turkish for 20+ years, mostly open source software 200+ projects. My focus is keeping translations consistent and in the right context so non-english users easily unlock their potential. I believe that I have a good base glossary from my fellow translators and my translated apps from many different interests. In these years, I've been through from text, excel, xml and po files to advanced dedicated platforms like Transifex, Crowdin and Weblate. Some known apps are 7-Zip, FileZilla, WinMerge, WinSCP, VLC Player, Audacity, KeePass (XC), and some web apps CiviCRM, CommunityBuilder, LimeSurvey, Mattermost, Matomo, SuiteCRM, Nextcloud, Transifex, Weblate plus many Joomla and WordPress pulgins. I'm also a reviewer of some big projects: All Proton products, Localization Lab projects (Tor, I2P, Orbot, VeraCrypt etc), WordPress, Concrete CMS. I saw InkScape is a very good project and the Turkish translation is not complete and consistent. The first thing is working on local po files with all 11k strings instead of Weblate ones so I could test easier and get terminology consistency on the whole app. My only hesitation was to have correct Turkish terminology because I didn't have a professional graphic design background and I mostly followed up previous translators' terminology. The translation is complete now and I'll keep it up to date on Weblate. Cheers, Kaya

2 1

Extracting strings from svg file into po for translating
by Lucas Vieites 22 Feb '26

22 Feb '26

Hi there, I want to translate the text content of a bunch of SVG files. I thought of using the same mechanism that we use for the Inkscape tutorials, but I can't find much information about how it works. The workflow I'm thinking of is: 1. Extract the strings from the SVG into .po files 2. Translate the .po files 3. Put the translated strings back into the SVG files. Can you help me work this out, please? Thank you. -- *Lucas Vieites <https://namedrop.io/lucasvieites>* lucasvieites.com LinkedIn <https://www.linkedin.com/in/lucasvieites>

3 4

Generate documentation, but only one language
by Lucas Vieites 19 Jan '26

19 Jan '26

Hi there, I've been working on the translation of the documentation, tutorials, man page, etc. and I wanted to generate the SVG and HTML files to review and correct. I saw in the README <https://gitlab.com/inkscape/inkscape-docs/documentation/#generating-documen…> that you can generate the whole package with `make all`, and that works fine, but I'd like to keep it fast and clean, and only generate one language (in my case, Spanish). Is this possible without a massive update to the Makefile? Thank you, -- *Lucas Vieites <https://namedrop.io/lucasvieites>* lucasvieites.com LinkedIn <https://www.linkedin.com/in/lucasvieites>

2 2

Inkscape 1.4.3 is out!
by Maren Hachmann 26 Dec '25

26 Dec '25

Inkscape 1.4.3 ============== Inkscape 1.4.3 is now available for all three supported operating systems (Linux, macOS, Windows)! You can download it from: https://inkscape.org/release/inkscape-1.4.3 BUGFIX and MAINTENANCE RELEASE ------------------------------ Inkscape 1.4.3 is be a maintenance and bugfix release, which brings you fixes for many critical or irritating bugs, and even a few new features. The most important fixes and changes in this release are: * 24 crash/freeze fixes many of which prevented users from opening certain files or exporting certain objects with Inkscape 1.4.2 * almost 100 bug fixes and small improvements, among them: * JPEG/JPG export works again on Windows. * The problem with user interface text showing up as rectangles ('tofu') instead of letters if certain fonts are installed on macOS is finally resolved. * Ungrouping big groups is faster again. * All pasting options ('on page', 'width'/'height'/'size'/…) are now accessible from the right-click menu on canvas. * The Measure tool snaps again at its end point, so you can make accurate measurements again. * The LPE dialog now offers to convert Line, Polyline or Polygon SVG objects to paths before applying a path effect to them * When resizing the Inkscape window, the buttons in the Commands bar (copy, paste, open, dialog shortcuts) show up one by one instead of waiting for the window to get big enough to show the second half at once. * When converting strokes to paths, patterns and gradients are no longer lost. * Aligning on a circle or arc now works more reliably. * Text on Path now also works with rectangles. * Many improvements have been made to the PDF import. * Results from path operations no longer end up at the bottom of the object stack unexpectedly and the Split Path operation has learnt to better handle nested shapes. * The current layer by default is now the one where you have last selected an object (might need a preferences reset to apply). * Whether the current page is changed when you select an object on it has been made optional. * You can now make small changes to how Inkscape looks without needing to modify the full theme file. * The bug that sometimes made it impossible to make gradients and patterns fully opaque has been prevented from reaching adulthood (it has been around since 2007!). * and 25 updated interface languages as well as 13 updated documentation languages! See the release notes for more information (also about known issues and workarounds): https://inkscape.org/doc/release_notes/1.4.3/Inkscape_1.4.3.html Inkscape 1.4.3 is also a 'bridge release' in the sense that it can be used to convert the planned Inkscape 1.5 multipage file format to the pre-1.5 multipage format. Versions lower than Inkscape 1.4.3 will not be able to interpret pages created in Inkscape versions 1.5 and upwards. Opening a document in Inkscape 1.4.3 and saving it will convert it to the current ('old') page format. Background: While the 'old' format of pages in Inkscape is a custom addition that only works in Inkscape, the new format will make use of the svg:view element, which is standardized and can work in other SVG viewers, too. Find more information about this in MR #7525: https://gitlab.com/inkscape/inkscape/-/merge_requests/7525 Report Bugs ----------- Please report all bugs you find in our Inbox bug tracker on GitLab! https://inkscape.org/report ----------------------------- Join an Inkscape project team ----------------------------- Inkscape is always happy to welcome new contributors in various areas: code, docs, translation, UX, bug triaging, or even outreach! The main ways to get involved are listed on https://inkscape.org/contribute/ and you can get in touch with us on https://chat.inkscape.org/ Thanks to everyone involved in this release! -- The Inkscape team

1 0

Reminder for man page translation
by Maren Hachmann 22 Dec '25

22 Dec '25

Hi all, as we've had a deterioration in the French man page translation, I'd like to send out a reminder for how to translate the man page syntax: * DO translate example text, like FILENAME, OBJECT-ID * DO NOT modify the structure of the syntax of the commands (e.g. turning --pdf-pages=PAGE[,PAGE] into --pdf-page=PAGE ) * DO NOT modify pieces of SVG source code, e.g. translate inkscape: or sodipodi: to just inkscape or sodipodi If anyone is available to fix the French man page, while it will be not be updated for 1.4.3, it may still go into a possible 1.4.4 (and I have not checked whether the master branch is affected also). Thanks all, Maren

1 0