How have file names longer than 31 characters?
Jim S
free myself of this limit?
Elliott Roper
<jsol...@ispwest.com> wrote:
> I need to use file names longer than 31 characters in Word. How do I
> free myself of this limit?
A. Wait for Microsoft to emit a fixed version of Word
B. In the meantime, save your file as Doofus.doc, then rename it in the
finder to "Oh migawd how much longer do I have to wait till Microsoft
can do long file names and while they are at it how about unicode
support instead of a command to draw home plate I kid you not.doc"
The good news is that you can open that file and save it with the same
name "Oh migawd how much longer do I have to wait till Microsoft can do
long file names and while they are at it how about unicode support
instead of a command to draw home plate I kid you not.doc"
While open, it will show "Oh migawd how much lo#C29E5.doc" on the title
bar, but if you save it, it saves OK with its original name. However,
if you change the name of the original file in the finder while the
document is open, Word tries to outsmart you and overwrites the
name-altered file with your new content. Your only safe way to make a
new version is to save-as with a new short name you later expand to
something useful.
Is this bright? Is this useful? I don't think so. When interworking
with Windows users, I make sure that my finished work is renamed to
something they would find no quarrel with. It is a royal pain in the
arse. Word is called a 'productivity' application. Why are there so
many 'features' that work as productivity preventers?
But in addition to "drawHomePlate" we have "InsertBackgroundSound"
in an effing word processor that won't do long filenames ferchrissake.
So *that's* all right then.
--
Swen has got to me. I thought I would be the last on earth to mangle my e-mail
address. fsnospam$elliott$$
J.E. McGimpsey
Elliott Roper <nos...@yrl.co.uk> wrote:
> But in addition to "drawHomePlate" we have "InsertBackgroundSound"
> in an effing word processor that won't do long filenames ferchrissake.
>
> So *that's* all right then.
Unicode I'll agree with you on...
...but after *years* of having to live with inventing 8.3 filenames
when my Mac was perfectly capable of 31 character filenames, just
because my clients chose to use DOS/Windows, I don't have any
problem limiting them to 31. Or even 27 if they insist on their
silly extensions.
I understand why MS didn't use the long filenames library (it wasn't
stable when they had to finalize Office v.X), and I appreciate it
('cause if they'd waited, there would have been a probably
fatally-extended period between introduction of OSX and the one
piece of software that keeps Macs reasonably tolerated in the
businessplace). I know that long filename support is on the list of
most desirable features (along with full Unicode support) for the
next version, so I'm grudgingly willing to wait.
Elliott Roper
J.E. McGimpsey <jemcg...@mvps.org> wrote:
I knew you would come in with words of sweet reasonableness. However,
just about all of my colleagues with machines from the dark side are,
by now, completely addicted to long filenames that encapsulate the
entire genealogy of the wretched file. Just about every other
application I use has improved the filename support they offer in the
same period. Especially those that had to do nothing but allow Apple to
refine their open and save dialogs, since they used the supplied
frameworks, Carbon or Cocoa, and did not crowbar in some hacks from a
totally different operating system.
It must be close to 3 years, and still there is no sign of a fix.
Anyhow, enough ranting
Happy New Year!
J.E. McGimpsey
Elliott Roper <nos...@yrl.co.uk> wrote:
> Just about every other
> application I use has improved the filename support they offer in the
> same period. Especially those that had to do nothing but allow Apple to
> refine their open and save dialogs, since they used the supplied
> frameworks, Carbon or Cocoa, and did not crowbar in some hacks from a
> totally different operating system.
As I understand it, the Office v.X dialogs are Carbon dialogs - just
using a different version than the later, long-filename versions. I
could be wrong.
In any case it's been suggested for a long while that v.X was not
likely to get "fixed", that medium-length filenames were so deeply
embedded that long filenames would have to wait for the next version.
I share your frustration that it's taken so long, but the rumor is
that the announcement of v.X + 1's debut will be made next week at
MacWorld.