IMPORTANT:
this is not a Support Forum! Experienced users might answer from time to time questions posted here. If you need a professional and reliable answer, or if you want to report a bug, please contact Altova Support instead.

Profile: marcino
About
User Name: marcino
Forum Rank: Newbie
Real Name:
Location
Occupation:
Interests:
Gender: None Specified
Statistics
Joined: Wednesday, August 8, 2018
Last Visit: Tuesday, January 8, 2019 12:35:56 PM
Number of Posts: 2
[0.01% of all post / 0.00 posts per day]
Avatar
Last 10 Posts
Topic: Problem with line-breaks in PDF transforms
Posted: Tuesday, January 8, 2019 12:32:01 PM
Hello,
This problem occur since I moved from Altova 2017 to 2019.

When I generate PDF file I have missing empty line-breaks which I defined on designer. This is only issued for PDF, other formats are generated correctly.

I checked XSLT-FO transform and I was searching part of code responsible for line-breaks. Then I noticed that definition for <fo:block/> is missing:

currently (not working):
Code:
xsl:template match="altova:line-break" mode="second-step">
        <xsl:variable name="name-following-sibling" select="name(following-sibling::*[1])"/>
        <xsl:variable name="name-preceding-sibling" select="name(preceding-sibling::*[1])"/>
        <xsl:if test="($name-following-sibling and $name-following-sibling != ''fo:table'' and $name-following-sibling != ''altova:line-break'' and $name-preceding-sibling != ''altova:basic-link-container'') or $name-preceding-sibling = ''altova:line-break''">
            <fo:block/>
        </xsl:if>
    </xsl:template>


previously (working):
Code:
<xsl:template match="altova:line-break" mode="second-step">
        <xsl:variable name="name-following-sibling" select="name(following-sibling::*[1])"/>
        <xsl:variable name="name-preceding-sibling" select="name(preceding-sibling::*[1])"/>
        <xsl:if test="($name-following-sibling and $name-following-sibling != ''fo:table'' and $name-following-sibling != ''altova:line-break'' and $name-preceding-sibling != ''altova:basic-link-container'') or $name-preceding-sibling = ''altova:line-break''">
            <fo:block>
                <xsl:if test="($name-preceding-sibling != ''altova:inline-container-substitute'' and $name-preceding-sibling != ''fo:inline'' and $name-preceding-sibling != ''fo:basic-link'' and $name-preceding-sibling != ''altova:bookmark'' and $name-preceding-sibling != ''altova:hyperlink'') or ($name-following-sibling != ''altova:inline-container-substitute'' and $name-following-sibling != ''fo:inline'' and $name-following-sibling != ''fo:basic-link'' and $name-following-sibling != ''altova:bookmark'' and $name-following-sibling != ''altova:hyperlink'')">
                    <fo:leader leader-pattern="space"/>
                </xsl:if>
            </fo:block>
        </xsl:if>
    </xsl:template>


I am not sure if it is Altova 2019 bug or it could be configured somewhere. I would be grateful if anyone could help me with this.
Topic: Generation time optimizing
Posted: Wednesday, August 8, 2018 2:04:00 PM
Hello,
I am working on sps file which looks like below on design mode:


Everything works fine but for long xmls it takes very long time to generate result HTML file.
It needs more than minute on my local PC to generate HTML with table which has more than 15 columns and 600 rows.
Is there any solution to design sps in other way to decrease this time? I would be grateful for any help.

Edit:
When I designed another table but with 15 specified columns to match my xml data it took only few seconds to generate table.
But it isn't solution for me because I need some kind of template for simple tables where columns are generated dynamically.
Is there any way to make template that would work faster?

Use of the Altova User Forum(s) is governed by the Altova Terms of Use.