Bug Tracker

ID:21 🔗
Category:makeglossaries (Perl)
Date:2013-01-31 02:24:08
Summary:makeglossaries error on Windows due to long username or accented character in it


When run on Windows (at least on Windows Seven) by a user with a long username or accented character(s) in it, makeglossaries gives error.

It used to happen for instance with a user named "Cécile" who was running:

  makeglossaries "essaiglossaire"
in directory:
She gets:
makeglossaries version 2.03 (2011-12-02)

added glossary type 'main' (glg,gls,glo)

xindy -L french -C utf8 -I xindy -M "essaiglossaire" -t
"essaiglossaire.glg" -o "essaiglossaire.gls" "essaiglossaire.glo"

*** - LOAD: A file with name C:\Users\CCILE~1\AppData\Local\Temp
\NTlhTzJ0ob does not exist

C:\texlive\2011\bin\win32\runscript.tlu:587: command failed with exit
code 1: 
So the problem came from the Windows conversion:
  C:\Users\Cécile -> C:\Users\CCILE~1
A similar case arose with a user named "Alejandro" (more than 8 characters).

The solution is to create a new user with shorter username and just ASCII characters in it. Then makeglossaries works nicely.

If this trouble, maybe inherent to Windows systems, cannot be dropped, maybe the above workaround should be mentionned in:


Thank you for the workaround. I've added an entry in the glossaries FAQ that links back to this. If a Windows user can suggest a solution, that would be great.


Comment from Denis Bitouzé
Date: 2013-02-07 10:39:26 CST

Thanks for having added an entry in the glossaries FAQ. IMHO, it should nevertheless be necessary to add in the FAQ entry the characteristic error messages:

*** - LOAD: A file with name C:\Users\...\AppData\Local\Temp\... does not exist

C:\texlive\...\bin\win32\runscript.tlu:587: command failed with exit code 1:

Otherwise, users who are facing the trouble could ignore the bug report and the workaround because they couldn't imagine it is related to long username or accented character in it.

Add comment or return to search results.

Watch This Report

If you would like to be notified whenever updates are made to this report, please fill in your email address in the box below and click on "Notify Me of Changes" button. (Please ensure the address is valid.) Your details won't be passed on to third parties in line with this site's Privacy Policy.

If you supply your name, it will be used in the email greeting, which provides a more personal message, otherwise you'll just get a generic greeting. If you have previously supplied your name when signing up for notifications, you don't need to resupply it unless you want to change it.

If you have previously subscribed to notifications for this report, you can unsubscribe by clicking on the "Stop Notification" button.

The "Confirm Bug ID" field helps to protect against spambots. Please enter the bug ID (which you can find at the top of this page).

E mail:
Confirm E mail:
Confirm Bug ID:

To unsubscribe from all notifications use the notifications page.


You can append a comment to the report using the form below. Comments are checked first before being added. Any spam or offensive content will be removed first according to this site's Terms of Website Use. Please bear in mind that I develop and maintain free software in my spare time. If you want commerical level support then you can hire a TeX consultant.

The "Confirm Bug ID" field helps to protect against spambots. Please enter the bug ID (which you can find at the top of this page).

(Optional. If provided, it will be shown with the comment.)
Confirm Bug ID:

You can use the following markup:

[pre]Displayed verbatim[/pre]
[tt]monospace text[/tt]
[em]emphasized text[/em]
[b]bold text[/b]
[url]web address[/url]

Ordered list:
[li]first item[/li]
[li]second item[/li]

Unordered list:
[li]first item[/li]
[li]second item[/li]

Click on the Preview button to preview the message.

Return to search results.