Mojca Miklavec wrote:
What about \neq and \[l]dots? How can I get those working in unicode
math input?
In general, it is better not to do that, (because it is slower
and needs lots of control sequences), but if the font does not contain
what you need, you have no choice, of course.
On 10/3/07, Taco Hoekwater wrote:
Mojca Miklavec wrote:
Hello,
While trying to convert some stuff from HTML to PDF (using LuaTeX) I
have noticed some minor problems: unicode math characters work OK in
text mode (under assumption that the font has them), but not in math
mode. In
Hi Mojca,
Your email message uses the chinese simplified (GB2312) encoding,
is that intentional?
Mojca Miklavec wrote:
Hello,
While trying to convert some stuff from HTML to PDF (using LuaTeX) I
have noticed some minor problems: unicode math characters work OK in
text mode (under
Hello Taco,
On 10/3/07, Taco Hoekwater wrote:
Your email message uses the chinese simplified (GB2312) encoding,
is that intentional?
Emmm ... no. But I have no influence on encoding - there seems to be
some smart algorithm behind gmail, which tries to guess which
encoding to use. Usually it
Aditya Mahajan wrote:
Hi,
While trying to convert some stuff from HTML to PDF (using LuaTeX) I
have noticed some minor problems: unicode math characters work OK in
text mode (under assumption that the font has them), but not in math
mode. In pdfTeX they work OK in both cases. (That
Mojca Miklavec wrote:
Hello,
While trying to convert some stuff from HTML to PDF (using LuaTeX) I
have noticed some minor problems: unicode math characters work OK in
text mode (under assumption that the font has them), but not in math
mode. In pdfTeX they work OK in both cases. (That
Mojca Miklavec wrote:
\definemathsymbol[≤] [rel] [sy] [14]
\definemathsymbol[·] [bin] [sy] [01]
You need \definemathcharacter, otherwise you are setting the math
equivalent of the control sequence \≤, not the character ≤.
It still doesn't work then, but that could be some
On 10/3/07, Taco Hoekwater wrote:
Mojca Miklavec wrote:
\definemathsymbol[≤] [rel] [sy] [14]
\definemathsymbol[·] [bin] [sy] [01]
You need \definemathcharacter, otherwise you are setting the math
equivalent of the control sequence \≤, not the character ≤.
Oh, I have
Emmm ... no. But I have no influence on encoding - there seems to be
some smart algorithm behind gmail, which tries to guess which
encoding to use.
Once my aunt wrote me an e-mail (in French) using Windows-1258, which was
designed ... for Vietnamese :-)
On 10/3/07, Hans Hagen [EMAIL PROTECTED] wrote:
well, we can start thinking of virtal fonts; on the other hand, a year
from now we will have math in the tex gyre fonts so maybe it's not worth
the effort
Also Cambria/Cambria Math is obtainable, and the Stix fonts have been
a month away for half
On 10/3/07, Mojca Miklavec [EMAIL PROTECTED] wrote:
Emmm ... no. But I have no influence on encoding - there seems to be
some smart algorithm behind gmail, which tries to guess which
encoding to use. Usually it takes ascii or utf-8, but apparently it
sometimes favors other encodings for some
Hello,
While trying to convert some stuff from HTML to PDF (using LuaTeX) I
have noticed some minor problems: unicode math characters work OK in
text mode (under assumption that the font has them), but not in math
mode. In pdfTeX they work OK in both cases. (That behaviour is
expected, but not
Hi,
While trying to convert some stuff from HTML to PDF (using LuaTeX) I
have noticed some minor problems: unicode math characters work OK in
text mode (under assumption that the font has them), but not in math
mode. In pdfTeX they work OK in both cases. (That behaviour is
expected, but not
13 matches
Mail list logo
