Hi - this is my first posting on this site so please excuse my ignorance!
Our company is developing a structured authoring tool based on a wiki platform. The wiki platform is Deki Wiki. Deki wiki encodes content as XHTML - not in some obscure wiki markup language.
Like many wikis, Deki Wiki supports tranclusion, which is the ability to insert content from one page into another. Using transclusion we are able to assemble topics into a book-like structure of any length, with Parts, Chapter and Sections.
Currently Deki Wiki has the ability to print / save the output as pdf. The problem is the the output looks lousy - i.e. no page breaks based on paper size, no table of contents (based on page hierarchy, not on html headers).
From what I gather, Prince is the only product capable of understanding the CSS rules required for printed output. Is this correct? Does our application sound like something Prince can handle?
Our company is developing a structured authoring tool based on a wiki platform. The wiki platform is Deki Wiki. Deki wiki encodes content as XHTML - not in some obscure wiki markup language.
Like many wikis, Deki Wiki supports tranclusion, which is the ability to insert content from one page into another. Using transclusion we are able to assemble topics into a book-like structure of any length, with Parts, Chapter and Sections.
Currently Deki Wiki has the ability to print / save the output as pdf. The problem is the the output looks lousy - i.e. no page breaks based on paper size, no table of contents (based on page hierarchy, not on html headers).
From what I gather, Prince is the only product capable of understanding the CSS rules required for printed output. Is this correct? Does our application sound like something Prince can handle?
