2008-06-05-04T13:20Z
Gillian -
I agree with Fred Ridder's opinion that, Spaces are evil.
If memory serves, I believe that Hedley Finger would _heartily_ agree -
including avoiding spaces in names of paragraph tags and such.
Dave Stamm
Publications Specialist, Senior Staff
General Dynamics
Spaces can have unintended consequences. For example, you can have spaces in
the top row cells of a spreadsheet; for example, Full Name. But if you
attempt to query the spreadsheet programatically with ODBC and the top rows
are column headers, the space can cause problems. Underscores make a
2008-06-04-03T19:25Z
I'm not so sure it's a problem with Acrobat. I think it might be with
FrameMaker. Or, more-precisely, with the name of the .fm file.
I remember learning (from Shlomo Perets, I think) that sometimes,
FrameMaker fails - without complaint - to produce a satisfactory .ps
file.
Dave Stamm wrote (in part):
I'm not so sure it's a problem with Acrobat. I think it might be with
FrameMaker. Or, more-precisely, with the name of the .fm file.
I've encountered this problem a few times. After trying every other
solution, I shortened the name of the .fm file to not more
In addition to never using spaces... I'm remembering that it isn't the
file name itself, but the total number of characters in the path
that's the problem. I'm thinking that the limitation was 256
characters total, but that could just be the number that's popping out
of the grey cells today
Flato, Gillian wrote:
I have found that if I have a Frame file that contains a very long name,
or if it is buried deep in a network path (folder within a folder within
a folder etc.) that I can't build a PDF. I get a message that Distiller
can't open the *.tps file. If I move the Frame file to
Check File Preferences General Cross Platform File Naming. That setting
can affect how many characters are allowed in the filename, as well as
disallow certain characters in the filename because they are illegal
characters in the chosen OS.
Mike Wickham
