unknownFormattingObject

2011-07-19 Thread Bogusław Fries
Hi,

 

I am using FOP version 1.0

I got the following error

 

java.util.MissingResourceException: Can't find resource for bundle 
org.apache.fop.util.XMLResourceBundle, key 
org.apache.fop.fo.FOValidationEventProducer.unknownFormattingObject

 

When I am using FOP 0.95 - same data and same tranformation - there is no error.

 

How to diagnose it?

 

Regards

 
Bogusław Fries

DPD Polska Sp. z o.o. 
02-274 Warszawa, ul. Mineralna 15 
mobile: 502 777 254

bfr...@dpd.com.pl BLOCKED::mailto:bfr...@dpd.com.pl 



 

 



RE: unknownFormattingObject

2011-07-19 Thread Eric Douglas
Try attaching a sample so someone can reproduce it.



From: Boguslaw Fries [mailto:bfr...@dpd.com.pl] 
Sent: Tuesday, July 19, 2011 5:03 AM
To: fop-users@xmlgraphics.apache.org
Subject: unknownFormattingObject



Hi,

 

I am using FOP version 1.0

I got the following error

 

java.util.MissingResourceException: Can't find resource for bundle 
org.apache.fop.util.XMLResourceBundle, key 
org.apache.fop.fo.FOValidationEventProducer.unknownFormattingObject

 

When I am using FOP 0.95 - same data and same tranformation - there is no error.

 

How to diagnose it?

 

Regards

 
Bogusław Fries

DPD Polska Sp. z o.o. 
02-274 Warszawa, ul. Mineralna 15 
mobile: 502 777 254

bfr...@dpd.com.pl BLOCKED::mailto:bfr...@dpd.com.pl 



 

 



RE: unknownFormattingObject

2011-07-19 Thread Bogusław Fries
OK., it is:

 

?xml version=1.0 encoding=UTF-8?

!DOCTYPE xsl:stylesheet [

!ENTITY nbsp #160;

!ENTITY start #135;

!ENTITY stop #138;

!ENTITY tab #9;

!ENTITY crlf #13;#10;

!ENTITY bull #8226;

]

xsl:stylesheet version=2.0 

xmlns:fo=http://www.w3.org/1999/XSL/Format;

xmlns:xsl=http://www.w3.org/1999/XSL/Transform;

xmlns:barcode=http://barcode4j.krysalis.org/ns;

xsl:output encoding=UTF-8 indent=no/

xsl:strip-space elements=* /

 

xsl:template match=/

fo:root

fo:layout-master-set

fo:simple-page-master master-name=page-domestic 
page-height=279mm page-width=210mm margin-top=8mm margin-left=1cm 
margin-bottom=2mm margin-right=1cm

fo:region-body region-name=content margin-top=25mm/

fo:region-before region-name=header-domestic 
extent=15mm/

/fo:simple-page-master

/fo:layout-master-set

fo:page-sequence master-reference=page-domestic 
force-page-count=no-force

fo:static-content flow-name=header-domestic 

xsl:call-template name=ReportHeader /

/fo:static-content

fo:flow flow-name=content font-size=12pt

fo:block

content

/fo:block

/fo:flow

/fo:page-sequence

/fo:root

/xsl:template

 

xsl:template name=ReportHeader

fo:block

fo:table table-layout=fixed width=100%

fo:table-column column-width=20%/

fo:table-body

fo:table-row

fo:table-cell

fo:block text-align=center

fo:instream-foreign-object

barcode:barcode

xsl:attribute name=message

xsl:value-of select=123/

/xsl:attribute

barcode:intl2of5


barcode:height11mm/barcode:height


barcode:module-width0.375mm/barcode:module-width


barcode:wide-factor3.0/barcode:wide-factor


barcode:checksumadd/barcode:checksum

human-readable

placementbottom/placement

font-nameArial/font-name

font-size8pt/font-size


display-checksumtrue/display-checksum

/human-readable

/barcode:intl2of5

/barcode:barcode

/fo:instream-foreign-object

/fo:block

/fo:table-cell

/fo:table-row

/fo:table-body

/fo:table

/fo:block

/xsl:template

/xsl:stylesheet

 

And error:  java.util.MissingResourceException: Can't find resource for bundle 
org.apache.fop.util.XMLResourceBundle, key 
org.apache.fop.fo.FOValidationEventProducer.unknownFormattingObject

Of course the library  barcode4j-fop-ext-complete is attached.

When I used fop 0.95 everything is ok.

 

Regerds

 

Bogusław Fries



From: Eric Douglas [mailto:edoug...@blockhouse.com] 
Sent: Tuesday, July 19, 2011 1:47 PM
To: fop-users@xmlgraphics.apache.org
Subject: RE: unknownFormattingObject

 

Try attaching a sample so someone can reproduce it.

 



From: Boguslaw Fries [mailto:bfr...@dpd.com.pl] 
Sent: Tuesday, July 19, 2011 5:03 AM
To: fop-users@xmlgraphics.apache.org
Subject: unknownFormattingObject

Hi,

 

I am using FOP version 1.0

I got the following error

 

java.util.MissingResourceException: Can't find resource for bundle 
org.apache.fop.util.XMLResourceBundle, key 
org.apache.fop.fo.FOValidationEventProducer.unknownFormattingObject

 

When I am using FOP 0.95 - same data and same tranformation - there is no error.

 

How to diagnose it?

 

Regards

 
Bogusław Fries

DPD Polska Sp. z o.o. 
02-274 Warszawa, ul. Mineralna 15 
mobile: 502 777 254

bfr...@dpd.com.pl BLOCKED::mailto:bfr...@dpd.com.pl 

 

 



AW: unknownFormattingObject

2011-07-19 Thread Georg Datterl
Hi Bogusław,

Actually, Eric was talking about the fo-file. Can you post that?

Regards,

Georg Datterl

-- Kontakt --

Georg Datterl

Geneon media solutions gmbh
Gutenstetter Straße 8a
90449 Nürnberg

HRB Nürnberg: 17193
Geschäftsführer: Yong-Harry Steiert

Tel.: 0911/36 78 88 - 26
Fax: 0911/36 78 88 - 20

www.geneon.dehttp://www.geneon.de

Weitere Mitglieder der Willmy MediaGroup:

IRS Integrated Realization Services GmbH:
www.irs-nbg.dehttp://www.irs-nbg.de
Willmy PrintMedia GmbH:  www.willmy.dehttp://www.willmy.de
Willmy Consult  Content GmbH:   
www.willmycc.dehttp://www.willmycc.de

Von: Bogusław Fries [mailto:bfr...@dpd.com.pl]
Gesendet: Dienstag, 19. Juli 2011 14:11
An: fop-users@xmlgraphics.apache.org
Betreff: RE: unknownFormattingObject

OK., it is:

?xml version=1.0 encoding=UTF-8?
!DOCTYPE xsl:stylesheet [
!ENTITY nbsp #160;
!ENTITY start #135;
!ENTITY stop #138;
!ENTITY tab #9;
!ENTITY crlf #13;#10;
!ENTITY bull #8226;
]
xsl:stylesheet version=2.0
xmlns:fo=http://www.w3.org/1999/XSL/Format;
xmlns:xsl=http://www.w3.org/1999/XSL/Transform;
xmlns:barcode=http://barcode4j.krysalis.org/ns;
xsl:output encoding=UTF-8 indent=no/
xsl:strip-space elements=* /

xsl:template match=/
fo:root
fo:layout-master-set
fo:simple-page-master master-name=page-domestic 
page-height=279mm page-width=210mm margin-top=8mm margin-left=1cm 
margin-bottom=2mm margin-right=1cm
fo:region-body region-name=content margin-top=25mm/
fo:region-before region-name=header-domestic 
extent=15mm/
/fo:simple-page-master
/fo:layout-master-set
fo:page-sequence master-reference=page-domestic 
force-page-count=no-force
fo:static-content flow-name=header-domestic 
xsl:call-template name=ReportHeader /
/fo:static-content
fo:flow flow-name=content font-size=12pt
fo:block
content
/fo:block
/fo:flow
/fo:page-sequence
/fo:root
/xsl:template

xsl:template name=ReportHeader
fo:block
fo:table table-layout=fixed width=100%
fo:table-column column-width=20%/
fo:table-body
fo:table-row
fo:table-cell
fo:block text-align=center
fo:instream-foreign-object
barcode:barcode
xsl:attribute name=message
xsl:value-of select=123/
/xsl:attribute
barcode:intl2of5

barcode:height11mm/barcode:height

barcode:module-width0.375mm/barcode:module-width

barcode:wide-factor3.0/barcode:wide-factor

barcode:checksumadd/barcode:checksum
human-readable
placementbottom/placement
font-nameArial/font-name
font-size8pt/font-size

display-checksumtrue/display-checksum
/human-readable
/barcode:intl2of5
/barcode:barcode
/fo:instream-foreign-object
/fo:block
/fo:table-cell
/fo:table-row
/fo:table-body
/fo:table
/fo:block
/xsl:template
/xsl:stylesheet

And error:  java.util.MissingResourceException: Can't find resource for bundle 
org.apache.fop.util.XMLResourceBundle, key 
org.apache.fop.fo.FOValidationEventProducer.unknownFormattingObject
Of course the library  barcode4j-fop-ext-complete is attached.
When I used fop 0.95 everything is ok.

Regerds

Bogusław Fries

From: Eric Douglas [mailto:edoug...@blockhouse.com]
Sent: Tuesday, July 19, 2011 1:47 PM
To: fop-users@xmlgraphics.apache.org
Subject: RE: unknownFormattingObject

Try attaching a sample so someone can reproduce it.


From: Boguslaw Fries [mailto:bfr...@dpd.com.pl]
Sent: Tuesday, July 19, 2011 5:03 AM
To: fop-users@xmlgraphics.apache.org
Subject: unknownFormattingObject
Hi,

I am using FOP version 1.0
I got the following error

java.util.MissingResourceException: Can't find resource for bundle 
org.apache.fop.util.XMLResourceBundle, key 

RE: unknownFormattingObject

2011-07-19 Thread Eric Douglas
Yes, that is an XSL file, which is meaningless without some XML.
FOP doesn't process XSL.  It accepts XSL input as a convenience which must 
transform to FO before any FOP classes are involved.
 



From: Georg Datterl [mailto:georg.datt...@geneon.de] 
Sent: Tuesday, July 19, 2011 8:24 AM
To: fop-users@xmlgraphics.apache.org
Subject: AW: unknownFormattingObject



Hi Bogusław,

 

Actually, Eric was talking about the fo-file. Can you post that?

 

Regards,

 

Georg Datterl

 

-- Kontakt --

 

Georg Datterl

 

Geneon media solutions gmbh

Gutenstetter Straße 8a

90449 Nürnberg

 

HRB Nürnberg: 17193

Geschäftsführer: Yong-Harry Steiert 

 

Tel.: 0911/36 78 88 - 26

Fax: 0911/36 78 88 - 20

 

www.geneon.de

 

Weitere Mitglieder der Willmy MediaGroup:

 

IRS Integrated Realization Services GmbH:www.irs-nbg.de 
http://www.irs-nbg.de  

Willmy PrintMedia GmbH:  www.willmy.de 
http://www.willmy.de 

Willmy Consult  Content GmbH:   www.willmycc.de 
http://www.willmycc.de  

 

Von: Bogusław Fries [mailto:bfr...@dpd.com.pl] 
Gesendet: Dienstag, 19. Juli 2011 14:11
An: fop-users@xmlgraphics.apache.org
Betreff: RE: unknownFormattingObject

 

OK., it is:

 

?xml version=1.0 encoding=UTF-8?

!DOCTYPE xsl:stylesheet [

!ENTITY nbsp #160;

!ENTITY start #135;

!ENTITY stop #138;

!ENTITY tab #9;

!ENTITY crlf #13;#10;

!ENTITY bull #8226;

]

xsl:stylesheet version=2.0 

xmlns:fo=http://www.w3.org/1999/XSL/Format;

xmlns:xsl=http://www.w3.org/1999/XSL/Transform;

xmlns:barcode=http://barcode4j.krysalis.org/ns;

xsl:output encoding=UTF-8 indent=no/

xsl:strip-space elements=* /

 

xsl:template match=/

fo:root

fo:layout-master-set

fo:simple-page-master master-name=page-domestic 
page-height=279mm page-width=210mm margin-top=8mm margin-left=1cm 
margin-bottom=2mm margin-right=1cm

fo:region-body region-name=content margin-top=25mm/

fo:region-before region-name=header-domestic 
extent=15mm/

/fo:simple-page-master

/fo:layout-master-set

fo:page-sequence master-reference=page-domestic 
force-page-count=no-force

fo:static-content flow-name=header-domestic 

xsl:call-template name=ReportHeader /

/fo:static-content

fo:flow flow-name=content font-size=12pt

fo:block

content

/fo:block

/fo:flow

/fo:page-sequence

/fo:root

/xsl:template

 

xsl:template name=ReportHeader

fo:block

fo:table table-layout=fixed width=100%

fo:table-column column-width=20%/

fo:table-body

fo:table-row

fo:table-cell

fo:block text-align=center

fo:instream-foreign-object

barcode:barcode

xsl:attribute name=message

xsl:value-of select=123/

/xsl:attribute

barcode:intl2of5


barcode:height11mm/barcode:height


barcode:module-width0.375mm/barcode:module-width


barcode:wide-factor3.0/barcode:wide-factor


barcode:checksumadd/barcode:checksum

human-readable

placementbottom/placement

font-nameArial/font-name

font-size8pt/font-size


display-checksumtrue/display-checksum

/human-readable

/barcode:intl2of5

/barcode:barcode

/fo:instream-foreign-object

/fo:block

/fo:table-cell

/fo:table-row

/fo:table-body

/fo:table

/fo:block

/xsl:template

/xsl:stylesheet

 

And error:  java.util.MissingResourceException: Can't find resource for bundle 
org.apache.fop.util.XMLResourceBundle, key 
org.apache.fop.fo.FOValidationEventProducer.unknownFormattingObject

Of course the library  barcode4j-fop-ext-complete is attached.

When I used fop 0.95 everything is ok.

 

Regerds

 

Bogusław Fries



From: Eric Douglas [mailto:edoug...@blockhouse.com] 
Sent: Tuesday, 

Re: character #133;

2011-07-19 Thread Andreas L. Delmelle
Just to be complete:

 I wrote
 
 fo:block font-family=”Arial”/
 xsl:texttestowe=12345#133;ABCD/xsl:text
 /fo:block
 
 On PDF his text was splitted into the two lines:
 12345
 ABCD

 #133; is the [next line] control character. It should not be used as
 this in FO to PDF.

That is true in this particular context, if you want to avoid the line-break.

However, for all other intents and purposes, #133; (or the corresponding 
Unicode codepoint U+0085) is a perfectly legitimate typographical aid, and may 
be used to enforce inline linefeeds, independent/regardless of 
linefeed-treatment=preserve. It is defined in UAX#14 as one of a handful of 
explicit break-characters, and as such, is supported by FOP.

There are a few control break-characters which should indeed never be used 
--classical form-feed and line-tabulation-- but those will already cause the 
XML parser to choke, so FOP would never see them.

See also: 
http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/test/layoutengine/standard-testcases/block_uax14_explicit-breaks.xml?view=markup


Regards,

Andreas
---
-
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org