transcoder.transcode destroys SVGCanvas

[rofl]

When I transcode a Batik SVGCanvas to pdf:
  transcoder.transcode(input, output);
where input is made with
  input = new TranscoderInput(document);
and output is a File stream, this leaves my SVGCanvas broken.
Every action yields NullPointerExceptions after that.
Any idea?

TIA,

 Robert


-- 
View this message in context: 
http://www.nabble.com/transcoder.transcode-destroys-SVGCanvas-tf2166414.html#a5989187
Sent from the FOP - Users forum at Nabble.com.


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

thanks and release of Word FO Designer

[Riz Virk]

Hi everyone,
 
I'd like to thank everyone on this list who helped in the beta testing cycle 
for our new "Word FO Designer" product, which allows you to use Microsoft Word 
to generate XSLT's which can produce PDF, RTF, and HTML from XML data without 
having to write XSLT's by hand.
 
We officially released the product this week - see press release below or click 
on the following if you're interested in learning more: 
http://www.cambridgedocs.com/products/downloads/WordFODesigner.htm 
 
Thanks again,
Riz
 

Rizwan Virk
CTO
CambridgeDocs
[EMAIL PROTECTED]
personal: [EMAIL PROTECTED]

 
  
Press Release   
NOW AVAILABLE - CambridgeDocs Word FO Designer   

Visual Design of XSL:FO and PDF for Multi-channel publishing


CambridgeDocs Announces Word FO Designer for Microsoft Word 
New plug-in for MS Word enables cross-platform, server-side, personalized, 
multi-channel publishing of XML content to PDF, RTF and HTML using XSL:FO.

Cambridge, MA - Aug 24, 2006 CambridgeDocs (www.cambridgedocs.com) an emerging 
leader in the field of unstructured data management and enterprise publishing, 
today announced the release of Word FO Designer, a new plug-in for Microsoft 
Word that allows organizations to easily add multi-channel publishing to their 
business applications. 

With this new capability, companies that publish large volumes of transactional 
documents and personalized correspondence, such as those in the insurance, 
financial services and healthcare industries, can dynamically custom-assemble 
documents for publication without having to manually maintain hundreds of 
document templates. Word FO Designer turns Microsoft Word into an authoring 
tool for creating electronic and print documents with no requirement to write 
custom code, thereby saving organizations thousands of dollars in development 
expense and enabling the creation of scalable, high- performance publishing 
applications in both Windows and UNIX environments.

Learn more and download. 

 

"We believe the Word FO Designer provides an effective way to map XML data to 
MS WORD document templates, that creates an efficient capability in our 
application to provide for automatic server-based generation of documents in 
the Health Care/Insurance space," said Loan Kenney, Senior Associate of 
Technology with Sapient Canada.

Visual Mapping of XML Data to PDF, HTML, and RTF
Examples of XML content that can be easily published using Word FO Designer 
include: 
* Personalized Correspondence
* Dynamic Reports
* Online Printable Forms
* Insurance Policies
* Press Releases


When used in conjunction with the CambridgeDocs xDoc Publishing Server, Word FO 
Designer allows organizations to generate Stylesheets from Microsoft Word 
documents. Based on the open w3c XSLT format, these Stylesheets can insert XML 
data into designated locations within Word documents and then dynamically 
populate their content, similar to a server-side Mail Merge.

"Our new tool turns Microsoft Word into a WYSIWYG designer for dynamic 
publishing applications. This allows organizations to implement multi-channel 
publishing without the expense of the many person- hours otherwise needed to 
write XSLT's and learn standards such as XSL:FO, " said Rizwan Virk, co- 
founder and CEO of CambridgeDocs. 

Word FO Designer also allows for inserting formatting control within templates 
through the use of ordinary Microsoft Word commands. Cross-platform server- 
based applications (written in either Java or .NET) can then call these 
document templates and include dynamic personalized multi-channel publishing 
within ordinary business processes.

The Word FO Designer is priced at $995 per copy, and is available for download 
immediately from CambridgeDocs website.

Learn More and Download the Word FO Designer 

 

About CambridgeDocs 

CambridgeDocs is a leader in the emerging market for XML-based content 
transformation and publishing. This market deals with the integration of legacy 
content with new XML-based systems (e.g. Content Management, Enterprise 
Information Portals, EAI, and Web Services) and standards (e.g. DocBook, DITA, 
HRXML, RIXML, FPML, NewsML, or any custom XML schema/DTD's, etc.). 

Towards this end, CambridgeDocs provides a technology platform & services for 
taking existing unstructured and semi-structured internal and external content 
(e.g. MS Word, HTML, PDF, Quark, etc.), and transforming it into "meaningful 
XML". Once transformed, the content can be made available for delivery through 
XML-based Web Services, aggregated, assembled and published in multiple 
different formats automatically.

W

Re: PDF Destinations

[Glen Mazza]

I agree with you too, the apparent RX/AH method of creating a 
destination for all "id"s seems very inefficient, possibly creating even 
security issues (theoretically, if one uses an id like an SSN next to 
the text giving data on a person but *without* the intention of the ID 
getting into the output PDF document, then mydoc.pdf#someSSN will open 
the document to the person's name.)  Also, AFAIK the XSL 1.1 Rec does 
not mandate us doing this for "id" anyway.  So having a fox:destination 
*property* in 0.9x instead of a fox:destination FO seems like a better idea.


Glen

Jeremias Maerki wrote:


Agreed, an extension property would be better than fox:destination, but
creating a destination for all "id" attributes doesn't sound ideal to me.

On 25.08.2006 16:11:34 Glen Mazza wrote:
 

I would prefer avoiding the use of fox:destination, as the XSL WG did 
not see a need for a separate FO for this when they placed bookmarks 
into 1.1.  Instead, I think it would be better to implement it the way 
the commercial processors handle them, which is I believe is relying 
either on the id on the element to be anchored or another property 
[1][2][3].  Relying on a property instead of a new FO would probably be 
easier/cleaner than introducing fox:destination back to the source code 
anyway, as there would be no XSL document validation issues to be 
checking for.


Glen

[1] http://sourceware.org/ml/docbook-apps/2005-q2/msg00214.html
[2] http://www.oasis-open.org/archives/docbook-apps/200602/msg00174.html
[3] http://sourceware.org/ml/docbook-apps/2005-q2/msg00216.html

Jeremias Maerki wrote:

   


Indeed, we had fox:destination in FOP 0.20.5 but this has not been
reimplemented, yet. Contributions are welcome as always. If you need
pointers, we're always eager to provide those to get you started.

On 24.08.2006 09:59:52 andyrob_24_7 wrote:


 


Is there a way to achieve destinations in a pdf (so you can link to a certain 
page), in FOP?

It seems this is not yet in 0.92?
   




Jeremias Maerki


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


 




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

Re: PDF Destinations

[Jeremias Maerki]

Agreed, an extension property would be better than fox:destination, but
creating a destination for all "id" attributes doesn't sound ideal to me.

On 25.08.2006 16:11:34 Glen Mazza wrote:
> I would prefer avoiding the use of fox:destination, as the XSL WG did 
> not see a need for a separate FO for this when they placed bookmarks 
> into 1.1.  Instead, I think it would be better to implement it the way 
> the commercial processors handle them, which is I believe is relying 
> either on the id on the element to be anchored or another property 
> [1][2][3].  Relying on a property instead of a new FO would probably be 
> easier/cleaner than introducing fox:destination back to the source code 
> anyway, as there would be no XSL document validation issues to be 
> checking for.
> 
> Glen
> 
> [1] http://sourceware.org/ml/docbook-apps/2005-q2/msg00214.html
> [2] http://www.oasis-open.org/archives/docbook-apps/200602/msg00174.html
> [3] http://sourceware.org/ml/docbook-apps/2005-q2/msg00216.html
> 
> Jeremias Maerki wrote:
> 
> >Indeed, we had fox:destination in FOP 0.20.5 but this has not been
> >reimplemented, yet. Contributions are welcome as always. If you need
> >pointers, we're always eager to provide those to get you started.
> >
> >On 24.08.2006 09:59:52 andyrob_24_7 wrote:
> >  
> >
> >>Is there a way to achieve destinations in a pdf (so you can link to a 
> >>certain page), in FOP?
> >>
> >>It seems this is not yet in 0.92?


Jeremias Maerki


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

Re: Image overflow

[Jeremias Maerki]

Well, FOP 0.20.5 did all sorts of not quite conformant things with
images. The new code is much more conformant to the spec. However, that
doesn't mean there's no room for improvement. Currently, there's no way
to scale down an image if there's not enough room to display it at full
size (using .minimum/.optimum/.maximum on block-progression-dimension
and inline-progression-dimension). XSL 1.1 introduces a few new
possibilities in this area but again, these are not implemented, yet.

What you can try is to use width="100%" and content-width="scale-to-fit"
but this will always scale an image to take up the full width of the
content area. Maybe you need to play a little with the properties
available.

If you have errors, you might also need to check if maybe some keep
constraints cause the error and not the image itself.

If you want more concrete help you'll need to post an example.


On 25.08.2006 14:45:12 Raphael Parree wrote:
> This might have been answered, but could only find something on this in the
> archive of 2003. I believe in the 0.20.5 release images that where to wide
> were scaled down. Many of my the content that used to end up in a successful
> transformed PDF, now break on not being able to fit the text on a page. Is
> my assumption right that in the 0.20.5 release it worked as described here,
> and is this something that can be turned on in the latest release?


Jeremias Maerki


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

Re: PDF Destinations

[Glen Mazza]

I would prefer avoiding the use of fox:destination, as the XSL WG did 
not see a need for a separate FO for this when they placed bookmarks 
into 1.1.  Instead, I think it would be better to implement it the way 
the commercial processors handle them, which is I believe is relying 
either on the id on the element to be anchored or another property 
[1][2][3].  Relying on a property instead of a new FO would probably be 
easier/cleaner than introducing fox:destination back to the source code 
anyway, as there would be no XSL document validation issues to be 
checking for.


Glen

[1] http://sourceware.org/ml/docbook-apps/2005-q2/msg00214.html
[2] http://www.oasis-open.org/archives/docbook-apps/200602/msg00174.html
[3] http://sourceware.org/ml/docbook-apps/2005-q2/msg00216.html

Jeremias Maerki wrote:


Indeed, we had fox:destination in FOP 0.20.5 but this has not been
reimplemented, yet. Contributions are welcome as always. If you need
pointers, we're always eager to provide those to get you started.

On 24.08.2006 09:59:52 andyrob_24_7 wrote:
 


Is there a way to achieve destinations in a pdf (so you can link to a certain 
page), in FOP?

It seems this is not yet in 0.92?
   





Jeremias Maerki


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


 




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

Re: javax.imageio.stream.MemoryCacheImageInputStream cannot be cast to java.io.InputStream

[Jeremias Maerki]

I cannot reproduce this. GIF images load just fine through the ImageIO
adapter on my machine.

Can you please state the JVM and version plus operating system you're
using? Maybe that narrows things down a little. A full stack trace of
the exception would also be very helpful.

On 24.08.2006 16:09:07 Nicolas Drosson wrote:
> Hi,
> 
> I am new to fop and am experiencing problems during the transformation
> from fo to pdf. I get the following message:
> 24. Aug 06 15:53:38 org.apache.fop.image.ImageIOImage loadBitmap
> SEVERE: Error while loading image:
> javax.imageio.stream.MemoryCacheImageInputStream cannot be cast to
> java.io.InputStream
> 
> I don't really have an idea of what is the problem or what I am doing
> wrong. Maybe someone can help me. The only I know is that images don't
> work. The resulting PDF file has frames instead of the image. 
> 
> Here is the FO-code I'm using of one of the images:
>   width="472px">
> src="url('zms_site_eigensch_link.gif')"
> role="html:img" border="1px solid" width="472px" height="111px"
> display="block"/>
>  
> 
> The image zms_site_eigensch_link.gif is in the same folder as the fo
> file and I'm using fop 0.92 beta.
> 
> Thx in advance for any help. Regards. Nico


Jeremias Maerki


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

Re: (Image)-Streams into pdf

[Jeremias Maerki]

If you're talking about supplying your own InputStreams for certain
images in an XSL-FO file, that's quite easy. Please take a look at the
ServletContextURIResolver which should give you an idea how you could do
this:
http://svn.apache.org/repos/asf/xmlgraphics/fop/trunk/src/java/org/apache/fop/servlet/ServletContextURIResolver.java

The FopServlet shows how to use a special URIResolver:
http://svn.apache.org/repos/asf/xmlgraphics/fop/trunk/src/java/org/apache/fop/servlet/FopServlet.java

In the example above we're mapping all URIs which start with
"servlet-context:" to fetch files (including images) from the
ServletContext. You can do something similar by defining your own
protocol prefix, like "myimage:" -> myimage:8723487.gif or whatever.

Is that what you need?

On 23.08.2006 15:07:09 Johannes Becker wrote:
> Hi,
> 
> I'm want to write (jpg)images from InputStreams into my Pdf. 
> 
> Is this possible with FOP 0.92?



Jeremias Maerki


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

Re: Font Symbol

[Jeremias Maerki]

On 25.08.2006 11:53:28 Chris Bowditch wrote:
> Andreas L Delmelle wrote:
> 
> > On Aug 25, 2006, at 00:11, Luis Ferro wrote:
> > 
> 
> 
> 
> > It doesn't seem too difficult to alter FontInfo.java to make it first  
> > look for a font with the same name/weight, but with default font-style.
> > 
> > Anyway, I'll give other devs a chance to chime in before I start  
> > fiddling with it. If no objections arise, I'll probably commit this  
> > small change during the weekend.
> 
> This change sounds like a good idea. If you decide to do it make sure 
> you update the message "replacing with default font" to reflect exactly 
> which font was used instead.

Well, it depends. :-) You could also say that you want to find a similar
font (PANOSE matching [1] which we don't have) but in the same variant,
i.e. italic in this case. It really depends what is more important to
you: that the font is similar but italic or that it's the same font but
you fall back to non-italic. That said, I'm ok with the change. It's
just that the decision should not be done just so.

[1] http://en.wikipedia.org/wiki/PANOSE


Jeremias Maerki


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

Re: PDF Destinations

[Jeremias Maerki]

Indeed, we had fox:destination in FOP 0.20.5 but this has not been
reimplemented, yet. Contributions are welcome as always. If you need
pointers, we're always eager to provide those to get you started.

On 24.08.2006 09:59:52 andyrob_24_7 wrote:
> Is there a way to achieve destinations in a pdf (so you can link to a certain 
> page), in FOP?
> 
> It seems this is not yet in 0.92?



Jeremias Maerki


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

Image overflow

[Raphael Parree]

Hi,

 

This might have been answered, but could only find
something on this in the archive of 2003. I believe in the 0.20.5 release images
that where to wide were scaled down. Many of my the content that used to end up
in a successful transformed PDF, now break on not being able to fit the text on
a page. Is my assumption right that in the 0.20.5 release it worked as
described here, and is this something that can be turned on in the latest
release?

 

Tx.,

 

Raphael

 

 

Re: Font Symbol

[Chris Bowditch]

Andreas L Delmelle wrote:


On Aug 25, 2006, at 00:11, Luis Ferro wrote:





It doesn't seem too difficult to alter FontInfo.java to make it first  
look for a font with the same name/weight, but with default font-style.


Anyway, I'll give other devs a chance to chime in before I start  
fiddling with it. If no objections arise, I'll probably commit this  
small change during the weekend.


This change sounds like a good idea. If you decide to do it make sure 
you update the message "replacing with default font" to reflect exactly 
which font was used instead.


Chris




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

Re: Font Symbol

[Chris Bowditch]

Luis Ferro wrote:


I've found a weird bug...


Its not weird and not a bug ;)



When i use the font "Symbol" (which is built it), all works well... except
if i try to use the "font-style='italic'" with it... it gives an error:

missing font (or something like that): 'Symbol, italic, 400' replacing with
default (or something like that).

Can others replicate the problem? (i sorted it out by forcing all symbols to
be "normal" but i think this should be sorted out)


Symbol, Normal is one of the built in 14 fonts.
Symbol, Italic is not!

Roughly list of 14 built in fonts is:

Times, Normal, Normal
Times, Bold, Normal
Times, Normal, Italic
Times, Bold, Italic
Helvetica, Normal, Normal
Helvetica, Bold, Normal
Helvetica, Normal, Italic
Helvetica, Bold, Italic
Courier, Normal, Normal
Courier, Bold, Normal
Courier, Normal, Italic
Courier, Bold, Italic
Symbol, Normal, Normal
ZapfDingbats, Normal, Normal



Chris




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