Request: Adding Information to the "ExportPDFCMYK" Wiki-Article
by niccorigi＠...1255...
Hello Wiki-Team,
I think I found something that would help future Users like me, and thus
should be mentioned in the wiki:
(I'm a Beginner, first time Inkscape for an Uni-Project),
For a printing-service, I needed the CMYK-Colorformat. (In an PDF).
But the recommended Extension (
http://wiki.inkscape.org/wiki/index.php/ExportPDFCMYK
<http://wiki.inkscape.org/wiki/index.php/ExportPDFCMYK> ) didn't work for
me.
(There was an Error during the Exporting).
However, following process worked for me:
1. Export to PDF via the normal Export-Function. (Result is a Cairo-PDF in
RGB-Colors)
2. Use ghostscript to convert it to CMYK: (found at
http://zeroset.mnim.org/2014/07/14/save-a-pdf-to-cmyk-with-inkscape/
<http://zeroset.mnim.org/2014/07/14/save-a-pdf-to-cmyk-with-inkscape/> )
gs -dSAFER -dBATCH \
-dNOPAUSE -dNOCACHE -sDEVICE=pdfwrite \
-sColorConversionStrategy=CMYK \
-dProcessColorModel=/DeviceCMYK \
-sOutputFile=document_cmyk.pdf \
document_rgb.pdf
This process was much easier for me, as I only had to execute one Command
Line, instead of installing two seperate Programs.
And it was the only one that worked, which was crucial, as I had deadlines
to follow. And I didn't notice any changes in the Appearance of my file, so
the colors were, to the eye, perfecly preserved, even on the eventually
printed PVC-Plane.
Could you add this to the "ExportPDFCMYK" Wiki-Article, that this process
existst?
I would be very thankful to that! And maybe future Users too witch the same
struggles I had.
Best regards,
Niccolò Rigi-Luperti
niccorigi@...1255... <mailto:niccorigi@...1255...>
5 years, 6 months
Proposed idea for an interim trunk release
by Bryce Harrington
After 0.92.2 is completed, I've been thinking about doing a development
release of trunk, to help us build towards 0.93. Something a bit more
than just a nightly snapshot, but far less than even an alpha release.
Call it an "unrelease" or just a "blessed snapshot".
Here's my reasoning for why I think this would be worth doing:
a. Our alphas get decent testing, but there's not time for the
necessary bug fixing, since we're anxious to get the actual release
out. This interim release would stimulate testing and bug fixing
independent of any such pressure.
b. Moving to gitlab, cmake, and gtk3 has changed a LOT structurally.
Doing a "practice release" would help find remaining problems with
these transitions.
c. Despite all the great work done setting up CI's, automated builds,
and rolling packaging systems, many advanced users want a fully
usable, QA'd build before they'll look at our work. Lesson learned
from last release is that we really need these kinds of users' input
on our features before we finalize stuff.
d. For the rest of us Inkscapers, it will provide a focal point for our
near term development, testing, documentation, and refactoring work.
But one that won't need all the rigor that a regular release would
have - no about screen contests, overly long feature freeze periods,
string freezes, worrying over release-blocker bugs, or needing to
polish up release notes and other docs.
Procedurally:
* A soft feature freeze for a week or two, max
* No more than one pre-release (if even that)
* Translations encouraged, but no string freeze
* Packaging needed for all platforms
* Packages available from website, but not linked prominently
* Lite marketing - basically just target to advanced users
* Is clearly marked UNSTABLE and UNSUPPORTED
Some other crazy ideas to consider, that might help prevent it from
becoming a support burden:
+ Annoying popup dialog declaring it so at run time?
+ No guarantee of file format compatibility?
+ Limited period for accepting bugs reports?
+ Expiring binary refuses to run after a certain date?
+ Advise distros to NOT distribute it?
So, your thoughts?
Bryce
5 years, 6 months
Hackfest regressions
by Eduard Braun
Hi all,
first of all I'd like to thank everybody for their contributions during
the hackfest!
As with all new code I noticed some regressions. As you probably know
best on what parts of the code you worked yourselves I'll just list
everything I noticed here, so you know about it and can attempt to fix
it. (If I need to file a bug for any of those please let me know, but I
hope most of those issues can be fixed easily):
1. The Inkscape Window is not restored to the correct position anymore
(probably related to
https://gitlab.com/inkscape/inkscape/commit/fa8a2ee7e2539b145a87ac9af0d97...).
On a multi-monitor system with two monitors oriented like [1][2]
with [2] being the primary monitor the Inkscape window is restored
somewhere on [1] if it was closed on [2], so probably the combined
screen area is not accounted for when calculating positions.
2. Some icons are broken or missing, see
https://inkscape.org/de/gallery/item/11147/broken_icons.zip (there
might be others, but those are the ones I noticed).
3. During the hackfest menu icons were re-added. However on Windows I
was only able to find them in a single location (the path menu).
Aren't there supposed to be more icons?
Also they look a bit weird (see
https://media.inkscape.org/media/resources/file/menu_icons.png):
Instead of using the space to the left they are indented like the
rest of the text shifting menu labels unnecessarily to the right
resulting in a very uneven look.
If I notice anything else I'll report it here.
If I can provide additional information or help with debugging please
let me know.
Regards,
Eduard
5 years, 6 months
to-do list for interface issues?
by brynn
Hi Friends,
As I've seen mentioned in this mailing list recently, it seems like a
lot of new work is planned for improving the interface, in the near future. We
come across issues all the time in forums. So I'm wondering if someone is
maintaining a to-do list, or list of issues that need to be addressed? It would
be easy for us to help you identify issues, by adding items to a list, if you
would find it helpful....if there is such a list somewhere.
Thanks,
brynn
5 years, 6 months
Hackfest Gallery
by Martin Owens
Hey all,
Our gallery is ready:
https://inkscape.org/en/*developer/galleries/
If you have photos from the hackfest, you can post them on the website
to this gallery. The best way is to drag and drop your photos to the
blue submit button. Or click the blue submit button.
I found a bug were rotated photos wouldn't auto rotate, so be aware.
Let me know if you post some, I'll curate them to make sure they're
good.
Best Regards, Martin Owens
5 years, 6 months
Windows 10, cmake, cannot compile rev f80d5b44
by alvinpenner
commit f80d5b44e2fdad56b6aad9ca7fb14f44c835915c
Author: Tavmjong Bah <tavmjong@...8...>
Date: Thu Jul 6 11:32:09 2017 +0200
Don't check if icon exists in default theme since that prevents use of
fallback icons.
...........................
attempting to compile this rev, I get the following sequence of errors,
after re-trying about 4 times:
[ 28%] Building CXX object src/CMakeFiles/inkscape_base.dir/io/http.cpp.obj
[ 28%] Building CXX object
src/CMakeFiles/inkscape_base.dir/svg/svg-color.cpp.obj
C:\Users\penne_000\AppData\Roaming\InkscapeGit\inkscape\src\io\http.cpp:36:26:
fatal error: libsoup/soup.h: No such file or directory
...
[ 28%] Building CXX object src/CMakeFiles/inkscape_base.dir/io/http.cpp.obj
[ 28%] Building CXX object
src/CMakeFiles/inkscape_base.dir/ui/clipboard.cpp.obj
C:\Users\penne_000\AppData\Roaming\InkscapeGit\inkscape\src\io\http.cpp:36:26:
fatal error: libsoup/soup.h: No such file or directory
...
[ 28%] Building CXX object src/CMakeFiles/inkscape_base.dir/io/http.cpp.obj
[ 28%] Building CXX object
src/CMakeFiles/inkscape_base.dir/ui/tool-factory.cpp.obj
C:\Users\penne_000\AppData\Roaming\InkscapeGit\inkscape\src\io\http.cpp:36:26:
fatal error: libsoup/soup.h: No such file or directory
...
[ 28%] Building CXX object src/CMakeFiles/inkscape_base.dir/io/http.cpp.obj
[ 28%] Building CXX object
src/CMakeFiles/inkscape_base.dir/ui/tools-switch.cpp.obj
C:\Users\penne_000\AppData\Roaming\InkscapeGit\inkscape\src\io\http.cpp:36:26:
fatal error: libsoup/soup.h: No such file or directory
compilation terminated.
src\CMakeFiles\inkscape_base.dir\build.make:5112: recipe for target
'src/CMakeFiles/inkscape_base.dir/io/http.cpp.obj' failed
mingw32-make[2]: *** [src/CMakeFiles/inkscape_base.dir/io/http.cpp.obj]
Error 1
mingw32-make[2]: *** Waiting for unfinished jobs....
CMakeFiles\Makefile2:338: recipe for target
'src/CMakeFiles/inkscape_base.dir/all' failed
mingw32-make[1]: *** [src/CMakeFiles/inkscape_base.dir/all] Error 2
Makefile:126: recipe for target 'all' failed
mingw32-make: *** [all] Error 2
--
View this message in context: http://inkscape.13.x6.nabble.com/Windows-10-cmake-cannot-compile-rev-f80d...
Sent from the Inkscape - Dev mailing list archive at Nabble.com.
5 years, 6 months
most icons missing, Windows 10, Inkscape 0.92+devel trunk-65-gf65c700 2017-07-04
by alvinpenner
just built Inkscape 0.92+devel trunk-65-gf65c700 2017-07-04:
commit f65c70038c52f305d0da7e97f96bf6695cb3554e
Author: Tavmjong Bah <tavmjong@...8...>
Date: Tue Jul 4 20:05:55 2017 +0200
More icon clean-up.
................................................................
most of the icons are missing. There are many messages of the type:
(inkscape.exe:9664): GLib-GIO-CRITICAL **: g_file_new_for_path: assertion
'path != NULL' failed
(inkscape.exe:9664): GLib-GIO-CRITICAL **: g_loadable_icon_load: assertion
'G_IS_LOADABLE_ICON (icon)' failed
(inkscape.exe:9664): GLib-GIO-CRITICAL **: g_file_new_for_path: assertion
'path != NULL' failed
(inkscape.exe:9664): GLib-GIO-CRITICAL **: g_loadable_icon_load: assertion
'G_IS_LOADABLE_ICON (icon)' failed
tia,
Alvin
--
View this message in context: http://inkscape.13.x6.nabble.com/most-icons-missing-Windows-10-Inkscape-0...
Sent from the Inkscape - Dev mailing list archive at Nabble.com.
5 years, 6 months
Update (merge request) for bool LPE
by Michael Soegtrop
Dear Inkscape Team,
I did a merge request for an updated bool LPE. See the merge request
comments.
What I still need is a method to check if a PathVector is closed or
open. I want to issue an error message if the operands are not as
expected, but I couldn't find a way to do this. Jabier wrote that there
is some isClosed() function, but I couldn't find anything around a
PathVector. Any help with this is appreciated.
Best regards,
Michael
5 years, 6 months
[Inkscape-board] Inkscape Board Meeting ~ Friday Jul 7th
by Bryce Harrington
== Board Meeting ==
This Friday July 7th will be the next monthly board meeting, at noon
Pacific in #inkscape-devel as usual. All members of the community are
welcome to participate.
http://wiki.inkscape.org/wiki/index.php/Board_Meetings
Agenda:
+ Paris 2017 Hackfest report
+ Merchandise sales status update
+ Other business
Action items from last meeting are below.
Bryce
----- Forwarded message from Bryce Harrington <bryce@...961...> -----
Date: Sun, 4 Jun 2017 00:01:01 -0700
From: Bryce Harrington <bryce@...961...>
To: inkscape-board@...6...
Cc: inkscape-devel@...6...
Subject: [Inkscape-board] Board Meeting Minutes ~ 2017-05-03
Reply-To: inkscape-devel@...6...
== Meeting Minutes for 2017-05-03 ==
I don't usually prepare meeting minutes, but there was a ton of
discussion with a lot of follow ups and action items, so figure it could
use some additional visibility.
Summary of Action Items:
+ ACTION: Need to sharpen pencil on budget to see where we're at exactly. [bryce]
+ ACTION: Draft https://inkscape.org/en/support-us/hackfest-2017/ [Tavmjong]
+ ACTION: Make a news item for the hackfest fundraiser [Tavmjong, doctormon]
+ ACTION: Advertise hackfest fundraiser on twitter [Mc, Tavmjong]
+ ACTION: Advertise hackfest fundraiser on facebook [Tavmjong or designee]
+ ACTION: Advertise hackfest fundraiser on G+ [Tavmjong or designee]
+ ACTION: Advertise hackfest fundraiser on Instagram [Rob-Sterbal, Tavmjong]
+ ACTION: Investigate stickers & pricing for hackfest [jabiertxof]
+ ACTION: Decide GUADEC attendance [Alex]
+ ACTION: Propose donation "add-on" for Win10 store to inkscape-devel@ [Mc]
+ ACTION: Jot signed-mug raffle idea down on Fundraising_Ideas page [CRogers]
+ ACTION: Test the message patch from ML [tedg]
+ ACTION: Announce plan for gitlab migration [tedg]
+ ACTION: Discuss scripting ideas for bug migration [Mc, doctormon]
+ ACTION: Re-raise topic of bugtracker migration at a future time [Mc]
+ ACTION: Help Mc kickoff funded devel of a feature [bryce]
+ ACTION: Propose a batch t-shirt run (e.g. for hackfest) [tedg]
+ ACTION: Re-contact Mihaela to finish starting up Spreadshirt [doctormon, bryce]
+ ACTION: Experiment with first-call / last-call dates on board votes [bryce]
+ ACTION: Check on board member voting [bryce]
Full log:
https://inkscape.org/en/paste/11064/
=== Paris Hackfest ===
* 5 devs + interest from a few others
* Note that Conservancy has clarified travel reimbursement documentation
+ Process hasn't changed but it's explained better.
+ Hackfest travelers should doublecheck
* Future hackfests may be short on cash
+ We have $8000 budgeted for hackfests currently
+ The 2017 hackfest allocates $13,000 expenses
- Most people won't use their full allocation
- Some people won't be able to attend
- So actual expense should be far less than the allocation
+ ACTION: Need to sharpen pencil on budget to see where we're at exactly. [Bryce]
* Should use this as opportunity to do fundraising for further hackfests
+ ACTION: Draft https://inkscape.org/en/support-us/hackfest-2017/ [Tavmjong]
+ ACTION: Make a news item for the hackfest fundraiser [Tavmjong, doctormon]
+ ACTION: Advertise hackfest fundraiser on twitter [Mc, Tavmjong]
+ ACTION: Advertise hackfest fundraiser on facebook [Tavmjong or designee]
+ ACTION: Advertise hackfest fundraiser on G+ [Tavmjong or designee]
+ ACTION: Advertise hackfest fundraiser on Instagram [Rob-Sterbal, Tavmjong]
* Should we plan a community "open day" at the Hackfest?
+ Sticker give-aways to visitors of the event (if any)
+ Stacks to distribute to regular attendees to give out at other
events
+ If it's done, designate a single day for visitors, to avoid
distraction, and make sure to advertise the fact prominently
+ Purpose of hackfest is not community outreach, so perhaps should be
left for a separate event.
* The SFC-produced stickers might not get done in time for the hackfest,
but the designs could be used for locally printed ones
+ Ryan Gorley recommends https://www.uprinting.com/vinyl-sticker-printing.html
+ Shoot for 20 per attendee, ~200 total
+ ACTION: Investigate stickers & pricing for hackfest [jabiertxof]
* Virtual attendance (e.g. livestream, google hangouts, etc.)
+ If someone sets it up, post explanation on how to get set up
=== GUADEC - Gtk3 ===
* Coming up end of July in Manchester
* Last year they said they could help us with Gtk3 stuff.
* Would be worthwhile if Alex could go, pertaining Gtk3
+ tghs (Mac gtk3) is in Leeds so can make it for attendance
* ACTION: Decide GUADEC attendance [Alex]
=== Sticker Printing by Conservancy ===
* Stickers are designed from the about screen entrants. Artists were
asked if they would be open to having their work printed on stickers.
+ https://inkscape.org/en/~doctormo/%E2%98%85stickers-2017-draw-freely
+ https://inkscape.org/en/~doctormo/%E2%98%85stickers-2017-landscape-inkscape
* Designs were sent to SFC with a $100 budget (vote approved by board)
+ Waiting on Brett to get back to us on it
=== Funded Projects ===
* Various funded feature development ideas were floated during the meeting:
+ 1% zoom limit (chr[])
+ hidpi support (Windows users want this particularly)
+ gtk3 migration may give a native-looking ui for mac os, and many
people would pay for that
* Various fundraising ideas were floated during the meeting:
+ Kickstarter fundraising based on feature sets that people ask for all
the time has worked very well for Krita
- krita succeeds well at advertizing becaue they work with awesome
artists to promote them
- They also deliver things that artists ask for as their primary goal.
+ Donation dummy "add-on" to Inkscape on the Windows store
- ACTION: Propose donation "add-on" for Win10 store to inkscape-devel@ [Mc]
+ Raffle for an inkscape mug and/or t-shirt signed by hackfest devs
- ACTION: Jot signed-mug raffle idea down on Fundraising_Ideas page [CRogers]
+ More ideas are being captured at:
http://wiki.inkscape.org/wiki/index.php/Fundraising_Ideas
=== Gitlab Migration ===
* General desire is to get it achieved prior to the hackfest
+ The hackfest would be a good opportunity to f2f through the various
followup work-items.
+ But should target getting it done a couple weeks prior, else major
issues could be disruptive of the event.
+ So need to target getting it done in the next week or so.
+ Followup-workitems for post-migration:
- Automating builds
- Fix cmake bzr-isms
- Update builds for windows
- Update builds for mac
- Fix jenkins
- Rewriting inkscape.org to re-document git instead of bzr
* Ted has done some dry runs. The 0.44 branches generate import errors,
but everything else looks happy.
+ Ted wants ~24hr downtime to deal with migration issues, so need to
disable commits for that interim.
+ ACTION: Test the message patch from ML [tedg]
+ ACTION: Announce plan for gitlab migration [tedg]
* plan -- send notice to the list (today?), then 24hr later change
ownership of inkscape.dev's branches or otherwise configure them so
they can't be committed to, run the migration script, do any cleanup,
and if all's well we reopen on gitlab 24 hr after that
+ Branches owned by individuals may need separate attention. People
can continue hosting branches in LP for now, but we might revisit
this later (esp. if/when we wish to close out the Inkscape LP
project.) With gitlab, user branches are kept more separate
(e.g. as forks) but we can import broadly and prune later.
+ Do the migration mid-week, as people seem to use W-E's for devel
* Bug reporting will remain with Launchpad for now.
+ Launchpad's spam problem has been growing...
+ Existing bzr revno references from bug reports will continue to
work, but going forward these will need to start referencing to git
SHA's at gitlab. For now we won't have the easy shortcuts from bug
reports to commits (or vice versa).
+ Non-trivial to import bugs to gitlab.com -- it doesn't permit
setting the bug owners/commenters for one thing.
- might be doable if we ran our own gitlab instance.
- Maybe be acceptable of old bugs/comments are just left owned by
inkscape.dev?
+ ACTION: Discuss scripting ideas for bug migration [Mc, DoctorMo]
+ ACTION: Re-raise topic of bugtracker migration at a future time [Mc]
=== Infrastructure backup/alternate hosting ===
* This effort is in early discussion/planning stage. Bryce and Martin
have been working on it behind the scenes but now ready for some wider
input and thinking.
* Rationale for investigating alternatives:
1. Capacity has been a bit limited with OSUOSL; we've banged our head on
this a few times now.
2. Responsiveness to IT requests has also been pretty slow. Two
infrastructure moves have had to be scuttled/replanned due to
this.
3. Outages occur periodically (generally due to #1 or #2 but
sometimes unrelated).
* Goal is having a primary host, with a second independent host we can
bring up as cold failover in emergencies.
+ Geographically separated, e.g. Europe + Canada/US
+ Backup host would be kept simple - a mirror of the primary that can
be manually switched on as needed.
+ Even if we stick with OSUOSL we still should have another host, just
for best practices in case of failures.
* Current hosting has been 100% sponsor supported. We have budget to
pay for IT support but obviously would prefer sponsor support here.
+ We're not yet ready to start contacting or engaging, but close
=== Funded development project management system ==
* Bryce still plugging away at it
* Manual funding of feature development also possibility
+ This would mainly involve recruiting and vetting developers to take
on one of the already defined and funded projects
+ Also need to track devel progress and completion, and coordinate
payment (via Conservancy)
+ Similar to GSoC but less teaching, and shorter durations
+ ACTION: Help Mc kickoff funded devel of a feature [Bryce]
=== Merchandise Sales ===
* Temporary-run batch T-Shirt sales
+ "Must pass this line, limited sale"
+ Could just use existing logo
+ Need to identify a good quality t-shirt supplier (Cotton Bureau?)
https://cottonbureau.com/submit-a-design
+ ACTION: Propose a batch t-shirt run (e.g. for hackfest) [tedg]
* Spreadshirt
+ On hold, no changes to report
+ Probably time to pick a kickoff date and run with what we have
+ ACTION: Re-contact Mihaela to finish starting up Spreadshirt [doctormon, bryce]
* If anyone wants to take lead on setting up other merchandising
options, contact bryce. We're pretty open to ideas, just need someone
to make arrangements and set up the order/shop/etc.
=== GSoC ===
* Just started this week, first evaluation in a month
* There will be an additional $500 per student for travel costs.
+ Does the board need to be involved in arranging or approving the
expenditures? Probably, since it'll go through conservancy...
+ We'll wait until the issue comes up; board can do a quick enough
vote on it. Contact bryce when you have specifics.
=== How's the Board Doing? ===
* More efficient voting
+ Need quicker turnaround
+ Not all board members are placing votes
+ ACTION: Experiment with first-call / last-call dates on board votes [bryce]
+ ACTION: Check on board member voting [bryce]
* Automation of board work
+ Need tool to upload text files to the website's pastebin
(I.e. to send IRC log snippets of board meetings, w/ metadata)
=== Other Business ===
None
=== Next Meeting ===
Same time & place, July 7th, 2017.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Inkscape-board mailing list
Inkscape-board(a)lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/inkscape-board
----- End forwarded message -----
5 years, 6 months
