RE: align=justify in preformatting content

2004-12-07 Thread Yann Bonnaillie
Yes I could, but it won't be very nice, and it would take a very long
time to do that...
I hope there is another way to solve my problem :)

Thanks

Yann



  -Original Message-
  From: Yann Bonnaillie [mailto:[EMAIL PROTECTED]
 
 
 Hi,
 
  Well, I succeed to keep my new line after fop transformation,
  but now when I use text-align=justify on my fo:block, last line
  of each chapter (ie : before each new line) are expanded, what
  looks very bad.
 
 Hmmm... Not really sure how to solve this, but I think you could avoid this
 by terminating your DOM nodes at the newline character (or character
 sequence)... That way, you would generate a separate fo:block for each
 paragraph...?
 
 May be a long shot, but HTH!
 
 Greetz,
 
 Andreas


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



FOP distorting images

2004-12-07 Thread Saptarshi Sen
Hi,
I am trying to generate PDF images (charts with embedded fonts) using
FOP version 0.20.5.

We first generate a SVG image using a charting tool called PopChart
(version 5.1.0). We then create the 'fo' file from this SVG. This is finally
fed to FOP to generate the PDF.

In doing so, legends in the chart are overlapping - the chart is
getting cutoff on the right hand side.

The SVG image is actually fine - which leads me to believe that the
problem crops up at the 'fo to pdf' stage. Attached alongwith are the SVG and
FO files as well as the PDF generated using FOP.

Can anyone help me with this?

Thanks,
Saptarshi.

 1102408131024.fo  1102408131024.SVG  1102408131024_fop.pdf 


1102408131024.fo
Description: 1102408131024.fo


1102408131024.SVG
Description: 1102408131024.SVG


1102408131024_fop.pdf
Description: 1102408131024_fop.pdf
-
Disclaimer
-

This message(including attachment if any)is confidential and may be 
privileged.Before opening attachments please check them
for viruses and defects.MindTree Consulting Private Limited (MindTree)will not 
be responsible for any viruses or defects or
any forwarded attachments emanating either from within MindTree or outside.If 
you have received this message by mistake please notify the sender by return  
e-mail and delete this message from your system. Any unauthorized use or 
dissemination of this message in whole or in part is strictly prohibited.  
Please note that e-mails are susceptible to change and MindTree shall not be 
liable for any improper, untimely or incomplete transmission.

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

Re: FOP distorting images

2004-12-07 Thread Chris Bowditch
Saptarshi Sen wrote:
Hi,
I am trying to generate PDF images (charts with embedded fonts) using
FOP version 0.20.5.
We first generate a SVG image using a charting tool called PopChart
(version 5.1.0). We then create the 'fo' file from this SVG. This is finally
fed to FOP to generate the PDF.
In doing so, legends in the chart are overlapping - the chart is
getting cutoff on the right hand side.
The SVG image is actually fine - which leads me to believe that the
problem crops up at the 'fo to pdf' stage. Attached alongwith are the SVG and
FO files as well as the PDF generated using FOP.
Why couldnt the problem be with the SVG to FO conversion that you mention 
above?
snip/
Chris
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


RE: FOP distorting images

2004-12-07 Thread Saptarshi Sen
Hi Chris,
I think I have got the reason for the problem - it is a font issue.
The SVG created refers to the font 'CF TradeGothic CondEighteen Bold';
However, there is no such font declared in my userconfig.xml file.

I have attached my config file.

Regards,
Saptarshi.


-Original Message-
From: Chris Bowditch [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 07, 2004 7:28 PM
To: [EMAIL PROTECTED]
Subject: Re: FOP distorting images


Saptarshi Sen wrote:

 Hi,
   I am trying to generate PDF images (charts with embedded fonts) using
 FOP version 0.20.5.
 
   We first generate a SVG image using a charting tool called PopChart
 (version 5.1.0). We then create the 'fo' file from this SVG. This is
finally
 fed to FOP to generate the PDF.
 
   In doing so, legends in the chart are overlapping - the chart is
 getting cutoff on the right hand side.
 
   The SVG image is actually fine - which leads me to believe that the
 problem crops up at the 'fo to pdf' stage. Attached alongwith are the SVG
and
 FO files as well as the PDF generated using FOP.

Why couldnt the problem be with the SVG to FO conversion that you mention
above?

snip/

Chris


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

!--!DOCTYPE configuration SYSTEM config.dtd--
!--
 this file contains templates which allow an user easy
 configuration of Fop. Actually normally you don't need this configuration
 file, but if you need to change configuration, you should
 always use this file and *not* config.xml.
 Usage: java org.apache.fop.apps.Fop -c userconfig.xml -fo fo-file -pdf pdf-file
--


configuration

!--
baseDir: normally the base directory is the directory where the fo file is
 located. if you want to specify your own, uncomment this entry.
 This value can also be a URL. Actually, the value is converted to
 a URL.
--
!--
  entry
keybaseDir/key
value/value
  /entry
--

!--
fontBaseDir: Similar to baseDir, except that this value is used for fonts. If
 it isn't specified, the value from baseDir is used.
--
!--
  entry
keyfontBaseDir/key
value/value
  /entry
--

!--

HYPHENATION

--

!--
   hyphenation directory
   if you want to specify your own directory with hyphenation pattern
   then uncomment the next entry and add the directory name
--

!--
  entry
keyhyphenation-dir/key
value/java/xml-fop/hyph/value
  /entry
--



entry
   keystrokeSVGText/key
   valuefalse/value
/entry









!--

  Add fonts here

--

fonts
 !-- example --

 font metrics-file=TRADE_GOTHIC.xml kerning=yes embed-file=TRADE_GOTHIC.ttf
font-triplet name=TradeGothic style=normal weight=normal/
 /font
 font metrics-file=FUTURA_BOOK.xml kerning=yes embed-file=FUTURA_BOOK.ttf
font-triplet name=Futura Book style=normal weight=normal/
 /font
 font metrics-file=FUTURA_COND_LIGHT.xml kerning=yes embed-file=FUTURA_COND_LIGHT.ttf
font-triplet name=Futura CondensedLight style=normal weight=normal/
 /font
 font metrics-file=FUTURA_HEAVY.xml kerning=yes embed-file=FUTURA_HEAVY.ttf
font-triplet name=Futura Heavy style=normal weight=normal/
 /font
 font metrics-file=FUTURA_MEDIUM.xml kerning=yes embed-file=FUTURA_MEDIUM.ttf
font-triplet name=Futura Medium style=normal weight=normal/
 /font
 font metrics-file=TRADE_GOTHIC_BOLD.xml kerning=yes embed-file=TRADE_GOTHIC_BOLD.ttf
font-triplet name=TradeGothic Bold style=normal weight=normal/
 /font
 font metrics-file=TRADE_GOTHIC_BOLD_COND20.xml kerning=yes embed-file=TRADE_GOTHIC_BOLD_COND20.ttf
font-triplet name=TradeGothic CondEighteen style=normal weight=bold/
 /font
 font metrics-file=TRADE_GOTHIC_COND_18.xml kerning=yes embed-file=TRADE_GOTHIC_COND_18.ttf
font-triplet name=TradeGothic CondEighteen style=normal weight=normal/
 /font

 font metrics-file=times.xml kerning=yes embed-file=times.ttf
font-triplet name=TimesRoman style=normal weight=normal/
 /font
 font metrics-file=timesbold.xml kerning=yes embed-file=timesbd.ttf
font-triplet name=TimesRoman style=normal weight=bold/
 /font
 font metrics-file=timesitalic.xml kerning=yes embed-file=timesi.ttf
font-triplet name=TimesRoman style=italic weight=normal/
 /font
 font metrics-file=timesitalicbold.xml kerning=yes embed-file=timesbi.ttf
font-triplet name=TimesRoman style=italic weight=bold/
 /font

font metrics-file=arial.xml kerning=yes embed-file=arial.ttf
font-triplet name=Arial style=normal weight=normal/
 /font
 font metrics-file=arialbold.xml kerning=yes embed-file=arialbd.ttf
font-triplet 

RE: align=justify in preformatting content

2004-12-07 Thread Andreas L. Delmelle
 -Original Message-
 From: Yann Bonnaillie [mailto:[EMAIL PROTECTED]


Hi,

 Yes I could, but it won't be very nice, and it would take a very long
 time to do that...

Aaahh... Blasted laziness! What do you mean exactly by 'not very nice'?
AFAICT, it would be:
a) far more 'appropriate' to enclose each paragraph in a fo:block. This
neatly complies with the spec stating that
The fo:block formatting object is commonly used for formatting paragraphs,
...
http://www.w3.org/TR/xsl/slice6.html#fo_block
For special cases, like blocks of code, you can always insert a nested
fo:block that overrides the alignment properties from the parent fo:block
(--should work, apart from a few nasty side-effects in quite exotic cases)
b) it can't be *that* difficult to make a slight adjustment to the module
creating the DOMs to end the node and start a new one whenever the CR-LF
char sequence is encountered

The problem would solve itself, because instead of having to worry about it,
you just let the formatter do what it was meant to do...

 I hope there is another way to solve my problem :)

I'm afraid I can't think of any solutions that are 'nice' (in terms of
XSL-FO idioms) :-)

Greetz,

Andreas


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



Blank Page on Every Other Page

2004-12-07 Thread Jordan S. Jones
Help
So I have googled around, read documentation, looked at examples, and 
still I can't find an answer to my question that I am about to ask for 
the first time.

I have a table that, thus far spans 3 pages. I have my xslt/fo document 
so it has even/odd page sequencing, which works perfectly, but now I 
want to be able to have a blank page on every other page. Meaning, the 3 
pages of table data is 1 1/2 peices of paper, 1 - front and back, 2 - 
front. I want to be able to put a blank page in between each generated 
page. I hope this is making sense. From what I gathered most people are 
trying to avoid this and get rid of extra blank pages..

Any suggestions on how to fix this? or a better way of phrasing my needs?
Thanks
Jordan S. Jones
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]