Hi Bettina,

one for you.

Frank

I think this could be generalised to other exportable formats. I rarely want 
to save anything but ODF for myself, but sometimes I need to export in order 
to communicate with others. They get a copy and then I want to continue 
working in native format. I always look under File->export... first when I 
want to do this. 
 
It also simply makes sense to have all savable formats under export... 
 

I'm going to echo this request since I came here to file this as a feature
request.  Because CSV doesn't support most formatting, I typically want to
EXPORT to it, rather than Save As...

As the csv is really an intermediary transport file used to transfer one sheet
of data from the spreadsheet to another program, I strongly support adding the
CSV-format to the EXPORT-possibilities.

The csv can't support formatting nor formulas, BUT most importantly, only the
*active sheet* is exported, so it is really ONLY an export, NOT a SAVE
AS-functionality.

I therefore strongly suggest to add this option to the EXPORT-dialog.

This has some practical consequences. Basically, it is impossible to perform any
sound statistics in Calc. At the same time, the ODF-format has become too
complex to implement accurate readers (that mimic all its bugs and limitations)
in professional statistic packages. It is therefore imperative to use a simple
format for data-transfer, and csv is simply the best suited one (tab-delimited
data is another one).

I therefore strongly hope that this enhancement gets implemented in Calc.

Basically, the export-dialog should have both PDF and CSV as options. Selecting
CSV should export the active sheet, using the sheet-name as default name. The
status of the ods-file should not change (i.e. do not set changed status).
That's it.

This issue has been discussed by UX for years now and having dug around in 3-4
years of discussions and lists I'm stunned by how such a practical feature has
been crushed under the albatros of "Oh but we can't do it THAT way because we
have to argue about a better way to do it."  I'm all for good UI design, the
importance of consistent UI, and respecting workflows... but after 3 years of 

A) having to search the forums for a visual basic script to do something a
simple as "export this file to format FOO so I can send it to another
Program/Collaborator, then continue working"
B) new users losing data because they don't understand the difference between
"You're working with data that won't be saved when you hit 'Save'"

It's time to accept a quite likely sub-optimal but pragmatic solution (aka: a
"hack") to get it done.  I'll start digging around in code to try and do it, but
I doubt it'll be the most efficient solution.

To grep the issues easier via "requirements" I put the issues currently lying on
my owner to the owner "requirements".