4 Replies Latest reply on Feb 15, 2007 5:36 PM by Newsgroup_User

    the tides have turned

    Level 7
      I remember when it seemed the Mac didn't care at all about file names but
      the PC was always verys stubborn about the rules.

      No it seems that it's the opposite. I have a project that opens PDF's,
      Excel sheet, etc and the file names have spaces and are very long because
      the client maintains a description of the file and the version number in
      each file name.

      For the longer names, OS 10 can't open certain documents and the pattern
      seems to be the longer files names. This happened with some mpeg file names
      as well. I've shortened the names and gotten rid of any spaces but I'd like
      to know what the actual restriction (s) is/are that I've run into here on
      the Mac. Anyone know?


      --
      Craig Wollman
      Lingo Specialist
      Word of Mouth Productions
      212-928-9581

      www.wordofmouthpros.com


        • 1. Re: the tides have turned
          Level 7
          forum.macromedia.com wrote:
          > I remember when it seemed the Mac didn't care at all about file names
          > but the PC was always verys stubborn about the rules.
          >
          > No it seems that it's the opposite. I have a project that opens
          > PDF's, Excel sheet, etc and the file names have spaces and are very
          > long because the client maintains a description of the file and the
          > version number in each file name.
          >
          > For the longer names, OS 10 can't open certain documents and the
          > pattern seems to be the longer files names. This happened with some
          > mpeg file names as well. I've shortened the names and gotten rid of
          > any spaces but I'd like to know what the actual restriction (s)
          > is/are that I've run into here on the Mac. Anyone know?

          I didn't think that unixen had such restrictions, so maybe it's a limitation
          of the xtra you're using to open the files.

          Ooh, hang on - the filenames don't have forward slashes in them, as in the
          unix path separator, do they? That could confuse something somewhere. OS X
          has to do something strange so that slashes can still be used in filenames
          as they were in MacOS.

          Andrew


          • 2. Re: the tides have turned
            Doc Raman Level 1
            As Andrew said, it is basically due to some things not being updated to use the long filenames.

            Various programs (and networking configurations) have issues with long name, although on the unix side of things under the hood that isn't a problem.

            I still keep short names to be sure of compatibility on all fronts.
            • 3. Re: the tides have turned
              Level 7
              No forward slashes. Nothing special, just some spaces and a some dashes. I
              did find that it was the burning process that is truncating filenames longer
              than 31 characters including the extension. Strange. When the projector is
              run from the partition on the Mac it's fine but when burned to a CD than
              played back on various Mac's, the longer file names aren't found. When I
              went into the folder where those longer file names were, they had special
              characters at the end of the name before the .extention. I know that DOS
              puts a ~ as the 8th character when a name is longer than 8 but I've never
              seen something like this on the Mac. The Mac used a different replacement
              scheme...I don't quite remember what it was. Toast is set to Custom Hybrid
              and Joliet is the naming format.

              --
              Craig Wollman
              Lingo Specialist
              Word of Mouth Productions
              212-928-9581

              www.wordofmouthpros.com
              "Andrew Morton" <akm@in-press.co.uk.invalid> wrote in message
              news:equip2$jj7$1@forums.macromedia.com...
              > forum.macromedia.com wrote:
              >> I remember when it seemed the Mac didn't care at all about file names
              >> but the PC was always verys stubborn about the rules.
              >>
              >> No it seems that it's the opposite. I have a project that opens
              >> PDF's, Excel sheet, etc and the file names have spaces and are very
              >> long because the client maintains a description of the file and the
              >> version number in each file name.
              >>
              >> For the longer names, OS 10 can't open certain documents and the
              >> pattern seems to be the longer files names. This happened with some
              >> mpeg file names as well. I've shortened the names and gotten rid of
              >> any spaces but I'd like to know what the actual restriction (s)
              >> is/are that I've run into here on the Mac. Anyone know?
              >
              > I didn't think that unixen had such restrictions, so maybe it's a
              > limitation of the xtra you're using to open the files.
              >
              > Ooh, hang on - the filenames don't have forward slashes in them, as in the
              > unix path separator, do they? That could confuse something somewhere. OS X
              > has to do something strange so that slashes can still be used in filenames
              > as they were in MacOS.
              >
              > Andrew
              >


              • 4. Re: the tides have turned
                Level 7
                If it's Toast that you're saying might not be up to date, I suppose it's
                possible.

                --
                Craig Wollman
                Lingo Specialist
                Word of Mouth Productions
                212-928-9581

                www.wordofmouthpros.com
                "Doc Raman" <webforumsuser@macromedia.com> wrote in message
                news:eqvikv$r13$1@forums.macromedia.com...
                > As Andrew said, it is basically due to some things not being updated to
                > use the
                > long filenames.
                >
                > Various programs (and networking configurations) have issues with long
                > name,
                > although on the unix side of things under the hood that isn't a problem.
                >
                > I still keep short names to be sure of compatibility on all fronts.
                >