Apache OpenOffice (AOO) Bugzilla – Issue 21282
"automatic filename extension" strips dotted parts of filename
Last modified: 2005-05-05 12:47:01 UTC
I have a file named "sip.progress.report.doc". I read it in to OOo. I wrote it out as an RTF. To my surprise the RTF was named "sip.progress.rtf". It turns out that this happened as I was saving the file. When I save, the first name appears as "sip.progress.report" (and has type "Microsoft Word 97/2000/Xp (.doc)". Then I switch types to RTF and the name becomes "sip.progress.rtf". How about a SIMPLE RULE: Don't muck around with the file names. This is NOT SMART. I work on unix operating systems, and they are happy to have such a long dotted name. If you HAVE to muck around with the name because OO is running on a DOS (Dumb Operating System) then DO NOT muck around when it is Unix. ---- "You must choose a subcomponent that corresponds to this issue. If necessary, just guess." Well I haven't a clue what "ui" is (user interface? How about HELPING people figure out things?) so I'll just mark this as "code" whatever THAT means ...
SIMPLE RULE: look for the feature you want before complaining. It may make you look NOT SO SMART if you overlook the obvoius. Simply uncheck "Automatic file-name extension" in the save-as dialog and the extension won't be touched. ->worksforme. BTW: this is not a support-medium. If you want help on how to do something, please ask in one of the mailing-lists (or search the available documentation).
closing.
Thanks for pointing that feature out. I tried it and the resulting RTF was named "sip.progress.report" instead of "sip.progress.report.rtf". It did countain rtf, however. In other words, there is still a bug. The OOo is not computing the LAST segment of the name. That is, from "a.b.c.d.e.doc" it should isolate "a.b.c.d.e" of type doc. Then when writing it out it should simply tack on the type, rtf, to get "a.b.c.d.e.rtf". It fails to do this. Therefore please reopen the bug.
> Thanks for pointing that feature out. I tried it > and the resulting RTF was named "sip.progress.report" > instead of "sip.progress.report.rtf". It did countain > rtf, however. This happened because it is the first time you deactivated the feature. (the extension was stripped when you run the Save-as dialog, when deselecting the "automatic-filename-extension" the original extension did not get restored. The extension won't be stripped when automatic filename-extension has already been disabled - the extension won't be touched then) > In other words, there is still a bug. The OOo is > not computing the LAST segment of the name. That is, > from "a.b.c.d.e.doc" it should isolate "a.b.c.d.e" > of type doc. Then when writing it out it should simply > tack on the type, rtf, to get "a.b.c.d.e.rtf". It > fails to do this. Therefore please reopen the bug. I misinterpreted your "Don't muck around with the file names. This is NOT SMART." Your report had too much fuzz to concentrate on the real issue. I'll reopen it since now I got the real problem...
confirming, target-milestone: not determined, OS/Platform: ALL original summary: file name changed (renamed)! Steps to reproduce: 0) Create a new text-document and save it as "a.b.c.sxw" 1) Now choose File|Save-as and choose a different file-type like doc -> the name changes to a.b.doc instead of a.b.c.doc 2) Choose File|Save-as again and choose a different filetype (e.g. rtf) -> file is saved as a.rtf The algorithm to strip the extension should only work on the original filename, not on the already stripped filename that is inserted in the name-field as proposal when saving.
forgot to reassign...
TM->FS: As talked about... this one is reproducible in a 1.1, please have a look, thanks !
.
removing the summary from the status-whiteboard..
*** Issue 22871 has been marked as a duplicate of this issue. ***
accepting
*** Issue 25693 has been marked as a duplicate of this issue. ***
*** Issue 34166 has been marked as a duplicate of this issue. ***
Closing this issue as the duplicate of the #i35830# where I'm waiting for an answer from 'ft' how to fix this from the users point of view ... *** This issue has been marked as a duplicate of 35830 ***