Hello,
I've just used the CVS version of inkscape from this AM to print to postscript file using postscript elements and it works fine for the SVG elements, but not for the .png or .tif or .jpg bitmaps included in an inkscape document.
Has this worked in the past? If not, should I write this up as a bug report, or as a feature request on the wiki?
Even without adding inclusion of bitmaps, Inkscape plus Scribus is a like-the-pros-use set of layout tools, and with plugins planned will outstrip those easily. Thanks for free publishing your efforts.
Who is working on writing docs? I can help there.
JG
On Wed, 7 Jan 2004, John Griessen wrote:
Hello,
I've just used the CVS version of inkscape from this AM to print to postscript file using postscript elements and it works fine for the SVG elements, but not for the .png or .tif or .jpg bitmaps included in an inkscape document.
Has this worked in the past? If not, should I write this up as a bug report, or as a feature request on the wiki?
Postscript has generally always been rather incomplete. People have reported problems with alpha channel, document boundaries not coming through correctly, and etc. I don't recall a report on problems with included rasters but you could check the tracker to be sure. In any case, yes please submit a bug report, and be sure to include everything needed to easily replicate the problem.
Even without adding inclusion of bitmaps, Inkscape plus Scribus is a like-the-pros-use set of layout tools, and with plugins planned will outstrip those easily. Thanks for free publishing your efforts.
Cool, thanks!
Who is working on writing docs? I can help there.
Several people are working on different kinds of documents. There's a user guide written originally for Sodipodi in French; I found that with Babblefish's help a non-French speaker with familiarity with Inkscape can translate reasonably quickly. This is probably the biggest task we need doc help on. This is in the 'manual' module in CVS. Would you be interested in taking this task on?
Tutorials are also in demand, especially for some of the newer features. So someone to just follow recent feature additions and write up explanations for users of how to put the features to use would be very handy. These tutorials can later feed into the user manual, where appropriate.
We also need help with code-level and architectural docs, but those will require knowledge of C and some experience with the codebase. If you're interested lemme know and I'll elaborate.
If you have knowledge of languages other than English, we also need translation assistance for the app itself. I'll give more details if there's interest.
Bryce
participants (2)
-
Bryce Harrington -
John Griessen