Hi,
In XeTeX, you can also use \XeTeXcharglyph to get the (font dependant) glyph
number for the character code.
\newcount\buffer
{%
\font\1="[./NotoSansManichaean-Regular.ttf] :script=mani"\1
\global\buffer\XeTeXcharglyph"FE00\relax
\XeTeXglyph\buffer\relax % prints the glyph
}
\number\buffer %
> Am 16.10.2022 um 21:25 schrieb Ulrike Fischer :
>
> Am Sun, 16 Oct 2022 18:47:30 +0200 schrieb Janusz S. Bień:
>
>> On Sun, Oct 16 2022 at 17:56 +02, Janusz S. Bień wrote:
>>
>> Frank Mittelbach was kind enough to provide me with the relevant information:
>>
>> On Sun, Oct 16 2022 at 9:21 -0
The documentation in the texlive installation contains a document
(xetex-reference.pdf) that describes this in detail. (locate the file or type
"texdoc xetex" if you have texlive installed.)
> Am 21.01.2016 um 03:23 schrieb Dominik Wujastyk :
>
> If you search this XeTeX forum, you'll find earl
2014-09-03 22:46 GMT+02:00 Lorna Evans :
It came from the Nikosh.ttf file. I have Microsoft Font Properties
Extension
installed and with that installed I can right click on a .ttf and
select
"Properties" and it gives me a whole range of tabs full of info
that were
not available without the e
OK, I can see that 'JFIF' in the tombe.jpg file. But it turns out
it's not in my file at all, only the 'Exif' header is there. Our
sysadmin guys haven't installed the suggested exiftool tool yet;
presumably exiftool will be capable of *adding* the JFIF header
(which I gather should come b
Turns out we've also been bit by this problem... please see my
questions below.
On 2014-08-04 01:55, Heiko Oberdiek wrote:
On 04.08.2014 01:27, Gildas Hamel wrote:
I append the jpg file (tombe.jpg).
The resolution data in tombe.jpg are inconsistent:
* JFIF header: 72 DPI
* EXIF header: 300 D
That is reasonable. I will follow your suggestion. Something like
this?
\edef\XeTeXVersionNumber{{\expandafter\@gobble\XeTeXrevision}
\ifnum\XeTeXVersionNumber<2
\else
\fi
Not sure about that snippet, but I usually use the more generic:
\ifdim\number\XeTeXversion\XeTeXrevision in<0.
Hi,
Just compiled the document under TeX Live 2013 (all updates till
the freeze) and still no dot. Besides the Apple PDF framework
(using TeXShop and Preview) I also viewed in Adobe Reader and no do
in any case shows up.
Good Luck,
Then it’s quite possible that the issue is Linux speci
Hi,
I think is is more an issue of the preview package.
Quote from the documentation of preview: „This works with DVI files
postprocessed by either Dvips and Ghostscript or dvipng, but it also
works when you are using PDFTEX for generating PDF files (usually
also postprocessed by Ghostscri
Sorry, but I cannot reproduce your problem. If I typeset your minimal
example, section numbers just show up fine in the text and the table
of contents. How did you typeset the document?
(As a remark: it's weird to use xelatex /and/ inputenc, since xetex
already handles unicode.)
best,
Stefa
Am 14.01.2014 um 18:47 schrieb >:
On Tue, 14 Jan 2014, C. Scott Ananian wrote:
On Tue, Jan 14, 2014 at 9:53 AM, wrote:
Does running tlmgr work to keep it updated?
Running apt-get keeps it updated, and in some newer distros this is
automated.
Okay. What I was really wondering was w
11 matches
Mail list logo
