On Monday 13 February 2006 21:54, Sven wrote:
> Hi there,
>
> again a short question: The FAQ is telling that using
> white-space-collapse="false" in a <fo:block/> is all you need to
> output preformatted text. Well, not for me. Whitespaces will still
> collapse. I am using the latest trunk (revision 377250). Am I doing
> something worng or is this a bug?
>
It's a known bug. Especially leading white space, that is white space at 
the beginning of each line is incorrectly removed.

It is documented, but not very prominently, in the release notes where 
there is a line saying:

#  There are several small problems around white space handling. 

One could argue that this not a really a 'small' problem :-).

> Thank you guys for your pretty good work. I would have never imagined
> to use trunk code in such a prolific way (to write my diploma thesis
> especially =)
>
>
> Here is a brief example:
>
> <?xml version="1.0" encoding="utf-8"?>
> <fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format";>
>     <fo:layout-master-set>
>         <fo:simple-page-master margin="4.5cm" page-width="21cm"
>             page-height="29.7cm" master-name="titlepage">
>             <fo:region-body />
>         </fo:simple-page-master>
>         <fo:simple-page-master margin="2.5cm" page-width="21cm"
>             page-height="29.7cm" master-name="default">
>             <fo:region-body margin-bottom="1cm" margin-top="1cm" />
>             <fo:region-before extent="1cm" />
>             <fo:region-after extent="1cm" />
>         </fo:simple-page-master>
>     </fo:layout-master-set>
>
>     <fo:page-sequence language="de" master-reference="default">
>         <fo:static-content flow-name="xsl-region-before">
>             <fo:block page-break-after="avoid"
>                 border-bottom="solid 1px silver" text-align="end"
> font-size="10pt"
>                 font-family="Helvetica">
>                 Grundlagen
>             </fo:block>
>         </fo:static-content>
>         <fo:static-content flow-name="xsl-region-after">
>             <fo:block font-size="12pt" font-family="Helvetica">
>                 <fo:page-number />
>             </fo:block>
>         </fo:static-content>
>         <fo:static-content flow-name="xsl-footnote-separator">
>             <fo:block>
>                 <fo:leader leader-length="100px"
> leader-pattern="rule" /> </fo:block>
>         </fo:static-content>
>         <fo:flow flow-name="xsl-region-body">
>
>             <fo:block hyphenation-remain-character-count="4"
>                 hyphenate="false" space-after="0.5em"
> text-align="justify" font-size="12pt" font-family="Times">
>                 Die JADE Extension ist eine an der Universität
> Hamburg entwickelte BDI Reasoning-Engine, die in Java geschrieben
> wurde. Ursprünglich als Erweiterung des
>
>                 Java Agent Development Framework
>
>                 konzipiert, sollte Jadex die Defizite von JADE
>                 beseitigen. Da sich die Entwickler von JADE auf die
>                 Konformität mit den FIPA-Spezifikationen und die
>                 Entwicklung von Werkzeugen zum Testen der Agenten
>                 konzentriert haben, blieb die Umsetzung eines
> internen Agentenkonzeptes bewusst unberücksichtigt
>                 <fo:inline>
>                     <fo:basic-link
>                         internal-destination="reference-PBL03">
>                         [PBL03]
>                     </fo:basic-link>
>                 </fo:inline>
>                 . Jadex war die Lösung dieses Defizits, indem es auf
>                 Basis der relativ einfach gestrickten JADE-Agenten
> ein Framework aufsetzte, das die Entwicklung von BDI-Agenten
> ermöglichte.
>             </fo:block>
>             <fo:block page-break-inside="avoid" margin="1em"
> space-after="0.5em" font-size="10pt" font-family="Helvetica"
> id="code-adf_aufbau">
> <fo:block border-bottom="solid 1px gray" border-top="solid 1px gray"
> linefeed-treatment="preserve" white-space-collapse="false"
> font-size="10pt" font-family="Courier">
> &lt;agent xmlns="http://jadex.sourceforge.net/jadex";
>     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>     xsi:schemaLocation="http://jadex.sourceforge.net/jadex
>                         http://jadex.sourceforge.net/jadex-0.94.xsd";
>     name="AgentTypeName"
>     package="your.package.here"&gt;
>
>     &lt;imports&gt;
>         &lt;!-- 1.) java imports --&gt;
>     &lt;/imports&gt;
>
>     &lt;capabilities&gt;
>         &lt;!-- 2.) by this agent used capabilties --&gt;
>     &lt;/capabilities&gt;
>
>     &lt;beliefs&gt;
>         &lt;!-- 3.)beliefs of this agent --&gt;
>     &lt;/beliefs&gt;
>
>     &lt;goals&gt;
>         &lt;!-- 4.) The goals the agent may have --&gt;
>     &lt;/goals&gt;
>
>     &lt;plans&gt;
>         &lt;!-- 5.) The plan library --&gt;
>     &lt;/plans&gt;
>
>     &lt;events&gt;
>         &lt;!-- 6.) All known events (messages, goals and internal
> events) --&gt;
>     &lt;/events&gt;
>
>     &lt;expressions&gt;
>         &lt;!-- 7.) used expressions and conditions --&gt;
>     &lt;/expressions&gt;
>
>     &lt;properties&gt;
>         &lt;!-- 8.) static values needed by this agent --&gt;
>     &lt;/properties&gt;
>
>     &lt;initialstates&gt;
>         &lt;!-- 9.) possibility to start agent with different initial
> states,
>                   like inital goals, plans or beliefs e.g. --&gt;
>     &lt;/initialstates&gt;
>
> &lt;/agent&gt;
>                     test XXX
>
>                 </fo:block>
> <fo:block>
>                             Code-Auszug 1:
>                         Aufbau des ADF von Jadex Agenten</fo:block>
> </fo:block>
> </fo:flow>
> </fo:page-sequence>
> </fo:root>
>

Manuel

>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail:
> [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to