Personally I don't like the font used in the text parts and the lack of 
page-breaks.
Also the class object "pictures" is to low-res compared to the running text.
Maybe I have read to many IBM manuals, that has an easy reading font and 
mostly,  page-breaks at a suitable place.
/hex


-------------------------
Ursprungligt Meddelande:
Från: David Ashley <[email protected]>
Till: Open Object Rexx Developer Mailing List 
<[email protected]>
Kopia: 
Datum: tisdag, 07 augusti 2012 23:02
Ämne: Re: [Oorexx-devel] Possible Documentation Change
I have refreshed the documents on the Build Server. I created a new
brand so now the doc references the correct license. I think this is
pretty close to as finished as I can make it.

As to the formatting issues, the Publican system uses CSS formatting. As
you may or may not know CSS is very weak in formatting multi-page output
for PDF documents. This because it primary use is for HTML pages which
have no multi-page concerns. The result can be some odd page breaks in
your PDF outout. There is not much you can do about this and anything
you do will probably make the situation worse either now or in the
future. But for the most part we can live with these issues as long as
the content does not go missing completely.

David Ashley

On Tue, 2012-08-07 at 20:41 +0100, Jeremy Nicoll - ml sourceforge wrote:
> David Ashley <[email protected]> wrote:
> 
> > The document looks outstanding!
> 
> It's certainly polished, in places.  I just looked at some pages at random
> though and found one problem, where the shaded box around a syntax diagram
> straddles a page break - for 5.18 SockRecv at the foot of page 24.
> 
> Similarly (though not as bad) see "7.2.16 state" at the foot of p55. 
> 
> And at the foot of p36 there's a "where" that's not connected with the text
> it introduces.
> 
> 
> I've never used XML or DocBook, but did long ago use IBM's DCF/Script
> package, writing macros for quite complex 3-pass processing of documents
> (where the macros did different things on different passes).  Script had
> control words (dot commands) for bracketing sections of text that should not
> be broken up, and others eg to force a page break if there was insufficient
> space at the foot of one page to start a new section of a document.  (These
> things only got used if one wrote macros that issued them with appropriate
> arguments in appropriate places.)
> 
> The output from this system looks a lot like it's created nice looking text
> but just poured it onto a series of pages without taking page-breaks into
> account.
> 
> 



------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Oorexx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Oorexx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Reply via email to