On 11/24/2010 09:39 PM, Sergiu Dumitriu wrote: > On 11/24/2010 11:11 AM, Marius Dumitru Florea wrote: >> Hi devs, >> >> Currently, the office importer module doesn't expose any configuration >> options for the office document conversion. Most of the available >> parameters are used to control the connection to the open office server. >> >> Office importer module uses jodconverter ( >> http://code.google.com/p/jodconverter/ ) to convert from different >> office document formats to HTML. The conversion is controlled by a >> "document format registry". jodconverter provides two >> DocumentFormatRegistry implementations: >> >> * a default implementation, that can be configured only >> programmatically; this is the one we're currently using >> >> * an implementation that reads the configuration from a JSON file; this >> is easy to overwrite by putting a document-formats.js file (with the >> JSON configuration) in /WEB-INF/classes/ >> >> I'd like to change the office import module to use the JSON document >> format registry if possible (i.e. document-formats.js is present and can >> be parsed) otherwise the default document format registry. >> >> This will allow us to control, for instance, the size of the images >> generated when importing/viewing a presentation (the default size is >> 640x480 which is not enough if you have slides with a lot of information). >> >> Do you think this is worth introducing in 2.7 or should I wait for 3.0? >
> If you can guarantee 100% backwards compatibility, then +1 for 2.7. You mean the behaviour? because the API isn't changing, just its internal implementation. Afaics document-formats.js from jodconverter jar is equivalent with the default document format registry we're using right now so there shouldn't be any change in the behaviour of the office importer module. Thanks, Marius _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
