Re: Barcode-line on a page....

2002-01-30 Thread fred redf

Hi,

Maybe you should have a look at iText java library. I
use it myself to add some static content on every page
of a document after fop processing.

Dref.


--- [EMAIL PROTECTED] a écrit :  
 thanks...
 
 but one solution shows me many more problems... :(
 My margins must be set to 0 now (leftmargin) and
 that screws up my whote
 document.
 anyway... thank you
 
 
 
 Jochen Maes
 EDP departement
 Programmeur
 
 KBC-Securities
 Havenlaan 16
 1080 Brussel
 
 Tel : 02/429.96.81
 Fax : 02/429.17.48
 E-mail : [EMAIL PROTECTED]
 

**
 
 This message is for the named person's use only. It
 may contain
 confidential, proprietary or legally privileged
 information. You must not,
 directly or indirectly, use, disclose, distribute,
 print, or copy any part
 of this message if you are not the intended
 recipient. KBC Securities
 reserves the right to monitor all e-mail
 communications through its
 networks. Any views expressed in this message are
 those of the individual
 sender, except where the message states otherwise
 and the sender is
 authorised to state them to be the views of any such
 entity.

**
 
 
 
 

 Edmond Pugnale  
 

 edmond.pugnale@fluTo:  
   [EMAIL PROTECTED]

 xmedia.fr cc:  
 

 Sent by:  
 Subject: Re: Barcode-line on a page 
  
 [EMAIL PROTECTED] 
 

 pes.fr  
 

 
 

 
 

 29-01-02 09:00 PM   
 

 Please respond to   
 

 fop-dev 
 

 
 

 
 

 
 
 
 
 [EMAIL PROTECTED] wrote:
 
  Now i need to be able to say (but then in FOP
 language)
  print a line here: 14.2(x from), 220(y from), 51(x
 to), 220(y to) the
 line
  must be 1 pt thick or 2 points whatever...
 
 If you want to draw horizontal or vertical lines,
 you can add flat block-containers inside appropriate
 static-content element :
 
   fo:static-content flow-name=first-before
 ...
 fo:block-container left=(x from)
 top=(y from)
width=(y width)
height=0
 position=absolute
 border-after-width=2pt
   
 border-after-style=solid/
 ...
   /fo:static-content
 
 
 Ed
 

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

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

___
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.fr

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




FO to MIF spécifications

2002-01-30 Thread Arnaud Malguy

Hi,

Because you have a MIF output in FOP, i wonder if you have some
specifications about the mapping between
MIF element and correponding FO tags or attributes. I have to implement
a MIF to FO
transcoder in my actual project. It helps me a lot and perhaps i could
help you with my results, once my project done.
Thanks in advance.

Arnaud.


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




Re: Barcode-line on a page....

2002-01-30 Thread Jochen . Maes


iTextJava


hmm if it reads/writes PDF it can be interesting
thanks...


Jochen Maes
EDP departement
Programmeur

KBC-Securities
Havenlaan 16
1080 Brussel

Tel : 02/429.96.81
Fax : 02/429.17.48
E-mail : [EMAIL PROTECTED]

**

This message is for the named person's use only. It may contain
confidential, proprietary or legally privileged information. You must not,
directly or indirectly, use, disclose, distribute, print, or copy any part
of this message if you are not the intended recipient. KBC Securities
reserves the right to monitor all e-mail communications through its
networks. Any views expressed in this message are those of the individual
sender, except where the message states otherwise and the sender is
authorised to state them to be the views of any such entity.
**


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




Re: Barcode-line on a page....

2002-01-30 Thread fred redf

iText does not allow you to decompile a pdf but you
can copy the whole content of one page of a
preexisting pdf to another then add your static
content. 
Dref.


--- [EMAIL PROTECTED] a écrit :  
 iTextJava
 
 
 hmm if it reads/writes PDF it can be interesting
 thanks...
 
 
 Jochen Maes
 EDP departement
 Programmeur
 
 KBC-Securities
 Havenlaan 16
 1080 Brussel
 
 Tel : 02/429.96.81
 Fax : 02/429.17.48
 E-mail : [EMAIL PROTECTED]
 

**
 
 This message is for the named person's use only. It
 may contain
 confidential, proprietary or legally privileged
 information. You must not,
 directly or indirectly, use, disclose, distribute,
 print, or copy any part
 of this message if you are not the intended
 recipient. KBC Securities
 reserves the right to monitor all e-mail
 communications through its
 networks. Any views expressed in this message are
 those of the individual
 sender, except where the message states otherwise
 and the sender is
 authorised to state them to be the views of any such
 entity.

**
 
 

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

___
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.fr

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




Re: out of memory exception in java ?

2002-01-30 Thread Joerg Pietschmann

Nick Winger [EMAIL PROTECTED] wrote:
 the footer is displayed is every page, but it overrides the text in the
 table...
 that means, the table doesn't stop at the region-after section...

You have to declare the body region properly in your page-master
so that it doesn't extend into the region-after.
For example
fo:simple-page-master master-name=content
  margin-top=6mm
  margin-bottom=0mm
  ...
  fo:region-body margin-top=25mm margin-bottom=20mm/
  fo:region-after extent=15mm/
/fo:simple-page-master
This means roughly
--   page top
^
|  margin-top of the page (6mm)
v
--
^
|  margin-top of region body (25mm)
v
--
^
|  region-body (size depends on page-height)
v
-x
^  -
|  margin-bottom of region body (20 mm) ^
|   | region after (15mm)
v   v
-x --
^
|  margin-bottom of the page (0mm)
v
--  page bottom

The XSLFO spec has nicer graphics.

 other question:
 what is a page-sequence ?
A sequence of pages. You can define static content for a page sequence
to put into regions defined in the page-master(s) for that sequence. You
can select a starting page number. The processor will generate a page,
take text defined in the fo:flow in the sequence, put as much as
possible/sensible onto the page, and if there is text left in the flow it
will start another page until it runs aout of text.

The XSLFO spec has a more detailed description of everything.

 can i have multiple page-sequences in one pdf file (fo-file)
Yes. Be aware that a new page sequence always starts at the top of a new
page.
It is not uncommon to have different page sequences for TOCs, indexes,
colophons, title pages, abstracts and some people create one for each
chapter/appendix. This is also a strategy to reduce total memory
consumption of FOP and the risk of running out of memory.

 because let's say i have 3 tables in one pdf file fo-file)
 and every page where there is a different table should have
 a different static-content flow-name=xsl-region-after
 ( every table a different footer... )
That's one of the most common reason to have several page sequences.

Furthermore:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] wrote:
  fo:block font-size=10pt font-family=Arialn
xsl:text___/xsl:text
  /fo:block
Wouldn't you use fo:leader for generating rules?
Also, it shouldn't be necessary to generate a footnote,
  fo:static-content flow-name=xsl-region-after
 fo:block
  fo:external-graphic src=stuff.jgp/
 /fo:block
  /fo:static-content
works just fine. I regularly put SVG into headers and footers. For
laout, it may be easier to use a blind table rather than a weird
combination of nested fo:inlines and fo:blocks.

HTH
J.Pietschmann

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




Re: Barcode-line on a page....

2002-01-30 Thread Joerg Pietschmann

[EMAIL PROTECTED] wrote:
 but one solution shows me many more problems... :(
 My margins must be set to 0 now (leftmargin) and that screws up my whote
 document.

You can define margins on the body region, where the text
flow goes. Define a region-start appropriately, where the
static-content is placed.
If you need marks alternatively on the left and right margin
(for books), use repeatable-page-master-alternatives.
There is more about this in the spec, for example at
 http://www.w3.org/TR/xsl/slice6.html#fo_simple-page-master
Note: Reading and understanding specs is the price to pay
for becoming a guru...

HTH
J.Pietschmann

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




Re: [ANNOUNCEMENT] FOP 0.20.3 Release Candidate available

2002-01-30 Thread Peter B. West



Arved Sandstrom wrote:

Hi, Peter

I've included an attachment which is a tree listing of what I obtained with
wget.

Please review and let me know what I missed. Thanks.


Arved,

All of the html-docs stuff is redundant as far as the docs build is 
concerned - it will all be generated.  It was only there because I 
wanted to check that the html geneartion was working.  What you need is 
the xml-fop/docs/alt.design directory and all of its contents.  The 
xml-fop/build.xml.diff patch file must be applied to xml-fop/build.xml 
(the build.xml in the directory structure below has the patch applied). 
 Same for xml-fop/docs/xml-docs/fop.xml.diff.  Once those patches are 
applied, and the xml-fop/docs/alt.design directory is established and 
populated, the build target 'htmldoc' should generate the html files.

Peter




xml-fop
|   build.xml
|   build.xml.diff
|   
docs

  |---alt.design
  |
  |   **Everything under here needs to be collected**
  |

|---xml-docs
|   fop.xml
|   fop.xml.diff
|   
html-docs

  Everything under html-docs will be generated in the 
full build





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




Please help, even if it's just a reply that it can't be done

2002-01-30 Thread Scott Moore

I cross-posted this several days ago and didn't get a single reply.  If
someone could please let me know what the problem is, I would greatly
appreciate it.  Even if it means that my SVG cannot use defs in FOP.

Is the problem in my XSL-FO?
Is the problem in my SVG?
Is the problem with Batik?
Is the problem with FOP?

I figure it's got to be one of the above.

Thanks very much,
Scott

PS. What version of Batik comes with FOP 0.20.3rc?


- Original Message -
From: Scott Moore
To: FOP User
Sent: Friday, January 25, 2002 10:43 AM
Subject: SVG Problem with FOP


I'm trying to embed the following SVG into my XSL-FO and run it thru
FOP (0.20.3rc).  Although the SVG looks fine using Adobe's SVG viewer and
Batik's viewer, I get an
error (below) from FOP.  Apparently, it doesn't like the url() reference
to the radialGradient.  How can I get this to work?

Thanks for any help,
Scott


svg width=3.5in height=1in viewBox=0 0 680 200 xmlns=
http://www.w3.org/2000/svg http://www.w3.org/2000/svg 
preserveAspectRatio=none
 g
  defs
   radialGradient id=PurpleToWhite gradientUnits=objectBoundingBox
cx=.5 cy=.5 r=.5
stop offset=5% stop-color=white/
stop offset=100% stop-color=rgb(100,0,100)/
   /radialGradient
  /defs
  rect fill=black stroke=black x=0 y=0 width=680
height=200/
  circle r=80 cx=270 cy=100 fill=url(#PurpleToWhite)/
  text font-family=Times font-size=135pt x=213 y=160
fill=whiteD/text
 /g
/svg


An I/O error occured while processing the URI
'file:D:/Projects/Dev/#PurpleToWhite' specified on the element circle
org.apache.batik.bridge.BridgeException: file:D:/Projects/Dev/:-1
An I/O error occured while processing the URI
'file:D:/Projects/Dev/#PurpleToWhite' specified on the element circle
at
org.apache.batik.bridge.BridgeContext.getReferencedElement(Unknown So
urce)
at org.apache.batik.bridge.PaintServer.convertURIPaint(Unknown
Source)
at org.apache.batik.bridge.PaintServer.convertPaint(Unknown
Source)
at org.apache.batik.bridge.PaintServer.convertFillPaint(Unknown
Source)
at
org.apache.batik.bridge.PaintServer.convertFillAndStroke(Unknown Sour
ce)
at
org.apache.batik.bridge.SVGShapeElementBridge.createShapePainter(Unkn
own Source)
at
org.apache.batik.bridge.SVGShapeElementBridge.buildGraphicsNode(Unkno
wn Source)
at org.apache.batik.bridge.GVTBuilder.buildGraphicsNode(Unknown
Source)
at org.apache.batik.bridge.GVTBuilder.buildComposite(Unknown
Source)
at org.apache.batik.bridge.GVTBuilder.buildGraphicsNode(Unknown
Source)
at org.apache.batik.bridge.GVTBuilder.buildComposite(Unknown
Source)
at org.apache.batik.bridge.GVTBuilder.build(Unknown Source)
at
org.apache.fop.render.pdf.PDFRenderer.renderSVGDocument(PDFRenderer.j
ava:413)
at
org.apache.fop.render.pdf.PDFRenderer.renderSVGArea(PDFRenderer.java:
382)
at org.apache.fop.svg.SVGArea.render(SVGArea.java:58)
at
org.apache.fop.render.pdf.PDFRenderer.renderForeignObjectArea(PDFRend
erer.java:366)
at
org.apache.fop.layout.inline.ForeignObjectArea.render(ForeignObjectAr
ea.java:50)
at
org.apache.fop.render.AbstractRenderer.renderLineArea(AbstractRendere
r.java:223)
at org.apache.fop.layout.LineArea.render(LineArea.java:163)
at
org.apache.fop.render.AbstractRenderer.renderBlockArea(AbstractRender
er.java:192)
at org.apache.fop.layout.BlockArea.render(BlockArea.java:82)
at
org.apache.fop.render.AbstractRenderer.renderAreaContainer(AbstractRe
nderer.java:158)
at
org.apache.fop.render.pdf.PDFRenderer.renderPage(PDFRenderer.java:735
)
at
org.apache.fop.render.pdf.PDFRenderer.render(PDFRenderer.java:700)
at
org.apache.fop.apps.StreamRenderer.queuePage(StreamRenderer.java:217)

at org.apache.fop.layout.AreaTree.addPage(AreaTree.java:81)
at
org.apache.fop.fo.pagination.PageSequence.format(PageSequence.java:30
7)
at
org.apache.fop.apps.StreamRenderer.render(StreamRenderer.java:200)
at
org.apache.fop.fo.FOTreeBuilder.endElement(FOTreeBuilder.java:182)
at
org.apache.fop.tools.DocumentReader.parse(DocumentReader.java:463)
at org.apache.fop.apps.Driver.render(Driver.java:481)
at org.apache.fop.apps.Driver.render(Driver.java:501)
at org.apache.fop.apps.Driver.run(Driver.java:552)






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




Re: 0.20.3rc bug

2002-01-30 Thread Elliotte Rusty Harold

Hello all,
   I have not posted any bugs before and don't really know the formal
procedure yet, and I haven't seen this brought up by anyone else either.
I have a stylesheet which produces an fo file with two fo:page-sequences.
It produces pdf's correctly with version =0.20.2rc.  With 0.20.3.rc it
produces the message:
   master-reference for fo:page-sequence matches no simple-page-master or
page-sequence-master

It seems that there is something wrong with the new version since I clearly
have two page-sequence-master s with the same names as the two
page-sequences.

No. There is something wrong with your stylesheet. Specifically, you 
are using the syntax from the XSL Proposed Recommednation rather than 
the syntax from the XSL 1.0 Recommmendation. The name of this 
attribute changed between the two. 0.20.3 supports the final syntax, 
not the earlier draft syntax. YOu need to change a master-name 
attribute to a master-reference attribute on the fo:page-sequence.
-- 

+---++---+
| Elliotte Rusty Harold | [EMAIL PROTECTED] | Writer/Programmer |
+---++---+
|  The XML Bible, 2nd Edition (Hungry Minds, 2001)   |
|  http://www.ibiblio.org/xml/books/bible2/  |
|   http://www.amazon.com/exec/obidos/ISBN=0764547607/cafeaulaitA/   |
+--+-+
|  Read Cafe au Lait for Java News:  http://www.cafeaulait.org/  |
|  Read Cafe con Leche for XML News: http://www.ibiblio.org/xml/ |
+--+-+

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




RE: 0.20.3rc bug

2002-01-30 Thread Matthew L. Avizinis

lol -- smack forehead
thanks much,
matthew a

 -Original Message-
 From: Elliotte Rusty Harold [mailto:[EMAIL PROTECTED]]
 Sent: Wednesday, January 30, 2002 3:19 PM
 To: [EMAIL PROTECTED]
 Subject: Re: 0.20.3rc bug


 Hello all,
I have not posted any bugs before and don't really know the formal
 procedure yet, and I haven't seen this brought up by anyone else either.
 I have a stylesheet which produces an fo file with two fo:page-sequences.
 It produces pdf's correctly with version =0.20.2rc.  With 0.20.3.rc it
 produces the message:
master-reference for fo:page-sequence matches no simple-page-master or
 page-sequence-master
 
 It seems that there is something wrong with the new version
 since I clearly
 have two page-sequence-master s with the same names as the two
 page-sequences.

 No. There is something wrong with your stylesheet. Specifically, you
 are using the syntax from the XSL Proposed Recommednation rather than
 the syntax from the XSL 1.0 Recommmendation. The name of this
 attribute changed between the two. 0.20.3 supports the final syntax,
 not the earlier draft syntax. YOu need to change a master-name
 attribute to a master-reference attribute on the fo:page-sequence.
 --

 +---++---+
 | Elliotte Rusty Harold | [EMAIL PROTECTED] | Writer/Programmer |
 +---++---+
 |  The XML Bible, 2nd Edition (Hungry Minds, 2001)   |
 |  http://www.ibiblio.org/xml/books/bible2/  |
 |   http://www.amazon.com/exec/obidos/ISBN=0764547607/cafeaulaitA/   |
 +--+-+
 |  Read Cafe au Lait for Java News:  http://www.cafeaulait.org/  |
 |  Read Cafe con Leche for XML News: http://www.ibiblio.org/xml/ |
 +--+-+

 -
 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: [PATCH] Proper use of font encodings for native fonts

2002-01-30 Thread Rainer Garus

References:

[1] http://marc.theaimsgroup.com/?l=fop-devm=100559770232644w=2
[2] http://marc.theaimsgroup.com/?l=fop-devm=100790930100949w=2
[3] http://marc.theaimsgroup.com/?l=fop-devm=100386481704186w=2

In fop 0.20.x unicode characters with value greater 256 not represented in the font 
are substituted with the character '#'. With the patch [1] all characters not 
represented in the font are substituted. This makes a problem in 
LineArea.getCharWidth. Because the line feed character has no glyph the width of the 
line feed is computed to the width of the '#' character and is unequal to the space 
character. This is the reason for the second problem described in [2].

Attached is a simple patch for fop 0.20.3RC to solve the problem. The patch from Peter 
[1](together with the two updates) can now entered in cvs in the maintenance branch.

The patch [1](together with the first update in [2]) should be entered in cvs in the 
main branch. The design is easier to understand and the patch solves some design 
problems [3]. The attached patch (second update) is not necessary for the main branch 
in the moment. I think it is better to wait until the patch is in cvs and then to 
change the interface of the font subsystem. If a character is not contained in a font, 
the font subsystem should generate an exception. The area tree builder can then decide 
to substitute the character or to print a warning message.

Rainer Garus

--- Fop-0.20.3rc/src/org/apache/fop/layout/LineArea.javaSat Jan 19 17:15:36 
2002
+++ Fop1/src/org/apache/fop/layout/LineArea.javaWed Jan 30 19:46:52 2002
@@ -1235,51 +1235,53 @@
  * versions of space that might not exists in the font.
  */
 private int getCharWidth(char c) {
-int width = currentFontState.width(currentFontState.mapChar(c));
-if (width = 0) {
-// Estimate the width of spaces not represented in
-// the font
-int em = currentFontState.width(currentFontState.mapChar('m'));
-int en = currentFontState.width(currentFontState.mapChar('n'));
-if (em = 0)
-em = 500 * currentFontState.getFontSize();
-if (en = 0)
-en = em - 10;
+int width;
 
-if (c == ' ')
-width = em;
-if (c == '\u2000')
-width = en;
-if (c == '\u2001')
-width = em;
-if (c == '\u2002')
-width = em / 2;
-if (c == '\u2003')
-width = currentFontState.getFontSize();
-if (c == '\u2004')
-width = em / 3;
-if (c == '\u2005')
-width = em / 4;
-if (c == '\u2006')
-width = em / 6;
-if (c == '\u2007')
-width = getCharWidth(' ');
-if (c == '\u2008')
-width = getCharWidth('.');
-if (c == '\u2009')
-width = em / 5;
-if (c == '\u200A')
-width = 5;
-if (c == '\u200B')
-width = 100;
-if (c == '\u00A0')
-width = getCharWidth(' ');
-if (c == '\u202F')
-width = getCharWidth(' ') / 2;
-if (c == '\u3000')
-width = getCharWidth(' ') * 2;
-if ((c == '\n') || (c == '\r') || (c == '\t'))
-width = getCharWidth(' ');
+if ((c == '\n') || (c == '\r') || (c == '\t') || (c == '\u00A0')) {
+width = getCharWidth(' ');
+} else {
+width = currentFontState.width(currentFontState.mapChar(c));
+if (width = 0) {
+// Estimate the width of spaces not represented in
+// the font
+int em = currentFontState.width(currentFontState.mapChar('m'));
+int en = currentFontState.width(currentFontState.mapChar('n'));
+if (em = 0)
+em = 500 * currentFontState.getFontSize();
+if (en = 0)
+en = em - 10;
+
+if (c == ' ')
+width = em;
+if (c == '\u2000')
+width = en;
+if (c == '\u2001')
+width = em;
+if (c == '\u2002')
+width = em / 2;
+if (c == '\u2003')
+width = currentFontState.getFontSize();
+if (c == '\u2004')
+width = em / 3;
+if (c == '\u2005')
+width = em / 4;
+if (c == '\u2006')
+width = em / 6;
+if (c == '\u2007')
+width = getCharWidth(' ');
+if (c == '\u2008')
+width = getCharWidth('.');
+if (c == '\u2009')
+width = em / 5;
+if (c == '\u200A')
+  

RE: 0.20.3rc bug

2002-01-30 Thread Matthew L. Avizinis

OK.  I've read the CHANGES file and I see the error of my ways.
but now what's this?  I don't see anything about it and didn't get this
before either.  My fo file doesn't have this any in it at all, so why the
warning now?  All the table column widths are measured in mm, btw.
[WARN]: table-layout=auto is not supported, using fixed!
[WARN]: Sum of fixed column widths 507400 greater than maximum specified IPD
487
thanks,
   Matthew L. Avizinis mailto:[EMAIL PROTECTED]
Gleim Publications, Inc.
   4201 NW 95th Blvd.
 Gainesville, FL 32606
(352)-375-0772 ext. 101
  www.gleim.com http://www.gleim.com

===
com·put·ing (kum' pyoot ing)
1. n the art of calculating how much time you wasted and money you spent in
a doomed attempt to master a machine with a mind of it's own. --from
computing: A HACKER'S DICTIONARY


 -Original Message-
 From: Scott Moore [mailto:[EMAIL PROTECTED]]
 Sent: Wednesday, January 30, 2002 3:28 PM
 To: [EMAIL PROTECTED]
 Subject: Re: 0.20.3rc bug


 Change master-name to master-reference on your fo:page-sequence.  In this
 case, the error is correct and your FO is wrong.  The previous
 versions were
 written to the Candidate Recommendation and not the Oct 15th
 Recommendation
 which had that change.

 Scott


 - Original Message -
 From: Matthew L. Avizinis [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Sent: Wednesday, January 30, 2002 3:09 PM
 Subject: 0.20.3rc bug


  Hello all,
I have not posted any bugs before and don't really know the formal
  procedure yet, and I haven't seen this brought up by anyone else either.
  I have a stylesheet which produces an fo file with two
 fo:page-sequences.
  It produces pdf's correctly with version =0.20.2rc.  With 0.20.3.rc it
  produces the message:
master-reference for fo:page-sequence matches no simple-page-master or
  page-sequence-master
 
  It seems that there is something wrong with the new version since I
 clearly
  have two page-sequence-master s with the same names as the two
  page-sequences.
  thanks,
 Matthew L. Avizinis mailto:[EMAIL PROTECTED]
  Gleim Publications, Inc.
 4201 NW 95th Blvd.
   Gainesville, FL 32606
  (352)-375-0772 ext. 101
www.gleim.com http://www.gleim.com
 
  ===
  com·put·ing (kum' pyoot ing)
  1. n the art of calculating how much time you wasted and money you spent
 in
  a doomed attempt to master a machine with a mind of it's own. --from
  computing: A HACKER'S DICTIONARY
 
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, email: [EMAIL PROTECTED]
 


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


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




ZapfDingbats font

2002-01-30 Thread Dunning, John

When using 
fo:block font-family=ZapfDingbats
I get the following error message for the character reference
#x2713;/#10003;
[ERROR]: unknown font ZapfDingbats,normal,bold so defaulted font to any

but not for #x27AA;, which displays correctly. (XEP displays both
correctly). 

I have no idea how fonts work -- does the tool (FOP/XEP) embed a certain
font, or does Acrobat have these embedded within the application?  How might
I proceed to display this character (checkmark)?

Thanks in advance for any assistance,
John

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




Re: Help with footer only on first page - please help

2002-01-30 Thread ewitness - Ben Fowler

At 8:50 am +0200 25/1/02, [EMAIL PROTECTED] wrote:
Hi all,

Could someone please help me with the correct way to implement a footer only
on the first page?

I believe that you need to establish two sequences of master pages,
and use one (which has the footer) on the first page, and the
other for the remainder.

This might be an FAQ. You can certinly find helpful info
on the web exempli gratia
URL: http://www.dpawson.co.uk/xsl/sect3/headers.html 

Ben

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




RE: [PATCH] Proper use of font encodings for native fonts

2002-01-30 Thread Arved Sandstrom

Noted.

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Rainer Garus
Sent: January 30, 2002 5:18 PM
To: [EMAIL PROTECTED]
Subject: Re: [PATCH] Proper use of font encodings for native fonts


References:

[1] http://marc.theaimsgroup.com/?l=fop-devm=100559770232644w=2
[2] http://marc.theaimsgroup.com/?l=fop-devm=100790930100949w=2
[3] http://marc.theaimsgroup.com/?l=fop-devm=100386481704186w=2

In fop 0.20.x unicode characters with value greater 256 not represented in
the font are substituted with the character '#'. With the patch [1] all
characters not represented in the font are substituted. This makes a problem
in LineArea.getCharWidth. Because the line feed character has no glyph the
width of the line feed is computed to the width of the '#' character and is
unequal to the space character. This is the reason for the second problem
described in [2].

Attached is a simple patch for fop 0.20.3RC to solve the problem. The patch
from Peter [1](together with the two updates) can now entered in cvs in the
maintenance branch.

The patch [1](together with the first update in [2]) should be entered in
cvs in the main branch. The design is easier to understand and the patch
solves some design problems [3]. The attached patch (second update) is not
necessary for the main branch in the moment. I think it is better to wait
until the patch is in cvs and then to change the interface of the font
subsystem. If a character is not contained in a font, the font subsystem
should generate an exception. The area tree builder can then decide to
substitute the character or to print a warning message.

Rainer Garus


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