On Tue, May 31, 2005 at 08:24:17PM +0200, Sven Schreiber wrote:
Hi, I just stumbled over what I think is a little quirk in tex2lyx. When
I convert a file that contains {\ss} latex codes, using the tex2lyx -
lyx2lyx - lyx 1.3.5 procedure from the wiki (on windows), the braces
appear as ERT in
On Tue, May 31, 2005 at 08:24:17PM +0200, Sven Schreiber wrote:
> Hi, I just stumbled over what I think is a little quirk in tex2lyx. When
> I convert a file that contains {\ss} latex codes, using the tex2lyx -
> lyx2lyx - lyx 1.3.5 procedure from the wiki (on windows), the braces
> appear as ERT
Georg Baum [EMAIL PROTECTED] writes:
Does LyX support \oe and \OE natively? If yes, we should convert \oe to the
native format (an inset?), if not we should leave it alone.
I'm not aware about native support in 1.3.5 (otherwise I would use it).
So leave it as is.
Note that tex2lyx does not
Jean-Pierre Chrétien wrote:
Georg Baum [EMAIL PROTECTED] writes:
Does LyX support \oe and \OE natively? If yes, we should convert \oe to the
native format (an inset?), if not we should leave it alone.
I'm not aware about native support in 1.3.5 (otherwise I would use it).
So leave it
Sven Schreiber wrote:
Jean-Pierre Chrétien wrote:
Georg Baum [EMAIL PROTECTED] writes:
Does LyX support \oe and \OE natively? If yes, we should convert \oe to the
native format (an inset?), if not we should leave it alone.
I'm not aware about native support in 1.3.5 (otherwise I would
Sven Schreiber [EMAIL PROTECTED] writes:
Jean-Pierre Chrtien wrote:
(No need to respond if this is a totally stupid/unrelated question, I
will get the subtle hint... but here goes:)
Aren't all western characters (iso-8...whatever) supported by lyx?
The French oe ligatures have not been
Angus Leeming wrote:
(No need to respond if this is a totally stupid/unrelated question, I
will get the subtle hint... but here goes:)
Aren't all western characters (iso-8...whatever) supported by lyx?
Does this answer your question?
Yes and no, it answered a lot, but the
Sven Schreiber wrote:
Yes and no, it answered a lot, but the misunderstanding I had was much
more basic: I simply wasn't aware that oe-lig is not officially
western (in contrast to the danish ae-lig, for example).
æ is not a ligature. It is a separate letter, just like ä is a separate
letter
Asger == Asger Alstrup [EMAIL PROTECTED] writes:
Asger Sven Schreiber wrote:
Yes and no, it answered a lot, but the misunderstanding I had was
much more basic: I simply wasn't aware that oe-lig is not
officially western (in contrast to the danish ae-lig, for
example).
Asger æ is not a
Angus Leeming wrote:
If you use some locale encoding (e.g. iso-8859 a.k.a. latin1) then you'll
be able to input characters like ß using your compose key (compose-ss) or
a dead key. The result is stored by LyX internally as a single character
(0xDF I believe) and will be shown on screen
Georg Baum wrote:
Angus Leeming wrote:
If you use some locale encoding (e.g. iso-8859 a.k.a. latin1) then you'll
be able to input characters like ß using your compose key (compose-ss) or
a dead key. The result is stored by LyX internally as a single character
(0xDF I believe) and will be
Georg Baum <[EMAIL PROTECTED]> writes:
> Does LyX support \oe and \OE natively? If yes, we should convert \oe to the
> native format (an inset?), if not we should leave it alone.
I'm not aware about native support in 1.3.5 (otherwise I would use it).
So leave it as is.
> Note that tex2lyx does
Jean-Pierre Chrétien wrote:
> Georg Baum <[EMAIL PROTECTED]> writes:
>
>
>
>>Does LyX support \oe and \OE natively? If yes, we should convert \oe to the
>>native format (an inset?), if not we should leave it alone.
>
>
> I'm not aware about native support in 1.3.5 (otherwise I would use it).
Sven Schreiber wrote:
Jean-Pierre Chrétien wrote:
Georg Baum <[EMAIL PROTECTED]> writes:
Does LyX support \oe and \OE natively? If yes, we should convert \oe to the
native format (an inset?), if not we should leave it alone.
I'm not aware about native support in 1.3.5 (otherwise I
Sven Schreiber <[EMAIL PROTECTED]> writes:
>
> Jean-Pierre Chrétien wrote:
>
> (No need to respond if this is a totally stupid/unrelated question, I
> will get the subtle hint... but here goes:)
> Aren't all western characters (iso-8...whatever) supported by lyx?
The French oe ligatures have
Angus Leeming wrote:
>>
>> (No need to respond if this is a totally stupid/unrelated question, I
>> will get the subtle hint... but here goes:)
>> Aren't all western characters (iso-8...whatever) supported by lyx?
>
> Does this answer your question?
Yes and no, it answered a lot, but the
Sven Schreiber wrote:
Yes and no, it answered a lot, but the misunderstanding I had was much
more basic: I simply wasn't aware that oe-lig is not officially
"western" (in contrast to the danish ae-lig, for example).
æ is not a ligature. It is a separate letter, just like ä is a separate
> "Asger" == Asger Alstrup <[EMAIL PROTECTED]> writes:
Asger> Sven Schreiber wrote:
>> Yes and no, it answered a lot, but the misunderstanding I had was
>> much more basic: I simply wasn't aware that oe-lig is not
>> officially "western" (in contrast to the danish ae-lig, for
>> example).
Angus Leeming wrote:
> If you use some locale encoding (e.g. iso-8859 a.k.a. latin1) then you'll
> be able to input characters like ß using your compose key (compose-ss) or
> a dead key. The result is stored by LyX internally as a single character
> (0xDF I believe) and will be shown on screen
Georg Baum wrote:
Angus Leeming wrote:
If you use some locale encoding (e.g. iso-8859 a.k.a. latin1) then you'll
be able to input characters like ß using your compose key (compose-ss) or
a dead key. The result is stored by LyX internally as a single character
(0xDF I believe) and will be
Sven Schreiber wrote:
Example: the latex input So{\ss}e should appear as Soße in the lyx file.
(Hope the German es-zett is preserved in the mail.) What appears is:
Soert{/ertßert}/erte.
Tried to workaround with So\ss{}e, which gives
Soßert{/ertert}/erte (still two different ert insets)
Georg Baum [EMAIL PROTECTED] writes:
Sven Schreiber wrote:
Example: the latex input So{\ss}e should appear as Soe in the lyx file.
(Hope the German es-zett is preserved in the mail.) What appears is:
Soert{/ertert}/erte.
Tried to workaround with So\ss{}e, which gives
Jean-Pierre Chrétien wrote:
The same happens with French ligatures OE and oe.
In lyx I have a shortcut to type in \oe{}, as c\oe{}ur,
and a round trip retrieves cert\oe/ertert{/ertert}/ertur.
Does LyX support \oe and \OE natively? If yes, we should convert \oe to the
native format (an
Sven Schreiber wrote:
> Example: the latex input So{\ss}e should appear as Soße in the lyx file.
> (Hope the German es-zett is preserved in the mail.) What appears is:
> So{ß}e.
>
> Tried to workaround with So\ss{}e, which gives
> Soß{}e (still two different ert insets)
Thanks for the report,
Georg Baum <[EMAIL PROTECTED]> writes:
>
> Sven Schreiber wrote:
>
> > Example: the latex input So{\ss}e should appear as Soße in the lyx file.
> > (Hope the German es-zett is preserved in the mail.) What appears is:
> > So{ß}e.
> >
> > Tried to workaround with So\ss{}e, which gives
> > Soß{}e
Jean-Pierre Chrétien wrote:
> The same happens with French ligatures OE and oe.
> In lyx I have a shortcut to type in \oe{}, as c\oe{}ur,
> and a round trip retrieves c\oe{}ur.
Does LyX support \oe and \OE natively? If yes, we should convert \oe to the
native format (an inset?), if not we
26 matches
Mail list logo
