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,FREEMAIL_FROM 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!news1.google.com!goblin1!goblin2!goblin.stu.neva.ru!aioe.org!not-for-mail From: =?utf-8?Q?Yannick_Duch=C3=AAne_=28Hibou57?= =?utf-8?Q?=29?= Newsgroups: comp.lang.ada Subject: Re: Generating PDFs with Ada Date: Sun, 16 Jan 2011 22:05:28 +0100 Organization: Ada @ Home Message-ID: References: <4d2908c7$0$22120$742ec2ed@news.sonic.net> <9f23e50a-2c2c-4ccc-bd56-f6ffdc6c7ee7@37g2000prx.googlegroups.com> <82aaj73jsr.fsf@stephe-leake.org> <7a048419-1126-45b2-bfa9-26f3ad6e480e@fu15g2000vbb.googlegroups.com> NNTP-Posting-Host: 8YsgJzdbsnaSVMKLcUWmzQ.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes Content-Transfer-Encoding: Quoted-Printable X-Complaints-To: abuse@aioe.org X-Notice: Filtered by postfilter v. 0.8.2 User-Agent: Opera Mail/11.00 (Win32) Xref: g2news2.google.com comp.lang.ada:17434 Date: 2011-01-16T22:05:28+01:00 List-Id: Le Sun, 16 Jan 2011 16:33:25 +0100, Simon Wright a = = =C3=A9crit: >> A hierarchy of text segments (chapter, paragraph etc) is a possible = >> view of >> the document, of which importance is quite minor and becoming more an= d = >> more >> negligible, because documents are never read sequentially. Document i= s = >> not >> a fiction novel. The structure of pages is also a view, a harmful vie= w, >> because pages have nothing to do either with the content or with the >> rendering on the display. > > Well, you've lost me there. If you had to write something on networkin= g > issues (I say 'something' because if you're going to chuck out book, > chapter, paragraph etc you might as well go the whole hog and chuck ou= t > document too :) how would you structure it? Pascal or Ludovic introduced DITA in this topic. May be he would like th= is = one ;) This one use multiple part to be later merged together (the merge= = may be done in multiple way, simultaneously), while DocBook create a = monolithic document the first time. I suppose what Dmitry was to notice, has more to deal with *premature = formating*, just like there is premature optmization, than with Book and= = Page used as paradigm to talk about the structure of a document. What to use depends on the area. Think about a software design, you have= = comments in the source, some documentation fragment on the topic of the = = application and its area. How could you create a single document from th= is = ? There is no way. You would better consider all of these to be standalo= ne = document fragments, then do an assemblage of these fragments targeting = users, another targeting the maintainers, another targeting document use= d = to promote the application, and so on. Obviously, you need something common to these fragment, something which = = make these to know about each other when required and be able to merged = = these together, to know what kind of fragment is this, how it relate to = = other. That is what DITA is for (and RDF may be useful too here). Now think about some movie review, there is less something like = independent fragments here, and you may prefer DocBook instead (DITA is = = likely to be useless at all here). Note 1: DITA may produce DocBook, these are not opposite. Note 2: I said DITA and DocBook, while this may be any other systems of = = conventions with the same functionalities (as an example, DocBook is kno= wn = to be too much for some applications, the same about DITA). -- = Si les chats miaulent et font autant de vocalises bizarres, c=E2=80=99es= t pas pour = les chiens. =E2=80=9CI am fluent in ASCII=E2=80=9D [Warren 2010]