Re: CopyrightYear is the correct command name in acmsiggraph-0.92.layout

2017-02-16 Thread Jürgen Spitzmüller 
Am Donnerstag, den 16.02.2017, 19:06 +0100 schrieb Jean-Pierre
Chrétien:
> Happily, ACM decided to shift to the sole acmart.cls class for all
> their 
> publications as Jürgen pointed out (see also 
> https://www.tug.org/tug2016/slides/veytsman.pdf), and made very
> recently all 
> their old class files unavailable.
> So we rather should cencentrate on creating a layout for the acmart
> class rather 
> than fighting with obsolete stuff like I did (it is stated that
> obsoleted LaTeX 
> acm packages won't be usable to submit publications after Spring
> 2017).

Nonetheless Günter's proposal makes sense and is a cheap fix for recent
versions of acmsiggraph. However, I'd stick with the old macro, since
the layout version indicates 0.92, and add to Style "Copyright_year":

Preamble
% Compatibility fix for acmsiggraph >= 0.93.
\@ifundefined{copyrightyear}{\let\copyrightyear\CopyrightYear}{}
EndPreamble

Jürgen

signature.asc
Description: This is a digitally signed message part

Re: Errors with some testcases because of redefined \strong

2017-02-16 Thread Jürgen Spitzmüller 
Am Donnerstag, den 16.02.2017, 16:19 +0100 schrieb Kornel Benko:
> > I'd probably use \providecommand. But you'd need to check whether
> the
> > output is identical (see below). And alternative is using \def or
> > \@ifundefined{strong}{\newcommand...}{\renewcommand...}
> 
> OK. Any solution is better than what we have now.

I have committed a fix using \providecommand. I have verified that
fontspec's strong produces formally identical output.

This should also go to stable.

Jürgen

signature.asc
Description: This is a digitally signed message part

Standalone Math Editor

2017-02-16 Thread Wei-Ting Lin 
Hi all,

I have used Lyx for several years. This is a really amazing software.

However, many people still write LaTex with text editors. That usually
means when we cowork on some article, we have to write LaTex directly.

This is ok. However, sometimes we have very long and complicated equations.
One of amazing features of Lyx is its math editor. This makes the equation
visible, when you're editing. That has helped me a lot.

Therefore, I'm thinking if it is possible to separate the math editor, as a
standalone, lightweight editor.

I'm also thinking if it is possible to call the editor from vim, emacs or
whatever, when we need to edit an equation, and then return the LaTex code
back to vim or emacs.

It seems there is no such work yet. I'm wondering how difficulty to
implement this. If this is not too hard, I would like to try to do it.

Thank you very much,
Wei-Ting

Re: [patch] Theorem environment: set NextNoIndent to 0

2017-02-16 Thread Scott Kostyshak 
On Thu, Feb 16, 2017 at 10:04:03AM +0100, Jürgen Spitzmüller wrote:
> Am Donnerstag, den 16.02.2017, 00:22 -0500 schrieb Scott Kostyshak:
> > Probably the ideal approach is to maximize a weighted average, where
> > the
> > weights are how often the document classes are used. Unfortunately, I
> > don't know how to calculate the weights.
> 
> This would be an application of the IfStyle tag Richard once proposed
> (but never implemented apparently):
> http://marc.info/?l=lyx-devel=124967798121429=2
> 
> You could use the most frequent setting in the module, and then in the
> diverging classes:
> 
> IfStyle Theorem
>   NextNoIndent  0
> End

Interesting. That is exactly the issue.

Scott


signature.asc
Description: PGP signature

Re: CopyrightYear is the correct command name in acmsiggraph-0.92.layout

2017-02-16 Thread Scott Kostyshak 
On Thu, Feb 16, 2017 at 07:06:48PM +0100, Jean-Pierre Chrétien wrote:
> Le 15/02/2017 à 02:09, Scott Kostyshak a écrit :
> > On Tue, Feb 14, 2017 at 05:20:19PM +0100, Jürgen Spitzmüller wrote:
> > > Am Dienstag, den 14.02.2017, 16:16 +0100 schrieb Jean-Pierre Chrétien:
> > > > diff --git a/lib/layouts/acmsiggraph-0-92.layout
> > > > b/lib/layouts/acmsiggraph-0-92.layout
> > > > index 5732ecc..30a35df 100644
> > > > --- a/lib/layouts/acmsiggraph-0-92.layout
> > > > +++ b/lib/layouts/acmsiggraph-0-92.layout
> > > > @@ -108,7 +108,7 @@ End
> > > > 
> > > >   Style "Copyright_year"
> > > >  CopyStyle   "TOG online ID"
> > > > -   LatexName   copyrightyear
> > > > +   LatexName   CopyrightYear
> > > >  LabelString "Year of copyright:"
> > > 
> > > Are you sure this command was not valid in previous versions? The
> > > changelog of 0.93 says: "Corrected \CopyrightYear command". Perhaps you
> > > should double-check with version 0.92.
> > 
> > +1
> > 
> > For more information on how to handle this situation, see the
> > Development manual section:
> > 3.3 Layouts for document classes with incompatible versions
> 
> Thanks for the pointer, I should have seen that asmsiggraph was the example
> used to illustrate the subject, and noticed that I had retrieved the 0.93
> version, so that really I should have rather created a
> acmsiggraph-0.93.layout file, and in master rather than in stable.
> 
> Happily, ACM decided to shift to the sole acmart.cls class for all their
> publications as Jürgen pointed out (see also
> https://www.tug.org/tug2016/slides/veytsman.pdf), and made very recently all
> their old class files unavailable.
> So we rather should cencentrate on creating a layout for the acmart class
> rather than fighting with obsolete stuff like I did (it is stated that
> obsoleted LaTeX acm packages won't be usable to submit publications after
> Spring 2017).

This is good to know. Thanks for looking into it.

Scott


signature.asc
Description: PGP signature

Re: Errors compiling some beamer files

2017-02-16 Thread Scott Kostyshak 
On Thu, Feb 16, 2017 at 11:54:28AM +0100, Kornel Benko wrote:
> Affected files:
>   lib/templates/fr_beamer-conference-ornate-20min.lyx
>   lib/examples/beamerlyxexample1.lyx
> 
> The errors are with xelatex and lualatex the same. It does not depend on tex 
> or non-tex font setting.
> 
>   ! Class beamer Error: Overprints may not overlap.
>   Desc: Class beamer Error: Overprints may not overlap.
>   Text:  \end{frame}
> 
>   This error message was generated by an \errmessage
>   command, so I can't give any explicit help.
>   Pretend that you're Hercule Poirot: Examine all clues,
>   and deduce the truth by order and method.
> 
> The created pdf looks OK though.
> Prior to this message I see in latex-log:
>   
>   LaTeX Font Info:Font shape `OT1/ptm/bx/n' in size <10.95> not 
> available
>   (Font)  Font shape `OT1/ptm/b/n' tried instead on input 
> line 54.
>   LaTeX Font Info:Font shape `OT1/ptm/bx/n' in size <8> not available
>   (Font)  Font shape `OT1/ptm/b/n' tried instead on input 
> line 54.
>   LaTeX Font Info:Font shape `OT1/ptm/bx/n' in size <6> not available
>   (Font)  Font shape `OT1/ptm/b/n' tried instead on input 
> line 54.
>   LaTeX Font Info:Font shape `T1/lmss/m/it' in size <10.95> not 
> available
>   (Font)  Font shape `T1/lmss/m/sl' tried instead on input 
> line 54.
>   LaTeX Font Info:Font shape `T1/lmss/m/it' in size <8> not available
>   (Font)  Font shape `T1/lmss/m/sl' tried instead on input 
> line 54.
>   LaTeX Font Info:Font shape `T1/lmss/m/it' in size <6> not available
>   (Font)  Font shape `T1/lmss/m/sl' tried instead on input 
> line 54.
>   LaTeX Font Info:Font shape `OT1/ptm/bx/n' in size <5> not available
>   (Font)  Font shape `OT1/ptm/b/n' tried instead on input 
> line 54.
>   LaTeX Font Info:Font shape `T1/lmss/m/it' in size <5> not available
> 
> Do I miss some font? This is weird, since the standard latex has no problems.

I see the same thing. The commit that caused these tests to fail for me
was after b863fb0. I just assumed the tests were inverted because they
work on an up-to-date TeX Live. I have not updated TeX Live recently.

Günter, do these tests pass for you? The tests corresponding to the
failings Kornel mentioned are:

3222 - export/examples/beamerlyxexample1_dvi3_texF (Failed)
3223 - export/examples/beamerlyxexample1_dvi3_systemF (Failed)
3227 - export/examples/beamerlyxexample1_pdf4_texF (Failed)
3228 - export/examples/beamerlyxexample1_pdf4_systemF (Failed)
3229 - export/examples/beamerlyxexample1_pdf5_texF (Failed)
3230 - export/examples/beamerlyxexample1_pdf5_systemF (Failed)

6039 - export/templates/fr_beamer-conference-ornate-20min_dvi3_texF 
(Failed)
6040 - export/templates/fr_beamer-conference-ornate-20min_dvi3_systemF 
(Failed)
6044 - export/templates/fr_beamer-conference-ornate-20min_pdf4_texF 
(Failed)
6045 - export/templates/fr_beamer-conference-ornate-20min_pdf4_systemF 
(Failed)
6046 - export/templates/fr_beamer-conference-ornate-20min_pdf5_texF 
(Failed)
6047 - export/templates/fr_beamer-conference-ornate-20min_pdf5_systemF 
(Failed)

Scott


signature.asc
Description: PGP signature

Re: CopyrightYear is the correct command name in acmsiggraph-0.92.layout

2017-02-16 Thread Jean-Pierre Chrétien 

Le 15/02/2017 à 02:09, Scott Kostyshak a écrit :

On Tue, Feb 14, 2017 at 05:20:19PM +0100, Jürgen Spitzmüller wrote:

Am Dienstag, den 14.02.2017, 16:16 +0100 schrieb Jean-Pierre Chrétien:

diff --git a/lib/layouts/acmsiggraph-0-92.layout
b/lib/layouts/acmsiggraph-0-92.layout
index 5732ecc..30a35df 100644
--- a/lib/layouts/acmsiggraph-0-92.layout
+++ b/lib/layouts/acmsiggraph-0-92.layout
@@ -108,7 +108,7 @@ End

  Style "Copyright_year"
 CopyStyle   "TOG online ID"
-   LatexName   copyrightyear
+   LatexName   CopyrightYear
 LabelString "Year of copyright:"


Are you sure this command was not valid in previous versions? The
changelog of 0.93 says: "Corrected \CopyrightYear command". Perhaps you
should double-check with version 0.92.


+1

For more information on how to handle this situation, see the
Development manual section:
3.3 Layouts for document classes with incompatible versions


Thanks for the pointer, I should have seen that asmsiggraph was the example used 
to illustrate the subject, and noticed that I had retrieved the 0.93 version, so 
that really I should have rather created a acmsiggraph-0.93.layout file, and in 
master rather than in stable.


Happily, ACM decided to shift to the sole acmart.cls class for all their 
publications as Jürgen pointed out (see also 
https://www.tug.org/tug2016/slides/veytsman.pdf), and made very recently all 
their old class files unavailable.
So we rather should cencentrate on creating a layout for the acmart class rather 
than fighting with obsolete stuff like I did (it is stated that obsoleted LaTeX 
acm packages won't be usable to submit publications after Spring 2017).


--
Jean-Pierre

Re: Errors with some testcases because of redefined \strong

2017-02-16 Thread Jürgen Spitzmüller 
Am Donnerstag, den 16.02.2017, 17:06 +0100 schrieb Kornel Benko:
> Isn't that the meaning of 'solution'?

You have a point.

Jürgen

signature.asc
Description: This is a digitally signed message part

Re: Errors with some testcases because of redefined \strong

2017-02-16 Thread Kornel Benko 
Am Donnerstag, 16. Februar 2017 um 16:47:43, schrieb Jürgen Spitzmüller 

> Am Donnerstag, den 16.02.2017, 16:19 +0100 schrieb Kornel Benko:
> > OK. Any solution is better than what we have now.
> 
> No, not any. Only one that does not break other documents. What we have
> now only breaks with Non-TeX fonts, and only with a very recent
> fontspec.

Isn't that the meaning of 'solution'?

> Jürgen

Kornel

signature.asc
Description: This is a digitally signed message part.

Re: Errors with some testcases because of redefined \strong

2017-02-16 Thread Jürgen Spitzmüller 
Am Donnerstag, den 16.02.2017, 16:19 +0100 schrieb Kornel Benko:
> OK. Any solution is better than what we have now.

No, not any. Only one that does not break other documents. What we have
now only breaks with Non-TeX fonts, and only with a very recent
fontspec.

Jürgen

signature.asc
Description: This is a digitally signed message part

Re: Errors with some testcases because of redefined \strong

2017-02-16 Thread Kornel Benko 
Am Donnerstag, 16. Februar 2017 um 15:08:24, schrieb Jürgen Spitzmüller 

> Am Donnerstag, den 16.02.2017, 11:15 +0100 schrieb Kornel Benko:
> > Hi,
> > the attached patch fixes it for me. 
> 
> This will fail for all cases were strong is not defined.
> 
> I'd probably use \providecommand. But you'd need to check whether the
> output is identical (see below). And alternative is using \def or
> \@ifundefined{strong}{\newcommand...}{\renewcommand...}

OK. Any solution is better than what we have now.

> > 16 testcases are affected.
> > E.g. export/doc/Additional_pdf4_systemF:
> > Desc: LaTeX Error: Command \strong already defined.
> > Text:  \newcommand{\strong}[1]{\textbf{#1}}
> > 
> > Your command was ignored.
> > Type  Ito replace it with another command,
> > orto continue without it.
> > 
> > Anybody else seeing this?
> 
> I suppose this is due to the recent fontspec update:
> 
> - v2.6 (2017/02/12)
> 
> [...]
> * Add `\strong` as the "weight" analogy to `\emph`. This will need
>   some extra syntactic sugar from `fontspec` before it becomes
>   truly useful. 

Feels like it will remain there from now on.

> Jürgen
> 
> > 

Kornel

signature.asc
Description: This is a digitally signed message part.

Re: Errors with some testcases because of redefined \strong

2017-02-16 Thread Jürgen Spitzmüller 
Am Donnerstag, den 16.02.2017, 11:15 +0100 schrieb Kornel Benko:
> Hi,
> the attached patch fixes it for me. 

This will fail for all cases were strong is not defined.

I'd probably use \providecommand. But you'd need to check whether the
output is identical (see below). And alternative is using \def or
\@ifundefined{strong}{\newcommand...}{\renewcommand...}

> 16 testcases are affected.
> E.g. export/doc/Additional_pdf4_systemF:
>   Desc: LaTeX Error: Command \strong already defined.
>   Text:  \newcommand{\strong}[1]{\textbf{#1}}
> 
>   Your command was ignored.
>   Type  I    to replace it with another command,
>   orto continue without it.
> 
> Anybody else seeing this?

I suppose this is due to the recent fontspec update:

- v2.6 (2017/02/12)

[...]
* Add `\strong` as the "weight" analogy to `\emph`. This will need
  some extra syntactic sugar from `fontspec` before it becomes
  truly useful. 

Jürgen

> 
>   Kornel

signature.asc
Description: This is a digitally signed message part

Errors compiling some beamer files

2017-02-16 Thread Kornel Benko 
Affected files:
lib/templates/fr_beamer-conference-ornate-20min.lyx
lib/examples/beamerlyxexample1.lyx

The errors are with xelatex and lualatex the same. It does not depend on tex or 
non-tex font setting.

! Class beamer Error: Overprints may not overlap.
Desc: Class beamer Error: Overprints may not overlap.
Text:  \end{frame}

This error message was generated by an \errmessage
command, so I can't give any explicit help.
Pretend that you're Hercule Poirot: Examine all clues,
and deduce the truth by order and method.

The created pdf looks OK though.
Prior to this message I see in latex-log:

LaTeX Font Info:Font shape `OT1/ptm/bx/n' in size <10.95> not 
available
(Font)  Font shape `OT1/ptm/b/n' tried instead on input 
line 54.
LaTeX Font Info:Font shape `OT1/ptm/bx/n' in size <8> not available
(Font)  Font shape `OT1/ptm/b/n' tried instead on input 
line 54.
LaTeX Font Info:Font shape `OT1/ptm/bx/n' in size <6> not available
(Font)  Font shape `OT1/ptm/b/n' tried instead on input 
line 54.
LaTeX Font Info:Font shape `T1/lmss/m/it' in size <10.95> not 
available
(Font)  Font shape `T1/lmss/m/sl' tried instead on input 
line 54.
LaTeX Font Info:Font shape `T1/lmss/m/it' in size <8> not available
(Font)  Font shape `T1/lmss/m/sl' tried instead on input 
line 54.
LaTeX Font Info:Font shape `T1/lmss/m/it' in size <6> not available
(Font)  Font shape `T1/lmss/m/sl' tried instead on input 
line 54.
LaTeX Font Info:Font shape `OT1/ptm/bx/n' in size <5> not available
(Font)  Font shape `OT1/ptm/b/n' tried instead on input 
line 54.
LaTeX Font Info:Font shape `T1/lmss/m/it' in size <5> not available

Do I miss some font? This is weird, since the standard latex has no problems.

Kornel

signature.asc
Description: This is a digitally signed message part.

Errors with some testcases because of redefined \strong

2017-02-16 Thread Kornel Benko 
Hi,
the attached patch fixes it for me. 16 testcases are affected.
E.g. export/doc/Additional_pdf4_systemF:
Desc: LaTeX Error: Command \strong already defined.
Text:  \newcommand{\strong}[1]{\textbf{#1}}

Your command was ignored.
Type  Ito replace it with another command,
orto continue without it.

Anybody else seeing this?

Kornel

signature.asc
Description: This is a digitally signed message part.
diff --git a/lib/layouts/logicalmkup.module b/lib/layouts/logicalmkup.module
index 33b954d..0b7a569 100644
--- a/lib/layouts/logicalmkup.module
+++ b/lib/layouts/logicalmkup.module
@@ -52,7 +52,7 @@ InsetLayout Flex:Strong
 	  Series  Bold
 	EndFont
 	Preamble
-	\newcommand{\strong}[1]{\textbf{#1}}
+	\renewcommand{\strong}[1]{\textbf{#1}}
 	EndPreamble
 	InToc true
 	HTMLTag   strong

Re: [patch] Theorem environment: set NextNoIndent to 0

2017-02-16 Thread Jürgen Spitzmüller 
Am Donnerstag, den 16.02.2017, 00:22 -0500 schrieb Scott Kostyshak:
> Probably the ideal approach is to maximize a weighted average, where
> the
> weights are how often the document classes are used. Unfortunately, I
> don't know how to calculate the weights.

This would be an application of the IfStyle tag Richard once proposed
(but never implemented apparently):
http://marc.info/?l=lyx-devel=124967798121429=2

You could use the most frequent setting in the module, and then in the
diverging classes:

IfStyle Theorem
  NextNoIndent  0
End

Jürgen

signature.asc
Description: This is a digitally signed message part