Scribus 1.5.3 released
by "Christoph Schäfer"
The Scribus Team is proud to announce the release of development release 1.5.3, another major step on the way to Scribus 1.6.0.
In addition to being a milestone in terms of typographic features, the Scribus Team is convinced that 1.5.3 has become stable enough to be used in new workflows and documents in a similar way to the transition from 1.3.3.x to 1.4.0 after the release of version 1.3.6. However, care must be taken, because this is still a development release.
Scribus 1.5.3 is very fast and has been thoroughly tested. Generally, everything that works reliably in 1.4.x also works in 1.5.3, but it's faster and more versatile. On top of that, it includes additional and already overwhelmingly reliant features galore.
Most Important Changes
======================
- The most important change isn't immediately visible, namely a completely rewritten text layout engine, which supports complex scripts like Arabic, Hindi or Thai, as well as providing access to advanced OpenType features, such as ligatures and alternate glyphs.
- Altogether, about 500 languages and/or scripts are supported. Please note that as of version 1.5.3, Scribus is supposed to render these diverse writing systems, which still needs thorough testing by those who are familiar with them.
- Typing on the canvas and text rendering in general has become a lot faster.
- Previews for fonts are now available in font selectors.
- The "Text" tab has been removed from the Properties Palette and is now a separate UI palette.
- The performance of copying and pasting objects in/from/to files with huge color palettes has been vastly improved.
- An import filter for Krita's KRA format has been added.
- Scribus now follows the XDG standard for configuration files. Therefore, the Scribus preferences directory has moved from ~/.scribus/ to a new default location: ~/.config/scribus/
- Color selectors display the color values as a tooltip.
- A longstanding problem with the launch option for an external image editing program has been resolved. Until version 1.5.3 it was necessary to manually close the external program before it could be started again from within Scribus. This is no longer necessary.
- The "Wikipedia RAL Classic" color palette has been updated, this time using Wikipedia's LAB color values.
- A script called "Caption" has been included, which adds a text frame to an image frame, based on the latter's proportions.
- The "Autoquote" scripts now supports inverted guillemets via the "de-g" parameter.
- Code improvements have been made based on recommendations from using both the Coverity scan tool (https://scan.coverity.com/) and the "clazy" tool (https://github.com/KDE/clazy). These changes improved efficiency, removed bugs and improved security.
- Countless bugs, mostly introduced with the new features in earlier releases of 1.5.x, have been fixed. For details see the 1.5.3svn changelog (https://bugs.scribus.net/changelog_page.php?version_id=102)
New Dependencies
================
- As of version 1.5.3, the minimum Qt version to compile the program is 5.5.
- harfbuzz and libicu, as well as the related development packages are now required.
Caveats
- Some newly introduced features, like footnotes, may not function as desired, at least not yet.
- The file format may undergo some changes between the current release and 1.6.0, so we advise caution when it comes to workflows that use automated document generation or parsing.
- Vertical writing systems aren't supported for the time being, but support will be added in a later release.
- The Online Help hasn't been completely updated, and it won't be until the final 1.6.0 release.
Special Credits
===============
- This version builds significantly on the code from 1.5.2 with the work that the Oman House of Open Source Technology team, led by Khaled Hosny, delivered.
- 1.5.3 uses all of the remainder of the code, and we have Fahad Al-Saidi to thank for his continued work and especially for the bug triaging and code changes.
- Andreas Vox introduced a layout cache to speed up text rendering.
- William Bader has fixed the issue of launching several instances of an external image editing program.
- Contributions to GUI translations via participants on the Transifex translation platform
Primary Download Locations
==========================
- Installation packages for Windows, Mac OS X, a Linux AppImage and the source code are available here: https://sourceforge.net/projects/scribus/files/scribus-devel/1.5.3/
- Fedora and CentOS RPMs: http://download.opensuse.org/repositories/home:/mrdocs
- OpenSUSE, SLED, and SLES RPMs: http://download.opensuse.org/repositories/home:/mrdocs
- Packaging for other Linux distributions, *BSD, Solaris and OpenIndiana is beyond our influence. We recommend updating the respective repository data on a regular basis.
- Windows Portable App: http://portableapps.com/apps/office/scribus_portable#test
Download Verification
=====================
Please visit the official announcement on https://wiki.scribus.net/canvas/1.5.3_Release for Sha256 and Sha1 checksums.
Expectations for Scribus 1.5.4
==============================
- An entire rebuild of the palette system used in Scribus, enabling a cleaner and more flexible GUI
- Updates to dependencies, with a likely increase to Qt 5.6
- Migration of build systems or targeted versions of operating systems to later versions
Credits
=======
The Scribus Team would like to thank Anduin.net and Modirum for their continued hosting of all of the Scribus websites.
We are grateful to the Organisation Internationale de la Francophonie and Linux New Media (Germany) for sponsoring.
The Scribus Team is also honored to have Resene Colours (New Zealand), dtp studio Oldenburg (Germany), Scientific Illustration Services Corp. (USA), the Newspaper Association of America (USA), Software Consulting Services (USA), freieFarbe e.V. (Germany), bauwerk Kommunikationsdesign (Germany) as Special Supporters and donors of color palettes and other content since the 1.4.x release, just like we are grateful to the owner of Vector Portal for the permission to distribute some of his work as Scribus Templates.
Porting Scribus to OS/2 and eComStation is being supported by Serenity Systems (USA).
Finally, the Scribus Team would like to thank the many end users, translators, testers and contributors who helped us with this release.
5 years, 9 months
SVGMatrix deprecated?
by Steve Litt
Hi all,
I have a bunch of groups of class "screw", each comprised of a circle
screwhead and a smaller square in the center called a screwsquare. In
every instance of "screw", screwhead and screwsquare have identical x,
y, height, width and r dimensions. Each screw's position is determined
by the screw group's transform=translate(xadjust, yadjust). This is
done automatically by Inkscape, and furthermore, it's easy to set
manually with:
myElement.setAttribute('transform','translate(xadjust,yadjust)');
The trouble comes in when you want to *get* that transform. Getting the
transform is necessary when you want to move element whatever2 in
relation to the location of screw1. Getting the translation is one of
the worst documented things I've seen, but the concensus seems to be
something like the following (for my screw case where the group has the
transform):
===============================================================
function screw_coords(screw){
matrix = screw.transform.baseVal.getItem(0).matrix;
var coords = [];
shead = screw.querySelector('.screwhead');
coords[0] = shead.cx.animVal.value + matrix.e;
coords[1] = shead.cy.animVal.value + matrix.f;
return(coords);
}
===============================================================
The preceding is ugly and fragile for a whole number of reasons, it's
inobvious and horribly undocumented. But the real problem is it appears
to be deprecated:
https://developer.mozilla.org/en-US/docs/Web/API/SVGMatrix
The preceding article says not to use SVGMatrix, and to update code as
soon as possible, but remains mute on what you use instead. How the
hell do you read a translation? It's a mystery.
The following article gives a crazy train regex kludge method to read a
translate:
https://stackoverflow.com/questions/10349811/how-to-manipulate-translate-...
If anybody knows the proper secret handshake to read a translate in a
non-deprecated, browser independent, non-kludgificent way, please let
me know, perhaps with some URLs of docs for such a functionality.
Thanks,
SteveT
Steve Litt
May 2017 featured book: Twenty Eight Tales of Troubleshooting
http://www.troubleshooters.com/28
5 years, 10 months
telegram inkscape
by Jabier Arraiza
Hi all anyone has get the t.me/inkscape from telegram direction. Its
cool if can delete the acount and the url reserved and send to inkscape
board to manage it.
Whith this inkscape community has the best link to telegram services we
want to add in the future.
Thanks so much in advance.
5 years, 10 months
Manuals: Inkscape Beginners' Manual ready for translation to English and editing
by Maren Hachmann
Hi everyone,
join us for translating and editing the Inkscape Beginners' manual,
which is based upon Elisa de Castro Guerra's French book "Initiation à
Inkscape" (Original French version available at
https://www.flossmanualsfr.net/initiation-inkscape/ - don't translate
this one ;-) ) !
Thank you, Elisa, for sharing your work and helping with licencing (also
for joining the admins)!
The plan is to translate the book from French to English (Sylvain and
Hinerangi already did some of the work), and make adjustments as we see
fit, then to make it available for people who only start using Inkscape
- if possible, accessible directly from inside the Inkscape program.
Here are some notes to get you started (we may tweak processes later, if
we find better ones):
Platform usage
==============
This book is written at flossmanuals.net, which is a website that allows
for collaborative editing of books about Free/Libre and Open Source
Software. To learn more about the community that's behind it, please
visit http://www.flossmanuals.org/about-floss-manuals-foundation.
The manual for this 'manual writing platform' (which is an instance of
the Booktype software), is available at
http://sourcefabric.booktype.pro/booktype-16-for-authors-and-publishers/ .
Joining
=======
Join the group at
http://write.flossmanuals.net/groups/beginners-manual-for-inkscape/ :-)
Also say hi on the docs mailing list (see below, section
"Communication", so we know who is who, and what you can help with.
Editing
=======
IMPORTANT: When you're editing the book, ALWAYS leave a screen either by
clicking on the 'Cancel' or on the 'Save' button. This is because, if
you leave it by just closing the tab in your browser, the chapter will
stay locked and inaccessible for other editors.
Version
=======
This book will refer to the Inkscape 0.92.x series (important for your
screenshots!).
Writing Style
=============
This book is meant as an introduction for people who are not yet
familiar with Inkscape terminology.
When deciding how to phrase something, think of yourself when you
started to use a vector editor, or think of a teen who you would like to
introduce to the program, and who you would like to enjoy the process,
and to be able to make nice drawings after reading the book.
Stay on topic, make it easy to understand, and keep the learning curve
shallow. Write less rather than more. Be nice and encouraging to the
reader. There exists another manual that provides the deep, technical
details. We need to keep in mind that it will also be read by people
whose native language is not English.
Communication
===============
Anyone who edits the book can exchange messages, files and snippets via
chat with other users who are online at the same time.
For discussions of wider interest, or when you hit an obstacle, please
subscribe and send a message to the inkscape-docs mailing list at
https://sourceforge.net/p/inkscape/mailman/inkscape-docs/ .
Currently, we have 4 book admins (Elisa, Brynn, CR and me). Admins can
change the book settings, add other admins and create release versions.
Chapter status
==============
Chapters move from one status to the next, when they're being worked on:
1. needs translation:
Chapter isn't (fully) translated yet. If you speak both French and
English, this is where your help is needed! This step only requires you
to work on the text. You can ignore any images.
2. to be proofed:
Chapter is translated, and needs to be checked by someone other than the
translator, to spot errors and do some polishing. If English is your
native language and you're good with words, grab this job!
3. needs images:
The chapter contains images, but those are still French. Either it's
just their file names that need to be changed (Workflow: download image,
rename it on your computer, reupload, change link in the Chapter(s),
provide meaningful alt text, delete French image) or a new screenshot is
needed from the English interface. If you know how to do these things,
please jump right in!
(Hint: all image links follow this scheme: static/image_file.ext)
4. completed:
This chapter is more or less finished. Concentrate your effort on the
other ones :) If you spot a mistake or typo, improvements are still
possible, of course.
Important: Don't forget to update a chapter's status, after you have
worked on it ;-)
When you've got a great idea that would introduce a major change in the
book's structure, please confer with other editors on the mailing list
to see what they think about this.
Cover
=====
If you're good at creating meaningful art, then we need you for creating
a cool cover image that shows what you can do with Inkscape and is
inviting for beginners. Read more about the Cover Manager in Booktype at
http://sourcefabric.booktype.pro/booktype-16-for-authors-and-publishers/_....
Let us know about your plans on the mailing list (see section about
Communication).
Styling and Customization
======================
If you know your CSS, you can help by improving the book's styling. You
can read all about customization for different output formats and the
front page in the design section of the Booktype manual at
http://sourcefabric.booktype.pro/booktype-16-for-authors-and-publishers/f....
For the book to appear on the flossmanuals.net frontpage, the steps
outlined here are required:
http://write.flossmanuals.net/floss-manuals-workflow/_draft/_v/1.0/how-do...
, section "Publish new details..."
License
=======
This book is licensed under the Creative Commons Attribution 4.0 license
(CC-By 4.0, see https://creativecommons.org/licenses/by/4.0/).
By contributing to this book, you agree to publish your content under
this license.
As a contributor, please add your name to the list in the 'About this
Book' chapter.
This chapter will *always* be in need of new content ;-)
Go!
===
Have fun working on the book at
http://write.flossmanuals.net/start-with-inkscape/_edit/#
You will find a copy of these notes in the 'Notes' tab, and you will
find me working on translating French -> English there, in the late
evenings (CEST).
See you there,
Kind Regards,
Maren
5 years, 10 months
How to make an *SVG* connector?
by Steve Litt
Hi all,
I want to be able to make an *SVG* connector that doesn't rely on the
facilities of Inkscape to do its thing. According to this URL there is
such a thing:
https://dev.w3.org/SVG/modules/connector/SVGConnector.html#ConnectorElement
When I make a connector in Inkscape using the little connector symbol,
in XML it shows up as a path, not a connector, and it has
inkscape:connector-type. When I save as plain SVG, the
inkscape:connector-type goes away, and it's nothing more than a line
segment.
How do I make a real SVG connector in Inkscape?
Thanks,
SteveT
Steve Litt
May 2017 featured book: Twenty Eight Tales of Troubleshooting
http://www.troubleshooters.com/28
5 years, 10 months
How to get rid of groups' transform=translate()
by Steve Litt
Hi all,
So I managed to get a line segment to route itself between 2 circles.
But if the 2 circles are in a group, and the group's been duped, the
circles have the same cx and cy and their group has a different
translate(). Ugh!
I have to dup groups because I want to input onclick, onmouseover,
onmouseout, and class only once on the group.
Does anyone know how a group's translate() can be incorporated into its
component paths' and circles' x and y or cx and cy so getting a
location is as simple as reading cx and cy, rather than doing all sorts
of arithmetic with the parent's translate()?
Thanks,
SteveT
Steve Litt
May 2017 featured book: Twenty Eight Tales of Troubleshooting
http://www.troubleshooters.com/28
5 years, 10 months
Re: [Inkscape-user] Problem with Image Sizing in Inkscape 0.92
by C R
It's because svg was designed as a web format and according to the wiki:
"Eventually, after long arguments, the CSS working group dictated that
one inch would be fixed to 96 pixels regardless of screen resolution"
Yea, that's the insanity we are stuck with. Pixels being units of
physical measurement.
The cure is to never, ever under ANY circumstances uses pixels as a
unit of measurement. It was always a bad idea, but since svg was meant
to contain css it's kinds what we are stuck with if we want to be/stay
compatible with web standards... even the ones that make no goram
sense. :)
Note: Inkscape still correctly will output your vectors at any dpi you
wish, but pixels should always be calculated based on a physical
measurement (metric or imperial), and pixels calculated as a dpi.
This is not a problem that will go away. The CSS working group will no
doubt decide to haphazardly change it again because "retina" displays
are so popular, in which case it will probably be 300px / inch.
It doesn't matter though. If you're using pixels to calculate witdth,
you will have to expect that the width will change based on the pixel
size of your output, so best thing is to not do that again in the
future.
Here's the scoop on units in Inkscape:
http://wiki.inkscape.org/wiki/index.php/Units_In_Inkscape
-C
On Fri, May 12, 2017 at 9:46 PM, Mick Ralph <mick.ralph@...3070...> wrote:
> As the background to my problem, I use Inkscape to prepare drawings
> of sides and ends, etc, to be made into model railway carriages. The
> designs are then opened in the Designer Edition (DE) of Silhouette
> Studio for cutting out of styrene sheet on the Silhouette Portrait
> cutting machine. DE can open SVG files, as created with Inkscape.
>
> For Inkscape 0.48 and 0.91, this works fine and the parts are cut to
> the same size as the Inkscape drawing, although it is necessary to
> ensure that the document properties are set to "default units" of mm
> and "custom size" "units" of px; if custom size units are left as mm,
> then the actual size of a part decreases from (say) 110mm to about
> 88mm. I created a new default template with these properties to
> ensure that the Inkscape drawings would always cut at the right sizes.
>
> When Inkscape 0.92 was released I downloaded it and I have just used
> it to draw out another carriage. I then opened the svg file in DE
> and without examining it, sent it to the cutter. The parts seemed
> too small. I then realised that the default template was no longer
> in mm/px, but was now in mm/mm. When I altered the document
> properties back to mm/px, I opened the file in DE and examined the
> size of the parts. I now find that the part which should have been
> 110mm is now about 117mm.
>
> This is clearly useless for making scale models. I opened in v 0.92
> a file which was originally created in Inkscape 0.91 and received the
> message that the original file was drawn at 1 inch = 90 px, but the
> new version uses 1 inch = 96 px. As a user rather than a developer,
> I do not understand the reason for this (nor do I need to understand
> it) - I just need to know that if I draw a line 100mm long it will
> cut at that length, as in the earlier versions.
>
> As I can see no option in v 0.92 to allow compatibility with earlier
> versions, it seems that I will have to reload v 0.91 and use that to
> create my drawings.
>
> Is there a compatibility option to allow drawings to be made at 90px
> per inch in v 0.92?
>
> Mick Ralph
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Inkscape-user mailing list
> Inkscape-user(a)lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/inkscape-user
5 years, 10 months
Re: [Inkscape-user] Problem with Image Sizing in Inkscape 0.92
by Maren Hachmann
Hi Mick,
the change was necessary to be compatible with CSS standards.
When you open the file with Inkscape, it will offer to scale it in that
dialog where it tells you about the changed size, which intends to make
the file compatible again.
In your specific case, the option "Scale elements" will hopefully do
what you need. Can you try that?
Kind Regards,
Maren
Am 12.05.2017 um 22:46 schrieb Mick Ralph:
> As the background to my problem, I use Inkscape to prepare drawings
> of sides and ends, etc, to be made into model railway carriages. The
> designs are then opened in the Designer Edition (DE) of Silhouette
> Studio for cutting out of styrene sheet on the Silhouette Portrait
> cutting machine. DE can open SVG files, as created with Inkscape.
>
> For Inkscape 0.48 and 0.91, this works fine and the parts are cut to
> the same size as the Inkscape drawing, although it is necessary to
> ensure that the document properties are set to "default units" of mm
> and "custom size" "units" of px; if custom size units are left as mm,
> then the actual size of a part decreases from (say) 110mm to about
> 88mm. I created a new default template with these properties to
> ensure that the Inkscape drawings would always cut at the right sizes.
>
> When Inkscape 0.92 was released I downloaded it and I have just used
> it to draw out another carriage. I then opened the svg file in DE
> and without examining it, sent it to the cutter. The parts seemed
> too small. I then realised that the default template was no longer
> in mm/px, but was now in mm/mm. When I altered the document
> properties back to mm/px, I opened the file in DE and examined the
> size of the parts. I now find that the part which should have been
> 110mm is now about 117mm.
>
> This is clearly useless for making scale models. I opened in v 0.92
> a file which was originally created in Inkscape 0.91 and received the
> message that the original file was drawn at 1 inch = 90 px, but the
> new version uses 1 inch = 96 px. As a user rather than a developer,
> I do not understand the reason for this (nor do I need to understand
> it) - I just need to know that if I draw a line 100mm long it will
> cut at that length, as in the earlier versions.
>
> As I can see no option in v 0.92 to allow compatibility with earlier
> versions, it seems that I will have to reload v 0.91 and use that to
> create my drawings.
>
> Is there a compatibility option to allow drawings to be made at 90px
> per inch in v 0.92?
>
> Mick Ralph
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Inkscape-user mailing list
> Inkscape-user(a)lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/inkscape-user
>
5 years, 10 months
Problem with Image Sizing in Inkscape 0.92
by Mick Ralph
As the background to my problem, I use Inkscape to prepare drawings
of sides and ends, etc, to be made into model railway carriages. The
designs are then opened in the Designer Edition (DE) of Silhouette
Studio for cutting out of styrene sheet on the Silhouette Portrait
cutting machine. DE can open SVG files, as created with Inkscape.
For Inkscape 0.48 and 0.91, this works fine and the parts are cut to
the same size as the Inkscape drawing, although it is necessary to
ensure that the document properties are set to "default units" of mm
and "custom size" "units" of px; if custom size units are left as mm,
then the actual size of a part decreases from (say) 110mm to about
88mm. I created a new default template with these properties to
ensure that the Inkscape drawings would always cut at the right sizes.
When Inkscape 0.92 was released I downloaded it and I have just used
it to draw out another carriage. I then opened the svg file in DE
and without examining it, sent it to the cutter. The parts seemed
too small. I then realised that the default template was no longer
in mm/px, but was now in mm/mm. When I altered the document
properties back to mm/px, I opened the file in DE and examined the
size of the parts. I now find that the part which should have been
110mm is now about 117mm.
This is clearly useless for making scale models. I opened in v 0.92
a file which was originally created in Inkscape 0.91 and received the
message that the original file was drawn at 1 inch = 90 px, but the
new version uses 1 inch = 96 px. As a user rather than a developer,
I do not understand the reason for this (nor do I need to understand
it) - I just need to know that if I draw a line 100mm long it will
cut at that length, as in the earlier versions.
As I can see no option in v 0.92 to allow compatibility with earlier
versions, it seems that I will have to reload v 0.91 and use that to
create my drawings.
Is there a compatibility option to allow drawings to be made at 90px
per inch in v 0.92?
Mick Ralph
5 years, 10 months
