(Apologies for the slow reply.) I've tried adding the \AtBeginDocument{} as
you suggest but while the error goes away, the cross ref formatting is not
honoured.
I think I might try to get my head around *refstyle* as this is the way LyX
is moving for cross ref formatting, correct?
On 10 December
(Apologies for the slow reply.) I've tried adding the \AtBeginDocument{} as
you suggest but while the error goes away, the cross ref formatting is not
honoured.
I think I might try to get my head around *refstyle* as this is the way LyX
is moving for cross ref formatting, correct?
On 10 December
(Apologies for the slow reply.) I've tried adding the \AtBeginDocument{} as
you suggest but while the error goes away, the cross ref formatting is not
honoured.
I think I might try to get my head around *refstyle* as this is the way LyX
is moving for cross ref formatting, correct?
On 10 December
On 2010-12-09, Jürgen Spitzmüller wrote:
Guenter Milde wrote:
I am glad you found the core of the problem.
(BTW: the current version of fontspec does no longer load xunicode, but
we should care for users with older versions.)
I have fontspec v2.1e (2010/11/17), which is the most recent
Justin Wood wrote:
The template files do actually have this embrace, but it doesn't prevent
the parsing error.
No. \addto\extrasenglish is not embraced by \AtBeginDocument{}
Or do you mean the next release will do something else
that will fix the problem? Thanks Jürgen.
No. Look below.
On 2010-12-09, Jürgen Spitzmüller wrote:
Guenter Milde wrote:
I am glad you found the core of the problem.
(BTW: the current version of fontspec does no longer load xunicode, but
we should care for users with older versions.)
I have fontspec v2.1e (2010/11/17), which is the most recent
Justin Wood wrote:
The template files do actually have this embrace, but it doesn't prevent
the parsing error.
No. \addto\extrasenglish is not embraced by \AtBeginDocument{}
Or do you mean the next release will do something else
that will fix the problem? Thanks Jürgen.
No. Look below.
On 2010-12-09, Jürgen Spitzmüller wrote:
> Guenter Milde wrote:
>> I am glad you found the core of the problem.
>> (BTW: the current version of fontspec does no longer load xunicode, but
>> we should care for users with older versions.)
> I have fontspec v2.1e (2010/11/17), which is the most
Justin Wood wrote:
> The template files do actually have this embrace, but it doesn't prevent
> the parsing error.
No. \addto\extrasenglish is not embraced by \AtBeginDocument{}
> Or do you mean the next release will do something else
> that will fix the problem? Thanks Jürgen.
No. Look below.
Guenter Milde wrote:
I am glad you found the core of the problem.
(BTW: the current version of fontspec does no longer load xunicode, but
we should care for users with older versions.)
I have fontspec v2.1e (2010/11/17), which is the most recent version on
CTAN. The documentation states:
On 10 December 2010 12:37, lyx-users-h...@lists.lyx.org wrote:
2. conflict in thesis template
Beyond that, changing to the automatic AMS math package in the thesis
document introduces new errors. In a brand new, entirely unmodified
chapter template file, XeTeX compilation now complains
On 10 December 2010 12:37, lyx-users-h...@lists.lyx.org wrote:
The reason for this is that XeTeX now uses polyglossia, which does not
know these \addto commands (which are from babel). Are these templates
shipped with LyX? If so, we need to embrace these calls in
However, I also found that even if I do not check any of the AMS math
options, LyX 2 behaves as if the Load AMS math automatically option
were set:
a) the AMS symbols toolbox is enabled.
b) inserting a symbol from it inserts \usepackage{amssymb} in the preamble.
c) even writing \Rrightarrow
Guenter Milde wrote:
I am glad you found the core of the problem.
(BTW: the current version of fontspec does no longer load xunicode, but
we should care for users with older versions.)
I have fontspec v2.1e (2010/11/17), which is the most recent version on
CTAN. The documentation states:
On 10 December 2010 12:37, lyx-users-h...@lists.lyx.org wrote:
2. conflict in thesis template
Beyond that, changing to the automatic AMS math package in the thesis
document introduces new errors. In a brand new, entirely unmodified
chapter template file, XeTeX compilation now complains
On 10 December 2010 12:37, lyx-users-h...@lists.lyx.org wrote:
The reason for this is that XeTeX now uses polyglossia, which does not
know these \addto commands (which are from babel). Are these templates
shipped with LyX? If so, we need to embrace these calls in
However, I also found that even if I do not check any of the AMS math
options, LyX 2 behaves as if the Load AMS math automatically option
were set:
a) the AMS symbols toolbox is enabled.
b) inserting a symbol from it inserts \usepackage{amssymb} in the preamble.
c) even writing \Rrightarrow
Guenter Milde wrote:
> I am glad you found the core of the problem.
> (BTW: the current version of fontspec does no longer load xunicode, but
> we should care for users with older versions.)
I have fontspec v2.1e (2010/11/17), which is the most recent version on
CTAN. The documentation states:
On 10 December 2010 12:37, wrote:
> > 2. conflict in thesis template
> > Beyond that, changing to the automatic AMS math package in the thesis
> > document introduces new errors. In a brand new, entirely unmodified
> > chapter template file, XeTeX compilation now
On 10 December 2010 12:37, wrote:
> >
> > The reason for this is that XeTeX now uses polyglossia, which does not
> > know these \addto commands (which are from babel). Are these templates
> > shipped with LyX? If so, we need to embrace these calls in
> >
> >
> However, I also found that even if I do not check any of the AMS math
> options, LyX 2 behaves as if the "Load AMS math automatically" option
> were set:
>
> a) the "AMS symbols" toolbox is enabled.
> b) inserting a symbol from it inserts \usepackage{amssymb} in the preamble.
> c) even writing
Justin Wood wrote:
1. conflict with AMS package
I've found that simply activating XeTeX under *Document Settings –
Fonts*will cause parsing errors on viewing if the document also has
*Math Options – Use AMS math package* checked; eg, LaTeX Error: Command
`\Finv' already defined, etc. I think
On 12/08/2010 05:58 AM, Jürgen Spitzmüller wrote:
Justin Wood wrote:
1. conflict with AMS package
I've found that simply activating XeTeX under *Document Settings –
Fonts*will cause parsing errors on viewing if the document also has
*Math Options – Use AMS math package* checked; eg, LaTeX
Jürgen Spitzmüller wrote:
2. conflict in thesis template
Beyond that, changing to the automatic AMS math package in the thesis
document introduces new errors. In a brand new, entirely unmodified
chapter template file, XeTeX compilation now complains about the use of '
\addto \extrasenglish{'
Jürgen Spitzmüller wrote:
Justin Wood wrote:
1. conflict with AMS package
I've found that simply activating XeTeX under *Document Settings –
Fonts*will cause parsing errors on viewing if the document also has
*Math Options – Use AMS math package* checked; eg, LaTeX Error: Command
`\Finv'
On 2010-12-08, Jürgen Spitzmüller wrote:
Jürgen Spitzmüller wrote:
Justin Wood wrote:
1. conflict with AMS package
I've found that simply activating XeTeX under *Document Settings –
Fonts*will cause parsing errors on viewing if the document also has
*Math Options – Use AMS math package*
Justin Wood wrote:
1. conflict with AMS package
I've found that simply activating XeTeX under *Document Settings –
Fonts*will cause parsing errors on viewing if the document also has
*Math Options – Use AMS math package* checked; eg, LaTeX Error: Command
`\Finv' already defined, etc. I think
On 12/08/2010 05:58 AM, Jürgen Spitzmüller wrote:
Justin Wood wrote:
1. conflict with AMS package
I've found that simply activating XeTeX under *Document Settings –
Fonts*will cause parsing errors on viewing if the document also has
*Math Options – Use AMS math package* checked; eg, LaTeX
Jürgen Spitzmüller wrote:
2. conflict in thesis template
Beyond that, changing to the automatic AMS math package in the thesis
document introduces new errors. In a brand new, entirely unmodified
chapter template file, XeTeX compilation now complains about the use of '
\addto \extrasenglish{'
Jürgen Spitzmüller wrote:
Justin Wood wrote:
1. conflict with AMS package
I've found that simply activating XeTeX under *Document Settings –
Fonts*will cause parsing errors on viewing if the document also has
*Math Options – Use AMS math package* checked; eg, LaTeX Error: Command
`\Finv'
On 2010-12-08, Jürgen Spitzmüller wrote:
Jürgen Spitzmüller wrote:
Justin Wood wrote:
1. conflict with AMS package
I've found that simply activating XeTeX under *Document Settings –
Fonts*will cause parsing errors on viewing if the document also has
*Math Options – Use AMS math package*
Justin Wood wrote:
> 1. conflict with AMS package
> I've found that simply activating XeTeX under *Document Settings –
> Fonts*will cause parsing errors on viewing if the document also has
> *Math Options – Use AMS math package* checked; eg, LaTeX Error: Command
> `\Finv' already defined, etc. I
On 12/08/2010 05:58 AM, Jürgen Spitzmüller wrote:
Justin Wood wrote:
1. conflict with AMS package
I've found that simply activating XeTeX under *Document Settings –
Fonts*will cause parsing errors on viewing if the document also has
*Math Options – Use AMS math package* checked; eg, LaTeX
Jürgen Spitzmüller wrote:
>> 2. conflict in thesis template
>> Beyond that, changing to the automatic AMS math package in the thesis
>> document introduces new errors. In a brand new, entirely unmodified
>> chapter template file, XeTeX compilation now complains about the use of '
>> \addto
Jürgen Spitzmüller wrote:
> Justin Wood wrote:
>> 1. conflict with AMS package
>> I've found that simply activating XeTeX under *Document Settings –
>> Fonts*will cause parsing errors on viewing if the document also has
>> *Math Options – Use AMS math package* checked; eg, LaTeX Error: Command
>>
On 2010-12-08, Jürgen Spitzmüller wrote:
> Jürgen Spitzmüller wrote:
>> Justin Wood wrote:
>>> 1. conflict with AMS package
>>> I've found that simply activating XeTeX under *Document Settings –
>>> Fonts*will cause parsing errors on viewing if the document also has
>>> *Math Options – Use AMS
36 matches
Mail list logo