Can't handle filenames with spaces
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
context (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: context
[06:26 PM] 471Mb$ uname -a
Linux craft 2.6.28-17-generic #58-Ubuntu SMP Tue Dec 1 18:57:07 UTC 2009 i686 GNU/Linux
[06:26 PM] 471Mb$ apt-cache show context
Package: context
Priority: optional
Section: universe/tex
Installed-Size: 33712
Maintainer: Ubuntu MOTU Developers <email address hidden>
Original-
Architecture: all
Version: 2008.05.21-1
Replaces: texlive-context
Provides: texlive-context
Depends: lmodern (>= 1.01), ruby, tex-common (>= 1.4), texlive-base (>= 2007), texlive-base-bin (>= 2007), texlive-metapost (>= 2007)
Recommends: luatex
Suggests: context-
Conflicts: tetex-bin (<< 2007), texlive-context
Filename: pool/universe/
Size: 9238430
MD5sum: b60c28da1e7a994
SHA1: 8d07cfab1f018c3
SHA256: 797f5794dccfbbc
Description: powerful TeX format
ConTeXt is a document-production system based, like LaTeX, on the TeX
typesetting system. Whereas LaTeX insulates the writer from
typographical details, ConTeXt takes a complementary approach by
providing structured interfaces for handling typography, including
extensive support for colors, backgrounds, hyperlinks, presentations,
figure-text integration, and conditional compilation. It gives the
user extensive control over formatting while making it easy to create
new layouts and styles without learning the TeX macro language.
ConTeXt's unified design averts the package clashes that can happen
with LaTeX.
.
ConTeXt also integrates MetaFun, a superset of MetaPost and a powerful
system for vector graphics. MetaFun can be used as a stand-alone
system to produce figures, but its strength lies in enhancing ConTeXt
documents with accurate graphic elements.
.
ConTeXt allows the users to specify formatting commands in English,
Dutch, German, French, or Italian, and to use different typesetting
engines (PDFTeX, XeTeX, Aleph, and soon LuaTeX) without changing the
user interface. ConTeXt is developed rapidly, often in response to
requests from the friendly user community.
Bugs: https:/
Origin: Ubuntu
[06:26 PM] 471Mb$ /usr/bin/texexec Front\ Page.tex
TeXExec | processing document 'Front'
TeXExec | no ctx file found
TeXExec | nothing to process
TeXExec | processing document 'Page.tex'
TeXExec | no ctx file found
TeXExec | nothing to process
TeXExec | runtime: 0.048238
[06:26 PM] 471Mb$ /usr/bin/texexec "Front Page.tex"
TeXExec | processing document 'Front'
TeXExec | no ctx file found
TeXExec | nothing to process
TeXExec | processing document 'Page.tex'
TeXExec | no ctx file found
TeXExec | nothing to process
TeXExec | runtime: 0.047943
[06:26 PM] 471Mb$ /usr/bin/texexec 'Front Page.tex'
TeXExec | processing document 'Front'
TeXExec | no ctx file found
TeXExec | nothing to process
TeXExec | processing document 'Page.tex'
TeXExec | no ctx file found
TeXExec | nothing to process
TeXExec | runtime: 0.048787
[06:26 PM] 471Mb$ /usr/bin/texexec *.tex
TeXExec | processing document 'Front'
TeXExec | no ctx file found
TeXExec | nothing to process
TeXExec | processing document 'Page.tex'
TeXExec | no ctx file found
TeXExec | nothing to process
TeXExec | runtime: 0.058287
Texexec should be able to handle spaces like every other application. This trips me up nearly every time I use it, and forced me to use workarounds to strip out spaces when Gitit calls texexec to make PDFs.
"It is highly recommended, that all input files, i.e. the ConTEXt source and other included files such as image files, have only the letters a–z, digits and dashes in their names, that is in the names of their full paths, otherwise you can easily get into problems. Especially the characters *, ?, the space character and some more are known to cause problems, sometimes because of ConTEXt itself (internal pattern matching), sometimes because of issues with the underlying operating system. The dot ‘.' is somewhat special: it's used to separate the suffix from the rest of the file-name, but at other places in the path it can cause trouble just like ‘*' or ‘?'." (http:// pmrb.free. fr/contextref. pdf)
This is IMHO a "Won't Fix".
As a workaround you can try "context" instead of "texexec", seem to work on your example, but no guarantees.