|Simon Glet||Feb 8, 2010 1:30 pm|
|Asiri Rathnayake||Feb 8, 2010 6:20 pm|
|Simon Glet||Feb 9, 2010 5:46 am|
|Asiri Rathnayake||Feb 9, 2010 9:15 am|
|Simon Glet||Feb 9, 2010 10:08 am|
|Guillaume Lerouge||Feb 9, 2010 11:36 am|
|Asiri Rathnayake||Feb 9, 2010 12:21 pm|
|Simon Glet||Feb 9, 2010 12:50 pm|
|Guillaume Lerouge||Feb 9, 2010 1:43 pm|
|Asiri Rathnayake||Feb 9, 2010 8:13 pm|
|Florin Ciubotaru||Feb 10, 2010 12:42 am|
|Jeremie BOUSQUET||Feb 10, 2010 1:56 am|
|Simon Glet||Feb 10, 2010 8:24 am|
|Simon Glet||Feb 10, 2010 8:30 am|
|Asiri Rathnayake||Feb 10, 2010 8:34 am|
|Vincent Massol||Feb 10, 2010 8:36 am|
|Simon Glet||Feb 10, 2010 8:40 am|
|Simon Glet||Feb 12, 2010 6:36 am|
|Guillaume Lerouge||Feb 12, 2010 6:56 am|
|Asiri Rathnayake||Feb 12, 2010 8:07 am|
|Asiri Rathnayake||Feb 12, 2010 8:10 am|
|Simon Glet||Feb 12, 2010 8:48 am|
|Subject:||Re: [xwiki-users] Office import error|
|From:||Jeremie BOUSQUET (jere...@gmail.com)|
|Date:||Feb 10, 2010 1:56:29 am|
Some words from a long-time user of XWiki ...
I think the issues you encountered might be linked also to the fact that these features rely on external tools (oo, ms office...), and also they are quite "recent" in xwiki history. So for sure, all integration issues might not have been encountered / fixed already. Of course if you need mainly these features, it might be a problem, but with some fixes there is no reason they won't work.
For the rest, I must say that on the other side, and even with some (known) flaws, xwiki is not comparable to other wikis I know. No one offers such liberty and customization possibilities. I use it for some years now at work (since v0.9) and migrated regularly to last versions, and progression is incredible, in terms of features and usability. A good basis is now in place, and I think not much is needed to have a nearly perfect tool :) But, again, this tool might need some involvement in order to get its best, even if it's more and more "plug & play".
I'll take an example, in my office we use a specific configuration management tool very uncommon, and that is integrated with nothing else. In wiki I could very easily create some macros to help users create links on various sources, reports and such in this scm tool. The wysiwyg editor works really well now, and the new macro displays in a dialog with parameters I defined, though I didn't code anything for the display. This is really helpful and really easy to put in place. I don't know much other tools, but I don't think you can do this kind of thing so easily... For now I did not install oO server for office import though, but I plan to.
Best regards, Jeremie
2010/2/9 Simon Glet <simo...@gmail.com>
I am a little confused by the quality of XWiki 2.1.1. At this point I find that there are many features that don't work properly or at all :
- Office plugin (the office 2007 ribbon has a very buggy behavior) - Document import (There is no documentation about version compatibility between the different elements) - Usage with SQL Server 2005 is impossible. Works fine with PostgreSQL though.
I can't continue testing such a product. To bad, it looked very good.
Best Regards Simon Glet
On Tue, Feb 9, 2010 at 12:15 PM, Asiri Rathnayake <asir...@gmail.com> wrote:
On Tue, Feb 9, 2010 at 7:16 PM, Simon Glet <simo...@gmail.com> wrote:
I currently use the latest version of OO (3.1.1 Build 9420). What else can I check ?
Well, you can try un-installing openoffice and reinstalling. But I doubt this will help.
Next thing you can try is use jodconverter directly and try to convert your document from odt to html.
Here is the link:
How to use it:
If the command-line conversion fails for your document, then the error should probably be reported to jodconverter users list.
Thanks Simon Glet
On Mon, Feb 8, 2010 at 9:20 PM, Asiri Rathnayake <asir...@gmail.com> wrote:
As you have understood it seems the problem is with your OOo installation. Can you try removing your existing OOo installation and installing the latest version from http://www.openoffice.org? This will most