Jonathan etc.,
I have a simple XeTeX script that produces one line of text. The line
(or the artwork, in general) has a certain bounding box. I'd like to
generate a PDF that is cropped exactly to the size of that artwork. Can
I do this directly in XeTeX? If not, is there any way to do it directly
(Plain XeTeX, not XeLaTeX).
Imagine I use a font which uses contextual alternates such as:
\font\samplefont = "Zapfino Extra LT Pro:+calt" at 72bp
\samplefont
\def \sampletext{finality}
\XeTeXuseglyphmetrics=1
\setbox1 \hbox{\sampletext \/}
So now, XeTeX has produced a box which has a serie
On 11-02-04 14:27, Jonathan Kew wrote:
> Unfortunately, I don't think there's currently any way to do that. (Well, no
> way within xetex, that is -- you could of course ship the box to the output
> file, then post-process that with a tool of some kind to determine the glyph
> ID, and then re-run
On 11-02-04 18:37, Adam Twardoch (List) wrote:
> So, ideally something like \XeTeXboxbounds would be great: work the same
> way as \XeTeXglyphbounds but for a box (taking 1, 2, 3, 4 as parameter,
> and a box).
Of course, if \XeTeXglyphmetrics=1, \XeTeXboxbounds2 (top) and
\XeTeXboxbounds
On 11-01-09 23:07, Alessandro Ceschini wrote:
> \documentclass{article}
> \usepackage{fontspec}
> \setmainfont{Minion Pro}
> \usepackage{polyglossia}
> \setmainlanguage{Serbian}
> \usepackage{xunicode}
> \usepackage{xltxtra}
>
> \begin{document}
> \fontsize{24}{24}\selectfont Уб
> \end{document}
I
Sorry, I replied prematurely. I did have to change my document to
\documentclass{article}
\usepackage{fontspec}
\usepackage{polyglossia}
\setmainlanguage{Serbian}
\usepackage{xunicode}
\usepackage{xltxtra}
\setmainfont[Script=Cyrillic,Language=Serbian]{Minion Pro}
\begin{document}
\fontsiz
On 11-02-05 22:41, Alessandro Ceschini wrote:
> Yeah, as I told you I'd taken a look in FontForge and it came out font
> designers had anticipated such combination in the kerning pairs table.
> In effect it works in PangoView but I can't figure out how to direct the
> output toward a pdf, so I can'
On 11-02-05 23:15, Alessandro Ceschini wrote:
> Sorry, I'd rather say there is too little space on top, not too much,
> the two characters are practically stuck on top, while there should
> be--FontForge and Pango show it--some additional space. Are you sure
> our outputs are the same?
Yes. Kerning
Ps. Technically speaking, in OpenType, kerning moves the right
sidebearing of the first glyph in a pair. Typically, it does so to the
left (if the kerning value is negative). In Minion Pro, the kerning
value for this pair is -181, so the right sidebearing of the У glyph is
moved by 181 font units t
On 11-02-05 23:25, Alessandro Ceschini wrote:
> OK, I got it know. Can you suggest me any workaround? This bug is very
> annoying since the combination occurs frequently.
I think you could search/replace for the combination and insert an
additional positive TeX \kern there, but I don't really know
I have identified this issue as a serious bug in XeTeX.
In MinionPro-Regular.otf (version 2.068 is the one I have, but it's
likely that it applies to all versions), the relevant kerning definition
excerpt looks like the following:
feature kern {
lookup kern1 {
pos uni0423 uni0431.ital -53
K
>
> On 7 Feb 2011, at 01:31, Adam Twardoch (List) wrote:
>
>> I have identified this issue as a serious bug in XeTeX.
>>
>> In MinionPro-Regular.otf (version 2.068 is the one I have, but it's
>> likely that it applies to all versions), the relevant kerning de
On 11-02-07 12:31, Jonathan Kew wrote:
> A couple of possible workarounds: either modify the font file to avoid the
> issue (Adam's analysis makes it clear how this could be done) -- provided
> this is compatible with your license, of course -- or use a different
> typeface that doesn't exhibit
I'd recommend checking the features in raw mode (typing from memory, please
double check the syntax):
\font\cardofont="[/Users/David/Desktop/Cardo-Regular.otf]:+liga,+dlig,+hlig" at
12pt
\cardofont
ghostly firefly acts strange
By accessing the font file directly using it's path, and specifying
The OpenType Layout mechanism is based on "glyph runs". First, the text
engine separates a line into glyph runs, and then applies features to
each run as if it were separate (i.e. there cannot be any feature
interaction between the runs).
The tricky part is that every layout engine has a different
My code is:
%!TEX TS-program = xelatex
%!TEX encoding = UTF-8
\documentclass{minimal}
\usepackage[margin=40pt, paperwidth=1024bp, paperheight=768bp]{geometry}
\usepackage{fp}
\usepackage{parskip}
\pagestyle{empty}
\newlength{\testlength}
\newlength{\testfontsize}
\newlength{\linesp}
\set
Stephan,
you can print font glyphs in XeTeX using \XeTeXglyph followed by the
glyph's decimal index.
You'd need to use a different tool to do the parsing of the OpenType
Layout tables, though. The Python package FontTools/TTX or FontForge
compiled as a Python module can be used to extract this in
> Yet, it remains one of the most
> powerful and cheapest typesetting systems to date.
"Cheap" in terms of initial investment -- surely, as it's open-source
and free.
"Cheap" in terms of implementing -- not quite so, because you need to
format your sources in a very specific, "isolated" syntax.
My Cambria is "Version 5.96", "© 2009 Microsoft Corporation. All Rights
Reserved."
A.
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Youcef is right:
AFIR, XeTeX supports three layout engines:
* ICU Layout, cross platform, working with OT Layout tables in SFNT fonts
* Graphite, cross-platform, working with Graphite tables in SFNT fonts
* ATT, Mac OS X only, working with OT Layout tables and AAT tables in SFNT
fonts.
I don't re
On 12-07-30 21:00, Zdenek Wagner wrote:
>> The question is: is it
>> easier to find a volunteer for maintaining XeTeX or a volunteer who
>> will implement missing features for luaotfload and port important
>> packages as Polyglossia to luatex?
It is definitely easier to replace the ICU Layout integ
Phil,
I cannot comment on how 100% compatible LuaTeX and XeTeX are when it
comes to the "core" set of TeX language and when only TeX-native fonts
are used. It's possible they are 100% compatible, or that they're not --
I don't know much about this.
However:
* XeTeX has several commands that were
On 12-07-30 23:40, Philip TAYLOR wrote:
> OK, thank you Adam. I think perhaps I was being unrealistic in
> asking whether the two PDFs would be visually identical; for the
> very reasons you adduce, it is clear that this can never be the
> case. But differences at the syntactic level are a far gr
On 12-07-31 11:34, Jonathan Kew wrote:
> ...of misinformation, I'm afraid.
Indeed.
Keith J. Schultz wrote:
>> Let us take ATSUI. Why has Apple abandon it? Well, I do not believe
>> there are are any native ATT-fonts in the MacOS X any more.
Most complex-script fonts (Arabic, Indic etc.) that ship
On 31.07.2012, at 13:02, Peter Dyballa wrote:
> it's questionable whether it's worth when XeTeX has reached its end of life
> cycle and LuaTeX is taking over – without micro-typography that seemed to
> have started in ConTeXt…
I don't think this is an accurate description of the situation. In
> Martin Schröder wrote:
>> And JS isn't designed for embedding
Interesting. I must admit that so far, I've *only* used JavaScript as an
embedded language -- starting with every web browser, plus most Adobe
applications, OpenOffice, as well pretty much all of Microsoft Office
applications (through
Nastaliq OpenType fonts typically use the GPOS LookupType 3 (cursive
attachment), which is not supported by some of the more simple-minded OpenType
Layout engines.
A.
Sent from my mobile phone.
On 02.08.2012, at 04:28, Mike Maxwell wrote:
> On 8/1/2012 6:48 PM, Khaled Hosny wrote:
>> I remem
specific (Arabic Typesetting uses cursive
> attachments extensively too, my Naskh font uses them occasionally as
> well). So, any sufficiently complex font will have issues with such
> engines, Nastaliq or not.
>
> Regards,
> Khaled
>
> On Thu, Aug 02, 2012 at 04:40:55AM +
Gerrit,
this is a custom functionality of the Windows API, a "poor man's" method to get
vertical typesetting in "normal" applications which cannot deal with real
vertical typesetting. The "vert" feature is different: it provides additional
90 degree rotation for those glyphs which are read bett
t works for rotating stuff like the
> colon (ten), the full stop (maru), brackets etc. A normal character would not
> have to be rotated. This is then necessary if you actually do it for rotating
> every single glyph, but not if the entire text becomes rotated and you
> basically just
On 12-12-07 09:23, Gerrit wrote:
> The problem is that many Japanese word processors rely on Japanese
> encodings, not on Unicode.
Looks like upTeX supports Unicode:
http://homepage3.nifty.com/ttk/comp/tex/uptex_en.html
A.
--
May success attend your efforts,
-- Adam Twardoch
(Remove "list." fr
On 13-01-10 16:23, Philip TAYLOR wrote:
> My Adobe Acrobat Professional is dated 2006;
> My XeTeX is dated 2011.
>
> Why does my 2011 XeTeX tell me that the PDF version
> generated by my 2006 Adobe Acrobat Professional is too recent ?
>
>> > ** WARNING ** Version of PDF file (1.6) is newer than ver
Doug,
if you think of the TFM slot indices as "glyph indices" rather than
"character codes", then possibly, you can find a 1:1 mapping of all TFM
indices to glyph IDs in the OTF. But not to Unicode codepoints. If your
method of drawing glyphs on screen allows you to address glyph IDs
directly
On 13-08-30 15:01, William Adams wrote:
Announced at the Microsoft //build conference:
A data structure, implemented as a new 'COLR' table in OpenType,
breaks down the base glyph into a separate set of glyphs, each
with its own z-order and single color reference. The color
references are handle
http://www.gust.org.pl/projects/e-foundry
Sent from my mobile phone.
> On 21.09.2014, at 08:44, Daniel Greenhoe wrote:
>
> What ever happened to the TeX Gyre font site at www.gust.org.pl ? It
> doesn't seem to be alive anymore. Anyone know what happened to them?
>
>
>
In modern text processing (Unicode+OpenType), a text run is a series of
characters with the same formatting (font, size, color etc.), directionality
(ltr, rtl) and script (writing system such as Latin, Greek, Arabic or Gujarati).
A.
Sent from my mobile phone.
> On 08.05.2015, at 11:45, David
This type of selective assumptions is guaranteed to be error-prone.
Greek is used not only in modern texts that are entirely in Greek language.
Greek text can be surrounded with various types of punctuation. In particular,
Greek words and phrases can be inserted into text written in other langu
Are these fonts TrueType-flavored OpenType (.ttf), CFF-flavored OpenType
(.otf), or some other format?
Sent from my mobile phone.
> On 01.11.2015, at 20:41, Hugo Roy wrote:
>
> Hello everyone,
>
> I have been modifying an old font from the 1990s in order to be able
> to use it with my setup,
XeTeX comes with its own PDF writer.
Adam
Sent from my mobile phone.
> On 02.11.2015, at 10:19, Hugo Roy wrote:
>
> ↪ 2015-11-02 Mon 10:11, Adam Twardoch (List) :
>> Are these fonts TrueType-flavored OpenType (.ttf), CFF-flavored OpenType
>> (.otf), or some other f
I think this is a phenomenal step. I don't think it's a specialized feature —
it actually opens up a completely different usage field for XeTeX. The past
treatment (single-word shaping) was making XeTeX difficult to deal with for
purposes eg. of automated font testing or typesetting documents th
Jonathan,
this is splendid. Adding support for the PDF "ActualText" tagging layer is a
huge step.
I wonder — what happens in case of mathematical formulae?
I think it would be rather clever to embed the TeX notation or even, huh huh,
MathML into the ActualText layer for the math mode — per
from my mobile phone.
> On 23.02.2016, at 16:00, Jonathan Kew wrote:
>
>> On 23/2/16 14:52, Adam Twardoch (List) wrote:
>> Jonathan,
>>
>> this is splendid. Adding support for the PDF "ActualText" tagging layer
>> is a huge step.
>>
>&g
42 matches
Mail list logo
