Guenter Milde wrote:
On 2009-01-05, leuven edwin wrote:
richard wrote:
The unicodesymbols file lists things like this: \"{o} and not like this: \"o
So G\"odel doesn't get translated.
isn't it possible to have multiple entries in the unicodesymbols file?
Mind, that th
On 2009-01-05, leuven edwin wrote:
> richard wrote:
>> The unicodesymbols file lists things like this: \"{o} and not like this: \"o
>> So G\"odel doesn't get translated.
> isn't it possible to have multiple entries in the unicodesymbols file?
Mind, that the primary use of the unicodesymbols file
Le 5 janv. 09 à 22:14, rgheck a écrit :
isn't it possible to have multiple entries in the unicodesymbols
file?
Yes, that would be another way to go. I'm not sure why that seemed
wrong to me, but it did.
This is a potential source of errors. Actually, since it is only a
convenience functi
leuven edwin wrote:
richard wrote:
The unicodesymbols file lists things like this: \"{o} and not like this: \"o
So G\"odel doesn't get translated.
isn't it possible to have multiple entries in the unicodesymbols file?
Yes, that would be another way to go. I'm not sure why that seem
richard wrote:
> The unicodesymbols file lists things like this: \"{o} and not like this: \"o
> So G\"odel doesn't get translated.
isn't it possible to have multiple entries in the unicodesymbols file?
Andre Poenitz wrote:
On Mon, Jan 05, 2009 at 11:16:09AM -0500, rgheck wrote:
Attached is the simpler approach, that just does what's necessary in
InsetBibtex. Lot's simpler, but of course less general.
rh
Index: src/insets/InsetBibtex.cpp
===
On Mon, Jan 05, 2009 at 11:16:09AM -0500, rgheck wrote:
> Attached is the simpler approach, that just does what's necessary in
> InsetBibtex. Lot's simpler, but of course less general.
>
> rh
>
> Index: src/insets/InsetBibtex.cpp
>
Jean-Marc Lasgouttes wrote:
rgheck writes:
This routine doesn't properly handle things like:
{\"u}ber
\"u{}ber
and the like, but only recognizes:
\"{u}ber
and similarly, of course, for many other cases. I did something to
deal with this case in the read_unicodesymbols() routine in
Jean-Marc Lasgouttes wrote:
rgheck writes:
This routine doesn't properly handle things like:
{\"u}ber
\"u{}ber
and the like, but only recognizes:
\"{u}ber
and similarly, of course, for many other cases. I did something to
deal with this case in the read_unicodesymbols() routine in
Jean-Marc Lasgouttes wrote:
rgheck writes:
This routine doesn't properly handle things like:
{\"u}ber
\"u{}ber
and the like, but only recognizes:
\"{u}ber
and similarly, of course, for many other cases. I did something to
deal with this case in the read_unicodesymbols() routine in
rgheck writes:
> This routine doesn't properly handle things like:
>{\"u}ber
>\"u{}ber
> and the like, but only recognizes:
>\"{u}ber
> and similarly, of course, for many other cases. I did something to
> deal with this case in the read_unicodesymbols() routine in
> lyx_1_6.py, so may
This routine doesn't properly handle things like:
{\"u}ber
\"u{}ber
and the like, but only recognizes:
\"{u}ber
and similarly, of course, for many other cases. I did something to deal
with this case in the read_unicodesymbols() routine in lyx_1_6.py, so
maybe something similar should b
12 matches
Mail list logo
