-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gregoriotex falis when there is a space in filename. #1224
Comments
Interesting, thanks a lot for the report! Here the culprit is more LuaTeX than Gregorio, but the line you indicated clearly could be improved, and we could also replace all filename-unfriendly characters (_, @, space, etc.) with hyphens... |
I thought that we allow
Am I missing any? |
oh, you're right about |
How about |
Well, but if I get it right, the file names are created on the basis of existing .tex or .gabc files, so if previous file exists in the filesystem => it must contain only valid characters. |
well, why not all these characters also, although I doubt it will be helpful... but who knows... |
imo quoting each parameter (e.g. |
The problem is with TeX. TeX interprets certain characters in a weird way, doing things like collapsing multiple spaces into one, and there's no perfect way to "quote" the filename, which is why @eroux said the problem is more with LuaTeX than Gregorio per se. The proposition is really a workaround to the weirdness of TeX. It's pretty much not a good idea to have filenames with spaces in them when dealing with TeX. |
The implementation that I am working on does this (for auto or force compile only):
The benefit of this is that the original filename is not changed on disk, so no surprises to the user. All the auto-generated files are "TeX friendly" and should still picked up by our garbage collection / old version cleanup. |
sounds good to me |
@eschwab any news on this? |
Yes, I have a fix ready. Just need to run the tests which I should have time to do tomorrow since the semester is finally over. |
For the changlog entry should this be filed under the Fixed or Added section? |
I'd say fixed. Most people would consider the old behavior a bug.
Henry
…On December 27, 2016 3:25:02 PM "Rev. Br. Elijah Schwab, O.Carm" ***@***.***> wrote:
For the changlog entry should this be filed under the Fixed or Added section?
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
#1224 (comment)
|
What's the status here? Can this go into 5.0? |
Fixed by #1344 |
* release-5.0: (44 commits) Fix some typos in fonts readme. Fix some typos in supplemental fonts documentation. CHANGELOG entry for bugfix and update version number Lua-based fixes from Akira Kakuto. The version number on the executable is a suffix, not a prefix. Update Version number and consolidate CHANGELOG entries Changed --enable-texlive to --disable-version-in-exe per Élie Roux. Part of the implementation for gregorio-project#1292. Added documentation of --enable-texlive to README.md. Part of the implementation for gregorio-project#1292. Added --enable-texlive flag and support for a suffix-less executable. Fixes gregorio-project#1292. Distribution additions Fix test TeXShop engine modifications Modifications to doc_check.sh and def_check.sh Corrected copy-paste error. Corrected macro name. Updated documentation for version 5.0.0. Update Version Number Add Changelog entry for fix gregorio-project#1224. Rename gabc files containing non-filename friendly symbols. Add trace messages to rest of functions in gregoriotex-signs.tex ...
At first sorry if I'll write something stupid - I'm not much experienced with TeX and I'm absolutely new to Gregorio.
But from what I've observed, there is a bug with not quoting file names, which leads to compilation errors, when gabc file, tex file, or some directory on path to them contains a space in it's name ("ResHodie Nobis.gabc").
At first I've found the bug (missing quotes) at this line. Fixing them locally was not enough - caused another error, so I decided to leave it to someone, who's more into the project.
Environment info
OS: Windows 7 x64
Gregoriotex version (comment from gregoriotex.tex file):
% [2016/07/05 v4.2.0-rc2 GregorioTeX system.]% PARSE_VERSION_DATE_LTX
Compilation log
The text was updated successfully, but these errors were encountered: