-
Notifications
You must be signed in to change notification settings - Fork 375
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docx - pdf conversion problem: Line Spacing and Character spacing greater in pdf #246
Comments
Any contribution are welcome! |
My small testdata: only 3 lines, with Times New Roman 10 input docx file: perfect pdf created with Acrobat/Create pdf command in MS Word: POI converted file: view lines in Adobe Acrobat Pro in Edit mode: In this 3 lines can see difference. |
@imajic |
Clicking on the pull request and then on the "Files changed" tab takes you to @imagic 's patch: https://github.com/opensagres/xdocreport/pull/250/files |
it's 2022. Any chances that this pull request will be merged in the future? |
If someone resolve conflict, I'm opened to merge it. |
@angelozerr There are no conflicts and in every version i am picking this snippet to avoid a formatting mess. Can you approve and merge it ? |
That is strange, in my pr view it is marked as "no conflicts". Can you state the Problem ? |
@angelozerr I made a new PR from a private fork.. can you please check it ? |
Conversion with PdfConverter:
import org.apache.poi.xwpf.usermodel.XWPFDocument;
import fr.opensagres.poi.xwpf.converter.pdf.PdfConverter;
import fr.opensagres.poi.xwpf.converter.pdf.PdfOptions;
...
XWPFDocument document = null;
try {
document = new XWPFDocument(is);
final PdfOptions pdfOptions = null;
PdfConverter.getInstance().convert(document, os, pdfOptions);
} catch (final Exception e) {
...
} finally {
document = null;
}
fr.opensagres.xdocreport: last version: 2.0.1
org.apache.poi: last version: 3.17
Conversion success, but Line Spacing and Character spacing greater in pdf.
From 1,5 page long docx convert 2,5 page long pdf.
The text was updated successfully, but these errors were encountered: