Uwe Stöhr wrote: > > My idea would be to provide a new layout with a new name > > (journalx-new.layout), then lyx2lyx could change this to > > journalx.layout in the new major release (and also the old > > journalx.layout) and revert accordingly. > > That is very confusing. What happens if we have 5 layout versions. How do we > name them?
This would be the easiest part, but I doubt this will happen very often within a minor release cycle (if it would, I would question the sanity of the respective class author). > But as I just explained, backward compatibility is not > necessary. You didn't convince me. As JMarc pointed out, people work on different machines (I work on three, as well). And you are not allowed to always use the most up-to-date version on each (e.g. if one is controlled by a thir person admin) > > This proper conversion would also prevent that people cannot process > > anymore their old paper because the layout names change. > > This is not a good idea. When I want to submit to a journal or update my CV > I would still want to have my old file compilable and only need to change > 2, or 3 things quickly. And this is possible with all my layout changes > (except of modernCV as I wrote). The suggested approach allows all: You can switch to the new layout (and change "2 or 3 things") and you can still use the old layout. In any case, a clean file format should always be priority. I understand that your approach is less work (for you), but that's life. Jürgen
