Images in document won't export to doc

dasuberadmin

Hello world!

When inserting an image into a rich text document and then exporting it to doc the image does not get loaded in.

Would it be possible to export the image into the doc file itself? Because I have the feeling that at the moment the image in the doc file is a hyperlink to cryptdrive.

Thanks!

Mathilde

Hello,

Thanks for reaching out and for your interest in CryptPad!

.doc export is working as intended here, all images are present in the exported file. Can you tell us a bit more about your setup?

What CryptPad instance are you on?
What version this instance is running?
What web browser you are using?
What version of this web browser?

Please also check the Common Issues section of our documentation FAQ.

Looking forward to your feedback! 😊

dasuberadmin

Hi Mathilde,

Thank you for your quick reply. I'll jump right to your questions:

I'm using the cryptpad.fr instance
Probably the latest & greatest
I'm using an ungoogled chromium browser
Version 107.0.5304.88 (Official Build, ungoogled-chromium) (64-bit)

I am using Word 2016 professional to open the exported .doc file which gives the following result:

My Word version:
Image description

Thanks!

Mathilde

You are very welcome!

Have you tried opening this .doc in LibreOffice? I had some issues opening mines in the past using Apple Pages.

If the issue persist, can you reach out privately using the integrated support system as detailed in CryptPad documentation? If that's fine with you, I'd like to try a few things.

dasuberadmin

No, haven't used LibreOffice in years but it is worth a shot though.

I'll get back to you on the support system if it still doesn't work after installing LO.

dasuberadmin

It works in LibreOffice. Any ideas on why it is supported in LO but not in Word?

Is this also something that is on the roadmap?

Mathilde

dasuberadmin It works in LibreOffice. Any ideas on why it is supported in LO but not in Word?

Sadly no, I have little knowledge how word processors work. Maybe that's something that could be reported to Microsoft? As a customer you must be entitled to some support by paying for their apps.

dasuberadmin Is this also something that is on the roadmap?

We didn't do anything special to not make it work under Microsoft Word 2016. If an issue is found we could work toward fixing it but so far it looks like it's on Microsoft's end.

If community members have access to other Microsoft Word versions it could be useful to gather feedback on what's working and what not. 😊

dasuberadmin

We didn't do anything special to not make it work under Microsoft Word 2016.

Sure hope not, that would be one epic troll.

Maybe this has something to do with one of the converter libraries you are using on the back-end? I saw that for spreadsheets you are using OnlyOffice. Is this also for the Rich Text editor? If you are using OO as your back-end then I'm sure I'm not the only one who is facing this issue.

I would love to file an issue with Microsoft but it would help to know exactly what the workflow is to reproduce the scenario.

Mathilde

Hello @dasuberadmin,

I've been digging a bit and here is what I can say about our .doc export format for Rich Text. It's in fact a DOCHTML file, sadly it seems that Microsoft dropped support for it somewhere in 2006 ~ 2007. Hopefully LibreOffice still support it (tested against v7.4.2).

Currently, a cumbersome workaround would be to use LibreOffice to convert the exported .doc file to .docx. Then you'll be able open it and edit it with Microsoft Word.

Arnaud

Maybe there is a problem of naming for the extension. When you have a .doc extension to a file, 99.9% of users will think that it is a MS Word .doc. So maybe it should be named something else. After all, it is html with some extensions. Maybe dhtml ? Don't know. But I find export to doc confusing in the context.