Thanks to the quick reply i'll try to implement it, but i have also other work to do...
soon (or later) you will hear about it.
Christian Riggenbach
Am Mittwoch 26 März 2008 01.42:03 schrieb Dan McMahill:
> Christian Riggenbach wrote:
> > Hi list
> >
> > What about to export a whole hirarchy of schemas in gschem and get a
> > linked (aka clickable) PDF? It's a bit nasty to print every single scheet
> > at once and then get them someway together.
> >
> > i'm not at all experienced with PDF or PS, so i ask this list.
>
> I've not looked at how to exactly get this into gschem (in particular
> the computation of the bounding box for instances and detection of a
> source= attribute), but here is generically what you need to do.
>
>
> On each schematic page, add a line in the corresponding postscript file
> like:
>
> [/Dest /MyUniquePerPageName /DEST pdfmark
>
> where "MyUniquePerPageName" needs to be a name for this page. Something
> based on the filename is probably good. Maybe "/gaf_schematic:filename".
>
> This gives that page a symbolic name.
>
> Then for each instance that has a source= attribute (in otherwords,
> there is an associated underlying schematic), you add a line like this:
>
> [/Rect [llx lly urx ury] /Border [0 0 0] /Dest
> /UniqueNameForTheInstanceMaster /View [/Fit] /Subtype /Link /ANN pdfmark
>
>
> where you replace the UniqueName... bit with the destination name for
> the schematic for the internals of the instance in question. The
> bounding box for the instance is used to fill in the [llx lly urx ury]
> bit in postscript coordinates. This creates a hyperlink for the area
> specified by the bounding box that links to the particular page.
>
> Now concatenate all your indivudual postscript files into one and run
> ps2pdf and presto, you'll have your hyperlinked pdf file.
>
> Bonus points if you create a text index that lists all schematics
> alphabetically and includes hyperlinks there too. Again, not hard, you
> just now need to find bounding boxes of postscript text.
>
> Bonus points if you can teach gschem to produce a set of postscript
> schematics along with a LaTeX file that pulls them all in and labels
> them with something like \label{gschem:filename} for easy inclusion in a
> document schematic appendix. Then you could do stuff like
>
> Figure \ref{gschem:sch1} shows the schematic for the blah blah blah...
>
> This probably isn't a job for a whole summer but it would still be
> really cool to have and could be part of a project.
>
> Go to the adobe web site. They have developer documentation available
> for PDF and have a document which fully documents this 'pdfmark' stuff.
>
> Hope this helps
> -Dan
--
mit freundlichen Grüssen
Christian Riggenbach
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
