Guenter Milde wrote: > On 2013-01-14, Enrico Forestieri wrote: >> On Mon, Jan 14, 2013 at 02:33:36AM +0100, Uwe Stöhr wrote: > >>> But to come to an end, decide once again but please act then >>> consistently. I will have to update IEEEtran and I want to know from >>> you what I should do now. > >> Nothing. If you do nothing, you break nothing. > >> http://www.lyx.org/trac/ticket/8503#comment:1 > > However, if you do nothing, you also do not fix something broken.
Did you read the link? I believe Enrico wanted to say that nothing is broken: Both the current template and layout file work fine with the new version. I currently have no installation to test, but I scanned the changelog and http://www.michaelshell.org/tex/ieeetran/, and I am pretty sure that Enrico is right: The only listed backward incompatible changes concern macros that are neither used in the layout file nor in the template. Therefore the only issue with the current IEEEtran support of LyX is missing support for the new macros \IEEEtitleabstractindextext and \IEEEdisplaynontitleabstractindextext, but this is nothing new since their predessors \IEEEcompsoctitleabstractindextext and \IEEEdisplaynotcompsoctitleabstractindextext are not supported either. BTW, IEEEtran.cls is a very good example, since it is widely used. You can easily verify the following facts: 1) Different conferences/journals require different versions of IEEEtran.cls Examples: Official IEEE transcations use the new version 1.8 mentioned by Uwe: http://www.ieee.org/publications_standards/publications/authors/author_templates.html https://files.ifi.uzh.ch/icseweb/how-to-submit/index.html required its own version 1.7a which is _not_ equal to the version 1.7a from CTAN. http://netcod2012.org/doku.php?id=submission recommended (but did not require) 1.7a from CTAN. 2) The template is not only used by the IEEE, but also by independent conferences Examples: https://files.ifi.uzh.ch/icseweb/home/index.html. I have also seen a local mini conference using it. 3) The IEEEtran.cls author knows that backward compatibility is important (see the notes on his website). IMHO, IEEEtran.cls does not support Uwe's reasoning at all, but rather the oppsosite. And I'd really like to see _one_ example of an updated journal/conference .cls file that broke an officially supported LyX .layout file (and no, unless somebody presents at least one incompatible change of the ACM classes that started this thread I won't believe that the new versions are backward incompatible: I only saw new commands, not changed or deleted old ones). Therefore, the best option is IMNSHO to use one of the several suggestions of versioned layouts, _if_ new layouts in the stable branch are necessary at all (but I repeat myself). Georg
