pod generated ods files do not open in Libreoffice nor MS Excel 2010
Bug #1173295 reported by
David Burke
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Appy |
Fix Released
|
Medium
|
Gaëtan Delannay | ||
Bug Description
Steps to reproduce
Generate a ods file like in the example at http://
Verify the file opens in Google Drive.
Opening the file in LibreOffice 4.0.2.2 in Linux or Window results in LibreOffice crashing.
Opening the file in MS Excel 2010 results in a message about it being corrupt.
I'm excited to start using the ods template feature! Let me know if I can help in any way. I've attached a sample ods file. The file was made in Libreoffice and processed by appy pod.
Revision history for this message
| David Burke (bufke) wrote | #1 |
| Changed in appy: | |
| milestone: | none → 0.9.0 |
| assignee: | nobody → Gaëtan Delannay (gaetan-delannay) |
| importance: | Undecided → Medium |
| status: | New → Fix Committed |
Revision history for this message
| Gaëtan Delannay (gaetan-delannay) wrote | #2 |
| Changed in appy: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Hi David,
Sorry for the late answer. Indeed, I could reproduce the problem and fix it. With LibreOffice >= 3.5, annotations can't be within paragraphs anymore for ODS. When pod produces an error, it embeds it into an annotation that lies within a paragraph (this was the case in your sample file). For ODT it works, but for ODS it makes LibreOffice 3.5 and 4.0 crash. LibreOffice >= 4.1 does not crash anymore but does not show the error message: the annotation is ignored.
It is tricky to solve this problem. What I have done for the moment is to force the appy.pod renderer to raise an error when generating a file from an ODS template (param "raiseOnError", see https:/
Cheers
Gaetan