On Tuesday 18 November 2008 09:38:01 Jürgen Spitzmüller wrote:
> However, it seems sensible for BRANCH_1_5_X (who knows?)
Yes.
> Jürgen
--
José Abílio
Joost Verburg wrote:
>> And yes, it will work with 1.5.7, that is the main point here. :-)
>
> Should I apply the patch to trunk?
However, it seems sensible for BRANCH_1_5_X (who knows?)
Jürgen
On Monday 17 November 2008 20:15:32 Joost Verburg wrote:
> Should I apply the patch to trunk?
No, please leave it as it is.
The question is that if we fix this we should also fix the corresponding entry
in lyx_1_5.py
So I would leave it as it is and later, if necessary, we can give it some
tho
José Matos wrote:
The patch works. There are probably other places where we need the same
remedy. For the moment since there are not other cases where lyx is used
outside of the current directory I am not too worried about this case.
And yes, it will work with 1.5.7, that is the main point her
On Monday 17 November 2008 15:49:29 Joost Verburg wrote:
> Jürgen Spitzmüller wrote:
> > Yes. This bug occured with the integration of lyx_1_6.py into 1.5.7,
> > because that file needs to access the unicodesymbols file, and lyx2lyx is
> > used by doc_toc.py.
>
> lyx_1.6.py assumes that the script
Joost Verburg wrote:
> lyx_1.6.py assumes that the script directory is the current working
> directory, which is not always the case. The attached patch solves this
> issue.
Thanks. I let José review this. For 1.5.7, best if that you just apply this
locally, I guess (unless we find out that impor
Jürgen Spitzmüller wrote:
Yes. This bug occured with the integration of lyx_1_6.py into 1.5.7, because
that file needs to access the unicodesymbols file, and lyx2lyx is used by
doc_toc.py.
lyx_1.6.py assumes that the script directory is the current working
directory, which is not always the c
Joost Verburg wrote:
> > What file? unicodesymbols?
>
> Right, it's generating the TOC but the error indeed refers to
> unicodesymbols. Is this a known bug?
Yes. This bug occured with the integration of lyx_1_6.py into 1.5.7, because
that file needs to access the unicodesymbols file, and lyx2lyx
Jürgen Spitzmüller wrote:
Joost Verburg wrote:
A file not found error for Resources\doc\TOC.lyx in the build directory.
What file? unicodesymbols?
Right, it's generating the TOC but the error indeed refers to
unicodesymbols. Is this a known bug?
Joost
Joost Verburg wrote:
> A file not found error for Resources\doc\TOC.lyx in the build directory.
What file? unicodesymbols?
Jürgen
Jürgen Spitzmüller wrote:
Joost Verburg wrote:
No, it doesn't make any difference. It will probably work when old TOC
files still exist in the build directory, but a clean build from the
tarball doesn't work.
What exactly is the error you get?
A file not found error for Resources\doc\TOC.lyx
Joost Verburg wrote:
> No, it doesn't make any difference. It will probably work when old TOC
> files still exist in the build directory, but a clean build from the
> tarball doesn't work.
What exactly is the error you get?
Jürgen
Jürgen Spitzmüller wrote:
Joost Verburg wrote:
I'm preparing installers for 1.5.7, but I'm not able to build the
tarball using scons. It complains about missing TOC files in the
Resources directory.
Do these help?
http://www.lyx.org/trac/changeset/27406
http://www.lyx.org/trac/changeset/27408
Joost Verburg wrote:
> I'm preparing installers for 1.5.7, but I'm not able to build the
> tarball using scons. It complains about missing TOC files in the
> Resources directory.
Do these help?
http://www.lyx.org/trac/changeset/27406
http://www.lyx.org/trac/changeset/27408
Jürgen
14 matches
Mail list logo
