https://bugs.documentfoundation.org/show_bug.cgi?id=116703
Mike Kaganski <mikekagan...@hotmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |RESOLVED
Resolution|--- |NOTABUG
--- Comment #25 from Mike Kaganski <mikekagan...@hotmail.com> ---
Since I wrote this, I got a bit clearer understanding of how it's implemented
(thanks to Kohei).
The filters that can *both* import and export are listed under File->Save As.
The filters that do not have import functionality (export-only) are listed
under File->Export. This makes Save As dialog to only list file types that you
can open, edit and save using File->Save (or corresponding toolbar button)
without choosing resulting file type (modulo "not a native file type" warning).
The quality of both import and export of the respective filter is, indeed, not
taken into account by the implementation.
So:
- there may be some file type that we can import and export using the same
filter. It will be in Save As.
- there may be a file type that we can import using one filter, and export
using a different filter (example: PDF). It will be in Export.
- there may be a file type that we can't import, but can export. It will also
be in Export.
- there may be a file type that we can import, but not export (example: DXF).
It will not be in either.
I am now OK with the current status (as a developer, seeing a clear picture).
*If* there would be user request to change something with this, there could be
some procedure:
1. Identify filters that do not offer good enough quality, that UX feels should
not be in Save As, but only in Export;
2. Change respective filter's registration into two different filters, one for
import, one for export.
But as said, not an issue for me anymore. Closing accordingly. UX: feel free to
open if needed.
--
You are receiving this mail because:
You are the assignee for the bug.
