Hello. What the best way to use commands "--- and others (works in
babel with Russian language) in XeTeX with polyglossia?
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
2010/5/31, Vadim Radionov :
> Vladimir,
>
> You know, that Russian babel short-hands do slightly more than just insert a
> glyph from the font: they adjust the spacing around the em-dash (and the
> length of the dash, too), and allow hyphenation of adjacent words (in case
> of hyphens). So even in
What's the reason in two versions polyglossiya in github? And when the new
commands from babel would be ready for use?
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
After upgrade to TL 2010 these commands not work. gloss-russian.ldf
now contain code from babel.
minimal example:
\documentclass{article}
\usepackage{polyglossia}
\setmainfont{PT Sans}
\setsansfont{PT Sans Caption}
\setmonofont{DejaVu Sans Mono}
\defaultfontfeatures{Scale=MatchLowercase, Mapping
I decided to try to replace the sign "~" in my text on the analogue of
the Unicode (code 00a0), and the words that are connected in such a
space no longer hyphenated. Is this normal? Or a feature not yet
implemented?
--
Subscriptions, Archive, a
Thanks. I think that's a good idea is to add this feature in one of the
basic package of XeTeX and enable it by default.
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Hey,
I ran into a problem when installing XeTeX (v. 0.996) TeXLive 2009.
The build script works w/o problem (after temporarily changing my PATH
to include the TeX binaries) but when I try to install ($ shell
./install-xetex) I get the following error (two times):
/usr/local/texlive/2009/bin/i386-
Sorry, that was my bad! TeXLive has XeTeX already included :|. Sorry
for the hassle.
2010/8/30 Alexander Schultheiß :
> Hey,
>
> I ran into a problem when installing XeTeX (v. 0.996) TeXLive 2009.
> The build script works w/o problem (after temporarily changing my PATH
> to
Hey,
I'm new to xetex/xelatex and I have problems with diacritical marks. I
found another thread describing a similar problem but the original
question sadly isn't addressed
(http://tug.org/pipermail/xetex/2004-August/000668.html).
Does xelatex honor anchors in GPOS tables of otf/ttf fonts? If I
Hey,
I'm starting this second thread because I'm unable to figure out how
to reply to a single message within a digest :(. I turned digest mode
off by now but decided to open a second thread in order to reply to
everybody in one mail. Thanks for all the help.
@ Ross Moore
> Please show the compl
Hey David,
> This is just not true. The example I sent you works correctly on my
> machine; I deliberately included y-macron-acute which does not exist in
> precomposed form in Unicode.
I don't think they work correctly, in the sense that they are
positioned according to the anchor points. I've
Hello Khaled
> I'm not sure whether this is done by XeTeX or by xunicode, XeTeX should
> not be doing any normalisation by default, but you can try:
>
> \XeTeXinputnormalization=0
>
> and see if it makes any difference (it is supposedly the default).
No, it didn't change anything, so I guess it'
Hello Jonathan,
As for this morning I wasn't able to connect to sil.org (ping gives
Destination Host Unreachable) to download the font you suggested but I
will definitely do that today.
> I have not attempted to follow this thread closely, but I will just comment
> that xetex DOES normally use O
found the entries
that compose the mdotmacronacute. It looks like the glyph I composed
by hand and attached to one of my previous posts (test4.pdf line 3.3)
but not quite like the mdotmacronacute in lines 2.2 and 2.4-6. Is this
maybe a rendering problem? Is there an order in which all the
informati
ut at this point with other pressing matters I don't really care
as I switch to XeTeX. Thanks everyone for the time they took in order
to help me. \bye
Alex
2010/9/2 Alexander Schultheiß :
> Hello Peter,
>
>> Something odd is going on here, but I don't think it has to do with an
After changing my main font in XeTeX I've lost all niceties of TeX,
like ligatures (fi, ffi), em/en dashes, typographical quotes &c. The
font decalrations are as follows:
\font\eighteenrm="[/path/to/fonts/myfontrm.ttf
:
> Hello Alexander,
> did you try this:
> \defaultfontfeatures{Mapping=tex-text}
> ?
> Marcin Grotomirski
>
> 2010/9/9 Alexander Schultheiß :
>> After changing my main font in XeTeX I've lost all niceties of TeX,
>> like ligatures (fi, ffi), em/en dashes
Thank you Fr. Michael,
this solved the problem. For the ligatures I still had to define a
ligature lookup (which I forgot in the first place).
Alex
On Thu, Sep 9, 2010 at 3:58 PM, Fr. Michael Gilmary
wrote:
> Hi Alex:
>
>
\font\eighteenrm="[/path/to/fonts/myfontrm.ttf]:script=latn" at 18tr
Hello Fr. Michael,
On Thu, Sep 9, 2010 at 4:55 PM, Fr. Michael Gilmary
wrote:
> But can't you also add ":+liga" to the \font command? There are other
> OpenType options, I think, via the same addition (e.g., +smcp, etc.)
I think the option"+liga" is set by XeTeX per default. XeTeX will not
sear
Without knowing a great deal about all the TeX flavors, I'd like to
point out that a "one documentation for everything and everybody" is
unlikely to get finished and to work out. It will rather confuse
readers, I think. I myself have switched from LaTeX/TeX to XeTeX for
the simple reason that XeTeX
Hello Marc
> o I'd like to know how to access certain glyphs in the font
> files. For example, the euro symbol, the long es, and
> ornamental symbols.
The command you're probably looking for is \char" where is
the hexadecimal number of the glyph in the font. You don't know the
number? See b
P.S. fontforge is a font editor but it also tells you where the glyphs
you are looking for are and what their hex numbers are. You could also
try this http://en.wikipedia.org/wiki/Gucharmap, though.
2010/9/13 Alexander Schultheiß :
> Hello Marc
>
>> o I'd like to know how
> I can't speak for others, but if I need a rare character, I fire up
> BabelMap, look for the thing by name, and then insert it. Until a second
> ago, for instance, I had no idea what the unicode value for a lower case o
> with macron (ō) was (turns out it's U+014D), and I won't have to remember i
tionaries of /Link
Annotations, but not elsewhere where defective /GoTo actions are
produced. See the example below which implements a hyperlink macro with
formatted tip text (requires AR for display).
Could (x)dvipdfmx be changed to keep the original destination string?
Alexander
\documentclass[
24 matches
Mail list logo
