[ 
https://issues.apache.org/jira/browse/PDFBOX-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14287160#comment-14287160
 ] 

Maruan Sahyoun commented on PDFBOX-2618:
----------------------------------------

I’m not looking into creating a typesetting application. But some **basic** 
block setting is needed for multiline form fields otherwise we will not be able 
to create the appearance for these.

And I do agree - we shouldn’t be replicating FOP.

> Create paragraphs with PDFBox
> -----------------------------
>
>                 Key: PDFBOX-2618
>                 URL: https://issues.apache.org/jira/browse/PDFBOX-2618
>             Project: PDFBox
>          Issue Type: Improvement
>          Components: Writing
>    Affects Versions: 2.0.0
>            Reporter: Tilman Hausherr
>
> [~mkl] wrote this morning on stackoverflow on the topic about creating tables 
> with PDFBox: 
> {quote}I'm afraid all those samples IMO meely are proofs of concept, probably 
> of use in limited use cases but by far not for generic use. PDFBox has its 
> strengths, e.g. a quite versatile content extraction framework and a content 
> rendering capability, but the absence a proper layouting API is a serious 
> weakness.{quote}
> To which I answered:
> {quote}I know... I just don't want to create another iText. We're not the 
> Samwer brothers.{quote}
> But he's right. We could of course look at what iText offers and implement 
> that on our own, that wouldn't even be illegal, but it wouldn't be nice. I've 
> never looked at or used iText, except once when answering this: 
> http://stackoverflow.com/a/26820598/535646
> IMO what we need to start, is a method to write a paragraph to a PDF. Such a 
> method would have these parameters:
> - text
> - rectangle (or width and height from current position)
> Such a method would then output the text and break the lines at the end of 
> the rectangle, and throw an exception if the space isn't enough.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to