Re: lib/examples/aas_sample.lyx uncompilable with TL18

2018-07-07 Thread Jürgen Spitzmüller
Am Samstag, den 07.07.2018, 14:08 +0200 schrieb Jean-Pierre:
> It's more complicated, AFAIR aas_sample.laas_sample.lyx compiles
> with 
> aastex62.cls, but the outpuoutput is wrong.

Then we also need a new template, I suppose, that is fit for aastex62
(and keep the old one for the old class).

Jürgen

> 
> --
> Jean-Pierre
> 
> 

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


Re: lib/examples/aas_sample.lyx uncompilable with TL18

2018-07-07 Thread Jean-Pierre




Le 7 juillet 2018 13:24:45 Jürgen Spitzmüller  a écrit :


Am Samstag, den 07.07.2018, 13:17 +0200 schrieb Kornel Benko:

Then there will still be missing a solution for aastex62.cls


Why? Just add the respectice aastex62.layout file.
It's more complicated, AFAIR aas_sample.laas_sample.lyx compiles with 
aastex62.cls, but the outpuoutput is wrong.


--
Jean-Pierre




Re: lib/examples/aas_sample.lyx uncompilable with TL18

2018-07-07 Thread Jürgen Spitzmüller
Am Samstag, den 07.07.2018, 13:17 +0200 schrieb Kornel Benko:
> Then there will still be missing a solution for aastex62.cls

Why? Just add the respectice aastex62.layout file.

Jürgen

> 
>   Kornel

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


Re: lib/examples/aas_sample.lyx uncompilable with TL18

2018-07-07 Thread Kornel Benko
Am Dienstag, 12. Juni 2018 21:01:13 CEST schrieb Jürgen Spitzmüller 
:
> >
> > Could we create a aastex layout which is independent of the aastex version?
> >
> > (Preferably maybe with help of \IfFileExists{filename}?)
> >
> 
> I would not do that. These are two distinct classes.
> 
> Jürgen
> 
> 

Then there will still be missing a solution for aastex62.cls

Kornel


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


Re: lib/examples/aas_sample.lyx uncompilable with TL18

2018-06-12 Thread Jürgen Spitzmüller
>
> Could we create a aastex layout which is independent of the aastex version?
>
> (Preferably maybe with help of \IfFileExists{filename}?)
>

I would not do that. These are two distinct classes.

Jürgen


>
> Kornel
>
>
>


Re: lib/examples/aas_sample.lyx uncompilable with TL18

2018-06-12 Thread Kornel Benko
Am Dienstag, 12. Juni 2018 18:43:34 CEST schrieb Jean-Pierre Chrétien 
:
> Le 12/06/2018 à 18:33, Jürgen Spitzmüller a écrit :
> > Am Dienstag, den 12.06.2018, 17:32 +0200 schrieb Jean-Pierre Chrétien:
> >> Le 12/06/2018 à 15:02, Kornel Benko a écrit :
> >>
> >>>
> >>> Hm, simply changing 'aastex6' to 'aastex62' does not help, because
> >>> now we have
> >>> the next error:
> >>>
> >>> ! Class revtex4-1 Error: \and is not supported.
> >>
> >> Looks like a compatibility problem between aastex62.cls and revtex4
> >> which did
> >> not appear with aastex6.cls,
> > 
> > Which is another argument for adding a separate aastex62.layout and
> > keeping aastex6.layout (in obsolete eventually). This is most probably
> > also the reason they renamed the class.
> 
> Sure.
> I was wrong in my previous mail, \slugcomment masked the real error, which 
> stems 
> from the fact that \and is deprecated in aastex62.tex:
> 
> 
> %% Note that the \and command from previous versions of AASTeX is now
> %% depreciated in this version as it is no longer necessary. AASTeX
> %% automatically takes care of all commas and "and"s between authors names.
> 
> 
> We should remove the 'And' style in the aastex62.layout file (which will call 
> the aastex.layout file).
> 
> Ans solving the issue in aas_sample.lyx is straightforward.
> 
> But should not we keep aas6_sample.lyx and aas62_sample.lyx, as well as
> aastex6.lyx and aastex62.lyx in the templates dir ?
> 6 in TL17 and 62 in TL18 are exclusive.
> 

Could we create a aastex layout which is independent of the aastex version?
(Preferably maybe with help of \IfFileExists{filename}?)

Kornel



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


Re: lib/examples/aas_sample.lyx uncompilable with TL18

2018-06-12 Thread Jean-Pierre Chrétien

Le 12/06/2018 à 18:33, Jürgen Spitzmüller a écrit :

Am Dienstag, den 12.06.2018, 17:32 +0200 schrieb Jean-Pierre Chrétien:

Le 12/06/2018 à 15:02, Kornel Benko a écrit :



Hm, simply changing 'aastex6' to 'aastex62' does not help, because
now we have
the next error:

! Class revtex4-1 Error: \and is not supported.


Looks like a compatibility problem between aastex62.cls and revtex4
which did
not appear with aastex6.cls,


Which is another argument for adding a separate aastex62.layout and
keeping aastex6.layout (in obsolete eventually). This is most probably
also the reason they renamed the class.


Sure.
I was wrong in my previous mail, \slugcomment masked the real error, which stems 
from the fact that \and is deprecated in aastex62.tex:



%% Note that the \and command from previous versions of AASTeX is now
%% depreciated in this version as it is no longer necessary. AASTeX
%% automatically takes care of all commas and "and"s between authors names.


We should remove the 'And' style in the aastex62.layout file (which will call 
the aastex.layout file).


Ans solving the issue in aas_sample.lyx is straightforward.

But should not we keep aas6_sample.lyx and aas62_sample.lyx, as well as
aastex6.lyx and aastex62.lyx in the templates dir ?
6 in TL17 and 62 in TL18 are exclusive.

--
Jean-Pierre


Re: lib/examples/aas_sample.lyx uncompilable with TL18

2018-06-12 Thread Jürgen Spitzmüller
Am Dienstag, den 12.06.2018, 17:32 +0200 schrieb Jean-Pierre Chrétien:
> Le 12/06/2018 à 15:02, Kornel Benko a écrit :
> 
> > 
> > Hm, simply changing 'aastex6' to 'aastex62' does not help, because
> > now we have 
> > the next error:
> > 
> > ! Class revtex4-1 Error: \and is not supported.
> 
> Looks like a compatibility problem between aastex62.cls and revtex4
> which did 
> not appear with aastex6.cls,

Which is another argument for adding a separate aastex62.layout and
keeping aastex6.layout (in obsolete eventually). This is most probably
also the reason they renamed the class.

Jürgen


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


Re: lib/examples/aas_sample.lyx uncompilable with TL18

2018-06-12 Thread Jean-Pierre Chrétien

Le 12/06/2018 à 15:02, Kornel Benko a écrit :



Hm, simply changing 'aastex6' to 'aastex62' does not help, because now we have 
the next error:


! Class revtex4-1 Error: \and is not supported.


Looks like a compatibility problem between aastex62.cls and revtex4 which did 
not appear with aastex6.cls,


Investigating further, the error appears in \slugcomment which appears in the 
preamble:


\begin_preamble
\newcommand{\vdag}{(v)^\dagger}
\newcommand{\myemail}{skywal...@galaxy.far.far.away}
\slugcomment{Not to appear in Nonlearned J., 45.}
\shorttitle{Djorgovski et al.}
\shortauthors{Collapsed Cores in Globular Clusters}
\end_preamble

\slugcomment was redefined with aastex6:

$ grep submitted  /opt/texlive/2017/texmf-dist/tex/latex/aastex/aastex6.cls
%  \centerline{\itshape\footnotesize\@submitted}
\def\submitted#1{\gdef\@submitted{#1}}
\let\slugcomment\submitted   % slugcomment == submitted
\submitted{Draft version \today}
\journalinfo{\@submitted}

and is no more redefined with  aastex62;

$  grep submitted  /opt/texlive/2018/texmf-dist/tex/latex/aastex/aastex62.cls
% \def\submitted#1{\gdef\@submitted{#1}}
% \let\slugcomment\submitted   % slugcomment == submitted
% \submitted{Draft version \today}
% \journalinfo{\@submitted}
{\def\@submitted{Submitted to #1}}%
\expandafter\ifx\csname @submitted\endcsname\relax\else
\expandafter\produce@RRAP\expandafter{\centerline{\@submitted\hbox

I will post a note to the class authors, but in the meantime we must find a 
workaround to make aas_sample.lyx work with TL18.


--
Jean-Pierre





Re: lib/examples/aas_sample.lyx uncompilable with TL18

2018-06-12 Thread Kornel Benko
Am Dienstag, 12. Juni 2018 14:41:01 CEST schrieb Kornel Benko :
> Am Dienstag, 12. Juni 2018 14:17:02 CEST schrieb Jean-Pierre Chrétien 
> :
> > Le 12/06/2018 à 12:13, Kornel Benko a écrit :
> > > We are requesting aastex6.cls, but this is not provided by TL18.
> > > 
> > > Instead there exists aastex62.cls (version 6.2 instead of version 6.0).
> > > 
> > > Looks like we need some general solution to be able to use existing .cls 
> > > file :(
> > 
> > When the new class has a different name, we can manage as described in 
> > section 
> > 3.3 of Development.lyx.
> > 
> > We should review of course the layout, there are some improvements in the 
> > new 
> > class. The big change in the aastex class came with aastex6.cls however, I 
> > do 
> > not know if we rewrote completely the template at the time. In addition, I 
> > guess 
> > they started a numeric naming of classes, there existed an aastex61.cls 
> > file 
> > between Oct. 2018 and Jan. 2018, which apparently did not get in TeXLive 
> > 2017.
> > 
> > We could move templates/aastex6.lyx to templates/obsolete/.
> 
> I do not favor this. Because TL18 may come much later for most distros.
> 
> > Would this be enough? Maybe obsolete is not correct there (used for classes 
> > which are not in use anymore). What about a 'deprecated' directory ?
> > 
> 
> I had something like regular expression in mind. For instance in 
> aastex6.layout
> we could have
>   
> #\DeclareLaTeXClass[aastex6[12]?,amssymb.sty,latexsym.sty,natbib.sty,verbatim.sty]{American
>  Astronomical Society (AASTeX v. 6)}
> 

Hm, simply changing 'aastex6' to 'aastex62' does not help, because now we have 
the next error:
! Class revtex4-1 Error: \and is not supported.

Kornel






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


Re: lib/examples/aas_sample.lyx uncompilable with TL18

2018-06-12 Thread Kornel Benko
Am Dienstag, 12. Juni 2018 14:17:02 CEST schrieb Jean-Pierre Chrétien 
:
> Le 12/06/2018 à 12:13, Kornel Benko a écrit :
> > We are requesting aastex6.cls, but this is not provided by TL18.
> > 
> > Instead there exists aastex62.cls (version 6.2 instead of version 6.0).
> > 
> > Looks like we need some general solution to be able to use existing .cls 
> > file :(
> 
> When the new class has a different name, we can manage as described in 
> section 
> 3.3 of Development.lyx.
> 
> We should review of course the layout, there are some improvements in the new 
> class. The big change in the aastex class came with aastex6.cls however, I do 
> not know if we rewrote completely the template at the time. In addition, I 
> guess 
> they started a numeric naming of classes, there existed an aastex61.cls file 
> between Oct. 2018 and Jan. 2018, which apparently did not get in TeXLive 2017.
> 
> We could move templates/aastex6.lyx to templates/obsolete/.

I do not favor this. Because TL18 may come much later for most distros.

> Would this be enough? Maybe obsolete is not correct there (used for classes 
> which are not in use anymore). What about a 'deprecated' directory ?
> 

I had something like regular expression in mind. For instance in aastex6.layout
we could have

#\DeclareLaTeXClass[aastex6[12]?,amssymb.sty,latexsym.sty,natbib.sty,verbatim.sty]{American
 Astronomical Society (AASTeX v. 6)}

Kornel




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


Re: lib/examples/aas_sample.lyx uncompilable with TL18

2018-06-12 Thread Jean-Pierre Chrétien

Le 12/06/2018 à 12:13, Kornel Benko a écrit :

We are requesting aastex6.cls, but this is not provided by TL18.

Instead there exists aastex62.cls (version 6.2 instead of version 6.0).

Looks like we need some general solution to be able to use existing .cls file :(


When the new class has a different name, we can manage as described in section 
3.3 of Development.lyx.


We should review of course the layout, there are some improvements in the new 
class. The big change in the aastex class came with aastex6.cls however, I do 
not know if we rewrote completely the template at the time. In addition, I guess 
they started a numeric naming of classes, there existed an aastex61.cls file 
between Oct. 2018 and Jan. 2018, which apparently did not get in TeXLive 2017.


We could move templates/aastex6.lyx to templates/obsolete/.
Would this be enough? Maybe obsolete is not correct there (used for classes 
which are not in use anymore). What about a 'deprecated' directory ?


--
Jean-Pierre