Windows shortens Font file name?

Hello, I just ran across what I believe to be an anomaly having to do with Windows Fonts. When I install a Type 1 font named OP______.PFM after installation, the file name, as it sits in C:\windows\fonts is now, OP_____.PFM. Yes, that is one
_ different then the original file name as it sits outside of the fonts directory. Windows appears to have shortened the file name during the installation of the font. We run SCCM 2012 and I wanted to know which PC's had this font installed so
I told SCCM to take inventory of OP______.PFM files in the Fonts directory . Nothing ever showed up in my reports so I've been beating my head against the wall for 2 days now searching client and server logs. Until I found out the file name was
shortened. I've since decided the % wildcard is my friend. ;-)
Anyway, I am posting here to simply find out if this is known behavior and if so, are there other places in Windows where file names get shortened?
Thanks for your time.

The most likely culprit is the font package itself. The font name is specified within the package and it would have been an error by the programmer, not a Windows anomaly.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”

Similar Messages

CS6 Links Window Shows jpeg file name but not tiff or psd file name

So I have a question, I noticed that in CS5 and CS6 that when i place a jpeg file in Illustrator, the file name does appear in the links window, but when i place a tiff or a psd file there is no file name in the links window, this drives me nuts. Is there a way to see the files name of placed psd and tiffs in the links window?

Here's my thoughts...
1. You are a bit confused and I wonder how you can determine a file is a PSD or a TIF by looking at it? Not all print drivers can recognize PSD's, but can recognize TIF ( this means almost all output devices can interpret TIF's no problem ). That said, PSD's can manage layers better than TIF's which add to file size each layer you include in the TIF.
2. Never say never. This all depends on the file's use. Layered TIFs can add complexity in which a print driver can or cannot deal with. As you work on an image, you may want to merge layers for whatever reason(s) and you always have the option to flatten whenever you feel like it. However, It is also a good idea to dupe the file as you move along. That means you always have a layered version to fall back on should you need to edit later on. I also Place transparent PSDs in Illustrator files with no problems. But, I save as EPS in Illustrator and when I do that, then the file is automatically flattened. This is perhaps what the internet was talking about.
3. Yes, see number 2 above. There's no such thing as automatic flattening of TIFFs. Again, this all depends on the printer and whether or not it can print while retaining original layers. Some do, some don't. Most of the time, I edit in PSD with layers intact. Then, when I prep the file for printing, I will save a copy as a flattened TIFF so the file streamlines through the RIP and Print process.
4. Makes no difference. Use 'em if you've got 'em.
Try to get some good resource material at a library or college bookstore or barnes & noble. Also, get Adobe's Print Publishing Guide. This is a good reference guide.
Message was edited by: John Danek

How do I shorten my file names

I have my catalog the way it should be but the file names seem to go forever. example top 45 copy 11111111111111.edit can I like turn them back to a simple file name I have thousands I need to do this to

Technical answer: yes, you can change your file names with large amounts of tedious effort; you will have to change each individually, using Organizer (not Windows)
Practical answer: It is not worth the effort.
Why does it even matter what the file names are?

Windows sharing long file names

Just after a bit of advice with regards long file names with OSX/Win.
I have a user that uses a mixture of SL and ML connection a shares on a Win 2008 R2 server. They had some issues a while back with long file names ( I think folder depth more than anything) and a previous engineer installed ExtremeZ-IP. However ever since they've been having random file permission issues.
I'm keen to remove the ExtremeZ software as I see it as an extra piece of management and failure and with the news of Apple dropping AFP, makes sense to lose it when possible. I do have other users using OSX and Win 2008 servers with no 3rd party software and not having any issues.
I'm thinking that the original problem was with using AFP not liking the Win file names and instead of moving to SMB, the software 'fix' was used. I feel that removing this software and forcing the clients to use SMB, will hopefully resolve the permission issues and have no implications on file names.
I would be grateful if someone could shed some light or thoughts on this if anybody has similar experience.

I suspect they are connecting to the server using Samba and you're using afp ?

Open files window cuts off file name and features date

How do I change this annoying behavior? Happens every time I need to open a new file within InDesign.

That's a standard Mac dialog...
Grab the right edge dividing line on the Name column label and drag it to the right.

Get a font's file name from the font's postscript name (on Windows)

I am trying to obtain the the font file name when the only information I have is the font's 'postscript' name. (Emphasis: the font's name is postscript and not the font).
For example I have the following postscript name: TimesNewRomanPSMT.
The real name that is saved in the registry is: Times New Roman (TrueType).
Is there any way of obtaining that name from the given postscript name?
Currently I am coding this for Windows, but it should be compatible, or at least have alternative code for MacOS

Funny. I'm having the same problem and was about to post the exact same question
In Photoshop, there is "app.fonts", which lets you get a font's postscript name from the font's name. This doesn't exist in After Effects.
My only hope is that there's a way to get a font's postscript name in Visual Basic. I'll let you know if I find anything useful.

File name too long cannot copy (cont'd)

This is a continuation of the post started September 01, 2009, with the last post on
October 17, 2011 named File name too long cannot copy
Since this is an ongoing unsolved issue, and the thread was locked, it continues here.
It is ever so easy to create a long file/path using explorer.exe as will be shown below.
What needs to be solved is, what is an easy way (no, not by listing out all the files in a directory to a text file and counting characters), perhaps using a shell extension, to find out which files in a directory and it's subdirectories will be (or were)
too long to copy, (and then perhaps even copying those over either intact or renamed)?
Maflagulator said:
I'm running the 7100 build...enjoying it except for one big thing:
While attempting to copy 402gb from my main storage volume onto a spare 500gb drive (for the purpose of changing to a new RAID array) I've come across something that I would expect a Windows 98 OS to give me.
It tells me that a file has TOO LONG of a file name, then provides with two unhelpful options: SKIP or CANCEL
I never had XP give me an issue like this at all, so what gives? And while some specific files did have long file names (such as for songs, etc.) it had 7 issues with folders stating that their name was too long, but in fact they were not since they were
titled '07-06-07' for the date that I dumped the audio files in them. However, they may have contained FILES with long file names though.
Anyone else get this same situation? Perhaps the RTM version does not do this? Can anyone verify this regarding their install of the RC or the RTM?
It made it through 400gb out of the 402gb transfer.
I'm just happy to see that it doesn't spazz out about an issue like this until it has done all the other transfers that it can do because it saves the issues it has with files until the very end. In XP it would spazz about it the moment it came across it
causing the transfer process to halt.
Since long path/file names can so easily be created on Win7, it might be useful to see a typical way this happens, which might then give clues how to work with them.
In Windows Vista, we learnt from:
File names and file name extensions: frequently asked questions that:
Windows usually limits file names to 260 characters. But the file name must actually be shorter than that, since the complete path (such as C:\Program Files\filename.txt) is included in this character count.
In Windows 7, we are told here:
File names and file name extensions: frequently asked questions that:
It depends on the length of the complete path to the file (such as C:\Program Files\filename.txt). Windows limits a single path to 260 characters. This is why you might occasionally get an error when copying a file with a very long file name to a location
that has a longer path than the file's original location.
From the Windows Dev Center - Desktop, we read about Maximum Path Length Limitation here:
Naming Files, Paths, and Namespaces
This helps us understand why a folder can be a maximum of 244 characters, from the defined 260 length of MAX_PATH as follows:
260 minus C:\ (3) minus <NUL> (1) = 256
256 minus 8.3 file name (12) = 244
We also learn there that: The Windows API has many functions that also have Unicode versions to permit an extended-length path for a maximum total path length of 32,767 characters.
And we read the claim that: The shell and the file system have different requirements. It is possible to create a path with the Windows API that the shell user interface is not be able to interpret properly.
There is also a comment below this document that reads: In a previous iteration of this document, it is mentioned that The Unicode versions of several functions permit a maximum path length of approximately 32,000 characters composed of components up to
255 characters in length. This information is now gone.
So we are in a position where the file system and Windows API can create long path/flies that the shell cannot handle.
But then we need to be able to handle it, so a little exploration might lead to a better understanding of how to do this.
For most tasks being performed on long folder/files, Windows 7 and other Windows programs balk when the Path+Filename length > 260
Let's create a long path/file.
Create a folder called A at the root of a Drive.
Create a sub-folder of A called: B
Create a sub-folder of B called: C
Make a FILE in sub-folder C called (no spaces or break, one long continuous string): 123456789A123456789B123456789C123456789D123456789E123456789F123456789G123456789H123456789I123456789J 123456789K123456789L123456789M123456789N123456789O123456789P123456789Q123456789R123456789S123456789T
123456789U123456789V123456789W123456789X123456.txt
Rename sub-folder C to the string (no spaces or break, one long continuous string) (The actual directory created will be slightly shorter than this full length): 123456789A123456789B123456789C123456789D123456789E123456789F123456789G123456789H123456789I123456789J
123456789K123456789L123456789M123456789N123456789O123456789P123456789Q123456789R123456789S123456789T 123456789U123456789V123456789W123456789X123456789Y123456789Z
Rename sub-folder B to the same full string above. (The actual directory created will be slightly shorter than this full length but 2 characters longer than the step above.)
Rename folder A to that same full original string. (Again the actual directory created will be slightly shorter than this full length but 2 characters longer than the step above.)
You now have the lovely file placed at (the breaks are just so it fits into the screen):
C:\123456789A123456789B123456789C123456789D123456789E123456789F123456789G123456789H123456789I123456789J 123456789K123456789L123456789M123456789N123456789O123456789P123456789Q123456789R123456789S123456789T 123456789U123456789V123456789W123456789X1234\ 123456789A123456789B123456789C123456789D123456789E123456789F123456789G123456789H123456789I123456789J
123456789K123456789L123456789M123456789N123456789O123456789P123456789Q123456789R123456789S123456789T 123456789U123456789V123456789W123456789X12\ 123456789A123456789B123456789C123456789D123456789E123456789F123456789G123456789H123456789I123456789J 123456789K123456789L123456789M123456789N123456789O123456789P123456789Q123456789R123456789S123456789T
123456789U123456789V123456789W123456789X\ 123456789A123456789B123456789C123456789D123456789E123456789F123456789G123456789H123456789I123456789J 123456789K123456789L123456789M123456789N123456789O123456789P123456789Q123456789R123456789S123456789T 123456789U123456789V123456789W123456789X123456.txt
You have a folder length of over 700 and a file length of over 250 for a total of over 950
However you will notice that each folder, when created, could only be a maximum of 247 charachters including the path (example C:\ , & C:\A , & C:\A\B
This only applies backwards, that is up the path. It did not matter what was further down the path.
Now, you can't easily access or rename the file, but you can rename the folders easily.
For best results, start renaming from the top of the Tree, working down the subfolders, because renaming from down up will limit you, and in fact won't work if the folder lengths are too long.
So how might knowing this help us?
Well, to copy this long_file from the C:\ drive to the D:\ drive, and keeping the path structure, this should work:
Note the name of the top folder. Rename it to something very short, say: A (Make sure C:\A does not exist)
Note the name of the 2nd folder. Rename it to something very short, say: B (Make sure C:\A\B does not exist)
Note the name of the 3rd folder. Rename it to something very short, say: C (Make sure C:\A\B\C does not exist)
Make sure D:\A does not exist - then copy the A folder on disk C: to disk D: (which gives you D:\A\B\C\long_file
Rename D:\A\B\C to D:\A\B\Original_3rd_Folder_name
Rename D:\A\B to D:\A\B\Original_2nd_Folder_name
Rename D:\A to D:\Original_top_Folder_name
Rename C:\A\B\C back to their original names, in this same reverse order starting with C, then B, then A
Note: If using Explorer, at some points you might have to press the F5 refresh key.
This is of course how you might copy such long path/files without using the other more "easy" techniques for the "normal" everyday user like:
sharing a sub-folder
using the commandline to assign a drive letter by means of SUBST
using AddConnectionunder VB to assign a drive letter to a path
using the "\\?\" prefix to a path string to tell the Windows APIs to disable all string parsing and to send the string that follows it straight to the file system
and so on.
See how simple Windows can be for Dummies!
But then, how can we know that files to be copied exceed this MAX_PATH? Or also after a copy has taken place, know exactly which files that have NOT been copied because of exceeding the MAX_PATH limit, and then a procedure to copy these either by renaming
them, or by copying them intact as they are?
There have been suggestions to use
LongPathTool, but this does not have a facility to check a series of folders and tell you which files are going to be caught by the error when copying. So once a copy has taken place using Windows 7, one does not know which files did not get copied, and
where exactly they are located.
Neither does the free
Old Path Scanner do that. It can only check for overly long directory paths, but misses out when the directory path is within limits, but adding in the file name puts it out of bounds.
So, as shown above, it is ever so easy to create a long file/path using explorer.exe
So, what then is an easy way (no, not by listing out all the files in a directory to a text file and counting characters), perhaps using a shell extension, to find out which files in a directory and it's subdirectories will be (or were) too long to copy,
(and then perhaps even copying those over either intact or renamed)?

This is a not a "solution" ....but a "work around": a low tech fix....for error message "your file name is too long to be copied, deleted, renamed, moved" :
1.   problem is this: the "file name" has a limit on number of characters.....the sum of characters really includes the entire path name; you gotta shorten it first (i.e, if the total number of characters in the file name + Path name are over the
limit, the error appears). The deeper your file folder sub levels are, the more this problem will come up, especially when you copy to a subfolder of a subfolder/subfolder of another path ...adds to character limit)
2. How do you know which combined file names + path names are too long if you are in the middle of a copy operation and this error pops up? Some files copied but the "long files error message" says "skip" or "cancel" ... but not which
files are the "too long" ones. If you hit "skip" or "cancel" the "too long" files are left behind...but are mixed in with non-offender "good" "short name" files.   Sorting thru 1000s of "good" files to find a few "bad" ones manually is impractical.
3.   Here's how you sort out the "bad" from the "good":
4.    Let's say you want to copy a folder ..."Football" ...that has five layers of subfolders; each subfolder contains numerous files:
C:/1 Football / 2 teams/ 3 players/ 4 stats/ 5 injuriessidelineplayerstoolong
       There are five levels root "1 football" with subfolders 2, 3, 4 and lastly "5 injuries"
5.    Use "cut" and "paste" (for example to backup all five levels to a new backup folder):
       select "1 football" ....cut....select target folder....paste
       ("cut" command means as the files are copied to the target destination, the file is deleted from the source location)
      Hint: avoid "cut" and "paste" to a target folder that is itself a sub/sub/sub folder ...that compounds the "characters over the limit" problem ...because the characters in the sub/sub/sub folder are included in the "file name
character limit"...instead "paste" to a C:/ root directory.
       Suppose in the middle of this operation...error pops up: "5 files have file names that are too long" Skip or cancel?
       select "skip" ...and let operation finish
6.    Now go back and look at the source location: since the software allows only the "good" "short name" files to be copied (and because you "skipped" the "bad" "Long name" files so they are not copied or deleted) ...all that remains
in the source location are the "bad" "long name files" (because "good" ones were deleted from the source location after the "cut" operation...the bad ones stick out like a sore thumb.
7.   You will find ....all that remains in source folders are: the "bad" "too long" files; in this example the "bad" file is in level 5:
      C:/ 1 football / 2 teams /3 players /4 stats /5 injuriessidelineplayerstoolong
8.   select folder 5 injuriessidelineplayerstoolong (that's right...select folder, not file) gotta rename the folder first.
9. hit F2 rename folder..folder name highlighted...delete some of the letters in the folder name:
       like this:   5 injuriessidelineplayers ....you should delete 'toolong'....from the folder name
10. then go into folder 5....and do the same operation ...with the too long file name:
        hit F2 rename file....file name hightlighted...delete some of the letters
           like this: injuriessidelineplayers.....you should delete 'toolong' from the file name
11. Now..."cut and paste" the renamed file to the target backup folder.
The Error message will pop up again if you missed any "bad" files....for example, it will indicate "5 files too long" ....then repeat process 5 times until you fix all of them
12.    Finally, copy the target destination files back to the source location (when you are certain all source location file folder locations are empty)
Of course, this "makeshift" solution would not be necessary if MSFT would fix the problem...

NT ATHORITY WITH LONG FILE NAME DESTROYING MY PC

THIS NT ATHORITY HAS REMOVED ALL GROUP POLICES,WRIGHTS TO FILES,FOLDERS.INHERIED RIGHTS TO DRIVES,SLOWLY DESTRORYS,ALL SECURE UPDATES,STACK UNKNOWN SOFTWARE,.DLL FILES OUT OF CONTROL.I BEEN WORKING WITH PCS AND WINDOWS FOR 20 YEARS,IM 56.NEVER SEEN SO
MANY SERVICES RUNNING WITH COMPLETE CONTROL OF PC.I USE ALL METHODS REQUIRED,VIRUS,MALWARE,TRY PROTECT FILES, ETC.BROWSER AND REGISTRY TAKING OVER.ITS THE SAME NT ATHORITY (LONG NAME)NO MATTER WHAT PC I OWN.(I HELP FIX OR UPDATE PCS WHERE I LIVE.DISABLED HOUSING,HELPING
MY NEIGHBORS WHEN I CAN.ALL MY PCS AND SOFTWARE ARE REGISTORED AND I COMPLY WITH ALL MICROSOFT,WINDOWS ,ACCEPT POLICYS.PLEASE HELP ME,AND MY DISABLED AND ELDERLY FRIENDS.PHONE 903-609-8628 HM.AND 903-401-O833 mobil.THANK U

Ugh. There are basically three people here, who show up repeatedly and relentlessly, always eager to explain that it wasn't Adobe's fault at first. (FTC regulations require them to disclose that they're compensated by Adobe.) I'm sure that even the actual authors of these applications don't like that first line of defense as it ultimately makes Adobe look bad, diluting useful feedback. Yes, we also file bug reports and yes, this bug was reported several times ever since at least CS5. Also, no reasonable user is too stubborn to shorten source file names, and that bug isn't the real issue -- it's that Adobe's applications (like this Encore example) simply freak out and crash over a well-known, clearly identified bug and then give no guidance as to what happened, or how to resolve it. So Adobe customers spend hours trying to find the answer -- around the distractions of those three guys -- and increasingly lose faith in the Creative Suite.
Stan, thanks for a concrete question that could lead to diagnosis. The file name that caused Encore to crash at the transcoding stage was not too far into the directories on my media drive, and named: "KIMIKO ISHIZAKA - Goldberg Variations BWV 988 - 16 - Variatio 15 a 1 Clav. Canone alla Quinta__44k-16b (with leading silence).wav" Once I halved the length of the filename (notably, while leaving in the spaces and dashes and underscores), it was smooth sailing. So, you could simply rename any of your audio files to that, import the asset, and try to transcode at final output to see what happens. Will be curious to know what you find, thanks!

File names when saving scanned documents

When I scan a document and then try and save the same, The scanned document is saved hiwever the name that I give to the scanned document gets truncated. I dont understand why, I am using windows 7

That is a long File Name.
Did you create this long file name system at the same time you started scanning these documents?
You have .pdf and .ld together as the file extension in the image you provided. What is .ld?
Can you go to the file name and rename it to add the other characters and it stays?
If not, I don’t think it’s the HP software doing this. It is most likely Windows.
The only thing I can think of is that Windows uses what’s called an 8.3 file naming convention. It is built into Windows and it shortens long file names for MS-DOS legacy applications. Every long file name has an alias that complies with the 8.3 file names for backward compatibility.
Take a look at this article from Microsoft on truncating names. This will explain what is happening (hopefully).
http://support.microsoft.com/kb/142982
Also,
Short file names may contain only the following characters:
·         Numbers (0,1-9)
·         Letters (A-Z, a-z)
·         Blank (blank spaces)
·         ASCII characters greater than 127
·         Special characters: $ % ' - _ @ ~ ` ! ( ) ^ # &
Long file names may contain only the following characters:
All of the characters supported by short file names
·         Special characters: + , ; = [ ]
Length of the long file names are limited to 255 characters (260 for full paths = the file name and root of the folder) and short file names are limited to 8+3 or 11 characters (80 for full path names).
You can disable the 8.3 convention in Windows but there may be problems with some applications not being able to find files and directories that have long file names.
This Microsoft article explains how to disable 8.3 on NTFS partitions.
http://support.microsoft.com/kb/121007
You will need to be logged in as an Administrator on the account. IF this computer is at your employers, you will have to contact their IT support for further discussion.
Go to Start and type CMD in the Search bar. Right click on CMD in the list and choose Run as Administrator.
Type in the command prompt
fsutil.exe behavior set disable8dot3 1
and press Enter.
This operation takes effect immediately (no restart required).

How to creat the logical file name.

Hello All,
I want to create Logical file name in my program, So Please guide me in this issue.
Thanks

Check this out
http://help.sap.com/saphelp_45b/helpdata/en/2a/fa02b7493111d182b70000e829fbfe/content.htm
FU FILE_GET_NAME
Text
Assign the Physical File Name Using a Logical File Name
Functionality
R/3 applications run on various platforms with various file systems. This function module enables you to use platform-independent logical file names in your application programs.
Based on definitions maintained in customizing tables for platform-independent file names, the function module converts a logical file name to the corresponding physical file name and path for the hardware platform concerned.
For this conversion to work for different platforms, the definition of a logical file name must include a logical file path, which in turn is converted to different physical file paths, depending on the particular platform. The platform-specific file name returned by the function module is composed of the physical file path for the current platform and the physical file name associated with the logical file name. Placeholders in physical file and path names are substituted at runtime by the corresponding current values.
Example
logical file name: MONTHLY_SALES_FILE
physical file name: VALUES<PARAM_1>
logical path: SALES_DATA_PATH
physical path (UNIX): /usr/<SYSID>/<FILENAME>
physical path (Windows): C:\SALES\<FILENAME>
Example 1
Get file name for UNIX platform
(current system: K11)
CALL FUNCTION 'FILE_GET_NAME'
EXPORTING
LOGICAL_FILENAME = 'MONTHLY_SALES_FILE'
IMPORTING
FILE_NAME = FILE
FILE_FORMAT = FORMAT.
Result:
FILE = /usr/K11/VALUES
FORMAT = WK1
Example 2
Get file name for UNIX platform, passing a parameter
(current system: K11)
CALL FUNCTION 'FILE_GET_NAME'
EXPORTING
LOGICAL_FILENAME = 'MONTHLY_SALES_FILE'
PARAMETER_1 = '_TST'
IMPORTING
FILE_NAME = FILE
FILE_FORMAT = FORMAT.
Result:
FILE = /usr/K11/VALUES_TST
FORMAT = WK1
Example 3
Get file name for WINDOWS platform, with file name extension
CALL FUNCTION 'FILE_GET_NAME'
EXPORTING
LOGICAL_FILENAME = 'MONTHLY_SALES_FILE'
WITH_FILE_EXTENSION = 'X'
IMPORTING
FILE_NAME = FILE
FILE_FORMAT = FORMAT.
Result:
FILE = C:\SALES\VALUES.WK1
FORMAT = WK1
Notes
All definitions needed for the platform-independent assignment of file names are maintained client-independently with transaction FILE. Logical file names (but not logical file paths) can also be defined specifically for the current client with transaction SF01. Transaction SF07 generates a list of current definitions.
The following concepts are used in the platform-independent assignment of file names:
Logical file name
A descriptive name for a file which is associated with these values:
physical file name
file format
logical file path.
If no logical file path is specified, the function module returns the physical file name only; placeholders are substituted by current values.
Physical file name
The physical file name may contain placeholders.
Logical file path
A descriptive name for a path which is associated with these values:
syntax groups (groups of operating systems)
physical file paths.
Physical file path
The physical file path is defined for a particular syntax group. It must contain the reserved word <FILENAME> as a placeholder for the file name. It may also contain other placeholders.
Operating system
Presentation server and application server can run under different operating systems. The current value for the application server can be obtained from the system field SY-OPSYS, the value for the presentation server by calling function module WS_QUERY.
Both operating systems must be defined and assigned to a syntax group.
Syntax group
Group of operating systems with a common syntax for file and path names (e.g. HP-UX and SINIX).
Placeholder
Reserved words, set in angle brackets, which can be included in physical file and path names (e.g. <DATE>, <FILENAME>). You can find information on possible reserved words in the online help (F1 help) for the fields physical file name and physical file path when maintaining platform-independent file names with transaction FILE.
If the logical path associated with a logical file name does not specify a physical path for the current operating system (syntax group), the path stored in the profile parameter DIR_GLOBAL of the current system is used for generating a complete platform-specific file name.
Parameters
CLIENT
LOGICAL_FILENAME
OPERATING_SYSTEM
PARAMETER_1
PARAMETER_2
PARAMETER_3
USE_PRESENTATION_SERVER
WITH_FILE_EXTENSION
USE_BUFFER
ELEMINATE_BLANKS
EMERGENCY_FLAG
FILE_FORMAT
FILE_NAME
Exceptions
FILE_NOT_FOUND
Function Group
SFIL
Thanks
mahesh

Variable Substitution in file name on the sender CC in PI 7.1

Hi
I am working on a File to File scenario, where I need to shorten the file name to something like mode1, mode2 or mod3,
How can i achive this, Please let me know if there is any example
Thanks
PR
Edited by: PR on Oct 29, 2009 1:08 PM
Edited by: PR on Oct 29, 2009 1:09 PM

Hi,
Mode1, mode2 and mode3 are file names?
You can achieve this by using 'Advanced Selection for Source File' in Communication channel in ID.
Refer the advanced selection of Source file concept from following link:
http://help.sap.com/saphelp_nw70/helpdata/en/e3/94007075cae04f930cc4c034e411e1/content.htm
-Supriya.

Logical File name of Transaction File

Hi All,
I am using FILE_NAME_GET function module to get the Physical file name based on logical file name.
But here i am not getting total file name, i maintained Physical File name as ZDM\INTB18\<PARAM_1>.
Transaction File is stored in application server and it's name is ZDM\INTB18\RMCB18_DATETIME.
Could you please anybody suggest how to get total file name.
Thanks,
Rami Reddy.

Hi Rami,
Have you utilised the Parameter WITH_FILE_EXTENSION in the function ... e.g.
Example
logical file name: MONTHLY_SALES_FILE
physical file name: VALUES<PARAM_1>
logical path: SALES_DATA_PATH
physical path (Windows): C:\SALES\<FILENAME>
Get file name for WINDOWS platform, with file name extension
CALL                                                                                FUNCTION                                                                                'FILE_GET_NAME'
   EXPORTING
      LOGICAL_FILENAME = 'MONTHLY_SALES_FILE'
      WITH_FILE_EXTENSION = 'X'
   IMPORTING
      FILE_NAME = FILE
      FILE_FORMAT = FORMAT.
Result:
FILE = C:\SALES\VALUES.WK1
FORMAT = WK1
Rgds, Derrick

Missing Breadcrumbs Caused by Similar File Names

Using RH9
Producing both WebHelp and HTML Help (with missing breadcrumbs the same in both)
Using only the SSL option to generate the breadcrumbs
As in some previously posted cases, a few topics in a large project are missing breadcrumbs. There are no quotation marks or other unsual characters in the file names or titles. I was able to narrow down one error to something I could fix in a test project.
In the following HHC entries, the breadcrumbs were missing from the "General Ledger Processing Recap (AM72)" topic when the help was generated. (Everything after the second item is a bookmarked TOC entry, with no breadcrumbs expected, but I left those items in the example in case they make a difference.)
<item name="General Ledger Options" link="SYSOVER\General_Ledger_Options.htm">
<item name="General Ledger Processing Recap (AM72)" link="SYSOVER\General_Ledger_Processing_Recap_AM72.htm">
<item name="What is a General Ledger Processing Recap?" link="SYSOVER\General_Ledger_Processing_Recap_AM72.htm#What_is_a_General_Ledger1">
</item>
<item name="Benefits of Using the General Ledger Processing Recap (AM72)" link="SYSOVER\General_Ledger_Processing_Recap_AM72.htm#Benefits_of_Using_the">
   <item name="User-Defined Recap Report" link="SYSOVER\General_Ledger_Processing_Recap_AM72.htm#User_Defined_Recap_Report1">
   </item>
   <item name="Ease of Defining Interface Data" link="SYSOVER\General_Ledger_Processing_Recap_AM72.htm#Ease_of_Defining">
   </item>
   <item name="Operations Balancing" link="SYSOVER\General_Ledger_Processing_Recap_AM72.htm#Operations_Balancing1">
   </item>
</item>
<item name="Components of the General Ledger Processing Recap (AM72)" link="SYSOVER\General_Ledger_Processing_Recap_AM72.htm#Components_of_the">
   <item name="Section" link="SYSOVER\General_Ledger_Processing_Recap_AM72.htm#Section">
   </item>
   <item name="Line" link="SYSOVER\General_Ledger_Processing_Recap_AM72.htm#Line">
   </item>
   <item name="Item" link="SYSOVER\General_Ledger_Processing_Recap_AM72.htm#Item">
   </item>
</item>
<item name="Defining the General Ledger Processing Recap (AM72)" link="SYSOVER\General_Ledger_Processing_Recap_AM72.htm#Defining_the_General">
   <item name="Completing Worksheets" link="SYSOVER\General_Ledger_Processing_Recap_AM72.htm#Completing_Worksheets">
   </item>
</item>
<item name="Defining the Recap" link="SYSOVER\General_Ledger_Processing_Recap_AM72.htm#Defining_the_Recap">
   <item name="Entering the Recap Definition Online" link="SYSOVER\General_Ledger_Processing_Recap_AM72.htm#Entering_the_Recap">
   </item>
</item>
<item name="Defining the Section" link="SYSOVER\General_Ledger_Processing_Recap_AM72.htm#Defining_the_Section">
</item>
<item name="Defining the Lines" link="SYSOVER\General_Ledger_Processing_Recap_AM72.htm#Defining_the_Lines">
   <item name="Valid Escrow Source Codes" link="SYSOVER\General_Ledger_Processing_Recap_AM72.htm#Valid_Escrow_Source_Codes">
   </item>
   <item name="Entering the Recap Line Definition Online" link="SYSOVER\General_Ledger_Processing_Recap_AM72.htm#Entering_the_Recap_Line">
   </item>
</item>
<item name="Verifying the Recap Definition" link="SYSOVER\General_Ledger_Processing_Recap_AM72.htm#Verifying_the_Recap">
</item>
<item name="Building the Recap Definition Files" link="SYSOVER\General_Ledger_Processing_Recap_AM72.htm#Building_the_Recap">
   <item name="Processing Recap Structure Validation Report" link="SYSOVER\General_Ledger_Processing_Recap_AM72.htm#Processing_Recap">
   </item>
   <item name="Printing the Report Structure Validation Report and the Sample General Ledger Processing Recap" link="SYSOVER\General_Ledger_Processing_Recap_AM72.htm#Printing_the_Report">
   </item>
</item>
</item>
</item>
But when I changed the file name of the parent topic from General_Ledger_Options.htm to GenLdgrOpt.htm, the breadcrumbs appeared correctly in the output for the parent and child topics.
This stragegy for fixing the breadcrumb problem seems to be hit-or-miss. For example, I've tried the same approach to fix another topic and have had no success so far. Is there anything about how breadcrumbs are generated that would explain how renaming the file would fix the problem?

Rick,
I think you are right about the file name length being an important factor, but the cause doesn't seem to be as simple as a too-deep nesting level. I was able to fix the problem in another topic by shortening the file name of the topic that preceded it at the same level.
The one hard case that remains is a topic that contains a lot of bookmarked subheadings. I found that if I cut that topic's number of subheading TOC entries to 33, the breadcrumbs for the topic worked, but with 34 TOC entries, they did not. My best guess is that there is a limitation of some kind on the internal aggregation of TOC information -- including information about siblings and children.
By the way, I also tried inserting breadcrumb placeholders, instead of automatically generating them. That caused RoboHelp to crash (instead of just failing to add breadcrumbs to the offending topic). When I removed the placeholder from the bad topic, it worked OK with the other topics.

Reader not showing pdf with long file names in IE8 for standard user

Hi,
I have this problem for standard users, that is, not Admin level. Admin level users have no problems.
If a web site opens up a pdf file with java, usually in a new window, and the file name is very long (I haven't figured out how long, but visually long) then the reader plug-in won't work and opens a blank page. If the file name is small then there is no problem, and reader opens the pdf without problem.
Interestingly, if I edit the document name (say for example the link has something on the end like "&Doc_Type=Statement" which is obviously not part of the document name but part of the SQL used to find the document by the web page) then reader will open the file no problem.
Again, this doesn't happen for Administrative level users.
Any ideas on how to fix?

I'll crosspost to the reader forum.
Yes, reader works in all other situations.

Relinking to modified file names is working in CS3 and not in CS2

We are trying to remove a few characters identified as illegal(cannot be used in the file names in Windows) from the file names and then modify the InDesign layout files to relink to the modified file names. We are using the InDesign CS3 server to open up the application and work on the layout files using Java and CORBA mode(used CS3 SDK). First we remove the illegal characters from the file names. Next we will go through all the links in a layout file and will identify the links with illegal characters and relink it to the modified files. The relinking will happen to only those files which has a state NORMAL before the file names are modified. This approach works fine for the CS3 files but for CS2 after the file names got modified the link rolls back to the file path on the original m/c where the link was created and the relinking is not working.
Have anyone did something similar to that, if so can you provide with some details on how to address this issue.
Do let me know if you need any more specific information for providing your inputs to address this issue. Any inputs will be highly appreciated.
Thanks

Thanks. I got it resolved by saving the document by passing in a OptArg.makeFile() instead of OptArg.noFile(). I modified this based on what I read from Adobe Livedocs which said that any CS2 file opened in CS3 will be converted to CS3 and will be considered as a new document.

Windows shortens Font file name?

Similar Messages

Maybe you are looking for