"Save copy as..." is missing

[barfoos]

Hi,

I regularly have to perform the following task:

I need to save the current OOWriter document as a Plain Text File with "Latin 1" encoding und "CR/LF" linebreaks.

What I do is:
1. "Save as..." -> text file format
2. close the file and reopen the original
3. open the text file within some decent text editor and convert from UTF-8 to Latin 1 und linebreaks to "CR/LF".

I would like to get rid of step 2 and 3. Step 3 could be eliminated, by using "Save copy as ..." instead of "Save as ..." in Step 1. But my OpenOffice 2.3 X11 under OS X 10.4 does not provide this.
Step 3 could be eliminated by having appropriate switches within the "Save as ..."-dialog.

Do you have any suggestions of how I could improve my 3 step workflow, which I really have to perform quite often?

thanks for your help

greetings
barfoos

[floris v]

I can only think of recording a macro.

[Bill]

File SaveAs/Export to TEXT: Export to different formats in addition to Save As...

Add File | Export... functionality for _all_ supported formats

You can register and vote for either or both of these enhancement requests.

[barfoos]

thanks for this hint.

At least I now know that it isn't my fault

Is there some possible workaround?

One thing I wounder about, is that the "filter options" checkbox in the save as dialog is disabled in my OO.
This at least would allow me to eliminate the extra step to convert the file from UTF-8 to Latin-1. Any idea,
why this is the case?

thanks

[Bill]

One thing I wounder about, is that the "filter options" checkbox in the save as dialog is disabled in my OO.

Have you tried saving as Text Encoded (.txt) instead of Text (.txt)?

[pete]

Have you tried saving as Text Encoded (.txt) instead of Text (.txt)?

You can choose Latin 3 in OOo 2.3. I don't know if this differs greatly from what you need.

[barfoos]

One thing I wounder about, is that the "filter options" checkbox in the save as dialog is disabled in my OO.

Have you tried saving as Text Encoded (.txt) instead of Text (.txt)?

Thanks for this hint. I actually never opend the drop down box. I went there with the Tab key,
pressed "T" for Text and thought I had found what I was looking for.
Indeed Text Encoded does the desired thing for me.

For solving my overall problem, I recorded a Macro as proposed by floris, that does
- Save
- Save As "exportet.txt" in Encoded Text as Latin1
- Save As "Original Filename.odt"

Running the script does what I want. Right now "Original Filename.odt" is hard coded into the Macro.
This leaves room to some improvemts...

thanks for your help

greetings
barfoos

[floris v]

If you save a file as text, I'm afraid it will no longer have the original formatting. So afterwards saving it as odt file will probably not help you. It's better to save as .odt, then as text encoded, then close the file and re-open the saved odt file.

[barfoos]

If you save a file as text, I'm afraid it will no longer have the original formatting. So afterwards saving it as odt file will probably not help you. It's better to save as .odt, then as text encoded, then close the file and re-open the saved odt file.

I thought so too, but having tried it, make me believe different now.

I remember, that older versions of OO even yielded a question upon closing a text document stating that you were about to loose formatting and proposed to save as openoffice format too.

That is why I think, that OO does not alter its in memory version of the document upon saving and saving as text and later on as odt does not cause formating damage. In my few test cases formatting was kept accross mulitple save as operations.

But that's just what I think. Can you provide some resource, that clarifies the case?

greetings
barfoos

[acknak]

You are correct. Using "Save As" to save a text file does not change the in-memory document at all--it only marks it as "saved". At that point, your file is in danger of being lost if you close it, but if you save it again as ODF, nothing will be lost.