Jean-Marc Lasgouttes wrote:
> Angus> The attached patch to LyX 1.3.x allows View->DVI to succeed.
> Angus> Obviously, I should test out the changes to InsetExternal and
> Angus> InsetBib too, but now it's late and I'm tired and, anyway, I'd
> Angus> like to check that what I've done looks reasonable.
>
> Looks reasonable. Insetead of the use_latex_path bool
> - result = subst(s, "$$FName", params_.filename);
> + string subst_path = use_latex_path ?
> + latex_path(params_.filename) : params_.filename;
> + result = subst(s, "$$FName", subst_path);
> you could also define a $$LName variable. Then the converter would be
> able to tell which format it wants.
Good idea.
Can you explain to me what is meant to happen to the \include and \input
entries in the presence of spaces? At the moement, without applying the
patch, LyX 1.3.x creates the following LaTeX file from trial.lyx.
I know that changing ~ to \string~ will fix this particular file, but what
happens if the temp dir and the sub~dir each contain spaces? Is it
sufficient to wrap these elements in inverted commas?
[EMAIL PROTECTED]"/tmp dir//"}}
\include{"sub [EMAIL PROTECTED]"}
foo \input{"sub dir/input.tex"}
Also, does the \input not need the '@' similar to the \include?
Angus
\batchmode
\makeatletter
[EMAIL PROTECTED]/home/aleem/trial_tex//}}
\makeatother
\documentclass[english,a4paper]{article}
\usepackage[T1]{fontenc}
\usepackage[latin1]{inputenc}
\usepackage{graphicx}
\makeatletter
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% User specified LaTeX commands.
\usepackage{graphicx}
\usepackage{babel}
\makeatother
\begin{document}
\section{This in insetgraphics}
\includegraphics{/tmp/lyx_tmpdir6514jLnBjG/lyx_tmpbuf0/_home_aleem_trial_tex_sub~dir_im~ge}
foo
\includegraphics{/tmp/lyx_tmpdir6514jLnBjG/lyx_tmpbuf0/_home_aleem_trial_tex_sub~dir_im~ge}
\section{What follows is included}
foo
[EMAIL PROTECTED]
\section{What follows is input}
foo \input{sub~dir/inp~t.tex}
\section{All done}
foo
\end{document}
--
Angus
