Skip to main content
A
anne.bovard1-Visitor
1-Visitor
February 11, 2011
Question

Whitespace in PDF output

  • February 11, 2011
  • 15 replies
  • 3844 views

Hi all,

I'm having a problem with Styler expressing whitespace in our PDF output. Please see the following code snippet and attached jpg of the output. When I manually remove the spaces between the para and section end tags, I have no problem. It seems that I should be able to strip the space somehow. I admit that the code is a little messy, but is there a way to ignore the whitespace in our output? We're using a FOSI-based Styler stylesheet. Thank you for your time and attention.

Kind regards,

Anne

SPI-turvalausekkeet<title>SPI-turvalausekkeet</title><conbody>
<section> <title>Johdanto</title>

Varoituksilla osoitetaan
tässä oppaassa vaaroja ja vakavuuden tasoa. Tutustu määritelmiin ja
merkityksiin.

Pocket Vieweriä ei ole tarkoitettu ensisijaiseksi
hälytyslähteeksi.

</section>
<section> <title>Vaarat</title>

Vaaratarkoittaa välitöntä
vaarallista tilannetta, jonka huomioimatta jättäminen johtaa vakavaan
loukkaantumiseen tai kuolemaan. Web Viewerissa ei ole äänihälytyksiä.</p<br/>>

</section>
<section> <title>Varoitukset</title>

VAROITUSVaroitus
tarkoittaa tilannetta, jossa saattaa olla vakavan loukkaantumisen
tai kuoleman mahdollisuus. Web Viewerissa ei ole äänihälytyksiä.</p<br/>> </section>
</conbody>
Johdanto


    15 replies

    Show previous replies
    G
    GarethOakes16-Pearl
    16-Pearl
    February 15, 2011
    Oh how I love dealing with whitespace in XML. Glad I'm not the only one J



    -G


    C
    ClayHelberg18-Opal
    18-Opal
    February 15, 2011
    Hi Manish-



    Your fname file is not getting generated as a result of the composition
    failure, it is not the cause of it. From what you've said I can't tell
    what's going wrong with your composition call. But you may be able to
    get some more useful information by looking at the following things:



    a) The transaction archive, available from the main PE application
    page. This should store copies of the original request and response as
    well as any intermediate files generated during the failed build. You
    may also want to change some of the options in your e3config.xml file to
    modify what gets saved under what circumstances.

    b) The PE log file, usually called "pelog.xml", located in the
    Tomcat logs folder. This may have some more detailed information on what
    is happening with the composition failures. If you need more detail, you
    can change settings in e3config.xml to increase various logging levels.



    If you are using 5.4, there is some helpful information on PE
    troubleshooting in the Arbortext Help Center. If you search for
    "troubleshooting errors", you'll find useful information there. Good
    luck!



    --Clay



    Clay Helberg

    Senior Consultant

    TerraXML


    M
    ManishaPawar1-Visitor
    1-Visitor
    February 15, 2011
    Hi Clay,

    Thanks for the information. I have checked this

    Its is saying not request body



    Also I checked for path Translated path ....Last e3 directory is not
    available on PE server. Does because of this it can fail?



    Thanks & Regards,
    Manisha




    Clay Helberg <chelberg@terraxml.com>
    02/15/2011 06:21 PM
    Please respond to
    -


    To
    -
    cc

    Subject
    [adepters] - RE: PE Composition Error.






    Hi Manish—

    Your fname file is not getting generated as a result of the composition
    failure, it is not the cause of it. From what you’ve said I can’t tell
    what’s going wrong with your composition call. But you may be able to get
    some more useful information by looking at the following things:

    a) The transaction archive, available from the main PE application
    page. This should store copies of the original request and response as
    well as any intermediate files generated during the failed build. You may
    also want to change some of the options in your e3config.xml file to
    modify what gets saved under what circumstances.
    b) The PE log file, usually called “pelog.xml”, located in the Tomcat
    logs folder. This may have some more detailed information on what is
    happening with the composition failures. If you need more detail, you can
    change settings in e3config.xml to increase various logging levels.

    If you are using 5.4, there is some helpful information on PE
    troubleshooting in the Arbortext Help Center. If you search for
    “troubleshooting errors”, you’ll find useful information there. Good luck!

    --Clay

    Clay Helberg
    Senior Consultant
    TerraXML
    C
    ClayHelberg18-Opal
    18-Opal
    February 15, 2011
    It looks to me as if your calling process is not packaging up the POST data properly. If the document is included in the request body then PE should be able to find it.



    Clay Helberg

    Senior Consultant

    TerraXML


    M
    ManishaPawar1-Visitor
    1-Visitor
    February 22, 2011
    Hi All,

    Regarding the following issue which I mentioned in the below mail , I have
    printed composer log and it showing me below error

    [ERROR] [A62020] Stylesheet '' has an extension other than '.style',
    '.fos', '.xsl', or '.3f'. Unknown stylesheet type.
    [INFO] [A20324] Operation canceled by user.

    Anybody knows about this error? Thanks in advance.





    Thanks & Regards,
    Manisha




    Clay Helberg <chelberg@terraxml.com>
    02/15/2011 06:21 PM
    Please respond to
    -


    To
    -
    cc

    Subject
    [adepters] - RE: PE Composition Error.






    Hi Manish—

    Your fname file is not getting generated as a result of the composition
    failure, it is not the cause of it. From what you’ve said I can’t tell
    what’s going wrong with your composition call. But you may be able to get
    some more useful information by looking at the following things:

    a) The transaction archive, available from the main PE application
    page. This should store copies of the original request and response as
    well as any intermediate files generated during the failed build. You may
    also want to change some of the options in your e3config.xml file to
    modify what gets saved under what circumstances.
    b) The PE log file, usually called “pelog.xml”, located in the Tomcat
    logs folder. This may have some more detailed information on what is
    happening with the composition failures. If you need more detail, you can
    change settings in e3config.xml to increase various logging levels.

    If you are using 5.4, there is some helpful information on PE
    troubleshooting in the Arbortext Help Center. If you search for
    “troubleshooting errors”, you’ll find useful information there. Good luck!

    --Clay

    Clay Helberg
    Senior Consultant
    TerraXML
    Terms & ConditionsAccessibility statement