Re: Problems with PCL Output (Euro-Sign)
Martin Roob wrote: 2. There is no EURO-sign in the PCL Umm... how do I get the Euro-Sign anyway? That´s quite easy (thanks to unicode) Put a character #x20AC; in your fo-document, for example with the following template rule (transform a euro/-tag to a fo:inline-element: xsl:template name=euro !-- Die Blanks hinter dem Eurozeichen sind da, weil FOP 0.0.15 in Tabellenzellen das Eurozeichen zu schmal rechnet -- fo:inline white-space-collapse=false xsl:text#x20AC; /xsl:text /fo:inline /xsl:template Ulrich -- Ulrich Mayring DENIC eG, Systementwicklung - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Problems with PCL Output
Hello there, we are using FOP (0.20.1) to create PDF and PCL Documents on an OS/390 System. There PDF generation works great, the PCL generation works nearly great. There are 3 problems with PCL 1. Table borders are mixed up 2. There is no EURO-sign in the PCL 3. landscape mode is not working. We simply change width and height of the document to the values of DIN A4 landscape, which is ok for PDF, but the PCL printer does not rotate the pages, so the last 1/3 of each page is empty, but the right part is not on the page. Is there anyone who has any ideas what to do against these problems (or at least against one of them) ? Thanks in advance Martin Roob
Re: fop and VAJ 3.5.3
..you have to deselect the hook on the NullPointerException on the tab Exceptions in the VA Debugger. Otherwise, VA will stop in the debugger on every NPE, even if the NPE is handled later (which is the case in StringPool.ensureCapacity). Otherwise you have to press the resume button for about 1000 times. In my opinion it is no good style to generate NPEs and handle them instead of avoiding them, but that's how it is here. This makes it somewhat difficult to debug real NPEs. Martin - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, August 20, 2001 6:09 PM Subject: fop and VAJ 3.5.3 hi, does anyone know what to do to make FOP run in Visual Age for Java 3.5.3? I tried to import: 1. all java and resource files from Fop's src directory and 2. import xerces-1.2.3.jar, xalan-2.0.0.jar, batic.jar, jimi-1.0.jar But I still get a NullPointerExeption while generating a new sax parser instace in org.apache.fop.configuration.ConfigurationReader.createParser() the actual exception occures in StringPool.ensureCapacity(). See also the screenshot. On the other hand: I could also use Forte3.0 instead of VAJ 3.5.3. Using Forte, would it be easier to get FOP run in the Debugger: (I would like to debug the FOP sourcecode)? Bodo Teichmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
