Re: [Inkscape-devel] Time to start thinking about a release?
PDF does not support blur, let alone PS. The only workaround you have is to convert blur to bitmap before exporting.
I think inkscape needs a pre-flight dialog then which gives you errors, warnings and messages concerning your export, otherwise the inexperianced user will struggle to understand why blur failed to export, much less how they can get around the issue. CorelDRAW has a rather nice example of a pre-flight dialog for printing.
---------------------------------------- From: "bulia byak" <buliabyak@...400...> Sent: 23 August 2007 23:51 To: "Adib Taraben" <taraben.a@...1512...> Subject: Re: [Inkscape-devel] Time to start thinking about a release?
On 8/23/07, Adib Taraben wrote:
also we need to mark the things that _have to_ go into the release. I do a lot of technical drawings and for me it is absolutely necessary to include the blur into the pdf and ps export formats.
PDF does not support blur, let alone PS. The only workaround you have is to convert blur to bitmap before exporting. We may eventually add an option to do this automatically but I don't think it's particularly high priority because the workaround is easy (just press Alt+B).
On 8/24/07, joel wrote:
PDF does not support blur, let alone PS. The only workaround you have is
to convert blur to bitmap before exporting.
I think inkscape needs a pre-flight dialog then which gives you errors, warnings and messages concerning your export, otherwise the inexperianced user will struggle to understand why blur failed to export, much less how they can get around the issue. CorelDRAW has a rather nice example of a pre-flight dialog for printing.
So has Scribus, and I would prefer having a solution similar to Scribus rather than something proprietary :)
Anyway, let's make a 1st level checklist:
Codebase
- define features that are planned for 0.46 for sure - define features that might go into 0.46
Translations
- make sure all files containing translatable messages are in po/POTFILES.in - define strings freeze period (like 2 weeks) - define most unsupported translations, liase with their authors, if not successful -- ask for help in correspondent translator communities (like GNOME ones) - work with other translators
Documentation
- update tutorials - add missing tutorials - make sure all tutorials are translated
Screenshots
- define features that need to be covered by screenshots - create screenshots
Release Notes
- make sure all new features are covered properly
News
- write news topic - send it to magazins
For this release it would be great having two more things:
1) Developers documentation (updated if required) hosted at inkscape.org 2) Gallery reorganization. I volunteer for this one.
Alexandre
participants (2)
-
Alexandre Prokoudine -
joel＠...1709...