Charpentier Philippe wrote:
> 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.
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 repres
On Tuesday 28 November 2006 1:54 pm, Jean-Marc Lasgouttes wrote:
> > "José" == José Matos <[EMAIL PROTECTED]> writes:
>
> José> Codewise this convertion seems easy and all the previous files
> José> should be working. Or am I missing something?
>
> No, it looks OK if this asciization is easy
> "José" == José Matos <[EMAIL PROTECTED]> writes:
José> Codewise this convertion seems easy and all the previous files
José> should be working. Or am I missing something?
No, it looks OK if this asciization is easy in python. One should
check against duplicates, though, like in the case of
On Wednesday 22 November 2006 5:29 pm, Charpentier Philippe wrote:
> Now if you decide to introduce a GUIname, in such a way the name of
> Styles have to be in ASCII, I think that all the lyx files
> I wrote will be unreadable with the next versions of lyx.
?
That is the task for layout2layou
> "Georg" == Georg Baum <[EMAIL PROTECTED]> writes:
Georg> Jean-Marc Lasgouttes wrote:
>> +docstring const translateIfPossible(docstring const & name);
>> +
>>
>> Should this be named translateIfAscii?
Georg> If you prefer that I'll change it. I used translateIfPossible
Georg> because I did
Jean-Marc Lasgouttes wrote:
> +docstring const translateIfPossible(docstring const & name);
> +
>
> Should this be named translateIfAscii?
If you prefer that I'll change it. I used translateIfPossible because I did
not want to emphasise the point that the string is ASCII if it comes from a
syste
> "Georg" == Georg Baum <[EMAIL PROTECTED]> writes:
Georg> Philippe Charpentier wrote:
>> Hi, just after the release alpha of lyx-1.5, I compile lyx-1.5svn
>> and test my layouts and ui files on it. They are written in
>> ISO-8859 with accented characters and work until 1.4.x. My layout
>> and
> "Georg" == Georg Baum <[EMAIL PROTECTED]> writes:
Georg> You mean to simply accept 8bit values as is and do not
Georg> interpret them at all? I really don't like that. If we are
Georg> going to accept these 8 bit names I would prefer to convert
Georg> them to utf8, even if that can result in
Georg Baum wrote
>Do your .ui files work with this patch (requires latest svn to apply
>cleanly)?
I tried your patch on revision 16011 and it seems to work: the menu
(UTF-8) is displayed correctly (except that if an entry in the ui
file contains non ASCII characters in the name of the layout (for
Jean-Marc Lasgouttes wrote:
> But what can we do for the layout files that use 8bit characters in
> layout names (and the accompanying .lyx file)? I suspect this is going
> to be a real problem. Solution could be something as rude as
> translating to quoted encoding really keeping it as 8bit (know
Philippe Charpentier wrote:
> Hi,
> just after the release alpha of lyx-1.5, I compile lyx-1.5svn and test my
> layouts and ui files on it. They are written in ISO-8859 with accented
> characters and work until 1.4.x. My layout and ui files, converted in
> UTF-8 or not, both crash this version of
12 matches
Mail list logo
