Joost Verburg wrote:
On 11/20/2010 2:51 PM, Jack Tanner wrote:
I see that Uwe has kindly uploaded the alternative 1.6.8 installer for
Windows. Is anyone preparing the official one also?
The installer is finished and will soon be available on the website.
It was delayed a bit because of a
Hi all
I had worked for a while only with lyx1.6.5 and have not tested the
development version for a while. But as I have seen that you have
released already a beta-version of lyx2.0, I updated my svn to do some
testing. Hope it's not too late.
What stroke me first, is that the old package-issue
Uwe Stöhr wrote:
Am 20.11.2010 19:57, schrieb Georg Baum:
This is possible (using the insert inset and move selection inside
mechanism and inset-dissolve internally), but would be more risk, so I'd
like to postpone this. If you want a more visible place you could put the
scripts into a
Enrico Forestieri wrote:
I wonder why you also disable nested script insets, given that things
such as a\textsuperscript{1\textsubscript{2}} seem to work well.
I thought it did not work, but it does indeed work. I allowed it now. The
font size does not become smaller anymore with a depth of
Richard Heck wrote:
Index: lib/lyx2lyx/lyx_2_0.py
===
--- lib/lyx2lyx/lyx_2_0.py (revision 36398)
+++ lib/lyx2lyx/lyx_2_0.py (working copy)
+# FIXME: Would be nice if we could use the information of the
.layout file
The attached patch adds support for polyglossia with XeTeX.
As estimated, the patch is rather big, and it needs good testing. I have
tested with multiple languages (including Arabic, Hebrew, and Greek), but of
course, there could be many things I have overlooked.
Jürgen
Index:
A Windows installer for 1.6.8 is already available:
Could someone please upload an installer-free binary package for
1.6.8 and 2.0beta1 for Windows onto ftp.lyx.org?
TIA,
Sincerely,
Wolfgang
Sebastian Guttenberg wrote:
* All my personal macros (including \ce) are defined in a child
document via \input. Apparently lyx does not look if \ce has been
defined in the child-document, before loading the package mhchem, so it
is loaded.
This is probably true. Using the master settings
Does the attached patch fix the problem? It sets mhchem to 0 if the
original document is from version 1.5.x or older.
Great! That indeed fixes the problem for me! Thanks a lot!
Probably one should do the same for all packages whose support was added
at a later stage and for all future new
Hi all
I have a very strange behaviour of lyx2.0. I can modify (and save)
write-only files!! Within lyx they are not indicated as being read-only
and after modifying and saving them, the old write-protected file was
indeed overwritten and its mode change to writable.
I have done the same
I have tested again, and the behavior has changed a bit. This time the
read-only file was respected. Let me give you something reproducible.
Just do the following steps:
* start a new file and save it as test.lyx (don't close it)
* open a terminal and change the file permissions to read-only:
see subject: can anyone confirm?
thanks, ed.
Yes, I'm working on a fixed version.
Joost
On 11/21/2010 4:19 PM, Edwin Leuven wrote:
see subject: can anyone confirm?
thanks, ed.
I found another, important issue:
you are using \usepackage{subscript} but subscript is not a real
LaTeX-package (the author calls it a fragment) and therefore not
installable via the package managers of TeXLive and MiKTeX:
On 21/11/2010 5:20 PM, Uwe Stöhr wrote:
That it is not included in MiKTeX, also not via the fragments or
fixltx2e package. Therefore all LyX on Windows would be forced to
install the file manually which is not acceptable.
How about using
\usepackage{fixltx2e}
for providing \textsubscript?
Op 21-11-2010 22:07, Sebastian Guttenberg schreef:
I have tested again, and the behavior has changed a bit. This time the
read-only file was respected. Let me give you something reproducible.
Just do the following steps:
* start a new file and save it as test.lyx (don't close it)
* open a
On Mon, 2010-11-22 at 01:10 +0100, Vincent van Ravesteijn wrote:
So, the only bug is that when LyX2.0 opens a LyX1.6.5 file, the
read-only flag is not set correctly?
This is the same problem as reported in bug
http://www.lyx.org/trac/ticket/7035 and discussed in the following
thread
hi,
by accident i successfully reproduced quite horrible problem of unsynced visual
cursor position and the actual position of typing, so this is no more MacOS
thing only. the key point was to switch to dejavu fonts in linux.
http://www.lyx.org/trac/ticket/6920
qt 4.6.3 here.
pavel
Op 22-11-2010 1:44, Sebastian Guttenberg schreef:
On Mon, 2010-11-22 at 01:10 +0100, Vincent van Ravesteijn wrote:
So, the only bug is that when LyX2.0 opens a LyX1.6.5 file, the
read-only flag is not set correctly?
This is the same problem as reported in bug
Jean-Marc Lasgouttes wrote:
What happens if the function decides to change nothing after all? We have a
useless
undo step.
so if somebody pushes ctrl+z, one step nothing happens? undo machinery could
detect and kill empty start-end undo block at the end.
recordUndo only applies to AtPoint
Vincent van Ravesteijn wrote:
The document ~/test.lyx could not be saved.
Do you want to rename the document and try again?
Rename Retry Cancel
This was changed to solve bug http://www.lyx.org/trac/ticket/6587.
Now we move the file to the backup file before saving the current file. So,
Georg Baum wrote:
As a first step, I committed what I had. This is much better than the
nice, please put some item or picture in http://wiki.lyx.org/LyX/NewInLyX20
pavel
On 21/11/2010 5:20 PM, Uwe Stöhr wrote:
That it is not included in MiKTeX, also not via the fragments or
fixltx2e package. Therefore all LyX on Windows would be forced to
install the file manually which is not acceptable.
How about using
\usepackage{fixltx2e}
for providing
On 21/11/2010 9:10 PM, Uwe Stöhr wrote:
As I said (you even cited this) fixltx2e is not available for MiKTeX, at
last not under MiKTeX 2.9.
OK, it is here on miktex 2.8 and also according to this page:
http://www.ctan.org/tex-archive/help/Catalogue/entries/fixltx2e.html
I did not know that it
OK, it is here on miktex 2.8 and also according to this page:
http://www.ctan.org/tex-archive/help/Catalogue/entries/fixltx2e.html
I did not know that it was dropped in 2.9 and don't see a mention of this in
the release notes.
Thanks for the hint. It seems indeed to be a packaging error in
Jürgen Spitzmüller wrote:
The attached patch adds support for polyglossia with XeTeX.
As estimated, the patch is rather big, and it needs good testing. I have
tested with multiple languages (including Arabic, Hebrew, and Greek), but
of course, there could be many things I have overlooked.
Am 22.11.2010 um 01:10 schrieb Vincent van Ravesteijn:
Op 21-11-2010 22:07, Sebastian Guttenberg schreef:
I have tested again, and the behavior has changed a bit. This time the
read-only file was respected. Let me give you something reproducible.
Just do the following steps:
* start a new
Joost Verburg wrote:
> On 11/20/2010 2:51 PM, Jack Tanner wrote:
> > I see that Uwe has kindly uploaded the alternative 1.6.8 installer for
> > Windows. Is anyone preparing the official one also?
>
> The installer is finished and will soon be available on the website.
> It was delayed a bit
Hi all
I had worked for a while only with lyx1.6.5 and have not tested the
development version for a while. But as I have seen that you have
released already a beta-version of lyx2.0, I updated my svn to do some
testing. Hope it's not too late.
What stroke me first, is that the old package-issue
Uwe Stöhr wrote:
> Am 20.11.2010 19:57, schrieb Georg Baum:
>>
>> This is possible (using the "insert inset and move selection inside"
>> mechanism and inset-dissolve internally), but would be more risk, so I'd
>> like to postpone this. If you want a more visible place you could put the
>>
Enrico Forestieri wrote:
> I wonder why you also disable nested script insets, given that things
> such as a\textsuperscript{1\textsubscript{2}} seem to work well.
I thought it did not work, but it does indeed work. I allowed it now. The
font size does not become smaller anymore with a depth of
Richard Heck wrote:
>> Index: lib/lyx2lyx/lyx_2_0.py
>> ===
>> --- lib/lyx2lyx/lyx_2_0.py (revision 36398)
>> +++ lib/lyx2lyx/lyx_2_0.py (working copy)
>>
>>
>> +# FIXME: Would be nice if we could use the information of the
The attached patch adds support for polyglossia with XeTeX.
As estimated, the patch is rather big, and it needs good testing. I have
tested with multiple languages (including Arabic, Hebrew, and Greek), but of
course, there could be many things I have overlooked.
Jürgen
Index:
> A Windows installer for 1.6.8 is already available:
Could someone please upload an installer-free binary package for
1.6.8 and 2.0beta1 for Windows onto ftp.lyx.org?
TIA,
Sincerely,
Wolfgang
Sebastian Guttenberg wrote:
> * All my personal macros (including "\ce") are defined in a child
> document via \input. Apparently lyx does not look if \ce has been
> defined in the child-document, before loading the package mhchem, so it
> is loaded.
This is probably true. Using the master
> Does the attached patch fix the problem? It sets mhchem to 0 if the
> original document is from version 1.5.x or older.
Great! That indeed fixes the problem for me! Thanks a lot!
Probably one should do the same for all packages whose support was added
at a later stage and for all future new
Hi all
I have a very strange behaviour of lyx2.0. I can modify (and save)
write-only files!! Within lyx they are not indicated as being read-only
and after modifying and saving them, the old write-protected file was
indeed overwritten and its mode change to writable.
I have done the same
I have tested again, and the behavior has changed a bit. This time the
read-only file was respected. Let me give you something reproducible.
Just do the following steps:
* start a new file and save it as test.lyx (don't close it)
* open a terminal and change the file permissions to read-only:
see subject: can anyone confirm?
thanks, ed.
Yes, I'm working on a fixed version.
Joost
On 11/21/2010 4:19 PM, Edwin Leuven wrote:
see subject: can anyone confirm?
thanks, ed.
>> I found another, important issue:
>>
>> you are using \usepackage{subscript} but subscript is not a real
>> LaTeX-package (the author calls it a fragment) and therefore not
>> installable via the package managers of TeXLive and MiKTeX:
>>
On 21/11/2010 5:20 PM, Uwe Stöhr wrote:
That it is not included in MiKTeX, also not via the fragments or
fixltx2e package. Therefore all LyX on Windows would be forced to
install the file manually which is not acceptable.
How about using
\usepackage{fixltx2e}
for providing \textsubscript?
Op 21-11-2010 22:07, Sebastian Guttenberg schreef:
I have tested again, and the behavior has changed a bit. This time the
read-only file was respected. Let me give you something reproducible.
Just do the following steps:
* start a new file and save it as test.lyx (don't close it)
* open a
On Mon, 2010-11-22 at 01:10 +0100, Vincent van Ravesteijn wrote:
> So, the only bug is that when LyX2.0 opens a LyX1.6.5 file, the
> read-only flag is not set correctly?
>
> This is the same problem as reported in bug
> http://www.lyx.org/trac/ticket/7035 and discussed in the following
> thread
>
hi,
by accident i successfully reproduced quite horrible problem of unsynced visual
cursor position and the actual position of typing, so this is no more MacOS
thing only. the key point was to switch to dejavu fonts in linux.
http://www.lyx.org/trac/ticket/6920
qt 4.6.3 here.
pavel
Op 22-11-2010 1:44, Sebastian Guttenberg schreef:
On Mon, 2010-11-22 at 01:10 +0100, Vincent van Ravesteijn wrote:
So, the only bug is that when LyX2.0 opens a LyX1.6.5 file, the
read-only flag is not set correctly?
This is the same problem as reported in bug
Jean-Marc Lasgouttes wrote:
> What happens if the function decides to change nothing after all? We have a
> useless
> undo step.
so if somebody pushes ctrl+z, one step nothing happens? undo machinery could
detect and kill empty start-end undo block at the end.
> recordUndo only applies to
Vincent van Ravesteijn wrote:
>> "The document ~/test.lyx could not be saved.
>> Do you want to rename the document and try again?
>> "
>
> This was changed to solve bug http://www.lyx.org/trac/ticket/6587.
>
> Now we move the file to the backup file before saving the current file. So,
> we
Georg Baum wrote:
> As a first step, I committed what I had. This is much better than the
nice, please put some item or picture in http://wiki.lyx.org/LyX/NewInLyX20
pavel
> On 21/11/2010 5:20 PM, Uwe Stöhr wrote:
>>
>>That it is not included in MiKTeX, also not via the fragments or
>>fixltx2e package. Therefore all LyX on Windows would be forced to
>>install the file manually which is not acceptable.
>
> How about using
>
> \usepackage{fixltx2e}
>
>
On 21/11/2010 9:10 PM, Uwe Stöhr wrote:
As I said (you even cited this) fixltx2e is not available for MiKTeX, at
last not under MiKTeX 2.9.
OK, it is here on miktex 2.8 and also according to this page:
http://www.ctan.org/tex-archive/help/Catalogue/entries/fixltx2e.html
I did not know that it
> OK, it is here on miktex 2.8 and also according to this page:
> http://www.ctan.org/tex-archive/help/Catalogue/entries/fixltx2e.html
>
> I did not know that it was dropped in 2.9 and don't see a mention of this in
the release notes.
Thanks for the hint. It seems indeed to be a packaging error
Jürgen Spitzmüller wrote:
> The attached patch adds support for polyglossia with XeTeX.
>
> As estimated, the patch is rather big, and it needs good testing. I have
> tested with multiple languages (including Arabic, Hebrew, and Greek), but
> of course, there could be many things I have
Am 22.11.2010 um 01:10 schrieb Vincent van Ravesteijn:
> Op 21-11-2010 22:07, Sebastian Guttenberg schreef:
>> I have tested again, and the behavior has changed a bit. This time the
>> read-only file was respected. Let me give you something reproducible.
>> Just do the following steps:
>>
>> *
54 matches
Mail list logo
