[tex-live] User names too longs or with diacritics on Windows

Lars Madsen daleif at imf.au.dk
Fri Apr 26 10:45:49 CEST 2013

I will not be near any Windows until Wednesday

But here is how I understand what happens in the test up.

The users share on the file server seems to be mounted as, say, the P: drive

And the Domain then redirects the normal 'Documents' folder to something like

P:\Users\name\My Documents

Such that when you add something to the Documents folder, it actually ends up in P:\Users\name\My Documents

(I think the Windows people in the organization is getting fed up with my questions about what is actually going on here).

BTW: Siep, do you happen to know about what Windows do in the situation above when one double clicks on a file?

We are trying to fix a problem with TeXStudio (I've mentioned it elsewhere in the thread).

Apparently TSX only receives a UNC path if the user double clicks the .tex file, not if TSX is started on the file via the CLI og if the file is opened via 'Open with'.

We cannot figure out it is an OS problem (where we cannot do anything) or if we can get the the path to the file in some other way.

/Lars Madsen
Institut for Matematik / Department of Mathematics
Aarhus Universitet / Aarhus University
Mere info: http://au.dk/daleif@imf / More information: http://au.dk/en/daleif@imf

From: tex-live [tex-live-bounces at tug.org] on behalf of Siep Kroonenberg [siepo at cybercomm.nl]
Sent: 25 April 2013 16:30
To: tex-live at tug.org
Subject: Re: [tex-live] User names too longs or with diacritics on Windows

On Thu, Apr 25, 2013 at 01:05:17PM +0000, Lars Madsen wrote:
> Wan't that what you called it?
> Sorry, 'folder redirection'

Ok. But usually a folder would not be directly redirected to a UNC
path. Instead, I would expect the UNC path to be mapped to a drive
letter and the folder to be redirected to this drive letter.

Check the registry key
folders or
HKCU\software\microsoft\windows\currentversion\explorer\user shell
folders for any UNC paths.

Let me list, just for fun, a few stumbling blocks when dealing with
the windows file `system':
- M$ has something resembling symlinks which it calls junction
  points or reparse points, and which cause all manner of
  unpleasantness. This seems to be done to accomodate programs which
  hard-code these shell folder names instead of looking them up in the
  approved way. E.g. `Documents and Settings' becomes visible if if
  you set Explorer to showing hidden files, but you cannot enter it
  either from a command-prompt or from Explorer.
- Plus there is the never-ending misery of localized names which
  may be localized just in explorer, or localized for real.

Maybe also worth mentioning: under linux you can set a codepage
parameter when mounting a [v]fat drive. This is for converting to
short names.

Siep Kroonenberg

More information about the tex-live mailing list