Martin Vermeer wrote:
On Fri, Jul 06, 2007 at 06:31:39PM +0200, Abdelrazak Younes wrote:
Philippe Charpentier wrote:
2) Accept the layout field as is and do not try to translate them.
Of course, accept Style names with non ASCII characters (like in the
previous versions of lyx) would be the simplest way for me. But in that
case
if the layout in UTF-8 probably the document has to be in the same
encoding (if its possible?) which means that lyx have to convert it
automatically.
...
I can try to finish my patch if others think that your use case is worth
supporting.
I think it is. If one user steps forward having this problem,
there must be dozens of others.
All my documents where written with my layouts and as I use lyx since
the 1.2 version I have a lot! (94 different files for the layouts
a lot of mathematical papers, mathematical books teaching documents,
letters etc...).
Traduce my layout to be accepted by the actual lyx-1.5 is not really
a problem, but traduce all my actual documents to be read by lyx-1.5 with
the
new Style names is for me probably almost impossible!
Not impossible with recursive search and replace.
This should really be in lyx2lyx then.
What I mean is that, if I finish my patch, there won't be a need to
handle that in lyx2lyx and bug 2992 would basically be a WONTFIX. I am
not sure myself what is the best solution. As long as we don't have a
GUI for creating layout, supporting non-ASCII style names seems natural
because the user won't have to think about the style name and the
GUIName of this style.
Abdel.
