[#XSL-986] Support: xslfast support call on 31.05.2006 - jira.jcatalog.com

Details

Type: Task
Status: Closed
Priority: Critical
Resolution: Won't Fix
Affects Version/s: Version 2.0.3
Fix Version/s: Version 2.0.3
Component/s: None
Labels:
None

Request Controller:
Please Select
External Supervisor:
Please select
Executing Programmer:
Please select

Description

We are working quite extensively with XSLFast version 2.03 and we are trying
to combine two layouts:
1. One layout is the order, for example.
2. Second layout is the terms and conditions for the order.
3. The layouts should look like this: 1st page order, 2nd page terms and
conditions, 1st page order, 2nd page terms and conditions, and so on until
the data on the order is finished and the last page is the terms and
conditions.

Going back to XSLFast 1.3 we were able to accomplish this with Multi-page
layout option. In this version the Use Body checkbox and
Header,Footer,Left,Right could be enabled and used at the same time (see
1.jpg attached). Of course, the two separate xmls had to be combined into
one first.

In the version 2.03 we are NOT able to accomplish this with Multi-page
layout option. In this version the Use Body checkbox and
Header,Footer,Left,Right could NOT be enabled and used at the same time (see
2.jpg attached.) This looks like a bug.

In case the Multi-layout feature is being deprecated, we tried the new
Page/InsertPage odd and even. One of the Tutorials does have what looks like
a correct example, but unfortunately it's not clear.

After describing the issue, our question is this: Is it possible to
accomplish what we want? If it is and we are not using the tool correctly,
please advise.

More Options
- Sort By Name
- Sort By Date
- Ascending
- Descending

Attachments

22_Table.zip

01/Jun/06 10:39 AM

165 kB

Krapivin, Victor
New_ord.xsf

07/Jun/06 4:12 PM

2,18 MB

Oleinik, Victoria
ORD_TEST.zip

06/Jun/06 5:36 PM

3 kB

Packianathan, Anton
ORD.zip

06/Jun/06 5:36 PM

80 kB

Packianathan, Anton
ORD1-1-1.pdf

07/Jun/06 4:12 PM

78 kB

Oleinik, Victoria
ORDACK.pdf

06/Jun/06 5:38 PM

27 kB

Packianathan, Anton

1.jpg

39 kB

31/May/06 4:43 PM
2.jpg

34 kB

31/May/06 4:43 PM

Activity

Ascending order - Click to sort in descending order

Hide

Permalink

Krapivin, Victor added a comment - 31/May/06 4:49 PM

As you can see in screenshot 1 both layouts are combined with one group; at 2nd screen only firsst layout were grouped. Did you tried to combine it into one group?

Concerning your question in 2.03 you able to place content to left or right regions as you need, and combine body elements into one (if it is necessary). The new abilities in 2.0 are simple and similar to book; you have title page, main area, and odd/even regions applied to that page. So you can specify empty body and place all to regions.

Note: region sizes are calculated up to first (main) page, so please be sure on all tabs you have the same region sizes and places.

Show

Krapivin, Victor added a comment - 31/May/06 4:49 PM As you can see in screenshot 1 both layouts are combined with one group; at 2nd screen only firsst layout were grouped. Did you tried to combine it into one group? Concerning your question in 2.03 you able to place content to left or right regions as you need, and combine body elements into one (if it is necessary). The new abilities in 2.0 are simple and similar to book; you have title page, main area, and odd/even regions applied to that page. So you can specify empty body and place all to regions. Note: region sizes are calculated up to first (main) page, so please be sure on all tabs you have the same region sizes and places.

Hide

Permalink

Krapivin, Victor added a comment - 01/Jun/06 10:39 AM

There are two layouts attached (sposob1.xsf and sposob2.xsf); layouts were created in XSLfast 3.0. First way (described as sposob1.xsf) also can be applied to XSLfast 2.x.

Show

Krapivin, Victor added a comment - 01/Jun/06 10:39 AM There are two layouts attached (sposob1.xsf and sposob2.xsf); layouts were created in XSLfast 3.0. First way (described as sposob1.xsf) also can be applied to XSLfast 2.x.

Hide

Permalink

Packianathan, Anton added a comment - 02/Jun/06 5:03 PM

Answer from the customer;
------------------------------------

As you can see in screenshot 1 both layouts are combined with one group;
at 2nd screen only first layout were grouped. Did you tried to combine
it into one group?

--Yes, I have tried every possible combination, (see attached 3.jpg). The
problem as I see it. version 2 doesn't allow me to select both body and
header, footer, left, right checkbox as it did in version 1.3. I got several
errors:
If I try to group by the same level, I get an error that the pages are
empty. If I try from first or last page, it is the same error, pages
empty... If I try use body on the terms and conditions, then the Page
Position options and Odd/Even are disabled for selection, meaning I cannot
click them to select.

Concerning your question in 2.03 you are able to place content to left
or right regions as you need, and combine body elements into one (if it
is necessary). The new abilities in 2.0 are simple and similar to book;
you have title page, main area, and odd/even regions applied to that
page. So you can specify empty body and place all to regions.

---If you are referring to the manual's example under Regions topic. I am
not so sure this is what I am looking to achieve. The example looks like the
first page is main and the rest of the pages are just that, the rest of the
pages. In this case our clients require us to have 1,2; 1,2;... pattern. If
I understand you correctly, you've just suggested I use the Page option
instead of multilayout option.

If this pattern layout is possible would you please advise with detailed
instructions. We are under a deadline and would like nothing better than to
solve this issue and continue making our clients happy with the XSLFast
tool. Especially, since this was relatively easy to do in version 1.3, but
our standard has changed to the 2.3 version...

Show

Packianathan, Anton added a comment - 02/Jun/06 5:03 PM Answer from the customer; ------------------------------------ As you can see in screenshot 1 both layouts are combined with one group; at 2nd screen only first layout were grouped. Did you tried to combine it into one group? --Yes, I have tried every possible combination, (see attached 3.jpg). The problem as I see it. version 2 doesn't allow me to select both body and header, footer, left, right checkbox as it did in version 1.3. I got several errors: If I try to group by the same level, I get an error that the pages are empty. If I try from first or last page, it is the same error, pages empty... If I try use body on the terms and conditions, then the Page Position options and Odd/Even are disabled for selection, meaning I cannot click them to select. Concerning your question in 2.03 you are able to place content to left or right regions as you need, and combine body elements into one (if it is necessary). The new abilities in 2.0 are simple and similar to book; you have title page, main area, and odd/even regions applied to that page. So you can specify empty body and place all to regions. ---If you are referring to the manual's example under Regions topic. I am not so sure this is what I am looking to achieve. The example looks like the first page is main and the rest of the pages are just that, the rest of the pages. In this case our clients require us to have 1,2; 1,2;... pattern. If I understand you correctly, you've just suggested I use the Page option instead of multilayout option. If this pattern layout is possible would you please advise with detailed instructions. We are under a deadline and would like nothing better than to solve this issue and continue making our clients happy with the XSLFast tool. Especially, since this was relatively easy to do in version 1.3, but our standard has changed to the 2.3 version...

Hide

Permalink

Krapivin, Victor added a comment - 06/Jun/06 4:14 PM

In basics, the BODY indicates content between regions; top/left/bottom/right are regions not whole pages. So you can combine from couple of layouts, which pieces of pages should be used.

Unfortunately, if you have two BODY parts, it will follow sequentially and no way to make it interleaved.

So you need to make main content as body, lioke an example

Front content for invoice XXX, page 1
Empty page
Front content for invoice XXX, page 2
Empty page

and so on.

By adding ODD region and its' content, you'll have the following regional layouts:

No region
Odd region, such static content
No region
Odd region, such static content, the same content as above

With checkboxes (or with pages) you can combine it in the following form:

BODY, Group A, use body, Expression: 1
ODD, Group A, use header/footer, Expression: 1

As an result you'll get every even page you'll see an content (front page), and every odd page (back page). By printing with duplex option in Acrobat Reader will have static text you need on the other side of paper.

Sorry, but there is one way and it have no dependency it related to 1.3, 2.0 or 3.0.

Show

Krapivin, Victor added a comment - 06/Jun/06 4:14 PM In basics, the BODY indicates content between regions; top/left/bottom/right are regions not whole pages. So you can combine from couple of layouts, which pieces of pages should be used. Unfortunately, if you have two BODY parts, it will follow sequentially and no way to make it interleaved. So you need to make main content as body, lioke an example Front content for invoice XXX, page 1 Empty page Front content for invoice XXX, page 2 Empty page and so on. By adding ODD region and its' content, you'll have the following regional layouts: No region Odd region, such static content No region Odd region, such static content, the same content as above With checkboxes (or with pages) you can combine it in the following form: BODY, Group A, use body, Expression: 1 ODD, Group A, use header/footer, Expression: 1 As an result you'll get every even page you'll see an content (front page), and every odd page (back page). By printing with duplex option in Acrobat Reader will have static text you need on the other side of paper. Sorry, but there is one way and it have no dependency it related to 1.3, 2.0 or 3.0.

Hide

Permalink

Oleinik, Victoria added a comment - 07/Jun/06 4:12 PM

This layout is made using Odd and Even regions. Terms and conditions are placed in Odd region, but this region is only a region, so it has the area of body region. That is why a little peace of the table from main page appears on the page with terms ang conditions. Unfortunately this body region can not be smaller.

Show

Oleinik, Victoria added a comment - 07/Jun/06 4:12 PM This layout is made using Odd and Even regions. Terms and conditions are placed in Odd region, but this region is only a region, so it has the area of body region. That is why a little peace of the table from main page appears on the page with terms ang conditions. Unfortunately this body region can not be smaller.

Hide

Permalink

Oleinik, Victoria added a comment - 07/Jun/06 4:14 PM

See attached ORD1-1-1.pdf and New_ord.xsf

Show

Oleinik, Victoria added a comment - 07/Jun/06 4:14 PM See attached ORD1-1-1.pdf and New_ord.xsf

Hide

Permalink

Packianathan, Anton added a comment - 08/Jun/06 10:58 AM

Comment from Customer
-----------------------------------------
Thank you very, very much for sending the example. I appreciate the work you
put into trying to solve our client's issue.

I think we are almost there, but unfortunately, not quite... I'd like to
bring to your awareness that nothing in that layout is written in stone. For
example, the detail section that shows up in the region doesn't have to be a
template, it can be anything else if it would help it not show up on the
terms page. Also, page numbering should not be forgotten... right now there
page numbering is not in place.

I went so far as to put a white.jpg to cover the region, but the lines still
show up... and that's not a serious solution. Let's get motivated to
complete the wonderful work you've done and bring it to the level of
production quality because as it stands now, it cannot be offered to
customers.

We are completely happy to receive a code fix or a patch for this
implementation and I am sure your other clients will appreciate the
enhancement as there are many companies that have terms and conditions,
contracts and disclaimers, which must be printed on the backs of pages.

If it would help to speed up a solution delivery, we would be happy to
discuss the issue with you development or management to explain how
necessary this solution is for both our companies.

Show

Packianathan, Anton added a comment - 08/Jun/06 10:58 AM Comment from Customer ----------------------------------------- Thank you very, very much for sending the example. I appreciate the work you put into trying to solve our client's issue. I think we are almost there, but unfortunately, not quite... I'd like to bring to your awareness that nothing in that layout is written in stone. For example, the detail section that shows up in the region doesn't have to be a template, it can be anything else if it would help it not show up on the terms page. Also, page numbering should not be forgotten... right now there page numbering is not in place. I went so far as to put a white.jpg to cover the region, but the lines still show up... and that's not a serious solution. Let's get motivated to complete the wonderful work you've done and bring it to the level of production quality because as it stands now, it cannot be offered to customers. We are completely happy to receive a code fix or a patch for this implementation and I am sure your other clients will appreciate the enhancement as there are many companies that have terms and conditions, contracts and disclaimers, which must be printed on the backs of pages. If it would help to speed up a solution delivery, we would be happy to discuss the issue with you development or management to explain how necessary this solution is for both our companies.

Hide

Permalink

Packianathan, Anton added a comment - 09/Aug/06 2:48 PM

we have made all possibility (amongst others with page interleaving),
but we haven't any solution (XSL-FO have no required features to make it better).

Show

Packianathan, Anton added a comment - 09/Aug/06 2:48 PM we have made all possibility (amongst others with page interleaving), but we haven't any solution (XSL-FO have no required features to make it better).

People

Assignee:

Packianathan, Anton

Reporter:

Packianathan, Anton

Vote (0)

Watch (0)

Dates

Created:

31/May/06 4:32 PM

Updated:

09/May/07 12:26 AM

Resolved:

09/Aug/06 2:48 PM