GoogleCodeExporter
commented
8 years ago Hi,
At first many thank's for your docx. I have add it to our Junit docx->pdf
converter
http://code.google.com/p/xdocreport/source/browse/#git%2Fthirdparties-extension%
2Forg.apache.poi.xwpf.converter.pdf%2Fsrc%2Ftest%2Fresources%2Forg%2Fapache%2Fpo
i%2Fxwpf%2Fconverter%2Fcore
To answer to your 2 questions:
> 1. Provide a list of the PDF converter improvements that you mention
See in the http://code.google.com/p/xdocreport/issues/list which starts with
docx->converter.
See too below link where you can see docx which we use to test our converter.
It exists again some problem but the result can start be good.
> 2. Indicate when 1.0.0-SNAPSHOT will be released - presumable as version
1.0.0.
I don't know. I would like finish to improve pdf->docx converter to manage
commons case (for instance shape will not be supported in the 1.0.0) but
develop a a docx->pdf converter is a very hard task for me (I'm not an expert
with iText and with docx). We develop XDocReport on our spare time so I cannot
tell you when it will be release (I hope we will able to do this release in one
months, but I cannot promise that).
If you want test 1.0.0 docx->pdf converter, you can :
1) test it with our live demo at
http://xdocreport-converter.opensagres.cloudbees.net/
2) get sources from Git and build it yourself.
3) use maven to get docx->pdf converter from maven central with version
1.0.0-SNAPSHOT.
> . Tables:
> . Row height of less than 1cm is converted to 1cm.
fixed. Try it with the live demo.
> . A table which is not of full page width will be centred in
> the page.
fixed. Try it with the live demo.
> . Coloured table borders are converted to black.
fixed. Try it with the live demo.
Table is very improved but now there is a problem with inside borders which are
doubled. I must manage that by developping the Conflict adjacent borders
algorythm.
> . Free text:
> . The number of characters per line appears to have increased
> between docx and pdf. The font size produced in the PDF appears
> to be slightly larger than the source. This is difficult to
> determine and requires further analysis to confirm what the
> exact nature of the difference is.
it's fixed. The problem came from that default font (Calibri) was not
retrieved. It works in my local JUnit but the live demo doesn't work? Why? I
don't know?
> . Font/style:
> . The PDF and DOCX rendering of the different fonts and sizes
> differs slightly (as mentioned in the free text section).
> . Header 3 styling appears to be too small.
it's the same problem than below. The default font Calibri was not applyed.
> . Strikethrough appears as normal text.
Ok I have created http://code.google.com/p/xdocreport/issues/detail?id=169 issue
. Subscript appears as normal text.
Ok I have created http://code.google.com/p/xdocreport/issues/detail?id=170 issue
. Superscript appears as normal text.
Ok I have created http://code.google.com/p/xdocreport/issues/detail?id=171 issue
. Highlighting is lost.
Ok I have created http://code.google.com/p/xdocreport/issues/detail?id=172 issue
> . Bullets:
> . Microsoft Word bullets are lost
> . Microsoft Word numbering is lost
> . Microsoft Word multilevel lists lose numbering and indentation
> beyond the first item.
Bullet/Numbered list is not managed. See
http://code.google.com/p/xdocreport/issues/detail?id=151
> Note however that all of these bullet representations can be
> reproduced as non-Microsoft bullets using normal text and will
> survive the pdf translation (see example in attached files).
> . Tabs:
> . Tabs within text are lost.
Tabs is very complex to manage. I have started to manage it. See
http://code.google.com/p/xdocreport/issues/detail?id=164
> . Images:
> . Text alongside an image results in both the text and the image
> being misplaced.
Image is basic for the moment (but it seems that 1.0.0 resolves a little your
problem (just a problem with space before the image).
Don't hesitate to create some issue and attach docx sample as you have done
like this. I will add it in our JUnit docx. More we will have docx sampel to
convert, more converter will be improved.
Many thank's.
Regards AngeloOriginal comment by angelo.z...@gmail.com on 18 Oct 2012 at 9:39
- Changed state: Accepted
Original issue reported on code.google.com by
Mr.M.McM...@googlemail.comon 17 Oct 2012 at 1:27Attachments: