Jim Oldfield wrote:
In the meantime, it would be useful if this was detected at/before LaTeX
compilation and users given a slightly more helpful error message e.g.
redirected to a wiki page. Otherwise they will probably go looking for a
subscript package, as I did, and end up getting lost.
Jim Oldfield wrote:
> In the meantime, it would be useful if this was detected at/before LaTeX
> compilation and users given a slightly more helpful error message e.g.
> redirected to a wiki page. Otherwise they will probably go looking for a
> subscript package, as I did, and end up getting
, 22 November, 2010 4:57:46
Subject: Re: [patch] fix bug 3008
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
.org>
> Cc: jri...@physics.utoronto.ca
> Sent: Mon, 22 November, 2010 4:57:46
> Subject: Re: [patch] fix bug 3008
>
> > 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
&g
On 2010-11-28, Georg Baum wrote:
Jürgen Spitzmüller wrote:
Guenter Milde wrote:
If LyX policy is to follow LaTeX policy regarding stability, it's a bit
more complicated:
No it's not. Everybody can put the line in their preamble and make that
the document default. I do not see why we should
On 2010-11-28, Georg Baum wrote:
> Jürgen Spitzmüller wrote:
>> Guenter Milde wrote:
>>> If LyX policy is to follow LaTeX policy regarding stability, it's a bit
>>> more complicated:
>> No it's not. Everybody can put the line in their preamble and make that
>> the document default. I do not see
Guenter Milde wrote:
If LyX policy is to follow LaTeX policy regarding stability, it's a bit
more complicated:
No it's not. Everybody can put the line in their preamble and make that the
document default. I do not see why we should do anything here. It has always
been good LyX policy not to
Georg Baum wrote:
Please use the fixltx2e package for \textsubscript:
I did not do that on purpose. It has side effects, and the usage of a
subscript should not cgange anything else.
Actually, I agree with this.
Jürgen
Guenter Milde wrote:
> If LyX policy is to follow LaTeX policy regarding stability, it's a bit
> more complicated:
No it's not. Everybody can put the line in their preamble and make that the
document default. I do not see why we should do anything here. It has always
been good LyX policy not to
Georg Baum wrote:
> > Please use the fixltx2e package for \textsubscript:
> I did not do that on purpose. It has side effects, and the usage of a
> subscript should not cgange anything else.
Actually, I agree with this.
Jürgen
On 2010-11-19, Georg Baum wrote:
Hi,
after I needed to explain several times lately why one should not use the
menu entries for sub/superscript in text and what to do instead, I finally
sat down and completed a fix for bug 3008 that I started years ago. It
implements a new inset for
Guenter Milde wrote:
I argue, that LyX-2 should by default always insert
\usepackage{fixltx2e}. This package collects a range of fixes and
improvements that are not not in the LaTeX core due to backwards
compatibility issues. The quantum-leap from 1 to 2 would be a good
place for this change:
On 2010-11-22, Uwe Stöhr wrote:
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
Le 21/11/2010 18:05, Georg Baum a écrit :
Yeah. I run into this a lot these days. But then I think: Do I really want
to write a layout parser for lyx2lyx?
These were exactly my thoughts. Nevertheless, it would be nice to have one
:-)
Could our in-LyX textclass parser be augmented to dump
On 11/22/2010 08:41 AM, Jean-Marc Lasgouttes wrote:
Le 21/11/2010 18:05, Georg Baum a écrit :
Yeah. I run into this a lot these days. But then I think: Do I
really want
to write a layout parser for lyx2lyx?
These were exactly my thoughts. Nevertheless, it would be nice to
have one
:-)
On 2010-11-22, Jürgen Spitzmüller wrote:
Guenter Milde wrote:
I argue, that LyX-2 should by default always insert
\usepackage{fixltx2e}. This package collects a range of fixes and
improvements that are not not in the LaTeX core due to backwards
compatibility issues. The quantum-leap from 1 to
Uwe Stöhr wrote:
What is the problem with using that package?
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.
That would be a bug in MikTeX. subscript.sty
Guenter Milde wrote:
Please use the fixltx2e package for \textsubscript:
I did not do that on purpose. It has side effects, and the usage of a
subscript should not cgange anything else. It is bad enough that the usage
of some math symbols of the wasy package has the side effect that e.g.
On 11/22/2010 03:58 PM, Georg Baum wrote:
Uwe Stöhr wrote:
What is the problem with using that package?
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.
Guenter Milde wrote:
I argue, that LyX-2 should by default *always* insert
\usepackage{fixltx2e}. This package collects a range of fixes and
improvements that are not not in the LaTeX core due to backwards
compatibility issues. The quantum-leap from 1 to 2 would be a good
place for this change:
On 2010-11-19, Georg Baum wrote:
> Hi,
> after I needed to explain several times lately why one should not use the
> menu entries for sub/superscript in text and what to do instead, I finally
> sat down and completed a fix for bug 3008 that I started years ago. It
> implements a new inset for
Guenter Milde wrote:
> I argue, that LyX-2 should by default always insert
> \usepackage{fixltx2e}. This package collects a range of fixes and
> improvements that are not not in the LaTeX core due to backwards
> compatibility issues. The "quantum-leap" from 1 to 2 would be a good
> place for this
On 2010-11-22, Uwe Stöhr wrote:
> > 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
Le 21/11/2010 18:05, Georg Baum a écrit :
Yeah. I run into this a lot these days. But then I think: Do I really want
to write a layout parser for lyx2lyx?
These were exactly my thoughts. Nevertheless, it would be nice to have one
:-)
Could our in-LyX textclass parser be augmented to dump
On 11/22/2010 08:41 AM, Jean-Marc Lasgouttes wrote:
Le 21/11/2010 18:05, Georg Baum a écrit :
Yeah. I run into this a lot these days. But then I think: Do I
really want
to write a layout parser for lyx2lyx?
These were exactly my thoughts. Nevertheless, it would be nice to
have one
:-)
On 2010-11-22, Jürgen Spitzmüller wrote:
> Guenter Milde wrote:
>> I argue, that LyX-2 should by default always insert
>> \usepackage{fixltx2e}. This package collects a range of fixes and
>> improvements that are not not in the LaTeX core due to backwards
>> compatibility issues. The
Uwe Stöhr wrote:
> > What is the problem with using that package?
>
> 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.
That would be a bug in MikTeX.
Guenter Milde wrote:
> Please use the fixltx2e package for \textsubscript:
I did not do that on purpose. It has side effects, and the usage of a
subscript should not cgange anything else. It is bad enough that the usage
of some math symbols of the wasy package has the side effect that e.g.
On 11/22/2010 03:58 PM, Georg Baum wrote:
Uwe Stöhr wrote:
> What is the problem with using that package?
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.
Guenter Milde wrote:
I argue, that LyX-2 should by default *always* insert
\usepackage{fixltx2e}. This package collects a range of fixes and
improvements that are not not in the LaTeX core due to backwards
compatibility issues. The "quantum-leap" from 1 to 2 would be a good
place for this
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
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?
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
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
>> 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?
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
On Fri, Nov 19, 2010 at 10:29:53PM +0100, Georg Baum wrote:
The attached patch has no known problems (the cursor position problem
mentioned in trac is fixed).
I see a couple of glitches.
- Whenever the cursor moves in the script, the following warning is issued:
Am 20.11.2010 15:30, schrieb Enrico Forestieri:
- It is possible to insert in the script inset things that cause latex
errors. For example, one can insert a math display inset.
I tested this and inserting math is valid and works. The only inset that must be further disabled is
the box
Am 20.11.2010 17:28, schrieb Uwe Stöhr:
- It is possible to insert in the script inset things that cause latex
errors. For example, one can insert a math display inset.
I tested this and inserting math is valid and works.
I was too rash here:
- inline math works, also AMS stuff
- displayed
Am 20.11.2010 17:28, schrieb Uwe Stöhr:
- It is possible to insert in the script inset things that cause latex
errors. For example, one can insert a math display inset.
I tested this and inserting math is valid and works.
I was too rash here:
- inline math works, also AMS stuff
- displayed
On Sat, Nov 20, 2010 at 07:57:30PM +0100, Georg Baum wrote:
The other problems mentioned by Enrico and you are fixed by the attached
patch. I prevented the insertion of some more insets (I hope I got all that
are needed).
I wonder why you also disable nested script insets, given that things
Looks great, Georg, and thanks for paying attention to the xhtml output.
Index: src/insets/InsetScript.cpp
===
--- src/insets/InsetScript.cpp (revision 0)
+++ src/insets/InsetScript.cpp (revision 0)
@@ -0,0 +1,464 @@
+/**
+ *
Am 20.11.2010 19:57, schrieb Georg Baum:
The repeated script is not nice, but this is the way how inset parameters
work in general (the first is the inset type, the second is the parameter
type). It can't be changed easily and certainly not at this time. Therefore,
the images need this ugly
On Fri, Nov 19, 2010 at 10:29:53PM +0100, Georg Baum wrote:
> The attached patch has no known problems (the cursor position problem
> mentioned in trac is fixed).
I see a couple of glitches.
- Whenever the cursor moves in the script, the following warning is issued:
Am 20.11.2010 15:30, schrieb Enrico Forestieri:
- It is possible to insert in the script inset things that cause latex
errors. For example, one can insert a math display inset.
I tested this and inserting math is valid and works. The only inset that must be further disabled is
the box
Am 20.11.2010 17:28, schrieb Uwe Stöhr:
- It is possible to insert in the script inset things that cause latex
errors. For example, one can insert a math display inset.
I tested this and inserting math is valid and works.
I was too rash here:
- inline math works, also AMS stuff
- displayed
Am 20.11.2010 17:28, schrieb Uwe Stöhr:
- It is possible to insert in the script inset things that cause latex
errors. For example, one can insert a math display inset.
I tested this and inserting math is valid and works.
I was too rash here:
- inline math works, also AMS stuff
- displayed
On Sat, Nov 20, 2010 at 07:57:30PM +0100, Georg Baum wrote:
> The other problems mentioned by Enrico and you are fixed by the attached
> patch. I prevented the insertion of some more insets (I hope I got all that
> are needed).
I wonder why you also disable nested script insets, given that
Looks great, Georg, and thanks for paying attention to the xhtml output.
Index: src/insets/InsetScript.cpp
===
--- src/insets/InsetScript.cpp (revision 0)
+++ src/insets/InsetScript.cpp (revision 0)
@@ -0,0 +1,464 @@
+/**
+ *
Am 20.11.2010 19:57, schrieb Georg Baum:
The repeated "script" is not nice, but this is the way how inset parameters
work in general (the first is the inset type, the second is the parameter
type). It can't be changed easily and certainly not at this time. Therefore,
the images need this ugly
Georg Baum wrote:
May the patch go in at this stage (I don't know
how the current policy is)? The risk of breakage is close to zero.
the current stage is stop for refactoring and enhacenments, with the remark
that small things which do not touch sensitive or large area of code can be
allowed
Am 19.11.2010 22:29, schrieb Georg Baum:
It
implements a new inset for subscript and superscript in text mode, including
correct output for all backends. There are some other ideas discussed in
http://www.lyx.org/trac/ticket/3008, but the inset approach is the best one
IMO.
Almost perfect! I
Georg Baum wrote:
> May the patch go in at this stage (I don't know
> how the current policy is)? The risk of breakage is close to zero.
the current stage is stop for refactoring and enhacenments, with the remark
that small things which do not touch sensitive or large area of code can be
allowed
Am 19.11.2010 22:29, schrieb Georg Baum:
It
implements a new inset for subscript and superscript in text mode, including
correct output for all backends. There are some other ideas discussed in
http://www.lyx.org/trac/ticket/3008, but the inset approach is the best one
IMO.
Almost perfect! I
66 matches
Mail list logo
