Extension Pages not implemented

Hi Richard,

what is the extension 'Pages'?
What does it do?
Who develops it?
Do you have a link for us?

Kind regards,
 Maren

The extension is known (the author did contribute a few patches to inkscape for the extension system in general, partially to ease developing that custom extension):
http://sourceforge.net/projects/inkscape-pages/

The 'inkscape-pages' extension mimics a feature not supported natively by SVG 1.1 by implementing a custom management of Inkscape layers (another custom Inkscape feature), and managing this via script-based extension(s). Even with moderately complex documents, the current extension system is too slow to handle this (performance-wise). Output to multi-page PDF files requires external tools to be installed on the local system which are not shipped with Inkscape packages for Windows and OS X.

The feature request is well known in Inkscape (tracked in bug #170369). Attempts to get this as native SVG feature included in the requirements for the next version of the SVG specification (SVG 2.0) have not been successful AFAIK. A proprietary implementation of such a feature in Inkscape (multi-page Inkscape SVG documents, with internal support for common export formats like PDF, maybe even TIFF) IMvHO should be implemented internally, not as script-based extension (Inkscape would have to provide at least fallbacks (possibly via <switch> elements) and conversion routines to SVG 1.1 in order to support viewing such files in other SVG renderers).

This question was expired because it remained in the 'Needs information' state without activity for the last 15 days.

Hi Hachmann
Sorry for not answering sooner.
See the following Page to get more information:Inkscape multiple pages support

|   |
|   |   |   |   |   |
| Inkscape multiple pages support Inkscape multiple pages support download. Inkscape multiple pages support 2013-04-17 21:12:26 free download. Inkscape multiple pages support Inkscape has now pages support. You can create a multiple page document using Inkscape, just like in Corel Draw. Install this extension, ... |
| |
| Auf sourceforge.net anzeigen  | Vorschau nach Yahoo |
| |
|   |

Kind regards,Richard

      Von: Hachmann <email address hidden>
 An: <email address hidden>
 Gesendet: 2:02 Mittwoch, 2.September 2015
 Betreff: Re: [Question #270994]: Extension Pages not implemented

Your question #270994 on Inkscape changed:
https://answers.launchpad.net/inkscape/+question/270994

    Status: Open => Needs information

Hachmann requested more information:
Hi Richard,

what is the extension 'Pages'?
What does it do?
Who develops it?
Do you have a link for us?

Kind regards,
 Maren

--
To answer this request for more information, you can either reply to
this email or enter your reply at the following page:
https://answers.launchpad.net/inkscape/+question/270994

You received this question notification because you asked the question.

Thank your for your useful information. My technical background is not that good to understand the word "fallback" but otherwise I think I understood what you wrote.Thank youRichard

      Von: ~suv <email address hidden>
 An: <email address hidden>
 Gesendet: 10:31 Mittwoch, 2.September 2015
 Betreff: Re: [Question #270994]: Extension Pages not implemented

Your question #270994 on Inkscape changed:
https://answers.launchpad.net/inkscape/+question/270994

~suv posted a new comment:
The extension is known (the author did contribute a few patches to inkscape for the extension system in general, partially to ease developing that custom extension):
http://sourceforge.net/projects/inkscape-pages/

The 'inkscape-pages' extension mimics a feature not supported natively
by SVG 1.1 by implementing a custom management of Inkscape layers
(another custom Inkscape feature), and managing this via script-based
extension(s). Even with moderately complex documents, the current
extension system is too slow to handle this (performance-wise). Output
to multi-page PDF files requires external tools to be installed on the
local system which are not shipped with Inkscape packages for Windows
and OS X.

The feature request is well known in Inkscape (tracked in bug #170369).
Attempts to get this as native SVG feature included in the requirements
for the next version of the SVG specification (SVG 2.0) have not been
successful AFAIK. A proprietary implementation of such a feature in
Inkscape (multi-page Inkscape SVG documents, with internal support for
common export formats like PDF, maybe even TIFF) IMvHO should be
implemented internally, not as script-based extension (Inkscape would
have to provide at least fallbacks (possibly via <switch> elements) and
conversion routines to SVG 1.1 in order to support viewing such files in
other SVG renderers).

--
You received this question notification because you asked the question.

On 2015-09-17 22:42 (+0200), Richard wrote:
> My technical background is not that good to understand the word
> "fallback"

Example: assume you create a document with 5 pages (based on a custom Inkscape feature, added on-top of the "regular" SVG structure of the file). Inkscape likely would implement features to edit this file page-wise, offer a layout and/or print preview feature, quick navigation between pages, and maybe even advanced topics like master pages, and printing.

The file would be saved as usual, in Inkscape's default file format (SVG).

Now assume you want to view (or share) the SVG file with another SVG viewer (e.g. any modern web browser): how would that viewer be able to display all pages? Since a browser would not be aware of whatever custom features Inkscape has implemented on-top of SVG, it would not know what to display - worst case would be all pages rendered fully visible on-top of each other, or maybe a completely empty document. Another interesting question would be what happens if you attempt to print this document e.g. from the browser ...

Fallbacks would mean that Inkscape includes elements in the SVG file which define how individual pages would be rendered in a viewer other than Inkscape (or in any SVG viewer which has no support for Inkscape's custom extensions of the SVG file format to support multi-page documents) - e.g. each page with a vertical offset of the page height, so that the full content could be viewed by scrolling a "long" document, or with a horizontal offset of the page width, and a margin. In Inkscape, these alternative views (fallback) would be hidden, and only updated if the page structure changes.

This question was expired because it remained in the 'Open' state without activity for the last 15 days.