Re: restrictions on accenting

1999-07-27 Thread Lars Gullik Bjønnes

Jean-Marc Lasgouttes [EMAIL PROTECTED] writes:

| I do not really know why these characters are considered as not
| valid. Maybe Lars could comment on this, since I believe he added that
| code. 

The "Allow Accents on all chars" was added for use with T1 fonts. All
accents found in T1 is enabled always, but if you want others (like
tilde-T) you have to check the box.

I am not sure if you should keep it.

Lgb



Re: restrictions on accenting

1999-07-27 Thread Lars Gullik Bjønnes

Jean-Marc Lasgouttes [EMAIL PROTECTED] writes:

| I do not really know why these characters are considered as not
| valid. Maybe Lars could comment on this, since I believe he added that
| code. 

The "Allow Accents on all chars" was added for use with T1 fonts. All
accents found in T1 is enabled always, but if you want others (like
tilde-T) you have to check the box.

I am not sure if you should keep it.

Lgb



Re: restrictions on accenting

1999-07-27 Thread Lars Gullik Bjønnes

Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:

| I do not really know why these characters are considered as not
| valid. Maybe Lars could comment on this, since I believe he added that
| code. 

The "Allow Accents on all chars" was added for use with T1 fonts. All
accents found in T1 is enabled always, but if you want others (like
tilde-T) you have to check the box.

I am not sure if you should keep it.

Lgb



Re: restrictions on accenting - solved - 2nd part

1999-07-24 Thread Sasa Janiska

On Sat, 17 Jul 1999, Greg Lee wrote:

As it was suggested earlier by Jean-Marc, by commenting the lines in
.cdef file (in my case I use Latin-2 encoding), now LyX puts proper
code for translation to LaTeX in file for the characters which are
commented in cdef file.

For example, before LyX was displaying s acute character in the .lyx
file and after commenting s acute in cdef file, now I have s acute on
the screen and inb the file there is proper code for translation to
LaTeX \i \'{s}.
Sincerely,
Sasa
 




Re: restrictions on accenting - solved - 2nd part

1999-07-24 Thread Sasa Janiska

On Sat, 17 Jul 1999, Greg Lee wrote:

As it was suggested earlier by Jean-Marc, by commenting the lines in
.cdef file (in my case I use Latin-2 encoding), now LyX puts proper
code for translation to LaTeX in file for the characters which are
commented in cdef file.

For example, before LyX was displaying s acute character in the .lyx
file and after commenting s acute in cdef file, now I have s acute on
the screen and inb the file there is proper code for translation to
LaTeX \i \'{s}.
Sincerely,
Sasa
 




Re: restrictions on accenting - solved - 2nd part

1999-07-24 Thread Sasa Janiska

On Sat, 17 Jul 1999, Greg Lee wrote:

As it was suggested earlier by Jean-Marc, by commenting the lines in
.cdef file (in my case I use Latin-2 encoding), now LyX puts proper
code for translation to LaTeX in file for the characters which are
commented in cdef file.

For example, before LyX was displaying s acute character in the .lyx
file and after commenting s acute in cdef file, now I have s acute on
the screen and inb the file there is proper code for translation to
LaTeX \i \'{s}.
Sincerely,
Sasa
 




Re: restrictions on accenting

1999-07-20 Thread Jean-Marc Lasgouttes

 "Greg" == Greg Lee [EMAIL PROTECTED] writes:

Greg On Mon, 19 Jul 1999, Jean-Marc Lasgouttes wrote:

  "Greg" == Greg Lee [EMAIL PROTECTED] writes:
 
Greg I can type and have displayed an "r" with acute accent, but not
Greg an "m" with acute accent.  I see in Reference.lyx that "m" in
Greg fact is not a valid letter to use with the accent-acute
Greg function.  But is there any good reason for this restriction?
Greg LyX is perfectly capable of drawing an acute accent over an "m"
Greg -- I can hand-edit a LyX file and put in "\i \'{m}", and then in
Greg LyX I see the accented "m".
  I do not really know why these characters are considered as not
 valid. Maybe Lars could comment on this, since I believe he added
 that code.
 
 In any case, I think you can use the only (!) toggle in
 Options-LaTeX to change this.

Greg Thank you; I didn't know about that option.  It isn't, though,
Greg exactly what I need.  (This isn't a complaint, at all, just a
Greg note about what might be useful in some future version.)  I
Greg would like to have acute- accented "r" and acute-accented "m"
Greg treated the same, as though LaTeX only knew about 7-bit
Greg encodings (even though I'm using T1-encoded fonts).  The reason
Greg is that I use the tipa package for IPA phonetic transcriptions,
Greg and tipa uses T3-encoded fonts, an encoding LyX doesn't (yet)
Greg know about.  A Latin-1 r-with-acute-accent character and a LaTeX
Greg "\'r" produce quite different results -- only the latter prints
Greg an acute-accented "r".  So, it would be useful someday, if I
Greg could get Lyx to store away "\i \'{r}" when I put an acute
Greg accent on an "r", just as now it stores away "\o \'{m}" when I
Greg put one on an "m".

You should have a look at the files iso.cdef in the lib/kbd/
directory. They allow to define a new font encoding. It should be
possible to define a simple ascii (or maybe) tipa encoding which fits
your needs.

JMarc



Re: restrictions on accenting

1999-07-20 Thread Jean-Marc Lasgouttes

 "Greg" == Greg Lee [EMAIL PROTECTED] writes:

Greg On Mon, 19 Jul 1999, Jean-Marc Lasgouttes wrote:

  "Greg" == Greg Lee [EMAIL PROTECTED] writes:
 
Greg I can type and have displayed an "r" with acute accent, but not
Greg an "m" with acute accent.  I see in Reference.lyx that "m" in
Greg fact is not a valid letter to use with the accent-acute
Greg function.  But is there any good reason for this restriction?
Greg LyX is perfectly capable of drawing an acute accent over an "m"
Greg -- I can hand-edit a LyX file and put in "\i \'{m}", and then in
Greg LyX I see the accented "m".
  I do not really know why these characters are considered as not
 valid. Maybe Lars could comment on this, since I believe he added
 that code.
 
 In any case, I think you can use the only (!) toggle in
 Options-LaTeX to change this.

Greg Thank you; I didn't know about that option.  It isn't, though,
Greg exactly what I need.  (This isn't a complaint, at all, just a
Greg note about what might be useful in some future version.)  I
Greg would like to have acute- accented "r" and acute-accented "m"
Greg treated the same, as though LaTeX only knew about 7-bit
Greg encodings (even though I'm using T1-encoded fonts).  The reason
Greg is that I use the tipa package for IPA phonetic transcriptions,
Greg and tipa uses T3-encoded fonts, an encoding LyX doesn't (yet)
Greg know about.  A Latin-1 r-with-acute-accent character and a LaTeX
Greg "\'r" produce quite different results -- only the latter prints
Greg an acute-accented "r".  So, it would be useful someday, if I
Greg could get Lyx to store away "\i \'{r}" when I put an acute
Greg accent on an "r", just as now it stores away "\o \'{m}" when I
Greg put one on an "m".

You should have a look at the files iso.cdef in the lib/kbd/
directory. They allow to define a new font encoding. It should be
possible to define a simple ascii (or maybe) tipa encoding which fits
your needs.

JMarc



Re: restrictions on accenting

1999-07-20 Thread Jean-Marc Lasgouttes

> "Greg" == Greg Lee <[EMAIL PROTECTED]> writes:

Greg> On Mon, 19 Jul 1999, Jean-Marc Lasgouttes wrote:

>> > "Greg" == Greg Lee <[EMAIL PROTECTED]> writes:
>> 
Greg> I can type and have displayed an "r" with acute accent, but not
Greg> an "m" with acute accent.  I see in Reference.lyx that "m" in
Greg> fact is not a valid letter to use with the accent-acute
Greg> function.  But is there any good reason for this restriction?
Greg> LyX is perfectly capable of drawing an acute accent over an "m"
Greg> -- I can hand-edit a LyX file and put in "\i \'{m}", and then in
Greg> LyX I see the accented "m".
>>  I do not really know why these characters are considered as not
>> valid. Maybe Lars could comment on this, since I believe he added
>> that code.
>> 
>> In any case, I think you can use the only (!) toggle in
>> Options->LaTeX to change this.

Greg> Thank you; I didn't know about that option.  It isn't, though,
Greg> exactly what I need.  (This isn't a complaint, at all, just a
Greg> note about what might be useful in some future version.)  I
Greg> would like to have acute- accented "r" and acute-accented "m"
Greg> treated the same, as though LaTeX only knew about 7-bit
Greg> encodings (even though I'm using T1-encoded fonts).  The reason
Greg> is that I use the tipa package for IPA phonetic transcriptions,
Greg> and tipa uses T3-encoded fonts, an encoding LyX doesn't (yet)
Greg> know about.  A Latin-1 r-with-acute-accent character and a LaTeX
Greg> "\'r" produce quite different results -- only the latter prints
Greg> an acute-accented "r".  So, it would be useful someday, if I
Greg> could get Lyx to store away "\i \'{r}" when I put an acute
Greg> accent on an "r", just as now it stores away "\o \'{m}" when I
Greg> put one on an "m".

You should have a look at the files iso.cdef in the lib/kbd/
directory. They allow to define a new font encoding. It should be
possible to define a simple ascii (or maybe) tipa encoding which fits
your needs.

JMarc



Re: restrictions on accenting

1999-07-19 Thread Greg Lee


On Mon, 19 Jul 1999, Jean-Marc Lasgouttes wrote:

  "Greg" == Greg Lee [EMAIL PROTECTED] writes:
 
 Greg I can type and have displayed an "r" with acute accent, but not
 Greg an "m" with acute accent.  I see in Reference.lyx that "m" in
 Greg fact is not a valid letter to use with the accent-acute
 Greg function.  But is there any good reason for this restriction?
 Greg LyX is perfectly capable of drawing an acute accent over an "m"
 Greg -- I can hand-edit a LyX file and put in "\i \'{m}", and then in
 Greg LyX I see the accented "m".
 
 I do not really know why these characters are considered as not
 valid. Maybe Lars could comment on this, since I believe he added that
 code. 
 
 In any case, I think you can use the only (!) toggle in Options-LaTeX
 to change this.

Thank you; I didn't know about that option.  It isn't, though, exactly
what I need.  (This isn't a complaint, at all, just a note about what
might be useful in some future version.)  I would like to have acute-
accented "r" and acute-accented "m" treated the same, as though LaTeX
only knew about 7-bit encodings (even though I'm using T1-encoded
fonts).  The reason is that I use the tipa package for IPA phonetic
transcriptions, and tipa uses T3-encoded fonts, an encoding LyX doesn't
(yet) know about.  A Latin-1 r-with-acute-accent character and a LaTeX
"\'r" produce quite different results -- only the latter prints an
acute-accented "r".  So, it would be useful someday, if I could get
Lyx to store away "\i \'{r}" when I put an acute accent on an "r",
just as now it stores away "\o \'{m}" when I put one on an "m".


Greg Lee [EMAIL PROTECTED]



Re: restrictions on accenting

1999-07-19 Thread Greg Lee


On Mon, 19 Jul 1999, Jean-Marc Lasgouttes wrote:

  "Greg" == Greg Lee [EMAIL PROTECTED] writes:
 
 Greg I can type and have displayed an "r" with acute accent, but not
 Greg an "m" with acute accent.  I see in Reference.lyx that "m" in
 Greg fact is not a valid letter to use with the accent-acute
 Greg function.  But is there any good reason for this restriction?
 Greg LyX is perfectly capable of drawing an acute accent over an "m"
 Greg -- I can hand-edit a LyX file and put in "\i \'{m}", and then in
 Greg LyX I see the accented "m".
 
 I do not really know why these characters are considered as not
 valid. Maybe Lars could comment on this, since I believe he added that
 code. 
 
 In any case, I think you can use the only (!) toggle in Options-LaTeX
 to change this.

Thank you; I didn't know about that option.  It isn't, though, exactly
what I need.  (This isn't a complaint, at all, just a note about what
might be useful in some future version.)  I would like to have acute-
accented "r" and acute-accented "m" treated the same, as though LaTeX
only knew about 7-bit encodings (even though I'm using T1-encoded
fonts).  The reason is that I use the tipa package for IPA phonetic
transcriptions, and tipa uses T3-encoded fonts, an encoding LyX doesn't
(yet) know about.  A Latin-1 r-with-acute-accent character and a LaTeX
"\'r" produce quite different results -- only the latter prints an
acute-accented "r".  So, it would be useful someday, if I could get
Lyx to store away "\i \'{r}" when I put an acute accent on an "r",
just as now it stores away "\o \'{m}" when I put one on an "m".


Greg Lee [EMAIL PROTECTED]



Re: restrictions on accenting

1999-07-19 Thread Greg Lee


On Mon, 19 Jul 1999, Jean-Marc Lasgouttes wrote:

> > "Greg" == Greg Lee <[EMAIL PROTECTED]> writes:
> 
> Greg> I can type and have displayed an "r" with acute accent, but not
> Greg> an "m" with acute accent.  I see in Reference.lyx that "m" in
> Greg> fact is not a valid letter to use with the accent-acute
> Greg> function.  But is there any good reason for this restriction?
> Greg> LyX is perfectly capable of drawing an acute accent over an "m"
> Greg> -- I can hand-edit a LyX file and put in "\i \'{m}", and then in
> Greg> LyX I see the accented "m".
> 
> I do not really know why these characters are considered as not
> valid. Maybe Lars could comment on this, since I believe he added that
> code. 
> 
> In any case, I think you can use the only (!) toggle in Options->LaTeX
> to change this.

Thank you; I didn't know about that option.  It isn't, though, exactly
what I need.  (This isn't a complaint, at all, just a note about what
might be useful in some future version.)  I would like to have acute-
accented "r" and acute-accented "m" treated the same, as though LaTeX
only knew about 7-bit encodings (even though I'm using T1-encoded
fonts).  The reason is that I use the tipa package for IPA phonetic
transcriptions, and tipa uses T3-encoded fonts, an encoding LyX doesn't
(yet) know about.  A Latin-1 r-with-acute-accent character and a LaTeX
"\'r" produce quite different results -- only the latter prints an
acute-accented "r".  So, it would be useful someday, if I could get
Lyx to store away "\i \'{r}" when I put an acute accent on an "r",
just as now it stores away "\o \'{m}" when I put one on an "m".


Greg Lee <[EMAIL PROTECTED]>