Antenna House is very pleased to announce the immediate availability
of Antenna House XSL Formatter V4.1, which is the first product to offer
full implementation of all the new features in the Extensible Stylesheet
Language (XSL) Version 1.1 recommended from the W3C.


What's new with V4.1:
~~~~~~~~~~~~~~~~~~~~~
     *Conforms to Extensible Stylesheet Language (XSL) Version 1.1.
     *Possible to format a very huge document which has <fo-page-number-
      citation> in large quantities by offering the two-pass formatting.
     *EPS can now be embedded as EPS in PDF in the environment where Adobe
      Distiller or Ghostscript are installed.
     *Styles and positions of an underline, etc. can now be adjusted.
     *Available to control the printer tray.
     *Possible to generate footnote numbers.
     *Corresponds to the jar scheme.
     *Possible to display a form of Anti-Aliasing in GUI.

Newly added or extended properties:
   http://www.antennahouse.com/news/V41newfeatureEN.htm

See for yourself why Antenna House XSL Formatter is used worldwide for
demanding formatting requirements whenever a reliable, fast and powerful
tool is needed to product technical documentation, manuals and reports.

For more details, please see the following URL:
   http://www.antennahouse.com/product/axfo40/axfo4top.htm

XSL Formatter V4.1 can be downloaded from:
   http://www.antennahouse.com/product/axfo40/download.htm

http://www.antennahouse.com


Thank you.

Has anyone published any performance data on open source or commercial
XSL-FO processors?

Any pointers would be much appreciated.

Mike W.

Hi:

Hi,
     POI has worked well for several features of our applications
involving Excel spreadsheets. Recently we explored the possibility of reading
Excel files that have been prepared on a Windows Mobile device (e.g. HP
IPAQ) using Pocket Excel. These devices are gaining popularity at
receiving sites, where they are often outfitted with a barcode scanner.
Although these files can be displayed with no problem on a desktop PC using
Excel, the files cannot be read by POI. We have found and tested an
open source package, JExcelAPI, that reads spreadsheets prepared using
either desktop or Pocket without a problem.  Can anybody give us some idea
about this?
   Thanks!
   Chung


  __________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

[Non-text portions of this message have been removed]

The Apache FOP team is proud to announce the release of Apache FOP
version 0.93.

The new codebase for FOP was started several years ago in order to
achieve better compliance with the XSL-FO spec. After three alpha and
beta releases, the new codebase has now reached production
quality. Therefore we present version 0.93 as the successor of version
0.20.5, FOP's production grade version during the past years.

* FOP 0.93 contains the new API first introduced in release 0.92
    beta. The preceding API has been removed.
* FOP 0.93 again contains many bug fixes and new features. See
    below for details.

Compliance
----------

FOP 0.93 implements the XSL 1.0 and 1.1 recommendations to a high
degree of compliance. See the compliance page
http://xmlgraphics.apache.org/fop/compliance.html for a detailed
overview.

Known issues
------------

The known issues of FOP 0.93 are listed at
http://xmlgraphics.apache.org/fop/knownissues.html.

Upgrading
---------

You will experience different behaviour compared to version
0.20.5. Please consult the "Upgrading" page
(http://xmlgraphics.apache.org/fop/stable/upgrading.html) for
details.

Major Changes in Version 0.93
-----------------------------

* Added support for the use of Open Type fonts.
* Support for the rgb-icc() function and for a proprietary cmyk()
    function (for device CMYK colors only through the PDF renderer so
    far).
* Enabled Copy/Paste from PDF content in Acrobat Reader for
    text using embedded TrueType fonts.
* Added support for PDF/A-1b and PDF/X-3:2003. (Note: this may still
    be a bit incomplete.)
* The Java2DRenderer (and therefore the print and bitmap renderers) is
    now offering the same quality as the PDF and PS renderers.
* Automatic support for all fonts available to the Java2D subsystem
    for all Java2D-descendant renderers (TIFF, PNG, print, AWT).

The long list of changes in this release is available at
http://xmlgraphics.apache.org/fop/0.93/changes_0.93.html.

The long list of changes in this and earlier releases is available at
http://xmlgraphics.apache.org/fop/changes.html.

The Apache FOP team asks you for your continued feedback on the
software.  We're also interested in success stories with the new
release. So if the latest version works fine for you, please tell us!
And if it doesn't, you may tell us as well, of course. ;-)

Release notes for older FOP versions can be found on:
http://xmlgraphics.apache.org/fop/relnotes.html

For the FOP team,
Simon Pepping

J.Pietschmann

Hi:

I am not sure if this is the right forum to post this question.
I amusing XML Spy and Renderx XEP for FO processing, and when I
generate the PDF, i get this error:

"The system cannot find the path specified".

Doea anybody have any idea why this is?

Altsoft announces beta release of its new Xml2PDF 2007 family of products,
containing Xml2PDF Server 2007 (.NET API), Xml2PDF Hotfolder 2007 and Xml2PDF
Workstation 2007.
Altsoft Xml2PDF 2007 is a .NET-based formatting engine for converting various
page layout formats into print-ready documents.
The new key features and improvements are:
- Significant refactoring and optimization.
- Essential improvement of Xml2PDF API interface.
- Improved XSL-FO 1.1 support including bookmarks, multiple flows, and floats.
- XPS output support.
- PostScript output support.
- DocX and XAML (Word 2007) input support.
- Significant improvement of graphics (TIFF, GIF, JPEG, PNG, WMF) output
support.
- Direct GDI+ print and preview function.
- Advanced font management options.
- Possibility to merge several documents of different formats into one output
document or use any source document as a background.
- Advanced configuration options.
Microsoft .NET Frameworks 2.0 and 1.1 are supported.
The commercial release is scheduled for March, 2007. Light, Standard and
Professional editions will be available for Xml2PDF Server 2007. All clients who
purchase Xml2PDF 3.0 Complete API in January and February 2007 will receive an
upgrade to Xml2PDF Server 2007 Professional for FREE!
Altsoft Xml2PDF Server 2007 beta (Professional edition) is available for
download at https://alt-soft2.com/Downloads_server_evaluation.aspx
Xml2PDF 2007 Hotfolder and Workstation editions will be available for download
soon.
Altsoft team
www.alt-soft.com

Ca anyone explain the difference between copy-of and copy in xslt?

mina_hurray wrote:

>
>
> Ca anyone explain the difference between copy-of and copy in xslt?

yes of course. copy just copies a single node to the result tree.
copy-of copies a complete node tree to the result tree.

BTW, pure XSLT questions are better off being asked on an XSLT list such
as the Mulberry list.

http://www.mulberrytech.com/xsl/xsl-list/

Chris


>
>

mina_hurray wrote:
> Ca anyone explain the difference between copy-of and copy in xslt?

Yes, but your question should be directed to xsl list
at Mulberrytech.com

That way, others would learn from any answers.




regards

--
Dave Pawson
XSLT XSL-FO FAQ.
http://www.dpawson.co.uk

XSLT and XPath questions would be better posted to the following list:

    http://www.mulberrytech.com/xsl/xsl-list

There are a number of subscribers who would enthusiastically respond
to such questions.

There is also an *excellent* XSLT FAQ at:

    http://www.dpawson.co.uk

and XML FAQ at:

    http://xml.silmaril.ie/

At 2007-01-22 15:56 +0000, mina_hurray wrote:
>Ca anyone explain the difference between copy-of and copy in xslt?

<xsl:copy-of> is a "deep copy" copying all addressed nodes and their
descendants down to the leaves of the XPath node tree.

<xsl:copy> is a "shallow copy" copying only the current node.

I hope this helps.

. . . . . . . . . . . . Ken

--
World-wide corporate, govt. & user group XML, XSL and UBL training
RSS feeds:     publicly-available developer resources and training
G. Ken Holman                 mailto:gkholman@...
Crane Softwrights Ltd.          http://www.CraneSoftwrights.com/f/
Box 266, Kars, Ontario CANADA K0A-2E0    +1(613)489-0999 (F:-0995)
Male Cancer Awareness Aug'05  http://www.CraneSoftwrights.com/f/bc
Legal business disclaimers:  http://www.CraneSoftwrights.com/legal

mina_hurray wrote:
> I am not sure if this is the right forum to post this question.

This is an XML Spy specific question and would have been best asked
in a forum dedicated specifically to XML spy users.

> I amusing XML Spy and Renderx XEP for FO processing, and when I
> generate the PDF, i get this error:
>
> "The system cannot find the path specified".
>
> Doea anybody have any idea why this is?

Well, the system cannot find the path specified. AFAIK this
is a configuration setting in XML spy, and the programs seems
be not amused that the path pointing to the XEP installation
doesn't exist. Check and replace this setting to the actual
path.

J.Pietschmann

Altsoft announces beta release of its new Xml2PDF 2007 family of
products, containing Xml2PDF Server 2007 (.NET API), Xml2PDF
Hotfolder 2007 and Xml2PDF Workstation 2007.

Altsoft Xml2PDF 2007 is a .NET-based formatting engine for converting
various page layout formats into print-ready documents.

The new key features and improvements are:

-Significant refactoring and optimization.
-Essential improvement of Xml2PDF API interface.
-Improved XSL-FO 1.1 support including bookmarks, multiple flows, and
floats.
-XPS output support.
-PostScript output support.
-DocX and XAML (Word 2007) input support.
-Significant improvement of graphics (TIFF, GIF, JPEG, PNG, WMF)
output support.
-Direct GDI+ print and preview function.
-Advanced font management options.
-Possibility to merge several documents of different formats into one
output document or use any source   document as a background.
-Advanced configuration options.

The Microsoft frameworks .NET 2.0 and 1.1 are supported.

The commercial release is scheduled for March, 2007. Light, Standard
and Professional editions will be available for Xml2PDF Server 2007.
All clients who purchase Xml2PDF 3.0 Complete API in January and
February 2007 will receive an upgrade to Xml2PDF Server 2007
Professional for FREE!

Altsoft Xml2PDF Server 2007 beta (Professional edition) is available
for download at:

https://alt-soft2.com/Downloads_server_evaluation.aspx

Xml2PDF 2007 Hotfolder and Workstation editions will be available for
download soon.

The beta version does not require any activation keys, but produces
an Altsoft watermark on each page and is valid till March 31, 2007.
Please, note that this version is not recommended for use on any
production environment.

Feel free to send your comments and bug reports to support@alt-
soft.com.

Altsoft nv
http://alt-soft.com/

I'm currently using FOP 0.20.5 to generate PDF. I'm working on a
peformance test to compare 0.20.5 and 0.93.

My workflow consists of building FO markup using server side scripting
such as Coldfusion. Then, invoking the FOP classes through Coldfusion
passing the generated FO. I've doubled my page output to about 7 pages
per second after having optimized the generated FO. Basically I had tons
of nested tables that I solved using positionned block-containers. I was
able to eliminate about 2/3 of the FO markup by doing so.

However, IT is bugging me about it still taking long (taking up
requests) and impacting the other unique sites on that shared server.

What are avenues that people take to alleviate such issues?

Dan

Greetings,

Our workaround is to deploy FOP as a distributed Apache application on dual-core
desktops. we use a tool called SetAffinity to set the processor mask on the
Apache service to limit it's use to one processor core (CPU 0) both to prevent
Apache from consuming too many CPU cycles and to eliminate overhead due to
context switching . We also set an upper limit for heap space to 600MB to
prevent the FOP process from using too much memory and execute a system exit
when running processes and all jobs in queue have finished to recover any leaked
memory. We've installed Apache as a Windows service and set the recovery (wait)
period to zero so that the system restarts quickly enough to respond to the next
request. We can't tell the difference in terms of response time or performance.
In fact, performance is marginally improved because FOP no longer has to compete
for resources with server-side applications. SetAffinity can also be used
against other desktop applications to prevent
  them from starving FOP although we haven't seen a need to do that yet. Since
computing resources for a distributed model of processing automatically expands
with the user base, it is unlikely that the application will ever be
bottle-necked. Additionally, if we wanted to, we can easily recode the
application to distribute job submissions from the requesting node to less busy
nodes in the network and pipe back the results.

Regards,

peter

----- Original Message ----
From: "Fournier,Danny [NCR]" <Danny.Fournier@...>
To: XSL-FO@yahoogroups.com
Sent: Wednesday, January 24, 2007 5:34:37 AM
Subject: [XSL-FO] Peformance Issues













             I'm currently using FOP 0.20.5 to generate PDF. I'm working on a

peformance test to compare 0.20.5 and 0.93.



My workflow consists of building FO markup using server side scripting

such as Coldfusion. Then, invoking the FOP classes through Coldfusion

passing the generated FO. I've doubled my page output to about 7 pages

per second after having optimized the generated FO. Basically I had tons

of nested tables that I solved using positionned block-containers. I was

able to eliminate about 2/3 of the FO markup by doing so.



However, IT is bugging me about it still taking long (taking up

requests) and impacting the other unique sites on that shared server.



What are avenues that people take to alleviate such issues?



Dan












<!--

#ygrp-mlmsg {font-size:13px;font-family:arial,helvetica,clean,sans-serif;}
#ygrp-mlmsg table {font-size:inherit;font:100%;}
#ygrp-mlmsg select, input, textarea {font:99% arial,helvetica,clean,sans-serif;}
#ygrp-mlmsg pre, code {font:115% monospace;}
#ygrp-mlmsg * {line-height:1.22em;}
#ygrp-text{
font-family:Georgia;
}
#ygrp-text p{
margin:0 0 1em 0;
}
#ygrp-tpmsgs{
font-family:Arial;
clear:both;
}
#ygrp-vitnav{
padding-top:10px;
font-family:Verdana;
font-size:77%;
margin:0;
}
#ygrp-vitnav a{
padding:0 1px;
}
#ygrp-actbar{
clear:both;
margin:25px 0;
white-space:nowrap;
color:#666;
text-align:right;
}
#ygrp-actbar .left{
float:left;
white-space:nowrap;
}
.bld{font-weight:bold;}
#ygrp-grft{
font-family:Verdana;
font-size:77%;
padding:15px 0;
}
#ygrp-ft{
font-family:verdana;
font-size:77%;
border-top:1px solid #666;
padding:5px 0;
}
#ygrp-mlmsg #logo{
padding-bottom:10px;
}

#ygrp-vital{
background-color:#e0ecee;
margin-bottom:20px;
padding:2px 0 8px 8px;
}
#ygrp-vital #vithd{
font-size:77%;
font-family:Verdana;
font-weight:bold;
color:#333;
text-transform:uppercase;
}
#ygrp-vital ul{
padding:0;
margin:2px 0;
}
#ygrp-vital ul li{
list-style-type:none;
clear:both;
border:1px solid #e0ecee;
}
#ygrp-vital ul li .ct{
font-weight:bold;
color:#ff7900;
float:right;
width:2em;
text-align:right;
padding-right:.5em;
}
#ygrp-vital ul li .cat{
font-weight:bold;
}
#ygrp-vital a {
text-decoration:none;
}

#ygrp-vital a:hover{
text-decoration:underline;
}

#ygrp-sponsor #hd{
color:#999;
font-size:77%;
}
#ygrp-sponsor #ov{
padding:6px 13px;
background-color:#e0ecee;
margin-bottom:20px;
}
#ygrp-sponsor #ov ul{
padding:0 0 0 8px;
margin:0;
}
#ygrp-sponsor #ov li{
list-style-type:square;
padding:6px 0;
font-size:77%;
}
#ygrp-sponsor #ov li a{
text-decoration:none;
font-size:130%;
}
#ygrp-sponsor #nc {
background-color:#eee;
margin-bottom:20px;
padding:0 8px;
}
#ygrp-sponsor .ad{
padding:8px 0;
}
#ygrp-sponsor .ad #hd1{
font-family:Arial;
font-weight:bold;
color:#628c2a;
font-size:100%;
line-height:122%;
}
#ygrp-sponsor .ad a{
text-decoration:none;
}
#ygrp-sponsor .ad a:hover{
text-decoration:underline;
}
#ygrp-sponsor .ad p{
margin:0;
}
o {font-size:0;}
.MsoNormal {
margin:0 0 0 0;
}
#ygrp-text tt{
font-size:120%;
}
blockquote{margin:0 0 0 4px;}
.replbq {margin:4;}
-->







[Non-text portions of this message have been removed]

I am trying to run 0.93 using 0.20.5's API. I'm just wondering if
someone would know off the top of their heads the equivalent calls?
Reading the upgrade page indicates that a new API was release with 0.93
and based on the error that I'm getting, I should be calling different
methods.

I was using the setInputSource(), setOutputStream() and run() methods.

Here is the list of relevant calls to FOP (in Coldfusion and some lines
were taken out for simplicity):

<cfset THIS.driver = CreateObject("java", "org.apache.fop.apps.Driver")>

<cfset var reader = CreateObject("java", "java.io.StringReader")>
<cfset var input = CreateObject("java", "org.xml.sax.InputSource")>
<cfset reader.init(foString)>
<cfset input.init(reader)>
<cfset THIS.driver.setInputSource(input)>

<cfset var output = CreateObject("java", "java.io.FileOutputStream")>
<cfset output.init( ARGUMENTS.pdfFile )>
<cfset THIS.driver.setOutputStream(output)>

<cfset THIS.driver.run()>


PS: I am not the originator of the original code that this was taken
from

Fournier,Danny [NCR] wrote:

>
>
> I am trying to run 0.93 using 0.20.5's API. I'm just wondering if
> someone would know off the top of their heads the equivalent calls?

If you have downloaded FOP onto your machine you can take a look at
example code on how to embed FOP with the new API in the following
directory below the root of your FOP install:

\examples\embedding\java\examples

Chris

<snip/>

a friendly, technically challenging, intensive, thought-provoking,
argumentative, welcoming, obstreperous conference on markup,
managing information, and information structures


CALL FOR PARTICIPATION
EXTREME MARKUP LANGUAGES 2007(r)
(a registered trademark of IDEAlliance)

THE MARKUP THEORY & PRACTICE CONFERENCE


Extreme is the leading international conference on markup theory and practice.
If you have interesting markup applications, difficult markup problems, or
intriguing solutions to problems related to the design and use of markup,
markup languages, or markup tools; if you want to know what the leading
theorists of markup are thinking; if you are the house markup expert and
want to spend time with your kind, then you should plan on attending
Extreme Markup Languages(r) 2007.


ABOUT THE CONFERENCE

Extreme is an open marketplace of theories about markup and all the
things that they support or that support them: the difficult cases in
publishing, linguistics, transformation, searching, indexing, and storage
and retrieval. At Extreme, markup enthusiasts gather each year to trade
in ideas, not to convince management to buy new stuff. At Extreme we push
the edges of markup theory & practice.

WHEN:      August 7-10, 2007
WHERE:     Montréal, Canada
HOST:      IDEAlliance


HOW TO PARTICIPATE

You can participate in Extreme Markup Languages in several ways:
   - Talk: submit a conference paper. Submit full papers in XML to
      extreme@.... Guidelines and details at
      http://www.extrememarkup.com/extreme/2007/submissions.html
   - Review: serve as a peer reviewer. To apply to serve on the Peer
      Review panel, follow the instructions (yes, this is a test) at:
      http://www.mulberrytech.com/Extreme/Peer/ReviewAppForm.html
   - Attend: come to the conference, listen to papers, learn about the
      latest and best techniques, the hottest and most pressing problems,
      the best and most promising solutions, and how the future of markup
      is shaping up. Meet the people who are shaping that future. Also,
      drink good coffee and eat great food in one of North America's
      greatest cities.


TOPICS

Possible topics include, but are not limited to:
   - XQuery, XSL-FO, XSLT, Pipelining, Topic Maps, RDF, TMQL,
       DSDL, OWL, SGML, XML, XSD, RELAX NG ...
   - markup for document production
   - markup for preservation and reuse of cultural artifacts
   - issues in the design and deployment of markup vocabularies
   - engineering tradeoffs in the design of markup-driven systems
   - overlapping structures and how to represent them
   - bias, objectivity, neutrality and ontological commitment in
        markup, markup design and software tools
   - trees, tuples, sequences, directed graphs, and other data
        structures for the representation of information
   - better markup as a tool for making the Web more useful
   - the future of multi-purpose content
   - the future of structured documents
   - designing, creating, using, mainipulating, and interpreting
        marked-up content
   - new markup-related tools
   - markup semantics
   - new approaches to old problems and new
   - things you can and can't do with XML
   - things it never occurred to you that anyone would want to
      do with XML
   - alternatives to popular specifications and techniques
   - treating non-XML data as if it were XML
   - treating XML data as if it were non-XML
   - implementation reports: love songs or horror stories


IMPORTANT DATES

9 March 2007: Peer review applications due
20 April 2007: Paper submissions due
13 May 2007: Speakers notified of paper selection
6 July 2007: Revised papers due
7-10 August 2007: Extreme Markup Languages 2007, Montréal


QUESTIONS: Email to extreme@... or call
             Tommie Usdin +1 301/315-9631


MORE INFORMATION as available: http://www.extrememarkup.com/
PROCEEDINGS of previous EXTREME MARKUP Conferences:
        http://www.idealliance.org/papers/extreme/proceedings/

     The Extreme Markup Languages Conference, formerly a production
     of IDEAlliance, is now developed by Mulberry Technologies, Inc.,
     which is solely responsible for its program.

--
======================================================================
Extreme Markup Languages 2007          mailto:extreme@...
August 7-10, 2007                  http://www.mulberrytech.com/Extreme
Montreal, Canada                          http://www.extrememarkup.com
======================================================================

[Non-text portions of this message have been removed]

Hi all:

I am not sure how to word my question. Basically, I have a graphic
having width and height in Inches. As in '7.5Inches' and '7.84Inches'.
Now, on the FO styles sheet, I use renderx xep as the processor, when
I am displaying the graphic height and width using
<fo:external-graphic content-width="" content-height=""/>

If my input xml graphic has:

<graphic src="" width="7.5Inches" height="7.84Inches"/>

On the fo style sheet,

Can I just say:

<fo:external-graphic>
<xsl:attribute name="content-width">
<xsl:choose>

<xsl:when test="@width">
<xsl:value-of select="@width"/>
</xsl:when>
<xsl:otherwise>90%</xsl:otherwise>
</xsl:choose>
</xsl:attribute>
<xsl:attribute name="content-height">
<xsl:choose>

<xsl:when test="@height">
<xsl:value-of select="@height"/>
</xsl:when>
<xsl:otherwise>90%</xsl:otherwise>
</xsl:choose>
</xsl:attribute>
</fo:external-graphic>

Will this just display the graphics with the right width and height or
should the width and height be converted to pixels?

Thanks in advance for all your help.

mina_hurray wrote:
> I am not sure how to word my question. Basically, I have a graphic
> having width and height in Inches. As in '7.5Inches' and '7.84Inches'.
...
> If my input xml graphic has:
>
> <graphic src="" width="7.5Inches" height="7.84Inches"/>
...
> <xsl:when test="@height">
> <xsl:value-of select="@height"/>
...
> Will this just display the graphics with the right width and height or
> should the width and height be converted to pixels?

Probably not, because XSLFO uses "in" as representation for
the unit "inch", as in
   content-height="7.5in"


You can try to strip the "Inches" suffix, if it is fixed, and
add the "in" in the XSLT. If the XML authors also use "1Inch"
and/or "7.84inches" or something, you probably are in trouble.

J.Pietschmann

Hi all:

I have graphic and a box below that. There is a gap between the box and
the graphic. How do I fill that up? i tried using padding but it did
not work. Please let me know.

Thank you.

Thank you for your response. Is it better then to convert the
measuments from inches to Pixels using dpi of 75? How do I set the
dpi?


--- In XSL-FO@yahoogroups.com, "J.Pietschmann" <j3322ptm@...> wrote:
>
> mina_hurray wrote:
> > I am not sure how to word my question. Basically, I have a graphic
> > having width and height in Inches. As in '7.5Inches'
and '7.84Inches'.
> ...
> > If my input xml graphic has:
> >
> > <graphic src="" width="7.5Inches" height="7.84Inches"/>
> ...
> > <xsl:when test="@height">
> > <xsl:value-of select="@height"/>
> ...
> > Will this just display the graphics with the right width and
height or
> > should the width and height be converted to pixels?
>
> Probably not, because XSLFO uses "in" as representation for
> the unit "inch", as in
>   content-height="7.5in"
>
>
> You can try to strip the "Inches" suffix, if it is fixed, and
> add the "in" in the XSLT. If the XML authors also use "1Inch"
> and/or "7.84inches" or something, you probably are in trouble.
>
> J.Pietschmann
>

At 2007-01-31 16:48 +0000, mina_hurray wrote:
>I have graphic and a box below that. There is a gap between the box and
>the graphic. How do I fill that up? i tried using padding but it did
>not work. Please let me know.

You don't show your XSL-FO which would help a lot if you did so.

Remember that a graphic is an inline object, and hence it sits on the
dominant baseline of your line.  I warn my XSL-FO students that this
will give the effect of a "superscripted" image, or in your case, a
gap between the image and the line below.

If you use alignment-baseline="after-edge" on your graphic, that will
drop the graphic from the dominant baseline to the after edge of the line.

I hope this helps.

. . . . . . . . . . Ken


--
World-wide corporate, govt. & user group XML, XSL and UBL training
RSS feeds:     publicly-available developer resources and training
G. Ken Holman                 mailto:gkholman@...
Crane Softwrights Ltd.          http://www.CraneSoftwrights.com/f/
Box 266, Kars, Ontario CANADA K0A-2E0    +1(613)489-0999 (F:-0995)
Male Cancer Awareness Aug'05  http://www.CraneSoftwrights.com/f/bc
Legal business disclaimers:  http://www.CraneSoftwrights.com/legal

--- In XSL-FO@yahoogroups.com, "mina_hurray" <mina_hurray@...> wrote:
>
> Hi all:
>
> I have graphic and a box below that. There is a gap between the box
and
> the graphic. How do I fill that up? i tried using padding but it did
> not work. Please let me know.
>
> Thank you.
>
Hi Meena
Please try using the different options of " alignment-baseline "
attribute on your graphic , I think it should work for you .

Thanks
Mpillai

mina_hurray wrote:
> Thank you for your response. Is it better then to convert the
> measuments from inches to Pixels using dpi of 75? How do I set the
> dpi?

I don't understand the purpose of this approach.
In most cases, image dimensions shouldn't be measured in pixels.
Inches are fine.

J.Pietschmann

Hi,

I'm have a dictionary style running heads that displays the title of the
active article in the page and the last article in the page using this
fo instruction:

<fo:retrieve-marker retrieve-class-name="header"
retrieve-boundary="page" retrieve-position="first-including-carryover"/>
— <fo:retrieve-marker retrieve-class-name="header"
retrieve-boundary="page" retrieve-position="last-starting-within-page"/>

When my page only contains a single article, my header will return the
title of the article twice separated by the em dash, which is normal by
following the instructions above. What I want, however, is to output
only the article title once without the em dash if the page contains
only one article and when there are two or more articles present in the
page, i want them displayed as first article em dash second article.

Thanks,
--
*Jeff Sese*

At 2007-02-01 15:33 +0800, Jeff Sese wrote:
>I'm have a dictionary style running heads that displays the title of the
>active article in the page and the last article in the page using this
>fo instruction:
>
><fo:retrieve-marker retrieve-class-name="header"
>retrieve-boundary="page" retrieve-position="first-including-carryover"/>
>— <fo:retrieve-marker retrieve-class-name="header"
>retrieve-boundary="page" retrieve-position="last-starting-within-page"/>
>
>When my page only contains a single article, my header will return the
>title of the article twice separated by the em dash, which is normal by
>following the instructions above. What I want, however, is to output
>only the article title once without the em dash if the page contains
>only one article and when there are two or more articles present in the
>page, i want them displayed as first article em dash second article.

There is no way to conditionally retrieve content ... you get what
you get by the class name, boundary and position, but you can't
arbitrate what you get when there are multiple markers, nor can you
test the absence of a marker.

You can get closer to what you want if you retrieve two separate
parts of the header, the bit at the start and then the bit at the
end, with the dash in the bit at the end.  But make the end marker
empty for the first entry.

The problem is on the last page when you get the last title twice ...
but I think you are closer to what you want.

I hope the example below helps.

. . . . . . . . . . . Ken

<?xml version="1.0" encoding="utf-8"?><!--marker6.fo-->
<root xmlns="http://www.w3.org/1999/XSL/Format"
        font-family="Times" font-size="20pt">

    <layout-master-set>
      <simple-page-master master-name="frame"
                          page-height="297mm" page-width="210mm"
                          margin-top="15mm" margin-bottom="15mm"
                          margin-left="15mm" margin-right="15mm">
        <region-body region-name="frame-body"
                     margin-bottom=".5cm" margin-top=".5cm"/>
        <region-before region-name="frame-before" extent=".5cm"/>
        <region-after region-name="frame-after" extent=".5cm"/>
      </simple-page-master>
    </layout-master-set>

<page-sequence master-reference="frame"
                xmlns="http://www.w3.org/1999/XSL/Format">
    <static-content flow-name="frame-before">
      <block>
        <retrieve-marker retrieve-class-name="header-start"
retrieve-boundary="page" retrieve-position="first-including-carryover"/>
        <retrieve-marker retrieve-class-name="header-end"
retrieve-boundary="page" retrieve-position="last-starting-within-page"/>
      </block>
    </static-content>

<flow flow-name="frame-body">
    <block space-after="3in" break-after="page">
      <marker marker-class-name="header-start">
        first
      </marker>
      <marker marker-class-name="header-end">

      </marker>
      Test
    </block>
    <block space-after="3in">
      <marker marker-class-name="header-start">
        second
      </marker>
      <marker marker-class-name="header-end">
        — second
      </marker>
      Test
    </block>
    <block space-after="3in">
      <marker marker-class-name="header-start">
        third
      </marker>
      <marker marker-class-name="header-end">
        — third
      </marker>
      Test
    </block>
    <block space-after="3in">
      <marker marker-class-name="header-start">
        fourth
      </marker>
      <marker marker-class-name="header-end">
        — fourth
      </marker>
      Test
    </block>
    <block space-after="3in">
      <marker marker-class-name="header-start">
        fifth
      </marker>
      <marker marker-class-name="header-end">
        — fifth
      </marker>
      Test
    </block>
    <block space-after="3in">
      <marker marker-class-name="header-start">
        sixth
      </marker>
      <marker marker-class-name="header-end">
        — sixth
      </marker>
      Test
    </block>
    <block space-after="3in">
      <marker marker-class-name="header-start">
        seventh
      </marker>
      <marker marker-class-name="header-end">
        — sevent
      </marker>
      Test
    </block>
    <block space-after="3in">
      <marker marker-class-name="header-start">
        eighth
      </marker>
      <marker marker-class-name="header-end">
        — eighth
      </marker>
      Test
    </block>
    <block space-after="3in">
      <marker marker-class-name="header-start">
        ninth
      </marker>
      <marker marker-class-name="header-end">
        — ninth
      </marker>
      Test
    </block>
    <block space-after="3in">
      <marker marker-class-name="header-start">
        tenth
      </marker>
      <marker marker-class-name="header-end">
        — tenth
      </marker>
      Test
    </block>

</flow></page-sequence>

</root>


--
World-wide corporate, govt. & user group XML, XSL and UBL training
RSS feeds:     publicly-available developer resources and training
G. Ken Holman                 mailto:gkholman@...
Crane Softwrights Ltd.          http://www.CraneSoftwrights.com/f/
Box 266, Kars, Ontario CANADA K0A-2E0    +1(613)489-0999 (F:-0995)
Male Cancer Awareness Aug'05  http://www.CraneSoftwrights.com/f/bc
Legal business disclaimers:  http://www.CraneSoftwrights.com/legal

Ken, I haven't tried your code yet but i think if i have a page like this:

page 1:       page 2:      page 3:
-------------  -------------  ------------
title0           some text    some text
some text    some text    some text
some text    some text    some text
title1           some text    some text
some text    some text    some text
some text    some text    title2
some text    some text    some text
-------------  -------------  ------------

It will still output the following headers:

page 1: title0-title1
page 2: title1-title1
page 3: title1-title2

But what i want is an output of:

page 1: title0-title1
page 2: title1
page 3: title1-title2

I tried this and i got the desired output, but i can seem to understand
how it happened.

<xsl:variable name="first" as="xs:string">
     <fo:retrieve-marker retrieve-class-name="header"
retrieve-boundary="page" retrieve-position="first-including-carryover"/>
</xsl:variable>
<xsl:variable name="last" as="xs:string">
     <fo:retrieve-marker retrieve-class-name="header"
retrieve-boundary="page" retrieve-position="last-starting-within-page"/>
</xsl:variable>
<fo:block>
     <xsl:choose>
         <xsl:when test="$first eq $last">
             <fo:retrieve-marker retrieve-class-name="header"
retrieve-boundary="page" retrieve-position="first-including-carryover"/>
         </xsl:when>
         <xsl:otherwise>
             <fo:retrieve-marker retrieve-class-name="header"
retrieve-boundary="page" retrieve-position="first-including-carryover"/>
— <fo:retrieve-marker retrieve-class-name="header"
retrieve-boundary="page" retrieve-position="last-starting-within-page"/>
         </xsl:otherwise>
     </xsl:choose>
</fo:block>

I tried outputting the content of the variable using xsl:message but i
get no output for their value:
<xsl:message>
     <xsl:copy-of select="$first"/>
     <xsl:copy-of select="$last"/>
</xsl:message>

Is my xslt above correct? It does give me the desired output though...
--
*Jeff Sese*

G. Ken Holman wrote:
>
> At 2007-02-01 15:33 +0800, Jeff Sese wrote:
> >I'm have a dictionary style running heads that displays the title of the
> >active article in the page and the last article in the page using this
> >fo instruction:
> >
> ><fo:retrieve-marker retrieve-class-name="header"
> >retrieve-boundary="page" retrieve-position="first-including-carryover"/>
> >— <fo:retrieve-marker retrieve-class-name="header"
> >retrieve-boundary="page" retrieve-position="last-starting-within-page"/>
> >
> >When my page only contains a single article, my header will return the
> >title of the article twice separated by the em dash, which is normal by
> >following the instructions above. What I want, however, is to output
> >only the article title once without the em dash if the page contains
> >only one article and when there are two or more articles present in the
> >page, i want them displayed as first article em dash second article.
>
> There is no way to conditionally retrieve content ... you get what
> you get by the class name, boundary and position, but you can't
> arbitrate what you get when there are multiple markers, nor can you
> test the absence of a marker.
>
> You can get closer to what you want if you retrieve two separate
> parts of the header, the bit at the start and then the bit at the
> end, with the dash in the bit at the end. But make the end marker
> empty for the first entry.
>
> The problem is on the last page when you get the last title twice ...
> but I think you are closer to what you want.
>
> I hope the example below helps.
>
> . . . . . . . . . . . Ken
>
> <?xml version="1.0" encoding="utf-8"?><!--marker6.fo-->
> <root xmlns="http://www.w3.org/1999/XSL/Format
> <http://www.w3.org/1999/XSL/Format>"
> font-family="Times" font-size="20pt">
>
> <layout-master-set>
> <simple-page-master master-name="frame"
> page-height="297mm" page-width="210mm"
> margin-top="15mm" margin-bottom="15mm"
> margin-left="15mm" margin-right="15mm">
> <region-body region-name="frame-body"
> margin-bottom=".5cm" margin-top=".5cm"/>
> <region-before region-name="frame-before" extent=".5cm"/>
> <region-after region-name="frame-after" extent=".5cm"/>
> </simple-page-master>
> </layout-master-set>
>
> <page-sequence master-reference="frame"
> xmlns="http://www.w3.org/1999/XSL/Format
> <http://www.w3.org/1999/XSL/Format>">
> <static-content flow-name="frame-before">
> <block>
> <retrieve-marker retrieve-class-name="header-start"
> retrieve-boundary="page" retrieve-position="first-including-carryover"/>
> <retrieve-marker retrieve-class-name="header-end"
> retrieve-boundary="page" retrieve-position="last-starting-within-page"/>
> </block>
> </static-content>
>
> <flow flow-name="frame-body">
> <block space-after="3in" break-after="page">
> <marker marker-class-name="header-start">
> first
> </marker>
> <marker marker-class-name="header-end">
>
> </marker>
> Test
> </block>
> <block space-after="3in">
> <marker marker-class-name="header-start">
> second
> </marker>
> <marker marker-class-name="header-end">
> — second
> </marker>
> Test
> </block>
> <block space-after="3in">
> <marker marker-class-name="header-start">
> third
> </marker>
> <marker marker-class-name="header-end">
> — third
> </marker>
> Test
> </block>
> <block space-after="3in">
> <marker marker-class-name="header-start">
> fourth
> </marker>
> <marker marker-class-name="header-end">
> — fourth
> </marker>
> Test
> </block>
> <block space-after="3in">
> <marker marker-class-name="header-start">
> fifth
> </marker>
> <marker marker-class-name="header-end">
> — fifth
> </marker>
> Test
> </block>
> <block space-after="3in">
> <marker marker-class-name="header-start">
> sixth
> </marker>
> <marker marker-class-name="header-end">
> — sixth
> </marker>
> Test
> </block>
> <block space-after="3in">
> <marker marker-class-name="header-start">
> seventh
> </marker>
> <marker marker-class-name="header-end">
> — sevent
> </marker>
> Test
> </block>
> <block space-after="3in">
> <marker marker-class-name="header-start">
> eighth
> </marker>
> <marker marker-class-name="header-end">
> — eighth
> </marker>
> Test
> </block>
> <block space-after="3in">
> <marker marker-class-name="header-start">
> ninth
> </marker>
> <marker marker-class-name="header-end">
> — ninth
> </marker>
> Test
> </block>
> <block space-after="3in">
> <marker marker-class-name="header-start">
> tenth
> </marker>
> <marker marker-class-name="header-end">
> — tenth
> </marker>
> Test
> </block>
>
> </flow></page-sequence>
>
> </root>
>
> --
> World-wide corporate, govt. & user group XML, XSL and UBL training
> RSS feeds: publicly-available developer resources and training
> G. Ken Holman mailto:gkholman@...
> <mailto:gkholman%40CraneSoftwrights.com>
> Crane Softwrights Ltd. http://www.CraneSoftwrights.com/f/
> <http://www.CraneSoftwrights.com/f/>
> Box 266, Kars, Ontario CANADA K0A-2E0 +1(613)489-0999 (F:-0995)
> Male Cancer Awareness Aug'05 http://www.CraneSoftwrights.com/f/bc
> <http://www.CraneSoftwrights.com/f/bc>
> Legal business disclaimers: http://www.CraneSoftwrights.com/legal
> <http://www.CraneSoftwrights.com/legal>
>
>
> ------------------------------------------------------------------------
>
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.5.432 / Virus Database: 268.17.18/662 - Release Date: 1/31/2007
3:16 PM
>

The page layout got distorted:

page 1:
------------
title0
some text
some text
title1
some text
some text
some text
------------
page 2:
------------
some text
some text
some text
some text
some text
some text
some text
------------
page 3:
------------
some text
some text
some text
some text
some text
title2
some text
------------

*Jeff Sese*

Jeff Sese wrote:
>
> Ken, I haven't tried your code yet but i think if i have a page like this:
>
> page 1: page 2: page 3:
> ------------- ------------- ------------
> title0 some text some text
> some text some text some text
> some text some text some text
> title1 some text some text
> some text some text some text
> some text some text title2
> some text some text some text
> ------------- ------------- ------------
>
> It will still output the following headers:
>
> page 1: title0-title1
> page 2: title1-title1
> page 3: title1-title2
>
> But what i want is an output of:
>
> page 1: title0-title1
> page 2: title1
> page 3: title1-title2
>
> I tried this and i got the desired output, but i can seem to understand
> how it happened.
>
> <xsl:variable name="first" as="xs:string">
> <fo:retrieve-marker retrieve-class-name="header"
> retrieve-boundary="page" retrieve-position="first-including-carryover"/>
> </xsl:variable>
> <xsl:variable name="last" as="xs:string">
> <fo:retrieve-marker retrieve-class-name="header"
> retrieve-boundary="page" retrieve-position="last-starting-within-page"/>
> </xsl:variable>
> <fo:block>
> <xsl:choose>
> <xsl:when test="$first eq $last">
> <fo:retrieve-marker retrieve-class-name="header"
> retrieve-boundary="page" retrieve-position="first-including-carryover"/>
> </xsl:when>
> <xsl:otherwise>
> <fo:retrieve-marker retrieve-class-name="header"
> retrieve-boundary="page" retrieve-position="first-including-carryover"/>
> — <fo:retrieve-marker retrieve-class-name="header"
> retrieve-boundary="page" retrieve-position="last-starting-within-page"/>
> </xsl:otherwise>
> </xsl:choose>
> </fo:block>
>
> I tried outputting the content of the variable using xsl:message but i
> get no output for their value:
> <xsl:message>
> <xsl:copy-of select="$first"/>
> <xsl:copy-of select="$last"/>
> </xsl:message>
>
> Is my xslt above correct? It does give me the desired output though...
> --
> *Jeff Sese*
>
> G. Ken Holman wrote:
> >
> > At 2007-02-01 15:33 +0800, Jeff Sese wrote:
> > >I'm have a dictionary style running heads that displays the title
> of the
> > >active article in the page and the last article in the page using this
> > >fo instruction:
> > >
> > ><fo:retrieve-marker retrieve-class-name="header"
> > >retrieve-boundary="page"
> retrieve-position="first-including-carryover"/>
> > >— <fo:retrieve-marker retrieve-class-name="header"
> > >retrieve-boundary="page"
> retrieve-position="last-starting-within-page"/>
> > >
> > >When my page only contains a single article, my header will return the
> > >title of the article twice separated by the em dash, which is normal by
> > >following the instructions above. What I want, however, is to output
> > >only the article title once without the em dash if the page contains
> > >only one article and when there are two or more articles present in the
> > >page, i want them displayed as first article em dash second article.
> >
> > There is no way to conditionally retrieve content ... you get what
> > you get by the class name, boundary and position, but you can't
> > arbitrate what you get when there are multiple markers, nor can you
> > test the absence of a marker.
> >
> > You can get closer to what you want if you retrieve two separate
> > parts of the header, the bit at the start and then the bit at the
> > end, with the dash in the bit at the end. But make the end marker
> > empty for the first entry.
> >
> > The problem is on the last page when you get the last title twice ...
> > but I think you are closer to what you want.
> >
> > I hope the example below helps.
> >
> > . . . . . . . . . . . Ken
> >
> > <?xml version="1.0" encoding="utf-8"?><!--marker6.fo-->
> > <root xmlns="http://www.w3.org/1999/XSL/Format
> <http://www.w3.org/1999/XSL/Format>
> > <http://www.w3.org/1999/XSL/Format <http://www.w3.org/1999/XSL/Format>>"
> > font-family="Times" font-size="20pt">
> >
> > <layout-master-set>
> > <simple-page-master master-name="frame"
> > page-height="297mm" page-width="210mm"
> > margin-top="15mm" margin-bottom="15mm"
> > margin-left="15mm" margin-right="15mm">
> > <region-body region-name="frame-body"
> > margin-bottom=".5cm" margin-top=".5cm"/>
> > <region-before region-name="frame-before" extent=".5cm"/>
> > <region-after region-name="frame-after" extent=".5cm"/>
> > </simple-page-master>
> > </layout-master-set>
> >
> > <page-sequence master-reference="frame"
> > xmlns="http://www.w3.org/1999/XSL/Format
> <http://www.w3.org/1999/XSL/Format>
> > <http://www.w3.org/1999/XSL/Format
> <http://www.w3.org/1999/XSL/Format>>">
> > <static-content flow-name="frame-before">
> > <block>
> > <retrieve-marker retrieve-class-name="header-start"
> > retrieve-boundary="page" retrieve-position="first-including-carryover"/>
> > <retrieve-marker retrieve-class-name="header-end"
> > retrieve-boundary="page" retrieve-position="last-starting-within-page"/>
> > </block>
> > </static-content>
> >
> > <flow flow-name="frame-body">
> > <block space-after="3in" break-after="page">
> > <marker marker-class-name="header-start">
> > first
> > </marker>
> > <marker marker-class-name="header-end">
> >
> > </marker>
> > Test
> > </block>
> > <block space-after="3in">
> > <marker marker-class-name="header-start">
> > second
> > </marker>
> > <marker marker-class-name="header-end">
> > — second
> > </marker>
> > Test
> > </block>
> > <block space-after="3in">
> > <marker marker-class-name="header-start">
> > third
> > </marker>
> > <marker marker-class-name="header-end">
> > — third
> > </marker>
> > Test
> > </block>
> > <block space-after="3in">
> > <marker marker-class-name="header-start">
> > fourth
> > </marker>
> > <marker marker-class-name="header-end">
> > — fourth
> > </marker>
> > Test
> > </block>
> > <block space-after="3in">
> > <marker marker-class-name="header-start">
> > fifth
> > </marker>
> > <marker marker-class-name="header-end">
> > — fifth
> > </marker>
> > Test
> > </block>
> > <block space-after="3in">
> > <marker marker-class-name="header-start">
> > sixth
> > </marker>
> > <marker marker-class-name="header-end">
> > — sixth
> > </marker>
> > Test
> > </block>
> > <block space-after="3in">
> > <marker marker-class-name="header-start">
> > seventh
> > </marker>
> > <marker marker-class-name="header-end">
> > — sevent
> > </marker>
> > Test
> > </block>
> > <block space-after="3in">
> > <marker marker-class-name="header-start">
> > eighth
> > </marker>
> > <marker marker-class-name="header-end">
> > — eighth
> > </marker>
> > Test
> > </block>
> > <block space-after="3in">
> > <marker marker-class-name="header-start">
> > ninth
> > </marker>
> > <marker marker-class-name="header-end">
> > — ninth
> > </marker>
> > Test
> > </block>
> > <block space-after="3in">
> > <marker marker-class-name="header-start">
> > tenth
> > </marker>
> > <marker marker-class-name="header-end">
> > — tenth
> > </marker>
> > Test
> > </block>
> >
> > </flow></page-sequence>
> >
> > </root>
> >
> > --
> > World-wide corporate, govt. & user group XML, XSL and UBL training
> > RSS feeds: publicly-available developer resources and training
> > G. Ken Holman mailto:gkholman@...
> <mailto:gkholman%40CraneSoftwrights.com>
> > <mailto:gkholman%40CraneSoftwrights.com>
> > Crane Softwrights Ltd. http://www.CraneSoftwrights.com/f/
> <http://www.CraneSoftwrights.com/f/>
> > <http://www.CraneSoftwrights.com/f/
> <http://www.CraneSoftwrights.com/f/>>
> > Box 266, Kars, Ontario CANADA K0A-2E0 +1(613)489-0999 (F:-0995)
> > Male Cancer Awareness Aug'05 http://www.CraneSoftwrights.com/f/bc
> <http://www.CraneSoftwrights.com/f/bc>
> > <http://www.CraneSoftwrights.com/f/bc
> <http://www.CraneSoftwrights.com/f/bc>>
> > Legal business disclaimers: http://www.CraneSoftwrights.com/legal
> <http://www.CraneSoftwrights.com/legal>
> > <http://www.CraneSoftwrights.com/legal
> <http://www.CraneSoftwrights.com/legal>>
> >
> >
> > ----------------------------------------------------------
> >
> > No virus found in this incoming message.
> > Checked by AVG Free Edition.
> > Version: 7.5.432 / Virus Database: 268.17.18/662 - Release Date:
> 1/31/2007 3:16 PM
> >
>
>
> ------------------------------------------------------------------------
>
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.5.432 / Virus Database: 268.17.18/662 - Release Date: 1/31/2007
3:16 PM
>

At 2007-02-01 17:02 +0800, Jeff Sese wrote:
>Ken, I haven't tried your code yet but i think if i have a page like this:

Well, I don't have the time to make *more* test data for your
requirements, so if you haven't tried the code I took the time to
suggest then I won't bother trying it either.

>I tried this and i got the desired output,

Then why did you post in your first message that you had a problem?

>but i can seem to understand how it happened.

I do not see why you have added complexity in your code.

><xsl:variable name="first" as="xs:string">
>     <fo:retrieve-marker retrieve-class-name="header"
>retrieve-boundary="page" retrieve-position="first-including-carryover"/>
></xsl:variable>
><xsl:variable name="last" as="xs:string">
>     <fo:retrieve-marker retrieve-class-name="header"
>retrieve-boundary="page" retrieve-position="last-starting-within-page"/>
></xsl:variable>
><fo:block>
>     <xsl:choose>
>         <xsl:when test="$first eq $last">

You have bound two specified sequence constructors to variables as
strings and then compared them.  Each string is empty. They will
always return the same result and will be considered equal.  How did
you think they were going to vary?

>I tried outputting the content of the variable using xsl:message but i
>get no output for their value:
><xsl:message>
>     <xsl:copy-of select="$first"/>
>     <xsl:copy-of select="$last"/>
></xsl:message>

Both variables are cast as strings and they are both empty, hence you
get their empty value.

>Is my xslt above correct?

"correct" for what purpose?  It does seem nonsensical to cast empty
string values and then compare them.

>It does give me the desired output though...

Well, I cannot see how, since your comparison of two empty strings
will always produce a "true" and you won't see the dash.  But since
you are seeing the dash, then I don't understand where you got your
snippet, or some other information is missing.

Remember that the XSL-FO process is arms-length from the XSLT
process.  There is no feedback loop.  There is *nothing* you can test
in your XSLT that is the result of any condition of formatting in your XSL-FO.

. . . . . . . . . . . . . Ken

--
World-wide corporate, govt. & user group XML, XSL and UBL training
RSS feeds:     publicly-available developer resources and training
G. Ken Holman                 mailto:gkholman@...
Crane Softwrights Ltd.          http://www.CraneSoftwrights.com/f/
Box 266, Kars, Ontario CANADA K0A-2E0    +1(613)489-0999 (F:-0995)
Male Cancer Awareness Aug'05  http://www.CraneSoftwrights.com/f/bc
Legal business disclaimers:  http://www.CraneSoftwrights.com/legal

Thank you for your input. I shall retain the measurment in Inches.


--- In XSL-FO@yahoogroups.com, "J.Pietschmann" <j3322ptm@...> wrote:
>
> mina_hurray wrote:
> > Thank you for your response. Is it better then to convert the
> > measuments from inches to Pixels using dpi of 75? How do I set the
> > dpi?
>
> I don't understand the purpose of this approach.
> In most cases, image dimensions shouldn't be measured in pixels.
> Inches are fine.
>
> J.Pietschmann
>