On 2-3-2010 13:34, T T wrote:
best is to settle on long names consistently (i noticed some short name issues a while ago)
This is not possible for two reasons: 1) there is still some old software breaking on long paths occasionally (or rather on names with spaces); we struggled recently with dviout but this is resolved now; I'm not aware of any other cases, atm. 2) even if we ignore old programs, short paths are accepted thoughout the Windows API and pop-up in various places from time to time (e.g. %TEMP% var); moreover, paths specified in mixed short/long convention are OK too and the only way to get a cannonical path on Windows is through GetShortPathName (or it's twin GetLongPathName, but this one is not nearly as useful)
isn't there a flag somewhere that makes env vars expand into long paths? Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------