Re: Trouble embbeding fonts
I've found the error! MANY HOURS WERE LOST, BUT I'VE FOUND IT. Thanks for help me!!! And for check my config files were ok. Trouble was in XSL used to generate, the error was so simple that i'd assumed that XSL was ok. FOP was and is operating ok. Thanks for all - Original Message - From: Chris Bowditch [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, June 30, 2004 5:19 PM Subject: Re: Trouble embbeding fonts Israel Romero Fijo wrote: Hi!!! I'm trying to config Fop for embedding my fonts, but obviously don't do it. Font embedding works for True Type Fonts in PDF. Your code and user config file look okay. Why do you think Font embedding hasnt worked? Is there an error message during rendering or does the output look wrong. Please describe your problem more precisely and we will try to help you. snip/ Chris - 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]
Font ttf - xml - java
Hi, Thanks to the mailing list, I succeded in using the 3Of9 codebar font. I ve created the 3of9.xml file with ttfReader.java. Then I ve updated my userconfig.xml and execute fop in command line as this : fop -cd font/usercongif.xml -xmltoto.xml -xsl toto.xsl -pdf toto.pdf. That s all right. But I want to integrate my fonts in my java project that already can create pdf and rtf with fop and thebase fonts. As I don t want to have my own fop.jar + (3of9.ttf + 3of9.xml+ etc...) andI want all myfiles in my fop.jar, I want to create my own font 3of9.JAVAsuch as Helvetica.java It first seemedeasy, because I saw in the header of helvetica.java : "this file was generated by font-file.xsl. Here is the probleme, 1. I ve tried the xsl file on the helvetica.xml include in fop, and the result seems light ( there is width[0x41] = 667 ) compare to the helvetica.java that is given in fop. 2. Even if the first problem is not one, my own helvetica.xml created with the ttfReader.java has not the same structure and the tags are differents, so the font-file.xsl will never work with my own xml files. Here is what is written in the header of the xsl file This files writes the class files for the fonts (Courier.java, Helvetica.java etc.). It uses the information in the font description files (Courier.xml, Helvetica.xml) to thisIn these font description files each character is referenced by its adobe name: char name="A" width="667"/To resolve this name and to find the code for this character it looks up the adobe name in thefile charlist.xml and extracts the WinAnsi code.. But my xml file has no char name="A" width="667"/ it looks like : ?xml version="1.0" encoding="UTF-8" ? - font-metrics type="TYPE0" font-nameArial/font-name embed / cap-height715/cap-height x-height518/x-height ascender905/ascender descender-211/descender - bbox left-664/left bottom-324/bottom right2000/right top1005/top /bbox flags32/flags stemv0/stemv italicangle0/italicangle subtypeTYPE0/subtype - multibyte-extras cid-typeCIDFontType2/cid-type default-width0/default-width - bfranges bf us="32" ue="126" gi="3" / bf us="160" ue="160" gi="3" / bf us="161" ue="161" gi="163" / bf us="162" ue="163" gi="132" / bf us="164" ue="164" gi="862" / bf us="165" ue="165" gi="150" / . /bfranges - cid-widths start-index="0" wx w="750" / wx w="0" / wx w="277" / wx w="277" / wx w="277" / wx w="354" / wx w="556" / wx w="556" / wx w="889" / /cid-widths /multibyte-extras - kerning kpx1="543" pair kpx2="543" kern="-26" / pair kpx2="528" kern="-26" / pair kpx2="305" kern="-26" / /kerning /font-metrics Thanks for your help !!! Edouard Créez GRATUITEMENT votre Yahoo! Mail avec 100 Mo de stockage ! Créez votre Yahoo! Mail Dialoguez en direct avec vos amis grâce à Yahoo! Messenger !
Re: fo:marker initial child error
Here is a sample table cell from the xalan processor (I stripped out almost anything that might cause an issue): fo:table-row fo:table-cell fo:marker marker-class-name=bill_of_ladingRBHZamp;P00111/fo:markerfo:marker marker-class-name=carrier/fo:marker marker-class-name=vesselVoyage//fo:marker /fo:table-cell /fo:table-row I get the following errors: [ERROR]: fo:marker must be an initial child,and 'marker-class-name' must be unique for same parent [ERROR]: fo:marker must be an initial child,and 'marker-class-name' must be unique for same parent It looks like the first marker is OK, but anything after that generates the error. Anything stand out? -Lou J.Pietschmann [EMAIL PROTECTED] To: [EMAIL PROTECTED] de cc: Subject: Re: fo:marker initial child error 06/27/2004 18:01 Please respond to fop-user [EMAIL PROTECTED] wrote: I'm having a problem with my markers in fop 0.20.3. The marker data displays correctly in the PDF, but I get a log full of the following message: 1088163278596 - ERROR [fop]:fo:marker must be an initial child,and 'marker-class-name' must be unique for same parent The most common reason for the must be an initial child message is that there is whitespace before the marker. Your code snippet doesn't give hints for this though. Try to run the XSL transformation standalone and check the result. J.Pietschmann - 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: fo:marker initial child error
On Jul 1, 2004, at 7:57 AM, [EMAIL PROTECTED] wrote: Here is a sample table cell from the xalan processor (I stripped out almost anything that might cause an issue): fo:table-row fo:table-cell fo:marker marker-class-name=bill_of_ladingRBHZamp;P00111/fo:markerfo: marker marker-class-name=carrier/fo:marker marker-class-name=vesselVoyage//fo:marker /fo:table-cell /fo:table-row I get the following errors: [ERROR]: fo:marker must be an initial child,and 'marker-class-name' must be unique for same parent [ERROR]: fo:marker must be an initial child,and 'marker-class-name' must be unique for same parent It looks like the first marker is OK, but anything after that generates the error. Anything stand out? -Lou Since they must be unique, they can only be on the page once. I don't know what you're trying to do, but the way I use them is to place a Continued on next page item. My solution was to place the marker at the *end* of my document--you could place yours after the table (the table-footer probably wouldn't work since it needs to be unique): fo:page-sequence master-reference=repeating force-page-count=no-force fo:static-content flow-name=xsl-region-before fo:block padding=0pt xsl:use-attribute-sets=attributes_DEFAULT xsl:call-template name=tmpHeader/ /fo:block /fo:static-content fo:static-content flow-name=xsl-region-after fo:block xsl:use-attribute-sets=attributes_DEFAULT xsl:call-template name=tmpFooter/ /fo:block /fo:static-content fo:flow flow-name=xsl-region-body fo:block xsl:use-attribute-sets=attributes_DEFAULT xsl:call-template name=tmpBody/ fo:block padding=0pt font-size=1pt fo:marker marker-class-name=table-continued/ /fo:block /fo:block /fo:flow /fo:page-sequence Then I call it like this: !-- REGION-AFTER: tmpFooter TEMPLATE -- xsl:template name=tmpFooter fo:block padding-left=18pt fo:table border=0pt padding-bottom=0pt padding-right=0pt padding-before=4pt table-layout=fixed fo:table-column column-width=20cm/ fo:table-body fo:table-row fo:table-cell text-align=left padding-left=6pt fo:block text-align=left font-weight=bold fo:retrieve-marker retrieve-class-name=table-continued retrieve-position=last-starting-within-page retrieve-boundary=page/ /fo:block /fo:table-cell /fo:table-row /fo:table-body /fo:table /fo:block .. /xsl:template Hope this information is useful... Web Maestro Clay p.s. Also, I suspect markers were improved in fop-0.20.4 fop-0.20.5. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: fo:marker initial child error
[EMAIL PROTECTED] wrote: Here is a sample table cell from the xalan processor (I stripped out almost anything that might cause an issue): fo:table-row fo:table-cell fo:marker I'd suspect the line feed before the fo:marker might cause the problem. Every marker will trigger this. I also suggest to put the markers into a fo:block in the cell (there must be at least one anyway, I vaguely remember problems if a marker was an immediate child of a fo:table-row or fo:table-cell. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: fo:marker initial child error
OK, I can get it to work if I manually remove the carriage returns and place the marker inside an inline: fo:inlinefo:marker marker-class-name=marker__bill_of_ladingRBHZamp;P00111/fo:marker/fo:inline fo:inlinefo:marker marker-class-name=marker__carrier//fo:inline However, xalan will not let me do this. When run the code through it, I get: fo:inline fo:marker marker-class-name=marker__bill_of_ladingRBHZamp;P00111/fo:marker /fo:inline fo:inline fo:marker marker-class-name=marker__carrier/ /fo:inline Which generates the error. It looks like I might have to move this discussion to the xalan group or try to implement what Clay showed on an earlier thread. -Lou J.Pietschmann [EMAIL PROTECTED] To: [EMAIL PROTECTED] de cc: Subject: Re: fo:marker initial child error 07/01/2004 13:13 Please respond to fop-user [EMAIL PROTECTED] wrote: Here is a sample table cell from the xalan processor (I stripped out almost anything that might cause an issue): fo:table-row fo:table-cell fo:marker I'd suspect the line feed before the fo:marker might cause the problem. Every marker will trigger this. I also suggest to put the markers into a fo:block in the cell (there must be at least one anyway, I vaguely remember problems if a marker was an immediate child of a fo:table-row or fo:table-cell. J.Pietschmann - 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: fo:marker initial child error
[EMAIL PROTECTED] wrote: OK, I can get it to work if I manually remove the carriage returns and place the marker inside an inline: ... However, xalan will not let me do this. The line feed probably comes from the input. Check whether xsl:strip-space elemets=*, or a better selection of elements, fixes this. If this doesn't help, or discards whitespace elsewhere, refine the template which generates the FO containing the markers. Otherwise, check whether you've set indent=yes in the xsl:output element, although this shouldn't have an effect if you run FOP with the xml+xsl command line. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Adobe Type Manager
I'm not sure I would call this a bug, but some might find this information useful regardless. I install my postscript fonts using Adobe Type Manager. FOP was able to use these fonts just fine. But when I tried to embed SVG text, the output came out in some default font like Arial. When I uninstalled the font from ATM and installed it natively in Win2K, the SVG text came out with the correct font. Is this the Way It Must Be Done(TM), or is there some way I can continue using ATM? -Adam - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Auto-sized block?
On Wed, 30 Jun 2004, Richard Evans wrote: I want to have a block of text with a border and background colour which is just wide enough for the text. The only solution I can think of involves having either a transform or simple program run through the XML font metric file and assess the width + kerning of your text to come up with an appropriate width for your block container. -Adam - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Auto-sized block?
Richard Evans wrote: I want to have a block of text with a border and background colour which is just wide enough for the text. Ive tried fo:block with border and background-color attributes but the block always seems to extend across the whole page. You need to use fo:inline or fo:inline-container for what you want. Unfortunately these elements have not been implemented properly, i.e. border and background color do not apply, and fo:inline is functionally the same as fo:wrapper. Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
