#2753 closed defect (fixed)
LyX doesn't support paths and filenames with parentheses
Reported by: | Uwe Stöhr | Owned by: | lasgouttes |
---|---|---|---|
Priority: | high | Milestone: | 1.5.0 |
Component: | file | Version: | 1.4.2 |
Severity: | major | Keywords: | |
Cc: | j.spitzmueller@… |
Description
Create for example a folder "C:\test(test)\" and copy a bst- and a bib-file to
it. Now open a LyX-document and try to use the bst-file for the BibTeX
references - the file "C:\test(test)\IEEEtran.bst" could be used, fine.
But now try to use the bib-file. LyX will then show an error message that it
doesn't support filenames with #, $, %, (, and so on. But the filename
"test.bib" doesn't contain such a character and having parentheses, braces, and
brackets in file or folder names is correct on windows.
Windows only prohibits these characters: \, /, :, <, >, *, ?, ", and |
Allowing parentheses in names is important because on Win XP x64 all programs
are by default installed in the folder
"C:\Program Files (x86)\"
Attachments (1)
Change History (13)
comment:1 by , 19 years ago
Milestone: | → 1.4.x |
---|
comment:2 by , 19 years ago
comment:3 by , 18 years ago
blocked: | → 3297 |
---|
comment:5 by , 18 years ago
Milestone: | 1.4.x → 1.5.0 |
---|---|
Summary: | LyX doesn't support paths with parentheses in its name → LyX doesn't support paths and filenames with parentheses |
The following characters are currently not supported in paths and filenames:
#, $, %, {, }, [, ], (, ), ", and
I put it on the LyX 1.5.0 agenda as WinXp x64 and Vista used such characters in
paths.
comment:6 by , 18 years ago
Severity: | normal → major |
---|
This bug seems to become more important especially for the Vista people.
Therefore major as this prevents for example to start with template files as
images included to them are in paths with parentheses on 64bit Windows systems.
comment:7 by , 18 years ago
Cc: | added |
---|---|
Keywords: | patch added |
comment:8 by , 18 years ago
blocked: | 3297 |
---|
comment:9 by , 18 years ago
The patch fixes the bug as far as I tested. (I didn't look into the code if all
changes there are correct but as it fixed the bug and you are the 1.5 maintainer
I would say put it in when José or the others give his OK.)
Many thanks for all your bug fixes today.
comment:10 by , 18 years ago
Keywords: | fixedintrunk added; patch removed |
---|
fixed for 1.5rc2 (rev18897).
comment:12 by , 17 years ago
Keywords: | fixedintrunk removed |
---|
This check (in PathValidator) is not needed anymore since we copy the files to
the temp dir, it should indeed be removed for the bibtex, external, graphics
and include inset. Of course that means that you will run into trouble if you
export to LaTeX and process the .tex file. We should issue a warning in that
case.