On 11/22/2010 01:50 AM, Pavel Sanda wrote:
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.
On 11/22/2010 09:57 AM, you...@lyx.org wrote:
Author: younes
Date: Mon Nov 22 09:57:33 2010
New Revision: 36430
URL: http://www.lyx.org/trac/changeset/36430
Log:
Work around bug #6920. This disables ligatures with involving 'f'
character.
Bennett, Stefan, please check that.
Abdel.
On 11/22/2010 08:58 AM, Abdelrazak Younes wrote:
On 11/22/2010 01:50 AM, Pavel Sanda wrote:
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
Jürgen Spitzmüller a écrit :
Jean-Pierre Chrétien wrote:
Attached.
Thanks. Committed to branch and trunk.
I have a warning with View DVI:
xdvi-xaw: Warning: Invalid papersize special `0.0pt,0.0pt'
Harmless because the DVI file is displayed all right and is
in A4 format.
This comes from
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 basically do not overwrite the original file, but we move away
the original read-only file and write a new file.
I have read the discussion
I've made a bug report about a crash when invoking a CAS in multine AMS
context. The LyX stdout doesn't tell anything useful.
Moreover I've a question about instant preview and PSTricks, see the
attachment, it doesn't show up the graph. I didn't make a bug report because
maybe it's just due to
Abdelrazak Younes wrote:
On 11/22/2010 09:57 AM, you...@lyx.org wrote:
Author: younes
Date: Mon Nov 22 09:57:33 2010
New Revision: 36430
URL: http://www.lyx.org/trac/changeset/36430
Log:
Work around bug #6920. This disables ligatures with involving 'f'
character.
Bennett, Stefan,
Jürgen Spitzmüller wrote:
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
On Mon, Nov 22, 2010 at 12:33:17PM +0100, Pavel Sanda wrote:
Abdelrazak Younes wrote:
On 11/22/2010 09:57 AM, you...@lyx.org wrote:
Author: younes
Date: Mon Nov 22 09:57:33 2010
New Revision: 36430
URL: http://www.lyx.org/trac/changeset/36430
Log:
Work around bug #6920. This
Enrico Forestieri wrote:
its fixed here now. Juergen this problem is also in branch.
I cannot reproduce this bug with any font (including DejaVu) on Linux,
Windows and Solaris, with or without this patch. I verified that the
ligatures are present at U+FB00-U+FB04, so it cannot be due to
Pavel Sanda wrote:
yes. please can you write some concise statement what has been changed wrt
xetex? i would like to put it into beta2 announce (or feel free to add it
there directly).
The statement would be something like:
Support for polyglossia, XeTeX's new language interface and babel
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
Hi all
I have now produced an example tex-file that my problem is of a more
general nature and can appear also with other packages than mhchem. I
have constructed an example of a conflict with the automatic package
support in the case of \tfrac of the ams-package.
The following is a bug for the
On 11/22/2010 12:57 PM, Pavel Sanda wrote:
Enrico Forestieri wrote:
its fixed here now. Juergen this problem is also in branch.
I cannot reproduce this bug with any font (including DejaVu) on Linux,
Windows and Solaris, with or without this patch. I verified that the
ligatures are
Jean-Pierre Chrétien wrote:
I have a warning with View DVI:
xdvi-xaw: Warning: Invalid papersize special `0.0pt,0.0pt'
Harmless because the DVI file is displayed all right and is
in A4 format.
This comes from this command added by LyX to the preamble:
hi Tommaso,
i dont see your commits like r36411 in our cvs list. is tomm...@lyx subscribed
there? iirc this was needed so distribution works properly. can you have a look?
pavel
2010/11/19 Waluyo Adi Siswanto was.u...@gmail.com:
It works by using this command (from the terminal)
QT_X11_NO_NATIVE_MENUBAR=1 lyx
Perhaps, for those using Ubuntu Netbook and have the same problem;
a) Create a file lyx_command.sh
#!/bin/sh
QT_X11_NO_NATIVE_MENUBAR=1 lyx
b)
(trunk)
This is what I get since today, with all po-files.
The appropriate messages in the po-files are:
msgid Itemize\r
msgid Description\r
msgid Labeling\r
msgid List\r
msgid 00.00.\r
msgid Enumerate-Resume\r
It is warning only, but does not look correct.
Kornel
signature.asc
Kornel wrote:
(trunk)
This is what I get since today, with all po-files.
The appropriate messages in the po-files are:
msgid Itemize\r
msgid Description\r
msgid Labeling\r
msgid List\r
msgid 00.00.\r
msgid Enumerate-Resume\r
It is warning only, but does not look correct.
i
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
i see, enumitem module is saved as crlf file...
pavel
Fixed in http://www.lyx.org/trac/changeset/36435.
;).
I accidentally set the svn property eol-style instead of
svn:eol-style. Being on windows, the crlf line endings got committed
which I just wanted to prevent by setting the
Vincent van Ravesteijn wrote:
i see, enumitem module is saved as crlf file...
pavel
Fixed in http://www.lyx.org/trac/changeset/36435.
;).
Sendinglayouts/enumitem.module
Transmitting file data .svn: Commit failed (details follow):
svn: File
On Mon, Nov 22, 2010 at 3:58 AM, Abdelrazak Younes you...@lyx.org wrote:
On 11/22/2010 09:57 AM, you...@lyx.org wrote:
Author: younes
Date: Mon Nov 22 09:57:33 2010
New Revision: 36430
URL: http://www.lyx.org/trac/changeset/36430
Log:
Work around bug #6920. This disables ligatures with
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
:-)
Out of curiosity, I checked out what it would need us to implement basic
support for Lua(La)TeX (basic in the sense of what we had for XeTeX prior to
the polyglossia commit today*). And it's really as simple as the attached.
What I would do additionally to the patch are just two cosmetic
Jürgen Spitzmüller wrote:
features, and of course I respect if this is gonna be postponed. OTOH, people
are just starting to use LuaTeX now for serious work, and I expect it to
become more mature within the next months. So I just wanted to let you know
i have rather general questions:
* are
Proper script is that:
#!/usr/bin/env sh
QT_X11_NO_NATIVE_MENUBAR=1 lyx $@
Such version allows passing of invocation arguments.
Oh.. yes, that's correct. Running LyX from the menu using the previous
script, creates another problem. Double clicking lyx document will not
be successful.
Pavel Sanda wrote:
i have rather general questions:
* are there security considerations (havent worked with it, but
its possible to write ERT for rm -rf/ in lua)?
I don't think so. The LuaTeX developers are rather security-aware guys (after
all, these are the pdflatex/context people, a
Il 22/11/2010 14:02, Pavel Sanda ha scritto:
hi Tommaso,
i dont see your commits like r36411 in our cvs list. is tomm...@lyx subscribed
there? iirc this was needed so distribution works properly. can you have a look?
Hi,
I confess I have no clue of what you're talking about. Please, explain
Am 22.11.2010 um 12:50 schrieb Enrico Forestieri:
On Mon, Nov 22, 2010 at 12:33:17PM +0100, Pavel Sanda wrote:
Abdelrazak Younes wrote:
On 11/22/2010 09:57 AM, you...@lyx.org wrote:
Author: younes
Date: Mon Nov 22 09:57:33 2010
New Revision: 36430
URL:
On 11/22/2010 10:55 AM, Jürgen Spitzmüller wrote:
Out of curiosity, I checked out what it would need us to implement basic
support for Lua(La)TeX (basic in the sense of what we had for XeTeX prior to
the polyglossia commit today*). And it's really as simple as the attached.
What I would do
If you mean the list that notifies me of each and every commit in LyX,
I probably don't actually need to be there :-).
Yes, you do. If you're not on that list, we are not notified either.
Vincent
On 2010-11-22, Jürgen Spitzmüller wrote:
Pavel Sanda wrote:
* why do we want it at all - or in more general, what are we aiming to
support? all pdftex, xetex, luatex?
Yes.
Seconded.
...
pdftex is very stable and reliable, and for people who do not need all
the nifty new features,
On 2010-11-22, Richard Heck wrote:
On 11/22/2010 10:55 AM, Jürgen Spitzmüller wrote:
Out of curiosity, I checked out what it would need us to implement basic
support for Lua(La)TeX (basic in the sense of what we had for XeTeX prior to
the polyglossia commit today*). And it's really as simple
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
On 22/11/2010 4:40 AM, veno...@arcadiaclub.com wrote:
Moreover I've a question about instant preview and PSTricks, see the attachment, it doesn't show up
the graph. I didn't make a bug report because maybe it's just due to some misconfiguration or
conflict specific to my system. You need
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.
Sebastian Guttenberg wrote:
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 supports: Set their default
off for all older lyx-documents...
Yes. AFAIK this is the case
Sebastian Guttenberg wrote:
Not being a programmer, I should not be demanding, but I personally
think that a proper fix would include the following:
* For any imported file lyx should neither load nor support any package
that has not been loaded in the original file
* deselecting packages
Am 22.11.2010 um 09:58 schrieb Abdelrazak Younes:
On 11/22/2010 09:57 AM, you...@lyx.org wrote:
Author: younes
Date: Mon Nov 22 09:57:33 2010
New Revision: 36430
URL: http://www.lyx.org/trac/changeset/36430
Log:
Work around bug #6920. This disables ligatures with involving 'f'
Il 22/11/2010 19:27, Vincent van Ravesteijn ha scritto:
If you mean the list that notifies me of each and every commit in
LyX, I probably don't actually need to be there :-).
Yes, you do. If you're not on that list, we are not notified either.
hmmm, and excellent opportunity to commit
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:
Hi Georg
Thanks a lot for your answers. I see the point.
I'm sorry, but in the meantime I was already impatient and sent another
message (with subject: examples of failing tex-import) to the mailing
list with an extended tex-file with a few more examples (I don't know
why it hasn't yet appeared
On 11/22/2010 01:50 AM, Pavel Sanda wrote:
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.
On 11/22/2010 09:57 AM, you...@lyx.org wrote:
Author: younes
Date: Mon Nov 22 09:57:33 2010
New Revision: 36430
URL: http://www.lyx.org/trac/changeset/36430
Log:
Work around bug #6920. This disables ligatures with involving 'f'
character.
Bennett, Stefan, please check that.
Abdel.
On 11/22/2010 08:58 AM, Abdelrazak Younes wrote:
On 11/22/2010 01:50 AM, Pavel Sanda wrote:
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
Jürgen Spitzmüller a écrit :
Jean-Pierre Chrétien wrote:
Attached.
Thanks. Committed to branch and trunk.
I have a warning with "View DVI":
xdvi-xaw: Warning: Invalid papersize special `0.0pt,0.0pt'
Harmless because the DVI file is displayed all right and is
in A4 format.
This comes from
> 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 basically do not overwrite the original file, but we move away
> the original read-only file and write a new file.
I have read the
I've made a bug report about a crash when invoking a CAS in multine AMS
context. The LyX stdout doesn't tell anything useful.
Moreover I've a question about instant preview and PSTricks, see the
attachment, it doesn't show up the graph. I didn't make a bug report because
maybe it's just due to
Abdelrazak Younes wrote:
> On 11/22/2010 09:57 AM, you...@lyx.org wrote:
>> Author: younes
>> Date: Mon Nov 22 09:57:33 2010
>> New Revision: 36430
>> URL: http://www.lyx.org/trac/changeset/36430
>>
>> Log:
>> Work around bug #6920. This disables ligatures with involving 'f'
>> character.
>>
>
Jürgen Spitzmüller wrote:
> 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,
On Mon, Nov 22, 2010 at 12:33:17PM +0100, Pavel Sanda wrote:
> Abdelrazak Younes wrote:
> > On 11/22/2010 09:57 AM, you...@lyx.org wrote:
> >> Author: younes
> >> Date: Mon Nov 22 09:57:33 2010
> >> New Revision: 36430
> >> URL: http://www.lyx.org/trac/changeset/36430
> >>
> >> Log:
> >> Work
Enrico Forestieri wrote:
> > its fixed here now. Juergen this problem is also in branch.
>
> I cannot reproduce this bug with any font (including DejaVu) on Linux,
> Windows and Solaris, with or without this patch. I verified that the
> ligatures are present at U+FB00-U+FB04, so it cannot be due
Pavel Sanda wrote:
> yes. please can you write some concise statement what has been changed wrt
> xetex? i would like to put it into beta2 announce (or feel free to add it
> there directly).
The statement would be something like:
"Support for polyglossia, XeTeX's new language interface and babel
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
Hi all
I have now produced an example tex-file that my problem is of a more
general nature and can appear also with other packages than mhchem. I
have constructed an example of a conflict with the automatic package
support in the case of \tfrac of the ams-package.
The following is a bug for the
On 11/22/2010 12:57 PM, Pavel Sanda wrote:
Enrico Forestieri wrote:
its fixed here now. Juergen this problem is also in branch.
I cannot reproduce this bug with any font (including DejaVu) on Linux,
Windows and Solaris, with or without this patch. I verified that the
ligatures are
Jean-Pierre Chrétien wrote:
> I have a warning with "View DVI":
>
> xdvi-xaw: Warning: Invalid papersize special `0.0pt,0.0pt'
>
> Harmless because the DVI file is displayed all right and is
> in A4 format.
>
> This comes from this command added by LyX to the preamble:
>
hi Tommaso,
i dont see your commits like r36411 in our cvs list. is tomm...@lyx subscribed
there? iirc this was needed so distribution works properly. can you have a look?
pavel
2010/11/19 Waluyo Adi Siswanto :
>> It works by using this command (from the terminal)
>>
>> QT_X11_NO_NATIVE_MENUBAR=1 lyx
>>
>
> Perhaps, for those using Ubuntu Netbook and have the same problem;
>
> a) Create a file lyx_command.sh
> #!/bin/sh
>
(trunk)
This is what I get since today, with all po-files.
The appropriate messages in the po-files are:
msgid "Itemize\r"
msgid "Description\r"
msgid "Labeling\r"
msgid "List\r"
msgid "00.00.\r"
msgid "Enumerate-Resume\r"
It is warning only, but does not look correct.
Kornel
Kornel wrote:
> (trunk)
> This is what I get since today, with all po-files.
>
> The appropriate messages in the po-files are:
>
> msgid "Itemize\r"
> msgid "Description\r"
> msgid "Labeling\r"
> msgid "List\r"
> msgid "00.00.\r"
> msgid "Enumerate-Resume\r"
>
> It is warning only, but does
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
> i see, enumitem module is saved as cr file...
> pavel
Fixed in http://www.lyx.org/trac/changeset/36435.
;).
I accidentally set the svn property "eol-style" instead of
"svn:eol-style". Being on windows, the crlf line endings got committed
which I just wanted to prevent by setting the
Vincent van Ravesteijn wrote:
> > i see, enumitem module is saved as cr file...
> > pavel
>
> Fixed in http://www.lyx.org/trac/changeset/36435.
>
> ;).
Sendinglayouts/enumitem.module
Transmitting file data .svn: Commit failed (details follow):
svn: File
On Mon, Nov 22, 2010 at 3:58 AM, Abdelrazak Younes wrote:
> On 11/22/2010 09:57 AM, you...@lyx.org wrote:
>>
>> Author: younes
>> Date: Mon Nov 22 09:57:33 2010
>> New Revision: 36430
>> URL: http://www.lyx.org/trac/changeset/36430
>>
>> Log:
>> Work around bug #6920. This
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
:-)
Out of curiosity, I checked out what it would need us to implement basic
support for Lua(La)TeX (basic in the sense of what we had for XeTeX prior to
the polyglossia commit today*). And it's really as simple as the attached.
What I would do additionally to the patch are just two cosmetic
Jürgen Spitzmüller wrote:
> features, and of course I respect if this is gonna be postponed. OTOH, people
> are just starting to use LuaTeX now for serious work, and I expect it to
> become more mature within the next months. So I just wanted to let you know
i have rather general questions:
*
> Proper script is that:
> #!/usr/bin/env sh
> QT_X11_NO_NATIVE_MENUBAR=1 lyx "$@"
>
> Such version allows passing of invocation arguments.
Oh.. yes, that's correct. Running LyX from the menu using the previous
script, creates another problem. Double clicking lyx document will not
be
Pavel Sanda wrote:
> i have rather general questions:
> * are there security considerations (havent worked with it, but
> its possible to write ERT for "rm -rf/" in lua)?
I don't think so. The LuaTeX developers are rather security-aware guys (after
all, these are the pdflatex/context people, a
Il 22/11/2010 14:02, Pavel Sanda ha scritto:
hi Tommaso,
i dont see your commits like r36411 in our cvs list. is tomm...@lyx subscribed
there? iirc this was needed so distribution works properly. can you have a look?
Hi,
I confess I have no clue of what you're talking about. Please, explain
Am 22.11.2010 um 12:50 schrieb Enrico Forestieri:
> On Mon, Nov 22, 2010 at 12:33:17PM +0100, Pavel Sanda wrote:
>
>> Abdelrazak Younes wrote:
>>> On 11/22/2010 09:57 AM, you...@lyx.org wrote:
Author: younes
Date: Mon Nov 22 09:57:33 2010
New Revision: 36430
URL:
On 11/22/2010 10:55 AM, Jürgen Spitzmüller wrote:
Out of curiosity, I checked out what it would need us to implement basic
support for Lua(La)TeX (basic in the sense of what we had for XeTeX prior to
the polyglossia commit today*). And it's really as simple as the attached.
What I would do
If you mean the list that notifies me of each and every commit in LyX,
I probably don't actually need to be there :-).
Yes, you do. If you're not on that list, we are not notified either.
Vincent
On 2010-11-22, Jürgen Spitzmüller wrote:
> Pavel Sanda wrote:
>> * why do we want it at all - or in more general, what are we aiming to
>> support? all pdftex, xetex, luatex?
> Yes.
Seconded.
...
> pdftex is very stable and reliable, and for people who do not need all
> the nifty new
On 2010-11-22, Richard Heck wrote:
> On 11/22/2010 10:55 AM, Jürgen Spitzmüller wrote:
>> Out of curiosity, I checked out what it would need us to implement basic
>> support for Lua(La)TeX (basic in the sense of what we had for XeTeX prior to
>> the polyglossia commit today*). And it's really as
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
On 22/11/2010 4:40 AM, veno...@arcadiaclub.com wrote:
Moreover I've a question about instant preview and PSTricks, see the attachment, it doesn't show up
the graph. I didn't make a bug report because maybe it's just due to some misconfiguration or
conflict specific to my system. You need
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.
Sebastian Guttenberg wrote:
> 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 supports: Set their default
> "off" for all older lyx-documents...
Yes. AFAIK this is the
Sebastian Guttenberg wrote:
> Not being a programmer, I should not be demanding, but I personally
> think that a proper fix would include the following:
> * For any imported file lyx should neither load nor support any package
> that has not been loaded in the original file
> * deselecting
Am 22.11.2010 um 09:58 schrieb Abdelrazak Younes:
> On 11/22/2010 09:57 AM, you...@lyx.org wrote:
>> Author: younes
>> Date: Mon Nov 22 09:57:33 2010
>> New Revision: 36430
>> URL: http://www.lyx.org/trac/changeset/36430
>>
>> Log:
>> Work around bug #6920. This disables ligatures with involving
Il 22/11/2010 19:27, Vincent van Ravesteijn ha scritto:
If you mean the list that notifies me of each and every commit in
LyX, I probably don't actually need to be there :-).
Yes, you do. If you're not on that list, we are not notified either.
hmmm, and excellent opportunity to commit
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
Hi Georg
Thanks a lot for your answers. I see the point.
I'm sorry, but in the meantime I was already impatient and sent another
message (with subject: "examples of failing tex-import") to the mailing
list with an extended tex-file with a few more examples (I don't know
why it hasn't yet appeared
94 matches
Mail list logo