New Acknowldegement for RenderX
Since we seem to be using this to generate pdf version at the end of the toolchain from Quickbook/Docbook thru XML to html and pdf XML to PDF by RenderX XEP XSL-FO Formatter, visit us at http://www.renderx.com/ I think it would be grateful to add an acknowledgement, perhaps to http://www.boost.org/status/compiler_status.html perhaps this text: <quote> [@http://www.renderx.com/ RenderX, Inc.] have kindly provided copies of their [@http://www.renderx.com/download/personal.html Personal Edition] of the XML to PDF by RenderX XEP XSL-FO Formatter (engine XEP.exe) to documentation writers. </quote> (In addition, you may notice a very discreet ad at the bottom of each pdf page. XML to PDF by RenderX XEP XSL-FO Formatter, visit us at http://www.renderx.com/ ) Perhaps someone would like to update this page? Thanks Paul --- Paul A Bristow Prizet Farmhouse, Kendal, Cumbria UK LA8 8AB +44 1539561830 & SMS, Mobile +44 7714 330204 & SMS pbristow@hetp.u-net.com
Paul A Bristow wrote:
Since we seem to be using this to generate pdf version at the end of the toolchain from Quickbook/Docbook thru XML to html and pdf
XML to PDF by RenderX XEP XSL-FO Formatter, visit us at http://www.renderx.com/
I think it would be grateful to add an acknowledgement, perhaps to
http://www.boost.org/status/compiler_status.html
perhaps this text: <quote>
[@http://www.renderx.com/ RenderX, Inc.]
have kindly provided copies of their
[@http://www.renderx.com/download/personal.html Personal Edition]
of the XML to PDF by RenderX XEP XSL-FO Formatter (engine XEP.exe) to documentation writers.
</quote>
At the risk of being curmudgeonly, I'm not sure I agree with this - the folks who have acknowledgements there currently all provided free copies of their compilers (that were/are not generally available) to aid with Boost testing. RenderX hasn't actually given us anything that isn't freely downloadable anyway. If they let us have a copy of the commercial version of the product - so we could produce advert free docs - that would be a different issue. Just my 2c worth... John.
-----Original Message----- From: boost-bounces@lists.boost.org [mailto:boost-bounces@lists.boost.org] On Behalf Of John Maddock Sent: 17 August 2007 13:20 To: boost@lists.boost.org Cc: 'Discussion of Boost Documentation' Subject: Re: [boost] New Acknowldegement for RenderX
Paul A Bristow wrote:
Since we seem to be using this to generate pdf version at the end of the toolchain from Quickbook/Docbook thru XML to html and pdf
XML to PDF by RenderX XEP XSL-FO Formatter, visit us at http://www.renderx.com/
I think it would be grateful to add an acknowledgement, perhaps to
At the risk of being curmudgeonly, I'm not sure I agree with this - the folks who have acknowledgements there currently all provided free copies of their compilers (that were/are not generally available) to aid with Boost testing. RenderX hasn't actually given us anything that isn't freely downloadable anyway. If they let us have a copy of the commercial version of the product - so we could produce advert free docs - that would be a different issue.
Well I'd be the last to accuse you of curmudgeonly-ness ;-) But I think we could not reasonablely expect them to dish out a free copy to every single Boost developer - and yet that's what we all need (to check what a pdf version of their stuff will look like) - and what we have effectively got. So on the grounds that it costs nothing to say thanks, I still feel it's the right thing to do. Paul --- Paul A Bristow Prizet Farmhouse, Kendal, Cumbria UK LA8 8AB +44 1539561830 & SMS, Mobile +44 7714 330204 & SMS pbristow@hetp.u-net.com
On Aug 17, 2007, at 11:23 AM, Paul A Bristow wrote:
But I think we could not reasonablely expect them to dish out a free copy to every single Boost developer - and yet that's what we all need (to check what a pdf version of their stuff will look like) - and what we have effectively got.
Unless we had a central place where we built Boost PDF documentation. Ideally, we'd have an automated (nightly?) process that built Boost documentation in PDF and HTML. MetaComm is (was?) building the HTML; we'd just need one license to build the PDF.
So on the grounds that it costs nothing to say thanks, I still feel it's the right thing to do.
Makes it harder it ask for that one copy to build PDFs of Boost documentation, if we've already given them the publicity in a public acknowledgment. - Doug
Paul A Bristow wrote:
Since we seem to be using this to generate pdf version at the end of the toolchain from Quickbook/Docbook thru XML to html and pdf
XML to PDF by RenderX XEP XSL-FO Formatter, visit us at http://www.renderx.com/
Hopefully boost will not rule out other ways of generating the docs. I think vendor lock in is the last boost should be trapped into. Just my opinion... Roland aka speedsnail
On Sat, 2007-08-18 at 17:14 +0200, Roland Schwarz wrote:
Paul A Bristow wrote:
Since we seem to be using this to generate pdf version at the end of the toolchain from Quickbook/Docbook thru XML to html and pdf
XML to PDF by RenderX XEP XSL-FO Formatter, visit us at http://www.renderx.com/
Hopefully boost will not rule out other ways of generating the docs. I think vendor lock in is the last boost should be trapped into.
XSL-FO is an open standard, and RenderX provides an implementation of that standard. We're always free to pick another vendor that implements the same standard but, frankly, RenderX does the best job of the tools I've seen. - Doug
Douglas Gregor wrote:
On Sat, 2007-08-18 at 17:14 +0200, Roland Schwarz wrote:
Paul A Bristow wrote:
Since we seem to be using this to generate pdf version at the end of the toolchain from Quickbook/Docbook thru XML to html and pdf
XML to PDF by RenderX XEP XSL-FO Formatter, visit us at http://www.renderx.com/
Hopefully boost will not rule out other ways of generating the docs. I think vendor lock in is the last boost should be trapped into.
XSL-FO is an open standard, and RenderX provides an implementation of that standard. We're always free to pick another vendor that implements the same standard but, frankly, RenderX does the best job of the tools I've seen.
Correct: and just to emphasise the point, the Open Source alternative - Apache FOP - and XEP are command line compatible, so you can use either just by altering the "using fop" line of your user-config.jam. Sadly Apache FOP currently has so many problems that it's hard to recommend for anything but simple usage requirements at present, hence the use of XEP for more complex documents. John.
participants (5)
-
Doug Gregor -
Douglas Gregor -
John Maddock -
Paul A Bristow -
Roland Schwarz