From: SourceForge.net <no...@so...> - 2007-05-03 00:20:58
|
Documentation Feature Requests item #1543985, was opened at 2006-08-21 16:41 Message generated for change (Settings changed) made by frank_kliewe You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=748235&aid=1543985&group_id=25576 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Documentation New Page/Section >Group: For 6.0 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Martijn Verburg (karianna) Assigned to: Nobody/Anonymous (nobody) Summary: [OS File Class] Initial classes Initial Comment: What we are missing are probably lessons that show them in practical use like we do in the LST file classes. There are a few tricks that can be done when using the existing tags creatively and some OS classes might document how to do that. Problem is to find an experienced OS Monkey with time to write them. e.g. The example of: Just saying: You can build that output already. |SPELLMEM.%class.%spellbook.%level.%spell.SCHOOL| will output the spell school. |SUB2.SPELLMEM.%class.%spellbook.%level.%spell.SCHOOL| will give you just the first 2 letters (SUB3 would give the first 3, etc.) and |SPELLMEM.%class.%spellbook.%level.%spell.SUBSCHOOL| is holding the subschools You will have to insert some IIF statements to cater for those schools where you prefer different than the first 2 letters, though. -- Frank ---------------------------------------------------------------------- Comment By: Martijn Verburg (karianna) Date: 2006-10-16 10:59 Message: Logged In: YES user_id=252169 What Frugal typed below would actually be a very good start on the doc for generating a PDF sheet. Could a tracker monkey add this to the FREQ for documenting the PDF sheets? Then maybe a DOC monkey can start on this. Chuck OS Chimp --- In pc...@ya..., "Frugal" <frugal@...> wrote: > > > On Fri, October 13, 2006 12:52 am, Chuck Pint wrote: > > --- In pc...@ya..., "Jay Anderson" <IanQuentin@> wrote: > >> > >> I was curious if there was any documentation that would explain how > >> the PDF output sheets worked. > >> > >> Specifically, I'm looking to have an output sheet where the equipment > >> and weight allowance pieces print on a separate page. > > > > That's a FREQ to do one of these days. It never seems to get a high > > priority. Your best bet is to take a look at fantasy_master_std.xslt > > in the outputsheets\d20\fantasy\pdf directory. The xslt is not too > > hard to follow. > > PCGen will first create an XML character sheet by using the standard > export tokens and the base.xml output sheet. PCGen will then store the XML > character sheet in the tmp directory. It will then run an xslt > transformation with the character sheet you have selected (eg. > csheet_fantasy_std_blue.xslt) to create an XSL:FO document which it then > converts to PDF. > > XSLT links: > http://www.w3.org/TR/xslt > http://www.zvon.org/xxl/XSLTreference/Output/index.html > http://www.zvon.org/xxl/XSLTutorial/Output/index.html > > XSL:FO links: > http://www.w3.org/TR/xsl/ > http://www.zvon.org/xxl/xslfoReference/Output/index.html > http://xmlgraphics.apache.org/fop/ > > When doing a lot of work on the xslt sheets I tend to run pcgen, export a > character to PDF. Take a look in the temp directory (/tmp on unixes, > Documents and Settings\{user}\Local Settings\Temp on windows) There should > be a file something like currentPC_99999.xml. Copy this file to whereever > you are working and then run the FOP process from the commandline. That > way you do not need to have PCGen running to test your sheets, adn each > test does not need to wait for PCGen to export the XML file first. > > 99% of the functionality for the PDF sheets is stored in > fantast_master_std.xslt. The main layout is all at the top of the file, > and the templates for each of the blocks is stored lower down in the file. > Ideally each block should be factored out into it's own file but that is a > completly different task. > > If all you want to do is force a page break before the equipment block > then have a look at the line "<xsl:template match="equipment">". In the > following line add the 'break-before="page"' attribute to the fo:block > element. > > -- > regards, > Frugal > ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=748235&aid=1543985&group_id=25576 |