Support for high DPI screens
Closed this issue · 9 comments
As follow of this thread:
http://lists.scribus.net/pipermail/scribus-dev/2016-May/003076.html
We need to support loading and configure the svg icon set. The SVG icon set is contributed by Mr. Dezso Markon (will be uploaded latter on). The ideal solution is Scribus follows the desktop settings configuration for the icon size (if they supporting hight DPI in the first place).
the icon set in svg format is attached.
We will need (preferably in an automated way) to extract the individual icons from this SVG files with the names Scribus expects. We can’t load the icons by id from a single SVG file.
As svg is xml based format, It is better to extract the ‘g’ element from each object id, then write new svg with the name which is in the inkscape:export-filename tag.
Here is python example:
https://gist.github.com/revolunet/dbe52d5cdf0e38ce35fd
If nobody can do it automatically, I will do it manually.
We need the icon file name and its width and height, not sure if the SVG file has all these information. The file also seems to have two sets of icons, so we need to know which elements to extract.
It seem there is a dark them and a light one but the current used icon set is the light one. However, there are a lot of duplication due to the need to export to different sizes and different names.
I will work to extract all icons manually.
here is the 202 icons each in a separate file.
svg-icons.zip
I think this enhanced belongs to trunk, not this branch. Remember that we still have to merge both branches at some point of time...
We send such independent enhancements to Scribus bug tracker. The previous
Hi-DPI patches are applied already.
On Mon, May 30, 2016, 12:52 PM andreas-vox notifications@github.com wrote:
I think this enhanced belongs to trunk, not this branch. Remember that we
still have to merge both branches at some point of time...—
You are receiving this because you commented.Reply to this email directly, view it on GitHub
#201 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AAFu2sE8jl3bmOKqgbeOeKlIR9Qsus0Qks5qGrN4gaJpZM4IkWf2
.
I think this fixed by now in trunk.