This is the mail archive of the
mailing list for the libstdc++ project.
[Tom Browder] Re: libstdc++ Manual in pdf?
- From: Ian Lance Taylor <iant at google dot com>
- To: libstdc++ at gcc dot gnu dot org
- Date: Thu, 09 Sep 2010 09:38:34 -0700
- Subject: [Tom Browder] Re: libstdc++ Manual in pdf?
What's up with this? We use non-free software to generate the PDF
version of the libstdc++ manual?
--- Begin Message ---
- From: Tom Browder <tom dot browder at gmail dot com>
- To: Ian Lance Taylor <iant at google dot com>
- Cc: gcc-help at gcc dot gnu dot org
- Date: Thu, 9 Sep 2010 09:12:17 -0500
- Subject: Re: libstdc++ Manual in pdf?
- Authentication-results: mx.google.com; spf=pass (google.com: domain of firstname.lastname@example.org designates 220.127.116.11 as permitted sender) email@example.com; dkim=pass (test mode) firstname.lastname@example.org
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=JESqudfzXI6X596avrGhsfiG5S0HNLG0KHaOL16Gjc0=; b=xQBbbJSSAlBWHxIDOjnwruBTMdYAiT/tYLtdnwCVTLg/gNMC4K69rhE6FBrI+mRx6U UPEHHJ5nooeSeR/muRwAiGarryVGk9P8sqfpqOGKM+nXlv/cw85ual8WgwCacush/Ky3 pqUepLGGYm7EdY10J85L/SF4kkYLQyQTm3ljU=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=sLJaehQDESyz3trfmQoF6SkVuEk3+dw3QNE2x8BEPZc9BS3XBSy2S3b4SvGuHNFb+v T/vaBHvNQKki3vE+kZT6662OzYWc8Ll7mmKNunzSDwaVEuxR3BnaktbmQt6hgsu91Tyu BUZ47L/xXUSZxH5hZHeUbuN2PzDyce9PZmDRI=
- References: <AANLkTi=M4WgU89bUwRtred69XVfk+pYqe9FfwdErWq2w@mail.gmail.com> <email@example.com>
- Xref: coign mail.misc:494072
On Tue, Sep 7, 2010 at 19:46, Ian Lance Taylor <firstname.lastname@example.org> wrote:
> Tom Browder <email@example.com> writes:
>> Does anyone know if the libstdc++ manual is available in pdf?
>> I see the xml sources for docbook, but I haven't found a pdf output
>> yet. ÂAnd I'm not sure it's configured to be built.
>> Someone has some missing pieces because the html is generated by
>> docbook from the xml.
Not docbook, prince (http://www.princexml.com/).
>> Is that product something that needs a volunteer to make happen in the
>> gcc build system?
Looks like the prince license may be one of the limiting factors (see below).
> You should be able to build it by running "make doc-pdf" in the
> TARGET/libstdc++-v3 build directory. ÂYou need to have some program
> called "prince" installed; I'm not sure where that comes from.
"prince" is not open source, but a commercial xml/html processor that
seems to allow open source projects a non-paid license. From the
prince web site (http://www.princexml.com/license/):
1.1 Non-commercial license
If this is a Non-commercial license, Licensee may download, install
and use the Software for Non-commercial Purposes on a computer that is
accessible to any number of end users. PDF documents generated by the
Software include notices that identify the Software. Licensee shall
not change or remove these notices or assist or encourage third
parties to remove or change such notices.
When the Non-commercial license is used to routinely generate
documents, a prominent link to the www.princexml.com Web site shall be
displayed on the pages from where the generated documents can be
fetched, and in a prominent Web page where business partners are
listed. If PDF documents are sent as email attachments by Licensee,
all email messages must contain the www.princexml.com Web address in
the message body.
Sounds to me like converting the libstdc++ doc build process to use
DocBook 5 and Apache Fop (both open source projects) would be a good
thing and enable the libstdc++ docs to be displayed with all the other
Thomas M. Browder, Jr.
--- End Message ---