Integrate with FilterFactory for filter details #20

Open
dagwieers opened this Issue Jan 9, 2012 · 5 comments

Comments

Projects
None yet
3 participants
@dagwieers
Owner

dagwieers commented Jan 9, 2012

Instead of integrating a static list of filters, we definitely should using the FilterFactory service to query the available filters and extensions. The office instance knows best what filters can do, and some filters come and go.

@dagwieers

This comment has been minimized.

Show comment Hide comment
@dagwieers

dagwieers Feb 7, 2012

Owner

Test-code exists, but lacks information about file extensions. Still ongoing...

Owner

dagwieers commented Feb 7, 2012

Test-code exists, but lacks information about file extensions. Still ongoing...

@lars-sh

This comment has been minimized.

Show comment Hide comment
@lars-sh

lars-sh Sep 17, 2012

Contributor

Took some minutes to consider those *.xcd files. As you said, there's no infomation about the file extensions. So what about...

Inside unoconv: Defining a static list of file extensions linking them to formats.

When getting the filter details dynamically, there might be unused file extensions - but we'd make sure unoconv aborts correctly. And in case of new file extensions (as docx some time ago), unoconv could/should throw something in verbose mode in order to let us add it to the list.

Contributor

lars-sh commented Sep 17, 2012

Took some minutes to consider those *.xcd files. As you said, there's no infomation about the file extensions. So what about...

Inside unoconv: Defining a static list of file extensions linking them to formats.

When getting the filter details dynamically, there might be unused file extensions - but we'd make sure unoconv aborts correctly. And in case of new file extensions (as docx some time ago), unoconv could/should throw something in verbose mode in order to let us add it to the list.

@dagwieers

This comment has been minimized.

Show comment Hide comment
@dagwieers

dagwieers Sep 17, 2012

Owner

Yes, seems the best approach. Although I expect something about extensions to be stored somewhere.

And there's a difference between import and export filters, where import filters do not care about the extension afaik, whereas export filters need an extension to name the file automatically.

Owner

dagwieers commented Sep 17, 2012

Yes, seems the best approach. Although I expect something about extensions to be stored somewhere.

And there's a difference between import and export filters, where import filters do not care about the extension afaik, whereas export filters need an extension to name the file automatically.

@dagwieers

This comment has been minimized.

Show comment Hide comment
@dagwieers

dagwieers Jul 5, 2015

Owner

For an example on how to get the list of filters/formats from LibreOffice, check out this code:
http://svn.erp5.org/erp5/trunk/utils/cloudooo.handler/ooo/cloudooo/handler/ooo/

Owner

dagwieers commented Jul 5, 2015

For an example on how to get the list of filters/formats from LibreOffice, check out this code:
http://svn.erp5.org/erp5/trunk/utils/cloudooo.handler/ooo/cloudooo/handler/ooo/

@regebro

This comment has been minimized.

Show comment Hide comment
@regebro

regebro Nov 24, 2017

Collaborator

I can't find a way to get any sort of doctype information out of LibreOffice, so this doesn't seem doable unless we refactory unoconv to not support a --doctype argument.

Collaborator

regebro commented Nov 24, 2017

I can't find a way to get any sort of doctype information out of LibreOffice, so this doesn't seem doable unless we refactory unoconv to not support a --doctype argument.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment