José Matos wrote:
That is the task for layout2layout and lyx2lyx, the convertion should be
seamless to the final user.
As an example, Théorème,
In 1.4
Style Théorème
...
End
In 1.5
Style Theoreme
GUIname Théorème
...
End
where Theoreme is a convertion from Théorème to an ascii only representation.
Codewise this convertion seems easy and all the previous files should be
working. Or am I missing something?
The name of the layout appears in three files:
in .layout or .inc:
Style Théorème
in .lyx:
\begin_layout Théorème
or
\layout Théorème
in .ui:
Item "Théorème" "layout Théorème"
and in some cases:
in the .layout : Style Théorème_ST
in the .lyx \begin_layout Théorème ST
in the .ui : Item "Théorème ST" "layout Théorème ST"
(the difference being for _ in the Style name)
Thus the conversion have to modify the three files correctly.
And of course it may happens that styles Théorème
and Theoreme and Thèoréme and Théorème_ST and
Théorème_T etc... exist in the files which are
input in a given .layout (recursively)... In that case
what happens? The best would be that the script
ask the user to choose new names(?) and do after
the right conversions in all files.
And, possibly, there is an other case I did not test: may be
it was possible to define a counter with non ASCII
characters, in that case, this also has to be
converted?
PhC
