Edgewall Software
Modify

Opened 19 years ago

Closed 17 years ago

#2207 closed enhancement (wontfix)

export all wiki content in a single printable file

Reported by: ltlennon (ltlennon@… Owned by: Jonas Borgström
Priority: normal Milestone:
Component: general Version:
Severity: minor Keywords: export wiki document
Cc: tapted@… Branch:
Release Notes:
API Changes:
Internal Changes:

Description

Wiki is awesome to make project documents, but eventually it is needed to print all documentation. It would be awesome is there was an export that would take all content of all pages and make a single file, like pdf or other format.
Perhaps it could be made so that the content is considered like a tree, where the pages are nodes and links point to other nodes.
I know that we don´t work with it as a tree when we use it to document, but perhaps it could export as one, so when a node goes 'back' to an upper level of the tree, it won´t be 'exported' again.
Also, it would be awesome if, when exporting, a sumary could be created, where each link is an entry in the sumary, so we can easily find each part of the document on the printed document.

This ticket is similar to #1468 , but here the format doesnt really matter and the request here is to make all content exported on one file.

Attachments (0)

Change History (9)

comment:1 by anonymous, 18 years ago

Milestone: 0.9.1

comment:2 by Matthew Good, 18 years ago

Milestone: 0.9.1

This is not going to happen for 0.9.1. This request really needs some more feedback about the organization of this document in order to address it. What is a logical way to structure a bunch of Wiki pages into a single document?

comment:3 by ericanderton@…, 18 years ago

Milestone: 0.9.3
Version: 0.8.4

One suggestion from this fly on the wall: If a single-file is not implementable (how would you represent/flag the start and end of a page), then why not a single .zip file of the entire wiki, instead? It could simply contain a dump of all the flat-text wiki files in the tree, without any formatting at all. That way, third-party tools can be relied upon for converting the .zip contents into a usable document in a perferred format. For what its worth, here's my $0.02 for a more generic solution than PDF export: For online doc management, a project needs version-appropriate documentation for any Trac project; especially if the version in development changes things dramatically. Providing wiki docs offline as a snapshot (via this proposed feature) is a much better solution than letting that version's docs get overwritten by the current work in development. To that end, this would also open the door to taking such an export and plugging it into a second wiki, if that's desired. Thank you for your time, and reading all this.

comment:4 by Christopher Lenz, 18 years ago

Milestone: 0.9.3

I don't see why you can't do that using the existing wiki dump command in trac-admin. Anyway, please don't target an enhancement like this at a bugfix milestone that is due in a couple of days :-P

comment:5 by Trent Apted <tapted@…>, 18 years ago

Cc: tapted@… added

See also ticket #2296 (export to LaTeX + pdflatex = much nicer PDF)

comment:6 by Christian Boos, 17 years ago

#4282 was marked as duplicate.

This is most certainly a candidate for a plugin (or an external tool).

Doesn't such a plugin already exist, btw?

comment:7 by sid, 17 years ago

Yep, check out CombineWikiPlugin.

comment:8 by sid, 17 years ago

Proposing to close as external ;) or worksforme

comment:9 by Christian Boos, 17 years ago

Resolution: wontfix
Status: newclosed

Didn't you propose wontfix for this case? point (2) (I tend to agree).

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain Jonas Borgström.
The resolution will be deleted. Next status will be 'reopened'.
to The owner will be changed from Jonas Borgström to the specified user.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.