|
Author
|
Message
|
|
Jack Rackham
|
Friday 08 April 2005 6:12:11 am
After waiting a long time for a new version to come, I fixed the image and øæå issue myself.
Here is a version of the openoffice.org extension that supports images and øæå.
http://hk5.50megs.com/
|
|
Bård Farstad
|
Monday 11 April 2005 5:59:48 am
New release of the OpenOffice.org extension is now available:
http://ez.no/community/contribs/import_export/openoffice_org_extension Please report any bugs you find. --bård
Documentation: http://ez.no/doc
|
|
Jack Rackham
|
Tuesday 12 April 2005 5:03:38 am
Bugs in beta 2
-Error when opening exported files. (Format error) Test on OO 1.1.3 winxp, Suse 9.2
-Exported files named "test".
|
|
Bård Farstad
|
Tuesday 12 April 2005 5:29:54 am
Haavard, do you have a bit more information on how we can re-produce this? --bård
Documentation: http://ez.no/doc
|
|
Jack Rackham
|
Tuesday 12 April 2005 6:19:45 am
Format error in content.xml 3,96(row,col)
|
|
Jack Rackham
|
Tuesday 12 April 2005 6:50:30 am
The problem is caused by images "in the xml part of the article" or by a image relation (standard image import at end of edit a article "Image [Object relation] (id:154)"). Because when I try to export an article without any images the document works fine. EZ generates the following error the first time OO ex. is started after clear cache, but they are most likely unrelated.
Error: eZTemplate @ extension/oo/design/standard/templates/oo/export.tpl:34[63] Apr 12 2005 14:36:43
parser error @ extension/oo/design/standard/templates/oo/export.tpl:34[78]
Extra characters found in expression, they will be ignored.
|i18n('design/standard/oo/import)' ('Export Object')
Error: eZTemplate:ElementParser::parseVariableTag Apr 12 2005 14:36:43
parser error @ s
Parser position did not move, this is most likely a bug in the template parser.
|
|
Jack Rackham
|
Wednesday 13 April 2005 11:53:38 am
My advice is that you skip the OO export in the next version, and instead concentrates on the import function, because EZ already have PDF support. But then again OO documents have some advantages over PDF.
|
|
Jack Rackham
|
Saturday 23 April 2005 11:13:24 am
When I started using the OO extension for real, I quickly discovered that there are a lot of bugs in beta 2 of the extension. Here are a few bugs.
- Random appearing of emphasize and strong in imported files
- Sometimes extra lines appears
- Random text is removed when importing docs To re-produce this errors try using another document that the example.
|
|
Bård Farstad
|
Tuesday 26 April 2005 1:02:32 am
Håvard, please provide more information when you discover bugs. It would be great if you could use the bugreporting system as well, so we can track the bugs reported. I am now looking into reproducing the image bug you mention. --bård
Documentation: http://ez.no/doc
|
|
Jack Rackham
|
Tuesday 26 April 2005 2:03:46 pm
Do the current version support different OO "styles". Looking at the ezoogenerator.php file I see that Illustration, Table, Text, Drawing is named, but what about default and the rest.
- Do you mean this image bug?
The problem is caused by images "in the xml part of the article" or by a image relation (standard image import at end of edit a article "Image [Object relation] (id:154)"). ....................
|
|
|
Tuesday 03 May 2005 3:51:07 am
I have installed and tried oo extension version 1.0 but when I export a document the size is always 0 bytes. Do I have to do some magic to get this working ?
Import works flawlessly though.
Tested on eZ 3.5.2
|
|
Bård Farstad
|
Tuesday 03 May 2005 5:10:59 am
Hans-Henry, to get export working you need to have the "zip" command line program installed or mod_gzip in PHP. --bård
Documentation: http://ez.no/doc
|
|
|
Tuesday 03 May 2005 6:12:50 am
I can export files after installing zip but when I try to open it in openoffice 1.1.4 I get the following error message:
"Read-Error.
Format error discovered in the file in sub-document content.xml at 4,129(row,col)." The row,col number is different from article to article. I have unzipped the sxw document and opened the content.xml document without any error messages.
|
|
Bård Farstad
|
Tuesday 03 May 2005 6:27:19 am
This is interesting. I did get reports about this happening. I have not been able to reproduce this on my systems. Can you provide more information on how this is re-produced? Does it always happen? What is your system information? --bård
Documentation: http://ez.no/doc
|
|
|
Tuesday 03 May 2005 6:32:26 am
Can I provide you with this information outside of this forum. I don't like to publish such information to everyone :)
|
|
Bård Farstad
|
Tuesday 03 May 2005 6:37:58 am
Yes, feel free to send me an e-mail. My initials at ez.no.
Documentation: http://ez.no/doc
|
|
|
Tuesday 10 May 2005 6:21:07 am
Hi, Have you had time to look through the info I sent you? Mail was sent Tuesday 03.05.2005 (DDMMYYYY) 15:44
|
|
Bård Farstad
|
Tuesday 10 May 2005 6:25:30 am
Hans-Henry, Yes, we have looked at the info you sent me. I have not been able to re-produce it on my systems (all Linux) but on a windows system. We haven't had time to find a solution for it. But the problem was related to the files generated in the ezoogenerator.php file. If someone with a windows environment would have time to look a bit at this problem happening during export that would be great ;) --bård
Documentation: http://ez.no/doc
|
|
Joshua Newman
|
Tuesday 10 May 2005 12:17:14 pm
I believe this is an OO.o bug not an eZ bug. I am using OO.o 1.9.100 on Linux but not using eZpublish, and am getting the same error (but with different row and column numbers). Did not ever see this error prior to upgrading to OO.o version 1.9.100 from version (I believe) 1.9.72.
|
|
Jack Rackham
|
Tuesday 10 May 2005 1:36:27 pm
I have tested the beta 2 on SUSE 9.2 and Windows XP, and the export don.t work on any of them. The same old error is displayed.
|
