Re: Need working example or help how to use PDF/A-1b with FOP 0.93

2007-02-15 Thread Virginijus Kandrotas


 yes exactly I can not run your example using my embedded code as I already
posted.  It seems that in embedded code configuration file is not read or
not set to fo userAgent. I'm getting in log this warning “WARN  [FontInfo]
Font 'Arial,normal,400' not found. Substituting with 'any,normal,400'.”. 

 On command line it works without problem.

 regards,

 Virginijus Kandrotas



Jeremias Maerki-2 wrote:
> 
> Does that mean you can't run my example? You get an error about
> "Times-Roman" with pdfa-example.fo? If yes, that's really weird.
> 
> I simply did this on the command-line:
> fop -c fop.xconf -fo pdfa-example.fo -pdfa1b pdfa-example.pdf
> 
> Have you tried it from the command-line?
> 
> On 14.02.2007 16:59:53 Virginijus Kandrotas wrote:
>> 
>> 
>> 
>> I just try to run your example (pdfa-example.fo), have no extra
>> references
>> to the fonts defined.
>> 
>> regards,
>> 
>> Virginijus Kandrotas
> 
> 
> 
> Jeremias Maerki
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Need-working-example-or-help-how-to-use-PDF-A-1b-with-FOP-0.93-tf3227266.html#a8983656
Sent from the FOP - Users mailing list archive at Nabble.com.


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



html with FOP.

2007-02-15 Thread Andre Groeneveld
Hi All,
 
Is it possible to create a PDF document with FOP if I have a HTML and no
XML document?
 
Thanks in advance.

Confidentiality Caution and Disclaimer

This message and/or any attachment thereto ("the message")
contains privileged and confidential information intended
only for the recipient named above. 
If you are not the intended recipient of this message,
please erase it permanently once you have notified the
sender, per return e-mail, that you have received the
message in error.
Unless the sender is duly authorised by either the Telesure
Group, or any of its subsidiary companies or I.S Services
("the Group") to send this message and unless the content
of this message is also duly authorised by the Group, any
views expressed in this message are those of the individual
sender and the Group will not accept liability therefore,
nor for any consequential damage arising therefrom.
Any recipient of an unacceptable communication, a chain
letter or offensive material of any nature is requested
to report it to [EMAIL PROTECTED]


AW: [SPAM] Re: fop and image sizing

2007-02-15 Thread Hinrich Aue
Thanks for the answer,

thats valuable information.

I can send you an example with a jpeg or png.
I'm using FOP 0.93
Can I attach it to the mailing list?

-Ursprüngliche Nachricht-
Von: Jeremias Maerki [mailto:[EMAIL PROTECTED] 
Gesendet: Mittwoch, 14. Februar 2007 18:53
An: fop-users@xmlgraphics.apache.org
Betreff: [SPAM] Re: fop and image sizing


On 14.02.2007 16:57:30 Hinrich Aue wrote:
> Hello everybody,
> 
>  
> 
> I was wondering about some things:
> 
> Why does FOP not use meta data (specially dpi) from images? I know it
> doesn't, I read the documentation. I just wonder why.

Wow, http://xmlgraphics.apache.org/fop/0.93/graphics.html seems quite a
bit out of date. A few things stated there are wrong.

FOP does interpret the resolution setting of most bitmap images. Only
formats like BMP don't contain a resolution. For JPEG and PNG this
should work fine.

> Of course, when you don't read that information, you have to set a dpi
> resolution.
> 
> Why is it 72 dpi? Every screen these days has >96dpi. Printers have even
> higher dpi.

72dpi is the default PostScript and PDF resolution.

> Another question is, is it configurable? I read a different post about
this,
> but nobody answered. Can I change these default 72 dpi to 96 dpi?

Yes, see:
http://xmlgraphics.apache.org/fop/0.93/configuration.html#general-elements
("source-resolution")

> 
> I'm asking these questions because I'm a docbook user, and I use FOP.

0.93???

> For our printed documentation we use FOP. We have _a lot_ of screenshots.
> 
> Now I have to set the absolute width for every image instead of setting
dpi
> to 96 dpi in FOP.

For screenshots, even 96dpi may be too little. How about using
percentages to scale down the images?

> I cannot scale the images, they are also used for our html documentation.
> 
>  
> 
> Is there something I can do?
> 
> Are there plans for FOP to use image meta data?

As indicated above, we already do that in most places. If the above
doesn't help, please post an example.



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]



AW: [SPAM] Re: fop and image sizing

2007-02-15 Thread Hinrich Aue
Can I test if FOP can interpret the document size?
What are the parameters for the fo:external-graphic that would scale the
image to it's intrinsic size?

Hinrich

-Ursprüngliche Nachricht-
Von: Jeremias Maerki [mailto:[EMAIL PROTECTED] 
Gesendet: Mittwoch, 14. Februar 2007 18:53
An: fop-users@xmlgraphics.apache.org
Betreff: [SPAM] Re: fop and image sizing


On 14.02.2007 16:57:30 Hinrich Aue wrote:
> Hello everybody,
> 
>  
> 
> I was wondering about some things:
> 
> Why does FOP not use meta data (specially dpi) from images? I know it
> doesn't, I read the documentation. I just wonder why.

Wow, http://xmlgraphics.apache.org/fop/0.93/graphics.html seems quite a
bit out of date. A few things stated there are wrong.

FOP does interpret the resolution setting of most bitmap images. Only
formats like BMP don't contain a resolution. For JPEG and PNG this
should work fine.

> Of course, when you don't read that information, you have to set a dpi
> resolution.
> 
> Why is it 72 dpi? Every screen these days has >96dpi. Printers have even
> higher dpi.

72dpi is the default PostScript and PDF resolution.

> Another question is, is it configurable? I read a different post about
this,
> but nobody answered. Can I change these default 72 dpi to 96 dpi?

Yes, see:
http://xmlgraphics.apache.org/fop/0.93/configuration.html#general-elements
("source-resolution")

> 
> I'm asking these questions because I'm a docbook user, and I use FOP.

0.93???

> For our printed documentation we use FOP. We have _a lot_ of screenshots.
> 
> Now I have to set the absolute width for every image instead of setting
dpi
> to 96 dpi in FOP.

For screenshots, even 96dpi may be too little. How about using
percentages to scale down the images?

> I cannot scale the images, they are also used for our html documentation.
> 
>  
> 
> Is there something I can do?
> 
> Are there plans for FOP to use image meta data?

As indicated above, we already do that in most places. If the above
doesn't help, please post an example.



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: html with FOP.

2007-02-15 Thread Vincent Hennebert
Hi Andre,

Andre Groeneveld a écrit :
> Hi All,
>  
> Is it possible to create a PDF document with FOP if I have a HTML and no
> XML document?

Have a look at CSSToXSLFO [1]. It can convert an XHTML document with CSS
statements into FO, which you can then convert to PDF with FOP.

If your source document is HTML and not XHTML, you may first convert it
to XHTML using tidy [2].

I haven't tested it but this route should work well.

[1] http://www.re.be/css2xslfo/
[2] http://tidy.sourceforge.net/


HTH,
Vincent


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



Re: Dynamic Running Heads

2007-02-15 Thread Andreas L Delmelle

On Feb 15, 2007, at 04:54, Jeff Sese wrote:

Hi,

I tested some variations of the position of the markers and the  
properties i used for the retrieve-marker, i finally got my desired  
output. Here's my fo code for reference:


Basically, I placed a marker that can be read when i specified a  
page-boundary of page-sequence. These were place as the first child  
of the parent block of the article and the first child of the last  
block of the article. Then I placed a marker for the separator and  
the title of the current article in the first block child of the  
main block, so that it can only be read by a page-boundary of page  
(I hope my understanding of the page-boundary property was correct).


Yep, seems about right. Just FYI, to see if you understood it  
correctly, I'll try to explain a bit more...


The retrieve-boundary property has an initial value of "page- 
sequence" (= specifying that value is the same as omitting the entire  
property specification). That value means that *only* markers within  
the same page-sequence as the retrieve-marker are qualified for  
retrieval. Setting this to "page" means that any marker that is  
retrieved, MUST be on the containing page (~ same page as the  
retrieve-marker).
So, this property only makes a difference if a given page (or page- 
sequence) does /not/ contain a marker of the specified marker-class- 
name:
* with a retrieve-boundary of "document", even a marker from a page  
in a preceding page-sequence may be retrieved
* with a retrieve-boundary of "page-sequence", a marker from a  
preceding page within the same page-sequence may be retrieved
* with a retrieve-boundary of "page", there would be no marker to  
retrieve


Note that markers on pages /following/ the containing page are / 
never/ qualified for retrieval, whether or not they're in the same  
page-sequence.


The retrieve-position property, OTOH, indicates a preference for  
which marker will be retrieved if there's more than one that  
qualifies based on the retrieve-boundary.


In your example:
1) the first page will contain only one marker, namely one of marker- 
class-name="heading-in-page-sequence", so that one will be retrieved.  
The other two retrieve-markers retrieve nothing. Due to retrieve- 
boundary="page", only markers on the containing page qualify.

2) the second page contains four markers:
  * two of marker-class-name="heading-in-page-sequence", so the one  
that satisfies the preference "first-starting-within-page" is retrieved
  * one of marker-class-name="heading-separator", so that one is  
retrieved

  * one of marker-class-name="heading", so that one is retrieved
3) the third page contains four markers: analogous to the second
4) the fourth page contains no markers, so only retrieve-markers with  
a retrieve-boundary other than "page" will actually retrieve anything


Only thing to take care of: in this case, all works nicely, since you  
control the page-breaks (break-after="page"). Using implicit,  
formatter-generated page-breaks would make things slightly more  
difficult.
If you remove the first explicit break-after, and the formatter would  
decide to break precisely between the first and second section, your  
output could turn out to look like:


page 1: first heading
...
page 2: second heading - second heading
...

Anyway, thanks for sharing your solution with the list! Always nice  
to have examples in the archives somewhere.



HTH!

Cheers,

Andreas


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



No allignment possible in nested tables?

2007-02-15 Thread Christian Loock
Hello,

i am using FOP 0.25 to render PDF Output. I tried to align a table which is 
nested inside another table on the right side using the text-align property but 
it didnt work.
If i use a normal fo:block it will be aligned as expected. Is there any way to 
align this nested table?



Viele Grüße/ Best Regards

Christian Loock
Software Engineer

___

  telephone: +49 (0) 28 21 . 9 78 56.21
  telefax: +49 (0) 28 21 . 9 78 56.77
  

[EMAIL PROTECTED]
  www.db-central.com

  Main office
  db-central gmbh, Hoffmannallee 41-51, D-47533 Kleve

  Subsidiary
  db-central gmbh, Königsallee 43, D-71638 Ludwigsburg
  db-central gmbh, Adalbertstr. 110, D-80798 München

  Managing Directors
  Dirk Rosomm, Benno van Aerssen

  Registered office
  Kleve - Germany, Amtsgericht Kleve, HRB 2746


___


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



Re: No allignment possible in nested tables?

2007-02-15 Thread Chris Bowditch

Christian Loock wrote:


Hello,

i am using FOP 0.25 to render PDF Output. I tried to align a table which is 
nested inside another table on the right side using the text-align property but 
it didnt work.
If i use a normal fo:block it will be aligned as expected. Is there any way to 
align this nested table?


text-align will only affect the position of text inside a table, not 
tables themselves.


Chris




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



Re: Exception in thread "main" java.lang.OutOfMemory Error

2007-02-15 Thread Krishna . Cherla
Hello All,

As i have discussed in the previous threads I get an  Exception in
thread "main" java.lang.OutOfMemory Error when I try to pdf xml
documents.

*   I tried increasing the memory available to the JVM (used this
command line option:
C:\Program Files\Altova\FOP\build>java -Xmx512m -jar fop.jar fop
-xsl test.xsl -xml test.xml -pdf test.pdf ). This helped me convert a
777KB Xml document into a PDF Document(about 100 pages). But when I try
converting an 4500KB Xml Document(approx. about 400 pages long) it gives
me an out of memory error again.I can't increase the memory more than
that as my physical RAM is only 523 MB.
*   I donot have any figures in the document.
*   I do use a page numbering scheme that includes a total number of
pages in the document that makes use of forward referencingand I cannot
bypass this. 
*   I have three page sequences but I'm afraid can't break the
document into any more. And each sequence does contain a lot of fo
elements.

Can anybody guide me more  in regards to this?

Sindhu

Email Firewall made the following annotations
 NOTICE 
---

This message is for the designated recipient only and may contain confidential, 
privileged or proprietary information. If you have received it in error, please 
notify the sender immediately and delete the original and any copy or printout. 
Unintended recipients are prohibited from making any other use of this e-mail. 
Although we have taken reasonable precautions to ensure no viruses are present 
in this e-mail, we accept no liability for any loss or damage arising from the 
use of this e-mail or attachments, or for any delay or errors or omissions in 
the contents which result from e-mail transmission.

-


Re: Dynamic Running Heads

2007-02-15 Thread Jeff Sese

Thanks for the explanation.

I've been working with the problem for quite some time now and the 
example i gave was just a simulation of how the original project would 
come out. In the original project though, i have no control over the 
page breaks, is there any way for me the make sure i can avoid the 
situation that you stated below (wherein the page breaks precisely 
between the first and second section)? Would using a keep-with property 
do the trick?


Regards,
*Jeff Sese*

Andreas L Delmelle wrote:

On Feb 15, 2007, at 04:54, Jeff Sese wrote:

Hi,

I tested some variations of the position of the markers and the 
properties i used for the retrieve-marker, i finally got my desired 
output. Here's my fo code for reference:


Basically, I placed a marker that can be read when i specified a 
page-boundary of page-sequence. These were place as the first child 
of the parent block of the article and the first child of the last 
block of the article. Then I placed a marker for the separator and 
the title of the current article in the first block child of the main 
block, so that it can only be read by a page-boundary of page (I hope 
my understanding of the page-boundary property was correct).


Yep, seems about right. Just FYI, to see if you understood it 
correctly, I'll try to explain a bit more...


The retrieve-boundary property has an initial value of "page-sequence" 
(= specifying that value is the same as omitting the entire property 
specification). That value means that *only* markers within the same 
page-sequence as the retrieve-marker are qualified for retrieval. 
Setting this to "page" means that any marker that is retrieved, MUST 
be on the containing page (~ same page as the retrieve-marker).
So, this property only makes a difference if a given page (or 
page-sequence) does /not/ contain a marker of the specified 
marker-class-name:
* with a retrieve-boundary of "document", even a marker from a page in 
a preceding page-sequence may be retrieved
* with a retrieve-boundary of "page-sequence", a marker from a 
preceding page within the same page-sequence may be retrieved
* with a retrieve-boundary of "page", there would be no marker to 
retrieve


Note that markers on pages /following/ the containing page are /never/ 
qualified for retrieval, whether or not they're in the same 
page-sequence.


The retrieve-position property, OTOH, indicates a preference for which 
marker will be retrieved if there's more than one that qualifies based 
on the retrieve-boundary.


In your example:
1) the first page will contain only one marker, namely one of 
marker-class-name="heading-in-page-sequence", so that one will be 
retrieved. The other two retrieve-markers retrieve nothing. Due to 
retrieve-boundary="page", only markers on the containing page qualify.

2) the second page contains four markers:
  * two of marker-class-name="heading-in-page-sequence", so the one 
that satisfies the preference "first-starting-within-page" is retrieved
  * one of marker-class-name="heading-separator", so that one is 
retrieved

  * one of marker-class-name="heading", so that one is retrieved
3) the third page contains four markers: analogous to the second
4) the fourth page contains no markers, so only retrieve-markers with 
a retrieve-boundary other than "page" will actually retrieve anything


Only thing to take care of: in this case, all works nicely, since you 
control the page-breaks (break-after="page"). Using implicit, 
formatter-generated page-breaks would make things slightly more 
difficult.
If you remove the first explicit break-after, and the formatter would 
decide to break precisely between the first and second section, your 
output could turn out to look like:


page 1: first heading
...
page 2: second heading - second heading
...

Anyway, thanks for sharing your solution with the list! Always nice to 
have examples in the archives somewhere.



HTH!

Cheers,

Andreas


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



--No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.441 / Virus Database: 268.17.39/687 - Release Date: 
2/14/2007 4:17 PM





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