----- Original Message -----
From: "Bo Peng" <[EMAIL PROTECTED]>
To: <lyx-users@lists.lyx.org>
Cc: <lyx-devel@lists.lyx.org>
Sent: Monday, January 02, 2006 4:41 PM
Subject: Re: [announce] sixth release of LyXWinInstaller
Dear all,
It is confirmed that if the .bst file is in a path without space, the
bibliography will be generated correctly, even if lyx is installed
under c:\program files\lyx. So,
1. It is safe to install lyx to c:\program files,
2. It is not safe to put .bst files in a path with spaces. .lyx files
and all figure files are OK, as well as .bib files.
Bo
To repeat back what you said in a different way for clarification:
It is better to install Miktex in C:\Miktex and/or C:\texmf
which usually contains the .bst files.
A problem is likely to arise if you install Miktex to
C:\program files\miktex and/or c:\program files\texmf
Storing the output .lyx file and retrieving it later does not
require avoiding using a work directory without spaces.
IOW, you can use
C:\documents and settings\username\My Documents
which has a space, or one can also use a nospace directory,
C:\MyDocs or C:\LyX\resources\lyx\work\Mydocs
So that working around the .bst problem of path and spaces by
using a nospace directory path such as C:\texmf\bibtex\bst does
not impact negatively on the Windows traditional use of storing
files in C:\Documents and Settings\username\My Documents or
C:\~...\...\Application data\LyX\Work for later retrieval. No change
needs to be made for My Documents to accomodate using a nospace
bst (texmf) directory path. Do I understand you correctly?
<speculative remark>
Apparently, the code that works for bibtex and paths with spaces
can't be easily substituted to handle bst (some kind of find/replace).
From what I read, TeX ends a filename when a space occurs. It
used to be that you could quote, "\path\with a space\" and the space
wouldn't cause a problem. But there seems to be a problem with
quotemarks, two, getting removed. I tried "\path\"with a space"\"
but \ is also used as an escape character which is why it maybe
doesn't work as well as a path delimiter as /.
</speculative remark>
Regards,
Stephen
