Howard Coles Jr. wrote:
> On Thursday 05 April 2007 01:55:05 pm LDR wrote:
>
>> I am having intermittent problem with saving documents in Writer.
>>
>> I'm wondering if this has anything to do with?:
>>
>> * My penchant for embedding '+'s, and '%'s '.'s in file names
>> * My use of a separate directory for backup copies of documents
>> * Occasionally changing the file name in mid-edit session (save as)
>> in order to protect myself from expected impending brain farts
>>
>> When this happens, my only recourse is to copy all of the contents of
>> the document, shut down, OOoW, open a copy afresh, and write it to the
>> old name.
>>
>> As they say on the Good Ship Lollipop, WTFO (which technology
>> feloniously obfuscates? ;-))?
>>
>
> First, don't hijack another thread, start a new one. In other words don't
> reply to another message and just change the subject, it "hijacks" the thread
> and isn't polite.
>
Sorry about that. (I can see from the tone of your response that you're
a real stickler for politeness.) I've attempted to restart the thread,
in a new message, with new headers. HTH.
> Second, do not use those characters in file names, period. Even if the app
> and OS allows you to do so, other apps, like backup and recovery, may not
> like them, so don't. And, if I were going to point to any of them its the
> file name issue.
>
>
I don't have problems with any other apps including MSO, Cygwin, MySQL,
Perl, shells, Xnview, Abiword, Acrobat, NVu, all kinds of backup, etc.
So, if that's the reason, it's a bug in OOo.
(I didn't mention it before, because I didn't think it was relevant, but
there are many characters that I do not tolerate in file names,
including: <space>, <comma>, <apostrophe>, '(', ')', '[', ']', '&',
any non-printing characters, any byte character greater than 127, such
as <TM-symbol>, <copyright symbol>, or <umlauted or diacritically marked
vowels>. I also try to avoid '$'s. This makes the ones that I do use,
including the aforementioned ones all the more important. My view of the
desirable and undesirable characters has to do with automatic processing
for backup, archiving, etc, using GNU tools from the Cygwin suite.)
I'm new to this list, so I'm not sure of the protocol, here, yet, but I
do know my way around the PC, Windows, *u*x, office, support, user
forums, etc, so I'd appreciate not being blown off with "authoritative
(autocratic?)", but superstitious edicts.
Moreover, the problem occurs sometimes when the aforementioned
characters are not in the file name. I mentioned the characters to see
if there was a known bug that was being worked on. My actual suspicion
was that it had to do with the single directory for backup. I've
experimented a bit, and haven't gotten a bead on the precursing events.
After waiting a while to see if there are more detailed responses I'll
do a more systematic research, and report the results, if anybody cares
and if they're consistent. I'm starting to use OOo, a lot more because
I've become addicted to the outline feature (although I still haven't
mastered it, yet), so I've got to get this figured out as a matter of
self-preservation..
Am I missing a bug reporting venue for OOo?
Also, are there other venues for OOo _and_ XML, or DocBook?
Thanks.
Lee
Lee D. Rothstein
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]