José Matos wrote:
On Wednesday 11 July 2007 13:34:18 Abdelrazak Younes wrote:
???
How are we disagreeing?
We are discussing an implementation detail, the final result should be the
same. Instead of the current:
Style Anão
...
End
I am proposing
Style Anao
LyXName "Anão"
...
End
That
On Wednesday 11 July 2007 13:34:18 Abdelrazak Younes wrote:
> José Matos wrote:
> > On Wednesday 11 July 2007 11:33:32 [EMAIL PROTECTED] wrote:
> >>> Regarding this subject I think that this course of action is sound so
> >>> I don't expect any major surprises. (Famous last words).
> >>
> >> If so
José Matos wrote:
On Wednesday 11 July 2007 11:33:32 [EMAIL PROTECTED] wrote:
Regarding this subject I think that this course of action is sound so I
don't expect any major surprises. (Famous last words).
If something does happen, your words might well make it into LyX's famous
quotes :-)
On Wednesday 11 July 2007 11:33:32 [EMAIL PROTECTED] wrote:
> > Regarding this subject I think that this course of action is sound so I
> > don't expect any major surprises. (Famous last words).
>
> If something does happen, your words might well make it into LyX's famous
> quotes :-)
AFAIU the
On Tue, 10 Jul 2007, José Matos wrote:
On Tuesday 10 July 2007 15:16:56 [EMAIL PROTECTED] wrote:
What's the risk of embarrassing[*] bugs? (As this is just before the
release of 1.5.0). There is no RC3 planned, right?
Do you want a formula with deltas and epsilons? ;-)
No there is not any
On Tuesday 10 July 2007 15:16:56 [EMAIL PROTECTED] wrote:
>
> What's the risk of embarrassing[*] bugs? (As this is just before the
> release of 1.5.0). There is no RC3 planned, right?
Do you want a formula with deltas and epsilons? ;-)
No there is not any RC3 planned. Do you think we need one
On Tue, 10 Jul 2007, José Matos wrote:
The plan for this change is then:
* to convert our layout files to utf8;
* apply your patch;
* add a comment to the release notes.
I propose to do this tomorrow to give some time for feedback. If by
tomorrow there are no voices against we will implemen
On Tuesday 10 July 2007 13:25:04 Abdelrazak Younes wrote:
> What about the documentation? It is probably time to convert them, isn't
> it?
As far as I remember there are no patches holding that change the file
format. If so then yes it is time to start updating the documentation to the
latest
José Matos wrote:
On Tuesday 10 July 2007 10:50:28 Abdelrazak Younes wrote:
Right.
Does anyone has any objection to this change?
The purpose of this release is the support of unicode, we are using utf8 for
the saved files so it makes all sense to follow the same route for layout
files.
On Tuesday 10 July 2007 10:50:28 Abdelrazak Younes wrote:
> Right.
Does anyone has any objection to this change?
The purpose of this release is the support of unicode, we are using utf8 for
the saved files so it makes all sense to follow the same route for layout
files.
In the special ca
José Matos wrote:
On Tuesday 10 July 2007 10:23:02 Abdelrazak Younes wrote:
So?
This patch fixes a crash and a regression against 1.4. Unless you want
to implement the layout2layout support and do the GUIName addition
before 1.5.0, this patch should go in now.
It's just a string -> docstring
On Tuesday 10 July 2007 10:23:02 Abdelrazak Younes wrote:
> So?
>
> This patch fixes a crash and a regression against 1.4. Unless you want
> to implement the layout2layout support and do the GUIName addition
> before 1.5.0, this patch should go in now.
>
> It's just a string -> docstring conversio
Abdelrazak Younes wrote:
Jean-Pierre Chrétien wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
1) provide a python script that converts the layout as good as possible:
Théorème -> Theoreme
Liste_à_puce -> Liste_a_puce
The problem is that it could be done easily for French but maybe no
Abdelrazak Younes wrote:
> I am not sure we have a lyx2lyx
> equivalent for layoouts, do we?
layout2layout.
Jürgen
Jean-Pierre Chrétien wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
1) provide a python script that converts the layout as good as possible:
Théorème -> Theoreme
Liste_à_puce -> Liste_a_puce
The problem is that it could be done easily for French but maybe not for
other languages. Se
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
>
> Charpentier Philippe wrote:
> > My problem is not the encoding of the layout. It is that, since 1.2
> > version of lyx I used layouts I wrote and they contain definition of
> > styles with non ASCII characters like this:
> >
> > Style Théorème ..
Abdelrazak Younes wrote:
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 see
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 ly
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
Abdelrazak Younes wrote:
Charpentier Philippe wrote:
I would like to try your patch but I dont know how to apply it
Can you tell me?
You'll need to retrieve the latest version of the code with svn (look at
http://www.lyx.org/devel/cvs.php for more details). Then something like
"svn apply xx
I would like to test your patch, but I don't understand how to apply it
Can you tell me?
Thanks
PhC
> Can you tell me?
http://en.wikipedia.org/wiki/Patch_%28Unix%29#Usage_examples
pavel
Charpentier Philippe wrote:
I would like to try your patch but I dont know how to apply it
Can you tell me?
You'll need to retrieve the latest version of the code with svn (look at
http://www.lyx.org/devel/cvs.php for more details). Then something like
"svn apply xxx.patch" should do the tri
I would like to try your patch but I dont know how to apply it
Can you tell me?
PhC
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
> 1) provide a python script that converts the layout as good as
possible:
> Théorème -> Theoreme
> Liste_à_puce -> Liste_a_puce
This seems difficult:
first such a script may give the same name to two different Styles
second this conversion has to be done also in the documents
> 2) Accept the l
Abdelrazak Younes wrote:
Abdelrazak Younes wrote:
Charpentier Philippe wrote:
This was working perfectly until 1.4.x. But now the 1.5 version crash
if I want to use one of my layouts (independently of the encoding):
non ASCII characters seems forbidden now for the Style name. As these
names app
Abdelrazak Younes wrote:
Charpentier Philippe wrote:
This was working perfectly until 1.4.x. But now the 1.5 version crash
if I want to use one of my layouts (independently of the encoding):
non ASCII characters seems forbidden now for the Style name. As these
names appear in the layout and in t
Charpentier Philippe wrote:
My problem is not the encoding of the layout. It is that, since 1.2
version of lyx I used layouts I wrote and they contain definition of
styles with non ASCII characters like this:
Style Théorème ...
Style Énumère ...
Style Liste_à_puce ...
etc...
and I did it bec
a écrit :
Charpentier Philippe <[EMAIL PROTECTED]> writes:
Hi,
I had in last November a discussion on this list about the encoding of
the layouts. As I said that time I use layouts containing non ASCII
characters in the definition of the Styles and they crash lyx-1.5
(every versions until no
Charpentier Philippe <[EMAIL PROTECTED]> writes:
>
> Hi,
> I had in last November a discussion on this list about the encoding of
> the layouts. As I said that time I use layouts containing non ASCII
> characters in the definition of the Styles and they crash lyx-1.5
> (every versions until now,
Hi,
I had in last November a discussion on this list about the encoding of
the layouts. As I said that time I use layouts containing non ASCII
characters in the definition of the Styles and they crash lyx-1.5
(every versions until now, with any encoding for the layout).
In that discussion I unders
Jürgen Spitzmüller <[EMAIL PROTECTED]> writes:
>
> Jean-Pierre Chrétien wrote:
> > could layout2layout.py
> > provide it as lyx2lyx does ? Or is there any workaround ?
>
> No. You have to convert it manually, e.g. with
> iconv -f latin1 -t utf-8 foo.layout >> foo-utf8.layout
OK, as I found no i
Jean-Pierre Chrétien wrote:
> could layout2layout.py
> provide it as lyx2lyx does ? Or is there any workaround ?
No. You have to convert it manually, e.g. with
iconv -f latin1 -t utf-8 foo.layout >> foo-utf8.layout
Cf. the discussion here:
http://bugzilla.lyx.org/show_bug.cgi?id=3521
Jürgen
Hello,
I have a set of local classes and templates.
I upgraded templates with lyx2lyx successfully wrt utf encoding.
As far as classes are concerned, running layout2layout.py on
1.4 classes changes the format from 2 to 4 all right, but leaves
8859 encoding, so that I get messages like:
Error ret
35 matches
Mail list logo
