Attachment File Names changing

J

jessieleah

Version: Entourage 2004 Version 11.1.0

Original Filename: CIM 18' wide axle view 7-20-05.pdf

The file is attached, sent, and received the filename is then: CIM 18'
wide axle view #AD13E.pdf

We have used this same type of file names in literally 1000's of
drawings, all of which were sent at one time or another via email. A
few days ago PDF (Version 6) and XLS (Excel 2004 Version 11.1.1)
attachment's filenames were being changed. Some of the filenames
changed didn't have dashes or other characters, just letters and/or
numbers. All less than 31 characters including spaces. I saw another
posting talking about maximum character length supported by Entourage
was 31.

Any ideas as to why this is happening and what to do to change fix it?

Jessica
 
J

JE McGimpsey

jessieleah said:
Version: Entourage 2004 Version 11.1.0

Original Filename: CIM 18' wide axle view 7-20-05.pdf

The file is attached, sent, and received the filename is then: CIM 18'
wide axle view #AD13E.pdf

We have used this same type of file names in literally 1000's of
drawings, all of which were sent at one time or another via email. A
few days ago PDF (Version 6) and XLS (Excel 2004 Version 11.1.1)
attachment's filenames were being changed. Some of the filenames
changed didn't have dashes or other characters, just letters and/or
numbers. All less than 31 characters including spaces. I saw another
posting talking about maximum character length supported by Entourage
was 31.

Any ideas as to why this is happening and what to do to change fix it?

My first inclination would be to check the version of Entourage that's
being used to receive the file.

Your example original filename is *NOT* less than 31 characters - it's
34, including the extension. Entourage v.X will produce the kind of
change that you cite. The only fix would be to upgrade.
 
J

jessieleah

Oh, I didn't realize the filename also included the period and file
extension. We are all using the same version of Entourage. So, if we
all upgrade to Entourage X, this will fix the problem?
 
J

JE McGimpsey

jessieleah said:
Oh, I didn't realize the filename also included the period and file
extension. We are all using the same version of Entourage. So, if we
all upgrade to Entourage X, this will fix the problem?

If you all upgrade from Entourage X to Entourage 2004, you won't have
the problem any longer.
 
M

Michel Bintener

There seems to be some confusion about the version of Entourage you and your
team are actually using, Jessica. In your original post, you wrote that you
were using Entourage 2004 v.11.1, yet the problems you're describing are
supposed to happen in Entourage v.X only, and that's why JE has been talking
about v.X all the time. So, for purposes of clarification only:
* Entourage v.X is OLDER than Entourage 2004, and the 31 characters
limitation is supposed to happen in Entourage v.X only.
* Going from Entourage 2004 to Entourage v.X is not an upgrade, but a
downgrade.
* In Entourage 2004, you should not encounter this problem anymore.
So could you please conform what version of Entourage you have?
 
D

Daiya Mitchell

There seems to be some confusion about the version of Entourage you and your
team are actually using, Jessica. In your original post, you wrote that you
were using Entourage 2004 v.11.1, yet the problems you're describing are
supposed to happen in Entourage v.X only, and that's why JE has been talking
about v.X all the time. So, for purposes of clarification only:
* Entourage v.X is OLDER than Entourage 2004, and the 31 characters
limitation is supposed to happen in Entourage v.X only.
* Going from Entourage 2004 to Entourage v.X is not an upgrade, but a
downgrade.
* In Entourage 2004, you should not encounter this problem anymore.
So could you please conform what version of Entourage you have?
PS. It sounds like these documents have been on a number of computers, so
check the Office version for all the computers. Also, I believe the 31
character limit does not apply only to Entourage, but to *all* the Office
programs in the Office X suite. All it takes is going through one person
who is running Entourage X or Excel X to munge the filenames, if I remember
correctly.
 
P

Paul Berkowitz

Not so much the question of what version jessieleah has, but what version
_everyone involved_ has.

As Michel says, 2004 is the most recent version, and the one without these
problems. As Daiya says, the problem arises (more often, in fact) with Word,
Excel and PowerPoint, in all earlier versions (v. X, 2001, 98, etc.), as
well as with Entourage X and 2001.

So what you want to do is get everyone to upgrade to Office 2004, and also
to re-save all older Word, Excel, and PowerPoint documents (checking that
the file names are what you want), or simply fix the file names in the
Finder, before sending them as attachments via Entourage 2004.

--
Paul Berkowitz
MVP MacOffice
Entourage FAQ Page: <http://www.entourage.mvps.org/faq/index.html>
AppleScripts for Entourage: <http://macscripter.net/scriptbuilders/>

Please "Reply To Newsgroup" to reply to this message. Emails will be
ignored.

PLEASE always state which version of Microsoft Office you are using -
**2004**, X or 2001. It's often impossible to answer your questions
otherwise.
 
J

JE McGimpsey

Daiya Mitchell said:
All it takes is going through one person who is running Entourage X
or Excel X to munge the filenames, if I remember correctly.

You do.
 
J

jessieleah

I STATED THE VERSION: Entourage 2004 v 11.1.0 everyone else has the
same thing. (All Office apps are 2004, all of them) I became confused
I guess, because the original reply was talking about Entourage X, when
the first thing I stated was the version of Entourage.

The documents (PDFs and Excel) are not made public, they are kept in
house. Emailed between team members and that's it.

We are all running the same versions of software. All equipment and
software were purchased at the same time. No one here has an older or
newer version of anything. I make sure the updates are done. I work
with 7 people all in the same office, trust me, we all the same version
of everything.

I did a test this morning after posting: When sending an attachment
using a long file name with the encoding of Macintosh (BinHex), the
attachment filename is truncated when the receiver gets it. I sent the
same document, but this time used the encoding Windows (MIME/Base 64)
and the filename was not truncated.

So if Entourage 2004 is suppose to support long file names, why is not
supporting them? If you need more info, please let me know.
 
C

Chris Ridd

I did a test this morning after posting: When sending an attachment
using a long file name with the encoding of Macintosh (BinHex), the
attachment filename is truncated when the receiver gets it. I sent the
same document, but this time used the encoding Windows (MIME/Base 64)
and the filename was not truncated.

So if Entourage 2004 is suppose to support long file names, why is not
supporting them? If you need more info, please let me know.

Perhaps Entourage 2004 calls some third-party library/app to do the
BinHexing. Perhaps Binhex files can't support long filenames.

Is there any reason you're not using "normal" MIME? It works pretty well,
and despite the label in Entourage, is nothing to do with Windows.

Cheers,

Chris
 
M

matt neuburg

jessieleah said:
I STATED THE VERSION: Entourage 2004 v 11.1.0 everyone else has the
same thing. (All Office apps are 2004, all of them) I became confused
I guess, because the original reply was talking about Entourage X, when
the first thing I stated was the version of Entourage.

The documents (PDFs and Excel) are not made public, they are kept in
house. Emailed between team members and that's it.

We are all running the same versions of software. All equipment and
software were purchased at the same time. No one here has an older or
newer version of anything. I make sure the updates are done. I work
with 7 people all in the same office, trust me, we all the same version
of everything.

I did a test this morning after posting: When sending an attachment
using a long file name with the encoding of Macintosh (BinHex), the
attachment filename is truncated when the receiver gets it. I sent the
same document, but this time used the encoding Windows (MIME/Base 64)
and the filename was not truncated.

You've just solved the problem. Use MIME encoding. m.
 
P

Paul Berkowitz

Perhaps Entourage 2004 calls some third-party library/app to do the
BinHexing. Perhaps Binhex files can't support long filenames.

Is there any reason you're not using "normal" MIME? It works pretty well,
and despite the label in Entourage, is nothing to do with Windows.


The norm is actually to use "Any Computer (AppleDouble)", and that should
work just fine, too, with no file name truncation. Chris must be right in
that to do BinHex, Entourage will be using the Stuffit Engine that comes
with Entourage (v7.0.4), and it's Stuffit 7 which still truncates long file
names. (If you happened to have Stuffit 9, it wouldn't, but it's not worth
buying just for that.) Either AppleDouble or MIME/Base64 should be fine.
Don't use BinHex.

By the same token, if you have to send folders, or anything else which needs
compression, don't use the built-in Macintosh (Stuffit) compression if you
want to avoid file name truncation. Again that uses Stuffit Engine 7.0.4
(unless you have your own v9 of DropStuff or Stuffit Deluxe). If you're in
Tiger, zip it instead: in the Finder, select the folder or file, right-click
or control-click it, and choose "Archive ..." That makes a .zip file with no
truncation - drag that in as an attachment. Don't drag uncompressed folders
in to Entourage messages or they will be automatically stuffed as .sit files
with file name truncation if longer than 31 characters.


--
Paul Berkowitz
MVP MacOffice
Entourage FAQ Page: <http://www.entourage.mvps.org/faq/index.html>
AppleScripts for Entourage: <http://macscripter.net/scriptbuilders/>

Please "Reply To Newsgroup" to reply to this message. Emails will be
ignored.

PLEASE always state which version of Microsoft Office you are using -
**2004**, X or 2001. It's often impossible to answer your questions
otherwise.
 
J

jessieleah

None of use the MIME encoding, just because...not default I guess.
I'll have people switch. Still, I have to wonder...Shouldn't Entoruage
support long files names no matter if I used the Binhex or MIME
encoding? Whatever the case, I am pacified.
Thanks!
 
Top