Enrico Forestieri a écrit :
On Sun, Apr 02, 2006 at 01:11:50PM +0200, Georg Baum wrote:- Implicit format change of .lyx files. I know that there are currently problems in this area due to the mixup, but for the future I would like to have only one representation of file names in .lyx files for a given platform.Indeed. When a .lyx file contains an absolute path, it has different styles depending on whether LyX is a win32 or posix app. This was one of the reasons I wanted to be able to switch the internal representation. I am always able to read a .lyx file produced by a win32 LyX using a cygwin LyX, but it may be not true the other way, as win32 doesn't understand posix. Perhaps it would be better to force a pseudo-win style when outputting file names to .lyx files in order to guarantee interoperability at least on windows. But if the internal format is fixed, we have added complexity. However, now I am almost convinced that this is unavoidable.
I am not sure about what you both are talking about but the .lyx file should contains path with forward slashes only independently from the system. This is _very_ important for interoperability between windows user and unix/posix users exchanging lyx files (paths must be relative then). For the same reason, LyX produced latex files _must_ _always_ use path with forward slashes.
Please make sure that this is the case. [...]
The fact that forward slashes work in external paths is proved by my daily use of it and the fact that no problems related to it have been reported so far. As I already said, even notepad and word do with forward slashes. So, if it was depending on me, I had avoided using backslashes even in the native win32 version.
I second that. Every little program I made under windows used forward slashes. This is a _very_ common approach. Even Microsoft compilers and libraries use forward slashes.
But I understand that in that case a wrapper script would be a
.bat file, so it is better to have proper win32 paths for the
fact that some stupid cmd.exe command could exchange them as a
switch introducer ('/' is used in win32 in the same way '-' is
used in *nix).
Just encapsulates the patch between quotes and it should be fine even in .bat file.
Abdel.
