simple query regarding PDF output using Turbo Styler

2003-01-15 Thread Chakraborty, Anshuman (BearingPoint)

Hi,
I am using ArborText's EPIC editor  Turbo Styler to generate XSL for a
certain XML file.
The final output is for PDF format. Now once the basic styling is done for
the paragraphs, sections etc. how do I set up the page layouts and related
attributes like margin areas, gutter area etc.

Thanks



**
The information in this email is confidential and may be legally
privileged.  Access to this email by anyone other than the
intended addressee is unauthorized.  If you are not the intended
recipient of this message, any review, disclosure, copying,
distribution, retention, or any action taken or omitted to be taken
in reliance on it is prohibited and may be unlawful.  If you are not
the intended recipient, please reply to or forward a copy of this
message to the sender and delete the message, any attachments,
and any copies thereof from your system.
**


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




Re: simple query regarding PDF output using Turbo Styler

2003-01-15 Thread Jeremias Maerki
I get the impression that you're in the wrong place. We can't help you
here with the EPIC editor or with Turbo Styler. I've never worked with
ArborText's tools, but don't they allow you already to generate PDFs?

FOP simply accepts XSL-FO as input an can produce various output formats
like PDF, PostScript etc.

If by XSL you mean XSL-FO then, of course, you should be able to produce
a PDF. If you mean an XSLT stylesheet to transform your XML format to
XSL-FO to then you're also in the right spot.

For things like page sizes, margins etc. have a look at the XSL-FO
specification or at one of the many tutorials on XSL-FO. There are also
example files in the FOP distribution that help you understand XSL-FO.

See here for links:
http://xml.apache.org/fop/resources.html

(Next time please post questions like these on the fop-user mailing list.
Thank you.)

On 15.01.2003 15:27:01 Chakraborty, Anshuman  (BearingPoint) wrote:
 I am using ArborText's EPIC editor  Turbo Styler to generate XSL for a
 certain XML file.
 The final output is for PDF format. Now once the basic styling is done for
 the paragraphs, sections etc. how do I set up the page layouts and related
 attributes like margin areas, gutter area etc.


Jeremias Maerki


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




Query!?

2002-11-06 Thread roopashree s
Hi,
I have arial.xml,arialbd.xml,ariali.xml,arialbi.xml,ariblk.xml under my Fop-0.18.1-DEV dir. But during the XML to PDF convertions through XSL using XSLT processor, i am facing problem. The FO with font-family "Arial" whichused is not displayed after the PDF conversion. Does the Windows-NT and /or UNIX support these FONT-FAMILY? If yes, whats the procedure? and which are the required files ?And where can I get them from?
Thanks.
Do you Yahoo!?
HotJobs - Search new jobs daily now

Re: Query!?

2002-11-06 Thread J.Pietschmann
roopashree s wrote:

I have arial.xml,arialbd.xml,ariali.xml,arialbi.xml,ariblk.xml under my 
Fop-0.18.1-DEV dir. But during the XML to PDF convertions through XSL 
using XSLT processor, i am facing problem. The FO with font-family 
Arial which used is not displayed after the PDF conversion. Does the 
Windows-NT and /or UNIX support these FONT-FAMILY? If yes, whats the 
procedure? and which are the required files ?And where can I get them from?

You have to produce a userconfig.xml file which declares the
fonts and use it with FOP. For more recent FOP versions this
procedure is described in the documentation distributed with
the binaries and the source, in docs/html-docs/fonts.html.
It is strongly recommended to upgrade to the latest FOP release
(0.20.4), the only exception being that you use the old API and
can't change.
The OS doesn't matter, except taht you probably can refer to the
font directory on Windows directly, while you'll have to download
the arial.ttf et al. files explicitely to the machine under Linux.

J.Pietschmann


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




Re: QUERY: Why doesn't PrintRenderer use the addLine routines for borders.

2001-08-19 Thread Karen Lease

Hello Struan,

It looks as though you must have changed addLine as well to add the
border-style, since that isn't in the current version (at least not the
one I got from CVS last night.)

I'm the one responsible for changing this code in doFrame because when
borders are drawn using lines in PDF, it didn't seem possible to avoid
pixel errors in the segment joins. This made for ugly table borders.

It's also true that the dashed border style is the only one which could
be (at least partially) handled using the PDF line operator. Due to the
fact that we the doFrame code draws four separate lines instead of
stroking a single path, I imagine that the the dashes are not going to
work great in all cases anyway.

However I understand that you may feel something is better than nothing.
Could you submit your modified addLine code as well? We will try to come
to some satisfactory solution.

(Sorry if you'd already done this; I've been away for a few days and
might have missed an earlier message in the stack I went through last
night.)

Regards,
Karen Lease

P.S. Also, I believe the 0.20.1 version of FOP should fix the problem
you reported in late July concerning vertical alignment in table-header
rows when the table was continued. If not, please let me (fop-dev) know!

Struan Judd wrote:
 
 Instead it uses the fillRect routines.
 
 Unfortunately, I needed to have a dashed border (in PDF's) and so put back
 (well not exactly hence the query) the old ways. Which seems to work fine
 (for me).
 
 If the reason for the change was that some of the other renderers couldn't
 cope, perhaps their addLine routines could be changed to redirect to the
 fillRect ones.
 
 In any case, could the other line styles please be restored to FOP-PDF.
 
 Here is the diff of org.apache.fop.render.PrintRenderer of what I've done
 (between the ''s):
 
 
 364c364,365
  addFilledRect(rx, ry, w, top,
 ---
  addLine(rx, ry, rx + w, ry, top,
bp.getBorderStyle(BorderAndPadding.TOP),
 365a367,369
  // addFilledRect(rx, ry, w, top,
  //   new
 PDFColor(bp.getBorderColor(BorderAndPadding.TOP)));
 
 367c371,372
  addFilledRect(rx - left, ry - h - bottom, left, h + top +
 bottom,
 ---
  addLine(rx, ry - h, rx, ry, left,
bp.getBorderStyle(BorderAndPadding.LEFT),
 368a374,376
  // addFilledRect(rx - left, ry - h - bottom, left, h + top +
 bottom,
  //   new
 PDFColor(bp.getBorderColor(BorderAndPadding.LEFT)));
 
 370c378,379
  addFilledRect(rx + w, ry - h - bottom, right, h + top +
 bottom,
 ---
  addLine(rx + w, ry - h, rx + w, ry, right,
bp.getBorderStyle(BorderAndPadding.RIGHT),
 371a381,383
  // addFilledRect(rx + w, ry - h - bottom, right, h + top +
 bottom,
  //   new
 PDFColor(bp.getBorderColor(BorderAndPadding.RIGHT)));
 
 373c385,386
  addFilledRect(rx, ry - h - bottom, w, bottom,
 ---
  addLine(rx, ry - h, rx + w, ry - h, bottom,
bp.getBorderStyle(BorderAndPadding.BOTTOM),
 374a388,389
  // addFilledRect(rx, ry - h - bottom, w, bottom,
  //   new
 PDFColor(bp.getBorderColor(BorderAndPadding.BOTTOM)));
 
 
 TTFN
 
 Struan Judd * And so it begins ...  ICQ: 4498196
 http://neongraal.sf.org.nz
 mailto:[EMAIL PROTECTED] Voicemail and Fax: +1 (201) 305-1011 x1006
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, email: [EMAIL PROTECTED]

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




Re: QUERY: Why doesn't PrintRenderer use the addLine routines for borders.

2001-08-19 Thread Karen Lease

Struan,

Oops, I hadn't noticed the second version of addLine taking the
ruleStyle since it wasn't being called in the doFrame stuff when I made
my change. Duhh.

The baseline alignment stuff is harder than the straight after align.
Our line-height calculations need to be right before we get into that,
so it's probably not coming up right away.

Cheers,
Karen

Struan Judd wrote:
 
 Karen,
 
 I figured that might be the reason.
 
 And yup, at the moment somthing is better than nothing.
 
 Also, Nope. No change to the addLine code was needed.
 I'm currently running the 0.20.1 release with only my patch to PrintRenderer
 as that's what we'll be deploying here so I haven't seen the current CVS but
 maybe there's been a change since then.
 
 and lastly, I haven't checked the vertical alignment issue as with what I'm
 doing display-align=after does not achieve the align to the last baseline
 for different sized font's across table cells, (Whew!) that I needed.
 
 Thanks anyway.
 
 TTFN
 
 Struan Judd * And so it begins ...  ICQ: 4498196
 http://neongraal.sf.org.nz
 mailto:[EMAIL PROTECTED] Voicemail and Fax: +1 (201) 305-1011 x1006


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




Re: QUERY: Why doesn't PrintRenderer use the addLine routines for borders.

2001-08-16 Thread Ralph LaChance

We will check whether any of the changes we made to AWTRenderer
(the -awt and -print options) should be reconsidered w/r/t/ the dashed
line style mentioned below.  I'm mostly on vacation and Andy is out of
town for the next week, so it'll be the Aug 25th before we can look at it.


At 09:27 AM 8/15/01 +1200, you wrote:

Instead it uses the fillRect routines.

Unfortunately, I needed to have a dashed border (in PDF's) and so put back
(well not exactly hence the query) the old ways. Which seems to work fine
(for me).

If the reason for the change was that some of the other renderers couldn't
cope, perhaps their addLine routines could be changed to redirect to the
fillRect ones.

In any case, could the other line styles please be restored to FOP-PDF.

Here is the diff of org.apache.fop.render.PrintRenderer of what I've done
(between the ''s):


364c364,365
 addFilledRect(rx, ry, w, top,
---
  addLine(rx, ry, rx + w, ry, top,
bp.getBorderStyle(BorderAndPadding.TOP),
365a367,369
  // addFilledRect(rx, ry, w, top,
  //   new
PDFColor(bp.getBorderColor(BorderAndPadding.TOP)));
 
367c371,372
 addFilledRect(rx - left, ry - h - bottom, left, h + top +
bottom,
---
  addLine(rx, ry - h, rx, ry, left,
bp.getBorderStyle(BorderAndPadding.LEFT),
368a374,376
  // addFilledRect(rx - left, ry - h - bottom, left, h + top +
bottom,
  //   new
PDFColor(bp.getBorderColor(BorderAndPadding.LEFT)));
 
370c378,379
 addFilledRect(rx + w, ry - h - bottom, right, h + top +
bottom,
---
  addLine(rx + w, ry - h, rx + w, ry, right,
bp.getBorderStyle(BorderAndPadding.RIGHT),
371a381,383
  // addFilledRect(rx + w, ry - h - bottom, right, h + top +
bottom,
  //   new
PDFColor(bp.getBorderColor(BorderAndPadding.RIGHT)));
 
373c385,386
 addFilledRect(rx, ry - h - bottom, w, bottom,
---
  addLine(rx, ry - h, rx + w, ry - h, bottom,
bp.getBorderStyle(BorderAndPadding.BOTTOM),
374a388,389
  // addFilledRect(rx, ry - h - bottom, w, bottom,
  //   new
PDFColor(bp.getBorderColor(BorderAndPadding.BOTTOM)));


TTFN

Struan Judd * And so it begins ...  ICQ: 4498196
http://neongraal.sf.org.nz
mailto:[EMAIL PROTECTED] Voicemail and Fax: +1 (201) 
305-1011 x1006


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


 ' Best,
 -Ralph LaChance



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