Multiple Pages Support

it could be also done using the blur filter

What's wrong with the specs approach, think it's quite
logical and straight forward?
I think it makes sense to stick as much to the specs a
possible and I don't see a disadvantage, frankly, exept that
it's harder to insert pages from another document.
The big advantage is to have all the definitions once only.
Or well, can the devs be in an external css, not sure right now?

Another SVG 1.2 enhancements I'd like to see (that is, that I
really need) are solid colors (spot colors etc.) and flow areas.

Multiple pages per sheet would be useful to me too.

I would like as well multipagesupport.
Best of all would be real multipage in one document, with
advantage of having definitions once only.
Evenbetter multipage of different formats with corresponding
pdf export...

1. multipages or single page divided in multiple prints...
2. better pdf/eps/ps/vectorlikelineworks import witch is an
important point for dataexchange

Originator: NO

the link no longer goes to anything specific
http://www.w3.org/TR/SVG12/#multipage
seems like multipage may have been postponed until a later version of SVG

inkview container files already sort of give us support for multipage even
if SVG doesn't offer it yet
if there is much more progress on OpenDocument support that makes another
format needing multipage support.

I expect the user interface for this would consist of tabs at the bottom
of the page, same as how OpenOffice Draw, Microsoft Visio, and Corel Draw.
(Adobe Illustrator doesn't do multipage but there is a third party
extension for it that does.)

I'd love to see multipage support myself.

Although I am not familiar with the inkscape codebase, I wonder if
multipage could be easily achieved by duplicating the code that runs layers
(with a few small changes). At the moment I use layers to do multipage
documents in inkscape - one layer per page. However, it's annoying when I
want to change pages - I have to turn one layer off, then change layers,
then turn the new layer on. It's also annoying when I want to print - I
have to turn on and print each layer individually.

At the moment in XML a layer apparently has this syntax:
<svg:g id="layer1">
It appears to me that inkscape always interprest the highest level svg:g
tags as layers.

What I'm suggesting is that the hightest level svg:g tags be interpreted
as pages, and the second highest svg:g tages be interpreted as layers.
Thus, the syntax would be like this:
<svg:g id="page1">
  <svg:g id="layer1">
  <svg:g id="layer2">
<svg:g id="page2">
  <svg:g id="layer3">

It appears to me that this would allow the copy/paste/insertion/deletion
of new pages with relative ease.

On the user interface front, I suggest a new menu that is exactly the same
as the layer menu, but with the word 'layer' changed to 'page'. And, at
the bottom of the screen next to the layers control, place little box with
the number/name of the current page, and a left and right arrow to navagate
between pages.

I know there is quite a bit of work to make this suggestion reality, but
it seems to me that by re-using the current layers code, which works well,
the effort required is minimised.

Thanks to everyone in the inkscape community for such awesome software.
(timATtimandlizDOTidDOTau)

The support for multiple pages would be a most welcome addition. Every day
I use Inkscape I wonder if it will be added to the next version. Almost all
the documents I make have several pages, and for printing purposes it would
be much simpler to print only one document. Now opening ten and printing
them separately is annoying and also printing on both sides of the paper
time consuming.

<email address hidden>

Originator: NO

If a developer is interested it might be a good idea to get a head start
on this.

OpenDocument Draw includes multiple pages and does PDF and Inkjar files
contain more than one page so Inkscape could probably implement a custom
solution until there is a suitable one to copy from the SVG specification.

[Users will continue to asked for Tabs abso-bloody-lutely everywhere and I
cannot see how that will play friendly with the requirements of a user
interface to show multipage documents but maybe we can get a better
understanding of _WHY_ users keep asking and figure out how the real
problems can be solved.]

Until support for multiple pages reappears in a SVG recommendation I believe this item must be considered incomplete.

Disagree--multipage is still on the inkscape roadmap, and there is useful discussion here about out-of-spec ways of implementing this often-requested feature... Marking wishlist...

Multiple Pages Support is a very important for us.
Can you do it in 0.47?
I read roadmap.... You will plan do it in 0.49.

Multiple pages support need to me too

The exact same syntax is still referred to in new documentation. The current http://www.w3.org/TR/SVG12/ simply is a rather empty placeholder, saying how little will change compared to the previous drafts.

The tags are mentioned at
http://www.w3.org/TR/2007/WD-SVGPrintPrimer12-20071221/#page and it
links to: http://www.w3.org/TR/2004/WD-SVG12-20041027/multipage.html

Multipage-Support is very useful to have and the spec seems stable. So if anyone has the resources, please go for implementing it.

About a month ago on the list, Bulia mentioned this, and using the SVGPrint 1.2 spec:

http://www.nabble.com/Multipage-plan-td16394431.html

From reading this one, it looks like it was moved verbatim from the SVG 1.2 draft.

But that makes sense. Use a non-image container for images, rather than have images with pages. This is similar to how XSL:FO handles pages.

That would be great if you could edit multiple pages like in DIA.
I am using Inkscape for drawing diagrams and when the diagram gets bigger than just one page I'd like to add "new page" next to the current one, but edit them as "one document".

Mac, could you provide a screen-shot how this is implemented in DIA.

Adib.
---

On Thu, Nov 20, 2008 at 11:21 AM, Mac <email address hidden> wrote:
> That would be great if you could edit multiple pages like in DIA.
> I am using Inkscape for drawing diagrams and when the diagram gets bigger than just one page I'd like to add "new page" next to the current one, but edit them as "one document".
>
> --
> Multiple Pages Support - SVG 1.2 Compliance
> https://bugs.launchpad.net/bugs/170369
> You received this bug notification because you are a member of Inkscape
> Bug Team, which is subscribed to Inkscape.
>

 Mac
I wait it 2 years.

I'm just listening to the bug, but here's a screenie.

Thank you, rubik-cube. That's exactly what I am waiting for. Of course, I could use Dia, but I prefer Inkscape much more.
Alexretij, that's not good news you've been waiting for that for such a long time... :(
Do you know what is the probability of implementing it in Inkscape?

You can help make it happen. ("Yes, we can.")

Please go to the blueprint section, add a new topic "mutiple pages
support" or so and fill your expectations.

There should go everything related:
- screen-shots of good examples (I don't see in the Dia screen-shot
how they handle multiple-pages)
- should guides work for all pages,
- should layer be in all pages or only in the one you created a layer
(probably the second)
- should the page format be for all pages the same
- how to save in formats that only support a single page
...
You see what I mean. This would collect all the wishes. Also we can
estimate the need.
And this would drop some load from this bug-report :-)

HTH, Adib.
---

On Wed, Nov 26, 2008 at 9:51 AM, Mac <email address hidden> wrote:
> Thank you, rubik-cube. That's exactly what I am waiting for. Of course, I could use Dia, but I prefer Inkscape much more.
> Alexretij, that's not good news you've been waiting for that for such a long time... :(
> Do you know what is the probability of implementing it in Inkscape?
>
> --
> Multiple Pages Support - SVG 1.2 Compliance
> https://bugs.launchpad.net/bugs/170369
> You received this bug notification because you are a member of Inkscape
> Bug Team, which is subscribed to Inkscape.
>

Hi,

I create new Blueprint. https://blueprints.launchpad.net/inkscape/+spec/mutiple-pages-support/
I don't know how to attach there an example, so I appreciate if someone could help.

Example view of Inkscape supporting multiple print pages is in attachment

screencast mockup proposal...
view: http://vimeo.com/2503097
get 8mb MP4: http://valessiobrito.info/tmp/vimeo.com_2503097.mp4

;)

ValessioBrito
Thank you.
When can I test it on Windows?

three months or three years, depend on more voluntary in the development of the future functionalities.

Part 02, screencast proposal mockup: http://vimeo.com/2511938
get 20mb, MP4: http://valessiobrito.info/tmp/vimeo.com_2511938.mp4

+- like "Multiple-Art Boards" Illustrator CS4:
http://help.adobe.com/en_US/Illustrator/14.0/WS0939CFEE-49EF-4c6f-B337-8897EC89DF89.html
http://www.dailything.com/2008/10/20/new-in-adobe-illustrator-cs4-multiple-art-boards/
http://br.youtube.com/watch?v=UJeHVukZOrw

I am waiting for you work!!!
Thank you.

theAdib wrote on the duplicate bug:

we need to focus on this feature to get this done. I think this is an
important feature for all technical based drawings.

There is a blueprint on this:
http://blueprints.launchpad.net/inkscape/+spec/mutiple-pages-support
and there is a reference page in the wiki:
http://wiki.inkscape.org/wiki/index.php/MultiplePages

those pages are recently created.

HTH, Adib.

This is a related bug with some thoughts on the multiple pages interface (in addition to multiple document tabs).
https://bugs.launchpad.net/inkscape/+bug/170257

All the exporters would need to get extra options in case of implementing multipage, like export all pages or specific range. In case of range >1 the page number would be appended to the filename, if pages=1, there is no need for this.

One not disableable master style would come with no cost at all (root level elements).

I would like to see this also.

Just commenting that multiple page support would be great. For a start, assuming each page size is identical is fine, but if you produced PDF output it would produce multiple PDF pages.

Multiple page support in SVG 1.2 has stagnated. The explanation I got at LGM2010 is that they received too many negative comments. The spec is too complex to do simple things and not complex enough to handle more complicated needs... so it pleased nobody. If people push, Doug Schepers of the SVG working group said that a simplified version could be added to SVG 2.0.

Please work on this. It is very important to use inkscape as an application for taking handwritten notes on a tablet pc.

Tavmjong, how can we "push" so that it gets implemented anytime soon?

Something that haven't been commented in this report is that if multiple pages are implemented, Inkscape could compete as well in the "presentations" field (like PowerPoint alternative): If all pages can be exported as PDF it can be combined with other tools (like http://impressive.sourceforge.net/). There is also a very interesting project about presentations using Inskcape: http://code.google.com/p/jessyink/.
Also, all pages could be exported as APNG, SMIL, etc. to create animations. I think this particular feature could be really useful for many animators and web designers.
I also think that only a simple interface showing "miniature" pages at the bottom (or as a list) can be created to jump from one document to another (simulating pages) in a single window. The only problem is that saving the whole document would generate several files. All files could be stored in a single directory, serialized. In that way, when opening the first file, it could search on the directory for consecutive files and ask if it should be loaded as a "multiple page" document.
My suggestion is to work first on the interface (with the approach which I just explained). Later versions, could implement saving it into a single SVG file.
I also tried this plugin: http://sourceforge.net/projects/inkscape-pages/, but I don't feel that is the approach it should be taken (using layers), which IMHO is not easy to manage.

I said it many times: multiple pages would be an excellent way to helping doing SVG ANIMATIONS.

Currently SVG animations are made saving DIFFERENT SVG frames as individual .svg files, and then using animation libraries like Snap.SVG to play those as frames and creating/blending the in-between frames automatically.

You can see an example of this in this excellent tutorial:
http://tympanus.net/codrops/2013/11/05/animated-svg-icons-with-snap-svg/

It is very painful to make animations using many different svg files, because you cannot compare them in an onion-layering way, or going back and fourth between frames with arrows when editing them. If Inkscape would add multipage support, it would allow to create animations using the pages as frames. For example for 1 second of a button animation you have 30 frames.
Then you just need to add some "key" pages at a certain indexes (es. page/frame 0, 10, 20, 30...). Then export the multipage svg, and import it in your web project. Here Snap.svg would automatically "tween" and interpolate the key frames generating the missing frames by interpolation.

Please add multipage animation support in Inkscape.

Here is an attachment with an image illustrating of a design proposal for the multipage onion skin feature.
You can read more about it in its own entry: https://bugs.launchpad.net/inkscape/+bug/1343411

Reverting bug status change: this is a known, valid and confirmed feature request for Inkscape (independent of the status of support in the current or in future SVG specifications).

The http://sourceforge.net/projects/inkscape-pages/ extension should be bundled with the next release to provide interim support for this.

Even though I`m aware we have scribus for writing books, leaflefts and other printed/web/digital text material I can already envision a lot of people writing books in Inkscape using the multipla pages support and the export do PDF Feature. :)
Keep up the good work everyone.

That feature would be awesome and would also put the first stone for building an animation frame mework into inkscape.

Any news about the spec?

The draft proposal is pretty simple.

 * Improve layers/objects user interface and prepare for page support
 * Implement custom layer type 'page' on group elements
 * Add custom attribute 'page dimensions' on group elements.
 * Enforce translation only transformations for 'page' layers.
 * Enforce one page visible at a time (for now)
 * Clean up 'Move to layer' to include move to page.

That should do for a first draft page support.

What about a fixed size/orientation to all pages in a doc?

All pages would default to having the parent document's size.

Do you mean we should not do page sizes yet?

This seems a feature than complex the proyect and dont be too much useful...

Wait a moment, Maybe we can make a "sprite" export with all pages joined into the less size box posibol in svg and pdf export, this is a cool feature to multiple page size and very useful to web devs.

Maybe we can made two views: first to selected page and the other a "sprite" one.

s/svg and pdf/svg and png

This would not be a feature for 'how to use pages' but how to get pages in the first place. Next stages are pdf import and export, flip books, other items.

Why are pages not useful?

Dont undertand me! Pages are super useful and the last feature is for give +1 to diferent page sizes.

Sorry for my english!

Well, this item is opened since August 2004, and many duplicates have been set in the meantime.
It's, er... more than TWELVE YEARS since this started!

I wonder if someone will ever start developing something.
An optimal, standard-compliant solution is the best, but even a non-optimal, custom solution is better than NO SOLUTION at all.
IMHO :-)

Regards,
Max - Italy

I guess seeing so many years have gone by must indicate how hard this feature would be to implement properly?

I know that these extensions are not a substitute for proper multiple page support. But just in case someone is desperate, they might want to look at these 3 different extensions providing PDF pages (import and export).

http://sourceforge.net/projects/inkscape-pages/

https://github.com/wvengen/inkscape-addons/tree/master/extensions

https://inkscape.org/en/~olibia/%E2%98%85multipage-export-extension
and
https://github.com/olibia/inkscape-multipage-export

Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new
bug tracker on GitLab, and closed it here.

Please feel free to file new bugs about the issues you're seeing at
http://inkscape.org/report.

Moved to: https://gitlab.com/inkscape/inbox/issues/362
Closed by: https://gitlab.com/doctormo