Op 18-3-2012 19:56, Nathan Becker schreef:
On Sat, Mar 17, 2012 at 9:31 AM, Vincent van Ravesteijn<v...@lyx.org> wrote:
Op 17-3-2012 16:06, Nathan Becker schreef:
Hi,
I am not certain if this is a bug or if I am using LyX incorrectly.
Since the behavior changed between 2.0.2 and 2.0.3 I suspect that it
may be a bug, so I'm reporting it here. Please let me know if there
is something that I'm supposed to change in my document to fix this.
I have created a simple test document in 2.0.2 and attached it under
the name test1.lyx. It contains text that renders a colored diamond
character. Lyx 2.0.2 can generate LaTeX output, which I have attached
as test1.tex.
When I open test1.lyx in 2.0.3 and try to generate LaTeX or PDF
output, I get the following error message:
Could not find LaTeX command for character '♦' (code point 0x2666)
It suggests to try using utf8 support, and I messed around with that a
bit, but I could not figure out how to fix this error message.
Thanks for your help,
Nathan
In LyX 2.0.2 we automatically loaded the 'txfonts' package when we encounter
a character which needs this package.
However, when such a package is automatically loaded, it changes the
appearance of all the math in your document. So, from now on it is no longer
automatically loaded, but this means that the character is not available.
The other suit characters should still be available (black club/spade, white
diamond/heart).
I don't know what is supposed to happen to these characters.
For more info:
- http://www.lyx.org/trac/ticket/7811
- http://www.lyx.org/trac/changeset/39894/lyxsvn
Vincent
I tried adding
\usepackage{txfonts}
to the LaTeX preamble. This did not fix the problem.
I don't think this is a LaTeX issue. The error message seems to occur
during the LyX to LaTeX conversion process. I am not seeing any LaTeX
error messages, because the PDF generation does not reach that stage.
You're right, LyX does not convert the document into LaTeX. It doesn't
because it does not know how to translate the suit symbol into LaTeX
without having to include the package txfonts. We don't want to include
this package because it seems to influence other parts of the document
as well.
Vincent
