er, it does allow you to easily access ligatures
in fonts that don't have an OT ligature table (e.g. Times New Roman
and Georgia, which is why I made the map file in the first place).
Hope someone will find this useful.
-Andy Lin
tex-text-ms.map
Description: Binary data
tex-text-ms.tec
Des
e very interested in seeing other people's thoughts on
the matter.
Side note: Calibri has numerous default ligatures aside from the
f/ff-type. If anyone is interested in a teckit mapping for that font,
I'll upload it when I find it.
ad the ligatures at both the
standard Unicode codepoint and in the PUA, but for whatever reason,
had their ligature tables point to the PUA glyph. At least, I think
that's what was happening.
If I am mistaken, please correct me.
-Andy Lin
> I had noticed that the ligatures 'ch
I found a copy of DTLUnicoST with the following details:
File size: 53 kb, Version 1.0, Generated on 14-03-2000 by Dutch Type Library
PostScript outlines, 245 glyphs, no standard kern pairs, no embedded bitmaps
OT: kern feature only.
If this is the font you have, you can use the tex-text-ms mappin
Avi: I got the same output as you using w32tex (XeTeX 0.9997.0 with
ICU 4.4.1), the problem is that the manual shows meteg in medial
position, not to the left of the hataf patah.
It appears the problem is probably with ICU. I've attached a picture
of the sequence in Notepad, which displays it corr
If the problem is with fitting the table onto A4 paper, you could
adjust \tabcolsep, as Ross mentioned, you could also try \resizebox
and/or \rotatebox.
\resizebox{\textwidth}{!}{Your table here}
or
\rotatebox{-90}{Your table here}
or
\resizebox{\textwidth}{!}{\rotatebox{-45}{Your table here}}
Ho
Regarding \textipa{U}, you're absolutely right. I'd noticed this in
Nov 2009, along with some other glyphs that were different from tipa.
Ross actually corrected the mappings almost immediately, but I guess
this one mapping wasn't changed, though I'm surprised I haven't caught
it myself.
Thanks fo
> I'm asking this because I actually do have this fixed in my personal
> copy, and it has been since version 0.93 in November 2009, I think.
Strange, CTAN only has version 0.91. Is there some way to get a later
version? After a couple of different google searches, the only thing
I've turned up is
The OpenType Font File Properties Extension (
http://www.microsoft.com/downloads/details.aspx?FamilyID=25a5e8c5-4a5a-4619-a856-6005b1f83235&DisplayLang=en
) will allow you to view which features a font has, but there are two
key limitations:
-only works on Windows XP
-doesn't show you the specific
Theoretically, you should be able to use a string such as
Space-ZWJ- to get a combining character in
isolation. However, for Indic scripts, this can fail, because there is
not always a simple one-to-one mapping from combining character input
to final composed output.
You may be able to select the
I've actually made a teckit mapping for TIPA before. But this was just
for the A-Z, 0-9 mappings. It didn't include any of the commands
involving a backslash. What you could do is to change the definitions
of \|, etc. to different, safe/non-TIPA characters/strings (e.g. $|
for \|, and $; for \;), a
On Windows, TeXworks will auto-update, as will Sumatra. To get
pstricks to work, if pdftricks or a similar package doesn't do what
you need, then I would compile the diagrams separately into eps or pdf
files, and then embed those into your document as graphics. The only
issue with this approach is
The Kanji_Test.tex file you attached is encoded in UTF-16. I'm
surprised you got output of any kind using the file as is.
However, if you're sure the file is UTF-8 on your end, try the
following, maybe inputenc is the culprit:
\documentclass{article}
\usepackage{fontspec}
\begin{document}
\fontsp
Could it be possible you have two copies of IPAMincho in your
system/texpath right now? This has been known to result in issues such
as incorrect glyphs showing up in the output, as in your case.
--
Subscriptions, Archive, and List information, etc.
I'm using MiKTeX 2.8 on Windows 7 and the following works for me (see
attached PDF).
\documentclass{article}
\usepackage{xltxtra}
\usepackage{bidi}
\begin{document}
\fontspec{Mv Elaaf Normal}
\setRL
ޓީވީއެމް އާއި ދިވެހިރާއްޖޭގެ އަޑުގެ ނަން ބަދަލުކޮށްފިއެވެ
\end{document}
-Andy
mvtest.pdf
Descri
I thought you could simply edit dvipdfmx.cfg?
>From the file:
%% PDF Version Setting
%%
%% PDF (minor) version stamp to use in output file.
%% This also implies maximal version of PDF file allowed to be included.
%% Dvipdfmx does not support 1.0, 1.1, 1.2 since TrueType font embedded
%% as CIDFont
Someone mentioned "improved compression" in the 1.5 version and
Jonathan replying that they could set it to be the default in
dvipdfmx.cfg . I didn't even remember it until Heiko mentioned that he
wanted to avoid the compression. According to google, the thread is
titled "unexpected improvement wit
\scantokens is my fault. I noticed that the IPA support in xunicode
didn't work with the linguex package, and Ross suggested the use of
\scantokens. I haven't tried to use linguex with xunicode recently,
but to give you an idea of where it used to fail:
\documentclass{article}
\usepackage{xltxtra}
are x-height.
On Wed, Sep 22, 2010 at 19:13, Alan Munn wrote:
> On Sep 22, 2010, at 2:37 PM, Andy Lin wrote:
>
>>
>>
>> If it works with linguex, that's great. If not, and you need textipa
>> with linguex, I have a TECkit mapping I can upload that converts
>&
lshort needs to be updated, not just because it's missing sections on
Unicode and XeTeX. It's also working under the assumption that people
will *need* to use the command line in order to process a document.
This should be a concern to anyone who's looked at it recently.
And while lshort is a very
\font\1="Kepler Std" at 8pt\1 %9pt uses Regular for me
Hallo Welt!
\font\2="Kepler Std" at 12pt\2
Hallo Welt!
\font\3="Kepler Std" at 14pt\3
Hallo Welt!
\font\4="Kepler Std" at 24pt\4
Hallo Welt!
\end
This is XeTeX, Version 3.1415926-2.2-0.9995.1 (MiKTeX 2.8) (preloaded
format=xetex 2010.10.3) 3
You can take a look at the gb4e package (or its predecessor
covington). It was designed for glosses in linguistics, but the
mechanism might suit your needs. It takes up to 3 lines of input,
reads the first word (or group) of each line, puts those in a box,
then reads the next word and puts those in
For linguistics, there's also linguex, but since that doesn't support
3-line glosses by default (I think I hacked it back in for a project I
was doing), I didn't mention it. But the main feature of linguex is
that it doesn't require you to explicitly begin and end an example
environment.
-Andy
On
IIRC, gb4e and linguex both use cgloss4e.sty (from covington) as a
base for their gloss commands. They all handle line-breaking the same
way, though they have also implemented different font formatting and
line spacing commands.
-Andy
On Thu, Oct 7, 2010 at 16:49, maxwell wrote:
> On Thu, 7 Oct
Gareth is right; that is how you use BoldFont. Take a look at the
example from the fontspec manual again. It's using the HN-Regular as
the bold font because it's heavier than HN-Ultralight.
-Andy
On Sun, Oct 10, 2010 at 23:05, David Perry wrote:
>
>>
>>>
>>> 2. Can anybody see what is wrong with
I've been seeing something different altogether. In addition to
activating +calt by default, it also gives some strange output when
using stylistic sets in Gabriola. I've attached 2 images:
tl2010gabriola shows the behaviour with tl2010 (I just installed
today), miktex28gabriola shows the correct o
n ss06 and ss07, but not to the extent of tl2010).
-Andy
On Sun, Oct 17, 2010 at 19:31, Andy Lin wrote:
> I've been seeing something different altogether. In addition to
> activating +calt by default, it also gives some strange output when
> using stylistic sets in Gabriola. I'
Unless there's something specific which ExPex provides for you, I'd
recommend using gb4e or linguex instead. Those are available on CTAN
and don't have the same kind of problems.
linguex in particular has much less code involved (no need to invoke
any \begin{} or \end{}), but you may find gb4e's c
tex-text.map only provides for some punctuation marks. You can add
these lines to your tex-text.map file (or use it as a base and name it
something different, like tex-text-f.map). Semicolons are comment
characters. Below, only fi and fl ligatures are active.
You'll need to run the file through te
fonts that don't have a liga feature for the roman alphabet
but have the glyph (Most Windows fonts from before Vista/7 are like
this).
On Tue, Feb 22, 2011 at 18:07, Jonathan Kew wrote:
>
> On 22 Feb 2011, at 22:55, Andy Lin wrote:
>
>> tex-text.map only provides for some punctuati
Try this. I'm not sure which variant you're looking for. The expert
form glyph omits one of the dots on the left hand side.
\documentclass{article}
\usepackage{fontspec}
\begin{document}
\fontspec{Kozuka Mincho Pr6N}辻
\addfontfeature{RawFeature=+expt}辻
\end{document}
HTH,
Andy
On Sun, Mar 27, 2011 at 12:49, Bob Beckett wrote:
> Result: This didn't work. It produced only the base character, not the
> variant. I also tried +aalt and +salt. No go.
Access All Alternates is something that needs to be supported by the
software you're using.
Stylistic Alternates don't apply
Sorry, this should be \fontspec{Kozuka Mincho Pr6N}\varchar
On Sun, Mar 27, 2011 at 18:50, Andy Lin wrote:
> \fontspec{Kozuka Mincho Pr6N}辻
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Oh, actually, I just checked genzi.sty and it has the solution you
need. The author did in fact add support for variant glyphs (he even
mentions it on his website, though it isn't documented very well).
With genzi.sty loaded, try
\itz[0]{辻} % should be the default
\itz[1]{辻} % should be the varian
Check the output of fc-list and see if the font name matches. (On a
windows machine I do fc-list>fontlist.txt , I don't know about macs).
For example (I don't have Helvetica), if I look in fontlist.txt, I see
the following line.
Helvetica Neue LT Std,HelveticaNeueLT Std Lt Cn:style=47 Light Conden
Have you tried \usepackage[active,tightpage,xetex]{preview}?
HTH
-Andy
On Fri, Apr 29, 2011 at 13:35, R (Chandra) Chandrasekhar
wrote:
> Dear Folks,
>
> I was able to compile the minimal example file below with lualatex but
> not with xelatex:
>
> ---
> \documentclass{article}
> \usepackage{tikz
I think this topic has been discussed before, and at the time, there
was a suggestion of using the interchartoks mechanism, and so the
ucharclasses package might work for you. BUT, and I might be
remembering wrong, I think it was thought to be a bad idea to do this
with numbers.
But if you're feel
Hmm, I've played with the file a little bit. Don't know how to make it
work. From the results of tightpage, it looks like the graphic is
being produced and the size is calculated, but is not actually placed
in the document. It's probably some kind of driver incompatibility
between tikz and preview,
IIRC, the fontspec manual mentions that font transparency through font
loading commands is only available on Macs because it requires the
xdv2pdf driver.
-Andy
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo
On Thu, Jun 16, 2011 at 06:38, Gerrit wrote:
> For Japanese and Chinese the advantage is that you have a universal
> romanization,
You have to be careful with Chinese. In Mandarin, you have Pinyin, but
you also have several conflicting romanization schemes in use in
Taiwan and older literature. F
On Sat, Jun 18, 2011 at 14:09, Gerrit wrote:
> I thought of romanization which is specific to the language the surrounding
> text is written in - e.g. French or German. And this is not so much the case
> for Chinese or Japanese (except for some words: Beijing in English but
> Peking in German). In
I'd forgotten about the state of Japanese romanization. I'm just so
used to seeing some form of mangled Hepburn because people don't
bother typing macrons. But this type of fragmentation is mostly
acceptable (that is, people can still understand each other despite
the variation) and doesn't necessa
I'm kind of confused. Couldn't you use the ucharclasses package for
this? Isn't this the precise reason it was created?
-Andy
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
My guess is that it used to use the combining diacritic with the y,
and now it only looks for the precomposed character. I'm not sure how
you'd go about solving your problem though.
On Sat, Aug 13, 2011 at 12:51, John McChesney-Young wrote:
> Since as far as I've seen no one has responded to you
Superscripts: xltxtra uses real super-/subscripts by default if the
font supports it, and fakes them if the font doesn't. The reason it
used to work for Times New Roman, ironically, is because the font
didn't actually support OpenType superscripts, so it would be faked.
The reason why it doesn't wo
You can also use fontlist and pipe the output to a text file.
The first part of the line (up to the first comma) is the family name.
And the part after "style=" refers to a specific font. Combine these
two to select any font. While fontspec will load most font families
automatically if you use \set
> An easy way is to define a TECkit map. Such maps for Devanagari are
> available in xetex-devanagari package, very elaborate solution for
> Arabic scripts is in ArabXeTeX. It should be quite easy to prepare
> such a map for Hebrew.
Such a map might already exist in the TECkit package from SIL. II
You can try digging in the source for Tong Wen Tang (a Firefox
extension). Or email its developers. They should have a map and
additional notes on the conversion.
On Tue, Oct 18, 2011 at 18:50, Daniel Greenhoe wrote:
> Hi Zdenek, Thank you for your suggestions.
>
> On Tue, Oct 18, 2011 at 2:53 PM
Which tipa characters are you referring to? If you're talking about
mapping from the tipa shorthands (e.g. \textbarl), most of these are
defined in the xunicode package. It also defines the textipa command,
but it's not a complete implementation (the special macros in section
3.2.4 of the tipa manu
Sorry, I'm a little sleep deprived so there isn't much academic rigor
in this response.
This is the relevant portion of xunicode, which deals with the exact
definition of the \textipa command
\DeclareRobustCommand{\implementTIPAtext}{%
\bgroup
\let\stone\TIPAstonebar
\let\tone\TIPAtonebar
\s
I did have a map lying around for that. I'll take a look when I get home.
-Andy
On Mon, Oct 24, 2011 at 17:27, Daniel Greenhoe wrote:
> Thank you Andy and Peter for your feedback. I did try including Andy's
> suggested code in the preamble and
> {\begin{textipaeEnvironment} TA@2"DENSU \end{textip
I've attached the map and the compiled .tec file. The annotation is
quite bare-bones, but it does have the substitution that you want. For
the most part, I've stolen the definitions from xunicode.sty (which is
convenient because it has all its definitions in one place). I don't
know if there are an
It's weird Mike hasn't replied yet, but I vaguely remember him saying
that he wanted to prevent fragmentation of the package.
That being said, the terms of the license don't prohibit you from
posting code that modifies the package (going back to a question in
Bruno's original post). Nor does it pr
I've looked at the tipa code, and basically what they did was redefine
\:, etc. to produce the characters. With that in mind...
Add this to your tex document
\newcommand{\setTIPAcommands}{
\def\*\char"FE50 %Replace FE50 with your choice of unicode codepoint,
I've chosen the small punctuation set b
On Thu, Oct 27, 2011 at 04:06, Daniel Greenhoe wrote:
> What I would really like is a "drop in" solution involving a TECkit
> map only. That is, I would like to be able to hand such a map off to a
> linguist, and to tell him/her to simply add in something like this to
> his/her tex file:
> \addf
I second looking through xunicode.sty. Most of the tipa commands are
the same, although a couple were altered, as precedence was given to
the math symbols (I think). The comments in file explain why a
particular command was assign to a particular character in these
cases, and IIRC, tell you what co
BTW, I don't know if this was mentioned already, but if you're having
a problem with diacritic placement due to your fonts not having proper
anchor points, you can try using the SIL unicode fonts, which have
proper anchor points, as well as a large repertoire of pre-composed
glyphs (Charis SIL in p
I sometimes use the list at http://www.wazu.jp/gallery/Fonts_IPA.html
to look up fonts.
IIRC (and I might not), Calibri, Meiryo, and Tahoma(Windows Vista or
later) should have at least partial support of IPA characters. My
fallback font is Lucida Sans Unicode.
As for Heuristica, it's possible tha
I don't use Ubuntu, but if you have both TL2010 and 2011, I'd check
the directories that are in fontconfig (or run fc-cache -v and see
which directories it's looking in). It may be that fontspec is
complaining because it finds duplicate sets of fonts between the two
installations. Your PDFs would b
Hmm, according to that ticket on the texwork site, someone else has
the same problem, so it doesn't seem to be something unique to your
set up. I'm surprised that it's SyncTeX that's the culprit, since the
project page hasn't been updated since 2008, unless it's moved.
Unfortunately, I can't help
On Mon, Nov 7, 2011 at 08:48, Alessandro Ceschini
wrote:
> Why should fontspec try to load a crappy slanted shape in the first place?
Slanted =/= crappy. You have have optically adjusted obliques for sans
serif typefaces. You can even have slanted serif fonts. Computer
Modern had a set of them. I
If your local Eslite doesn't have such a booklet, and they can't order
one, you might want to try asking around at small print shops. They're
actually fairly substantial and are along the same lines as the
Pantone book that you found. However, if you're at a print shop
anyway, you can just ask to s
Hyphenation or linebreaking?
If the latter, try adding this to your preamble:
\XeTeXlinebreaklocale "zh"
If you're talking about romanized text, I'm not sure.
-Andy
On Sun, Dec 4, 2011 at 23:13, Matthew Overland
wrote:
> Dear all
>
> I was just wondering how to get xelatex to correctly hyphenat
Actually, he does load polyglossia. It's in the clump following xltxtra.
On Mon, Dec 5, 2011 at 02:29, Keith J. Schultz wrote:
> Hi,
> I am no expert, but
>
> 1) using XeTeX et al. you normally should not be using the fontenc
> package!
>
> 2) In the example below you are
On Wed, Dec 7, 2011 at 01:40, Keith J. Schultz
wrote:> Anyway, after that he loads babel! I am almost sure first load
font spec, polyglossia and then babel is> likely to cause some weird
side effects.
Yeah, it's really easy to miss package conflicts when using LyX. I
actually started using LaTeX t
Or... you could use context. I've never used context, but I hear good
things about it.
On Wed, Dec 7, 2011 at 22:59, Daniel Greenhoe wrote:
> 2011/12/8 Zdenek Wagner :
>> No, I do not agree. I can only agree that the LaTeX user
>> documentatioin is incomplete. ...
>> Without knowledge of the
>> m
The small caps glyphs are definitely there, but they might only be
considered part of the IPA extension range, i.e. they are not intended
as small caps for general use. Which seems weird to me. But anyhow,
this is a case where a teckit mapping could solve your problem. Or you
could file a ticket wi
I've made teckit mappings for Persian that output different levels of
vocalization (none, some, full) and romanization (1 to 1, common), all
from the same source. You don't get that kind of flexibility if you
type directly in Arabic script unless you vocalize everything to begin
with. Granted, not
You'll want to check out the other thread related to xecjk from this
month. In essence, xecjk overrides fontspec mechanisms for font
selection, so you'll need to do something like:
\setCJKfamilyfont{sungtiGBfamily}{AR PL SungtiL GB}
\newcommand{\sungtiGB}[1]{{\CJKfamily{sungtiGBfamily}#1}}
HTH
-A
I've never heard of pinyin.sty, but then again, I probably would have
made a teckit mapping without ever looking up the existence of such a
package.
There is, however, a package called xpinyin, which you might find
useful. It's not drop-in compatible with pinyin though. Are you just
starting to wr
I got bored so I made a teckit mapping anyway. (The solution we
reached off-list was to just use the US Extended keyboard already
present on Mac OSX for native unicode entry since backwards
compatibility was not a concern.)
It'll do placement according to what I understand from reading wikipedia:
Do you have to use the verbatim environment? If not, you could try the
listings or fancyvrb package. IIRC, both will let you escape parts of
the code so you can do things like changing the font and text
direction.
--
Subscriptions, Archive, and List
I'm not sure I understand the desired layout, but why not:
\newcommand{\sessoentry}[1]{\noindent\makebox[4cm][l]{\textbf{#1}}}
\newcommand{\classeentry}[1]{\textbf{#1}}
If the TITLE and WORD are meant to fit on a single line, then this should
be fine.
On Mon, Nov 19, 2012 at 1:15 PM, Lucio Crus
If you can't wait, the TECkit mapping will work regardless of your XeTeX
version.
On Tue, Jan 15, 2013 at 10:24 AM, Khaled Hosny wrote:
> On Tue, Jan 15, 2013 at 09:13:12AM -0500, Mike Maxwell wrote:
> > On 1/15/2013 12:58 AM, Khaled Hosny wrote:
> > >BTW, next XeTeX (thanks the new HarfBuzz lay
Probably a combination of fontspec and xeCJK. I haven't used xeCJK
extensively since I haven't typeset many documents requiring CJK, but the
package is still being developed, unlike zhspacing, which doesn't look like
it's been updated since 2008. I could translate the documentation for you,
but the
Hello!
There's a new font, Sitka, being released with Windows 8.1, which supports
optical sizing, but not in the standard OpenType way (that would be too
easy). Instead, they've decided to add two new fields to the OS/2 table
(see here:
http://typedrawers.com/discussion/470/new-microsoft-size-speci
76 matches
Mail list logo
