From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Thread: 103376,666bab5bfbdf30c2
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,UTF8
Path: 
 g2news2.google.com!news4.google.com!proxad.net!feeder1-2.proxad.net!194.25.134.126.MISMATCH!newsfeed01.sul.t-online.de!newsfeed00.sul.t-online.de!t-online.de!npeer.de.kpn-eurorings.net!npeer-ng0.de.kpn-eurorings.net!newsfeed.arcor.de!newsspool2.arcor-online.net!news.arcor.de.POSTED!not-for-mail
Date: Mon, 10 Jan 2011 11:19:01 +0100
From: Georg Bauhaus <rm.dash-bauhaus@futureapps.de>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US;
 rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
Newsgroups: comp.lang.ada
Subject: Re: Generating PDFs with Ada
References: <4d2908c7$0$22120$742ec2ed@news.sonic.net>
 <4D297FED.8080201@obry.net> <82vd1x330z.fsf@stephe-leake.org>
 <op.vo2p6nipule2fv@garhos>
In-Reply-To: <op.vo2p6nipule2fv@garhos>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Message-ID: <4d2add0f$0$6884$9b4e6d93@newsspool2.arcor-online.net>
Organization: Arcor
NNTP-Posting-Date: 10 Jan 2011 11:18:55 CET
NNTP-Posting-Host: ea686a9a.newsspool2.arcor-online.net
X-Trace: 
 DXC=97X3M@3G\GaFXUDVUnEXQmA9EHlD;3Ycb4Fo<]lROoRa8kF<OcfhCOkJWT34[li>Rcnc\616M64>jLh>_cHTX3jmlYGfhEQ9fIk
X-Complaints-To: usenet-abuse@arcor.de
Xref: g2news2.google.com comp.lang.ada:17323
Date: 2011-01-10T11:18:55+01:00
List-Id: <comp.lang.ada>

On 10.01.11 04:48, Yannick Duchêne (Hibou57) wrote:
> Le Mon, 10 Jan 2011 03:29:00 +0100, Stephen Leake
> <stephen_leake@stephe-leake.org> a écrit:
>> I considered that path once for building better PDF versions of the Ada
>> language reference manual. I concluded it was not any easier than
>> generating the PDF in the first place.
>>
>> I suppose it depends on how complex your document is.
> Also I feel LaTeX and its typical utilities are not that much Unicode ready
> (although Unicode is already 20 years old exactly this year). Writing PDF at
> the first place is better for that reason at least.

Another approach is to rely on existing standards and tools:
produce input suitable for PDF rendering via XSL FO.
Control the process from within your Ada program.

OK, that's less sexy than writing NIH software.