Hi all,
I just tested the Windows 1.5 RC1 version which is a great improvement
IMHO -- thanks to all the developers.
I have one problem so far, regarding LyX Functions. I use functions like
the following in my bind file:
\bind C-M-o command-sequence self-insert ø
This worked in LyX
Dominik Waßenhoven wrote:
\bind C-M-o command-sequence self-insert ø
This worked in LyX 1.4.3 without problems. However, this does not work
any longer, because of the non-standard letter ø. If I have, say,
command-sequence self-insert test, everything works fine. Is this a
known bug or a
Jürgen Spitzmüller wrote:
Try unicode insert 0x00f8.
Rather unicode-insert 0x00f8.
Jürgen
Jürgen Spitzmüller schrieb am 19.06.2007:
Dominik Waßenhoven wrote:
\bind C-M-o command-sequence self-insert ø
This worked in LyX 1.4.3 without problems. However, this does not work
any longer, because of the non-standard letter ø. If I have, say,
command-sequence self-insert test,
Dominik Waßenhoven wrote:
I see, it's a new feature then.
Yes. You can insert any unicode character this way, provided you know the code
point.
Jürgen
Dominik Waßenhoven wrote:
Hi all,
I just tested the Windows 1.5 RC1 version which is a great improvement
IMHO -- thanks to all the developers.
I have one problem so far, regarding LyX Functions. I use functions like
the following in my bind file:
\bind C-M-o command-sequence
Georg Baum schrieb am 19.06.2007:
It is supposed to work if you convert the bind file from latin1 to utf8 (is
this mentioned in the release notes?). All non-ASCII stuff in config files
has to be encoded in utf8.
If converting to utf8 does not help then it is a bug.
My file was in ansinew
On Tuesday 19 June 2007 05:12, Georg Baum wrote:
It is supposed to work if you convert the bind file from latin1 to utf8 (is
this mentioned in the release notes?). All non-ASCII stuff in config files
has to be encoded in utf8.
If converting to utf8 does not help then it is a bug.
Does this
Steve Litt wrote:
On Tuesday 19 June 2007 05:12, Georg Baum wrote:
It is supposed to work if you convert the bind file from latin1 to utf8
(is this mentioned in the release notes?). All non-ASCII stuff in config
files has to be encoded in utf8.
If converting to utf8 does not help then it
Hi all,
I just tested the Windows 1.5 RC1 version which is a great improvement
IMHO -- thanks to all the developers.
I have one problem so far, regarding LyX Functions. I use functions like
the following in my bind file:
\bind C-M-o command-sequence self-insert ø
This worked in LyX
Dominik Waßenhoven wrote:
\bind C-M-o command-sequence self-insert ø
This worked in LyX 1.4.3 without problems. However, this does not work
any longer, because of the non-standard letter ø. If I have, say,
command-sequence self-insert test, everything works fine. Is this a
known bug or a
Jürgen Spitzmüller wrote:
Try unicode insert 0x00f8.
Rather unicode-insert 0x00f8.
Jürgen
Jürgen Spitzmüller schrieb am 19.06.2007:
Dominik Waßenhoven wrote:
\bind C-M-o command-sequence self-insert ø
This worked in LyX 1.4.3 without problems. However, this does not work
any longer, because of the non-standard letter ø. If I have, say,
command-sequence self-insert test,
Dominik Waßenhoven wrote:
I see, it's a new feature then.
Yes. You can insert any unicode character this way, provided you know the code
point.
Jürgen
Dominik Waßenhoven wrote:
Hi all,
I just tested the Windows 1.5 RC1 version which is a great improvement
IMHO -- thanks to all the developers.
I have one problem so far, regarding LyX Functions. I use functions like
the following in my bind file:
\bind C-M-o command-sequence
Georg Baum schrieb am 19.06.2007:
It is supposed to work if you convert the bind file from latin1 to utf8 (is
this mentioned in the release notes?). All non-ASCII stuff in config files
has to be encoded in utf8.
If converting to utf8 does not help then it is a bug.
My file was in ansinew
On Tuesday 19 June 2007 05:12, Georg Baum wrote:
It is supposed to work if you convert the bind file from latin1 to utf8 (is
this mentioned in the release notes?). All non-ASCII stuff in config files
has to be encoded in utf8.
If converting to utf8 does not help then it is a bug.
Does this
Steve Litt wrote:
On Tuesday 19 June 2007 05:12, Georg Baum wrote:
It is supposed to work if you convert the bind file from latin1 to utf8
(is this mentioned in the release notes?). All non-ASCII stuff in config
files has to be encoded in utf8.
If converting to utf8 does not help then it
Hi all,
I just tested the Windows 1.5 RC1 version which is a great improvement
IMHO -- thanks to all the developers.
I have one problem so far, regarding LyX Functions. I use functions like
the following in my bind file:
\bind "C-M-o" "command-sequence self-insert ø"
This worked in LyX
Dominik Waßenhoven wrote:
> \bind "C-M-o" "command-sequence self-insert ø"
>
> This worked in LyX 1.4.3 without problems. However, this does not work
> any longer, because of the non-standard letter "ø". If I have, say,
> "command-sequence self-insert test", everything works fine. Is this a
>
Jürgen Spitzmüller wrote:
> Try "unicode insert 0x00f8".
Rather "unicode-insert 0x00f8".
Jürgen
Jürgen Spitzmüller schrieb am 19.06.2007:
Dominik Waßenhoven wrote:
\bind "C-M-o" "command-sequence self-insert ø"
This worked in LyX 1.4.3 without problems. However, this does not work
any longer, because of the non-standard letter "ø". If I have, say,
"command-sequence self-insert test",
Dominik Waßenhoven wrote:
> I see, it's a new feature then.
Yes. You can insert any unicode character this way, provided you know the code
point.
Jürgen
Dominik Waßenhoven wrote:
> Hi all,
>
> I just tested the Windows 1.5 RC1 version which is a great improvement
> IMHO -- thanks to all the developers.
>
> I have one problem so far, regarding LyX Functions. I use functions like
> the following in my bind file:
>
> \bind "C-M-o"
Georg Baum schrieb am 19.06.2007:
It is supposed to work if you convert the bind file from latin1 to utf8 (is
this mentioned in the release notes?). All non-ASCII stuff in config files
has to be encoded in utf8.
If converting to utf8 does not help then it is a bug.
My file was in ansinew
On Tuesday 19 June 2007 05:12, Georg Baum wrote:
> It is supposed to work if you convert the bind file from latin1 to utf8 (is
> this mentioned in the release notes?). All non-ASCII stuff in config files
> has to be encoded in utf8.
> If converting to utf8 does not help then it is a bug.
Does
Steve Litt wrote:
> On Tuesday 19 June 2007 05:12, Georg Baum wrote:
>
>> It is supposed to work if you convert the bind file from latin1 to utf8
>> (is this mentioned in the release notes?). All non-ASCII stuff in config
>> files has to be encoded in utf8.
>> If converting to utf8 does not help
27 matches
Mail list logo
