Garbage ?

OK, so, after testing :

– .docx doesn’t work

– .doc work but result is not accurate

– .pdf work but result is vastly not accurate

Is this because of Google’s tools limitations or because another problem?

Everything made using Word 2013.

It’s not quite possible for me to know exactly what the document is supposed to look like, but here is some general information that’s been mentioned on these forums for some time:

1) As far as the “accuracy,” the document to image conversion is handled by Google Viewer. If your document doesn’t work, or comes out ugly here, it will have the same effect when used with GDE.

2) Most Office 2013 files (.docx, .xslx, etc.) work normally, but some show “garbage” text and special characters. I typically recommend what you have done, either converting to the lower Office version or to PDF, when this occurs.

If you suspect there is something not right coming out of the plugin based on those two points, feel free to give a more thorough description or example. Thanks.

Kevin

I updated with a PDF.

If you check it, you’ll see that the text fonts are displayed randomly.

But if you download the PDF and watch it with your own PDF viewver (Acrobat or anything else), the document will show accurately.

You can easily compare the downloaded PDF with the one currently displayed to understand what’s not going right.

I can see that the PDF renders correctly in pdf.js, but Google’s viewer isn’t handling it correctly.

https://docs.google.com/viewer?url=https://cippa.paris-sorbonne.fr/wp-content/uploads/2013/07/Mode%CC%80le-CIPPA-0.4-Copie1.pdf

Per my note above, I can only give you what Google gives me. Sorry!

Kevin

After more tests, I conclude that:

1. .docx is not at all handled by Google (it produces full garbage).

2. .doc is handled but without accuracy (same bugs than when opening a .doc with TextEdit or Mac OS preview, BTW); accuracy problem is, by example, the head letter being separated from her paragraph, which is a disaster design wise.

3. Word 2013 (and I suspect other versions) produce flawed PDF by default (fonts are not displayed correctly, but it works accurately if you force Word to produce a PDF/A.

I don’t see problems with the plugin itself but with both Google and Microsoft. They really need to do their homework.

Anyway, thank you for your kind support. ??

Sorry I am not able to help more in your situation, but there are a good number of docx files that do work correctly, and the majority of documents do convert very well using this method. I expect the way in which your document is made or laid out is an unusual and problematic combination. Not to say it’s necessarily avoidable on your part, of course, but I’ve not seen a similar problem in several years of supporting this plugin, so I wouldn’t rule out an underlying cause in your document itself. The fact that other programs also struggle to render it correctly would support that diagnosis.

Best wishes,

Kevin