[wex]

I've been tolerating this annoying little thing for too long. Whenever I go to save a file in Word X, it truncates files over 31 characters. The exact error I get is:

------
The file name you entered is too long.
The file name cannot exceed 31 characters. Enter a shorter file name and try saving again.
------

I have a really hard time believing that that's just a limitation of Word X! I couldn't find any info anywhere on this error online. Is it just me? Is there a workaround?

Thanks,
Lance

(running on G4 Powerbook with OSX 10.4)

[CharlesS]

Yes, it's a limitation of Word X. Word X used the old-style FSSpec instead of the newer FSRef. No, there's nothing you can do about it. The workaround is to upgrade to Word 2004.

[new newton]

If you've got a file name for a Word document that's over 31 characters, you're not doing yourself any favors. KISS it. I don't know why people can't keep their file names a bit shorter. Writing out a sentence in the file name only leads to problems.

[rickey939]

Originally Posted by CharlesS

The workaround is to upgrade to Word 2004.

Correct, Word 2004 supports up to 255 characters.

[Maflynn]

Why in the world would you have such a long file name. The way the finder works you won't see the entire name when its that long.

I'm with new_newton and keeping is short and simple.

[TETENAL]

The workaround is to save the file with a shorter filename, then go into the Finder and rename it to whatever you want.

[new newton]

Originally Posted by TETENAL

The workaround is to save the file with a shorter filename, then go into the Finder and rename it to whatever you want.

That's the sort of thing that can lead to problems in the future. I've dealt with a lot of "broken" documents over the years, where the user just didn't seem to understand that a long file name wasn't healthy or necessary. Bad advice.

[CharlesS]

Originally Posted by new newton

That's the sort of thing that can lead to problems in the future. I've dealt with a lot of "broken" documents over the years, where the user just didn't seem to understand that a long file name wasn't healthy or necessary. Bad advice.

Well, sometimes you have a specific reason that a long file name is necessary (which is why they were introduced in the first place). For example, take the fact that MP3 tags are completely inadequate for classical music, forcing you to cram a whole lot of stuff in the filename. Here are the names of a few files in my iTunes music library:

01 Concerto for Orchestra - Introduzione_ Andante non troppo; Allegro vivace.m4a

2-10 Valses nobles et sentimentales_ IV. Assez animé.m4a

1-05 Symphony No. 2 in D major, op. 36; I. Adagio molto - Allegro con brio.m4a

2-04 Sonata no.1 in F minor op.120 IV. Vivace.m4a

8-13 No. 27, op. 90 in E minor - I. Mit Lebhaftigkeit und durchaus mit Empfindung und Ausdruck.m4a

etc.

[porieux]

...

[Tsilou B.]

Originally Posted by CharlesS

8-13 No. 27, op. 90 in E minor - I. Mit Lebhaftigkeit und durchaus mit Empfidung und Ausdruck.m4a

etc.

That file should be renamed to "...Empfindung..."

[CharlesS]

Originally Posted by porieux

people who use long file names usually need a lesson in hierarchical organization structures.

Okay, Mr. Smart-Ass, how should I name those files in a way that would:

1. have the full name of the work and movement visible when played on an iPod

2. not hijack fields like Artist, Composer, and Album that are already being used for their intended uses

3. work even though "Valses nobles et sentimentales", "Symphony No. 2 in D major, op. 36", "Sonata no.1 in F minor op.120", and "I. Mit Lebhaftigkeit und durchaus mit Empfindung und Ausdruck" alone are longer than 31 characters when the track number and filename extension are added, even if it were possible to separate out work and movement somehow?

Originally Posted by Tsilou B.

That file should be renamed to "...Empfindung..."

Argh, I grab one out of the almost 2000 tracks, and it would be one with a typo in it. I knew that too, since I've played that piece. Argh.

In my defense, the typo probably came from the CDDB.

[new newton]

To be fair, we're not talking about music files. We're talking about Word docs. Apples and oranges in some ways. I've never heard a good reason for having a Word file with more than 31 characters in the name. It's very easy to avoid this potential problem, and people should do so. Overly long file names are a bad habit that, in general, is pretty easy to prevent.

[porieux]

...

[CharlesS]

Okay. I thought you were referring to me since your post came immediately after mine.