[XeTeX] Ligatures and searching in PDFs
Sorry to revive this topic, but I think I've found a solution. The original post described a problem when using the rare ligatures (e.g. "fty") in the Junicode font, in that the strings could not be found by their decomposed characters. At the time, it was suggested the /ActualText PDF feature would be useful, but no implementation was given. I'll save the details for how I stumbled onto the solution for another time, but here's the result: There are two ways about this: font encoding and text mapping. If you have any Adobe OpenType fonts, you might have noticed that the ffi and ffl ligatures can be copied from a PDF intact, but the fi and fl ligatures will show up as ??. On the other hand, if you use Latin Modern, you will not encounter any problem of the sort. This is because the font tables in LM were done properly. If your font does not have the proper tables, you can supplement them with a TECkit mapping, which are quite powerful. (I posted in Sept '09 about using them for Inuktitut syllabary-romanization conversion, and I've also used them for Persian script-transliteration conversion.) You've probably used Mapping=tex-text at some point, and the solution I'm proposing requires you to just add a couple of lines to the tex-text.map file and compile it (you may wish to make a copy and make changes to that). When you open the tex-text.map file (in \fonts\misc\xetex\fontmapping for miktex portable), you'll see mappings from individual characters to composed unicode glyphs, for example: ; ligatures from Knuth's original CMR fonts U+002D U+002D <> U+2013 ; -- -> en dash U+002D U+002D U+002D<> U+2014 ; --- -> em dash In order to make the common f/ff ligatures searchable in PDFs, add the following lines and compile the map file with teckit_compile (should be in the bin folder): U+0066 U+0066 <> U+FB00 ; ff -> ff ligature U+0066 U+0069 <> U+FB01 ; fi -> fi ligature U+0066 U+006C <> U+FB02 ; fl -> fl ligature U+0066 U+0066 U+0069<> U+FB03 ; ffi -> ffi ligature U+0066 U+0066 U+006C<> U+FB04 ; ffl -> ffl ligature I've attached such a map file and the resulting tec file for those who aren't interested in the nitty-gritty. Simply drop these into the fonts\misc\xetex\fontmapping folder and run texhash/mktexlsr. BTW, when you use this teckit mapping for ligatures, it bypasses the OpenType ligature setting, i.e. you can't turn them off unless you use a different mapping. And it won't check to see if your font has the required glyphs. However, 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 Description: Binary data -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Ligatures and searching in PDFs
> One ting I'm wondering about: not all of the fonts I use always have > all those ligatures. From what I understand from you, can't check > right now, glyphs will be replaced usgin the mapping regardless of > glyph availability, which would lead to missing glyphs in the docuemnt > if not available. This is correct. I actually ran into a different problem with Cronos Pro: the wrong glyph was at the code point (this is the case even if you use the font's own OT table!) > Would it therefore make more sense to put these mappings in a separate > file and load that mapping as well when required? Can multiple > mappings be loaded? Not at the same time for the same font, that I know of. The problem is that teckit mappings were designed to handle legacy (non-Unicode) fonts, which do not have OT tables to produce the proper glyph combinations when given complex input (such as Arabic or Indic script). Thus, when a font has its own OT tables, things don't necessarily work as one might expect. In the case that a font has OT features, these are only applied AFTER the teckit mapping is applied, so there's no way for the teckit engine to anticipate which ligatures a font may have. Nor do I know of a way for XeTeX to discern which ligatures a font may have (aside from doing a "if glyph exists at U+FB01" check for each possible ligature glyph, which wouldn't catch Junicode's rare/historical ligatures (although this might be useful for fonts with the regular repertoire of ligatures)). > Can't try this out for a while and guess I'm not the only one who > thinks of this, so just posting the question to list. This is definitely something that's been on my mind for a while as well, I would be 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. I'll make one for Junicode if someone can provide me with a list of the ligatures it has. -Andy Lin -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Ligatures and searching in PDFs
It seems I misunderstood what exactly the TECkit mapping does. All it does is change the input as instructed. All other "features" -- copy/paste and search compatibility -- I'd assumed was attributed to TECkit is actually that of the PDF reader (in my case, Adobe Reader). So, when Adobe Reader encounters the f-ligature, it knows to treat it as 'f' and another character; they have specific Unicode code points and thus any program can decompose them if they need to. However, the 'ch' and 'Th' ligatures in Linux Libertine are in the Private Use Area, which are, by definition, non-standard, so they cannot be anticipated by a PDF reader. Now, I'm assuming it's possible to make these ligatures copy/paste/search-able, just as it's possible to make small caps searchable (although Charis SIL is the only I've found that's managed it), but TECkit is not the way to do it. All TECkit does is take the input, modify it based on the mapping, and pass the result to the font/type engine without any additional information. The reason why the TECkit mapping worked for the fonts I mentioned in my previous post is because they had 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' and 'Th' are not searchable in > Linux Libertine. I added the following mappings: > U+0063 U+0068 <> U+E03B ; ch -> ch ligature > U+0054 U+0068 <> U+E049 ; Th -> Th ligature > But these do not make it possible to search or copy/paste as uncompiled. > The .tec file is compiled correctly and XeTeX finds it. Any thoughts? -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Absence of ligatures
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 mapping file
I sent a couple of days ago under the "Ligatures and searching in
PDFs" topic:
\setmainfont[Mapping=tex-text-ms]{DTLUnicoST}
or
\fontspec[Mapping=tex-text-ms]{DTLUnicoST}
The earlier post has further details and warnings.
Hope this helps,
Andy
DTLUnicoSTGlyphs.pdf
Description: Adobe PDF document
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Fontspec and SBL Hebrew: Possible Bug?
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 correctly. -Andy <> -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] XeTeX Digest, Vol 75, Issue 34
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}}
Hope this helps,
-Andy
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Bug in \textipa from xunicode.sty
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 for posting about this
-Andy
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Bug in \textipa from xunicode.sty
> 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 Khaled Hosny's fork for LuaTeX (v0.92 dated 2010/02/04). Is there something obvious I'm missing? -Andy -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Font Browser
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 glyphs (so you'd have to pick stylistic alternates by trial and error) The alternative is a little bit more involved: Download any version of kaxaml from http://www.kaxaml.com/ Open it, then copy and paste the following into the code field (the bottom one) http://schemas.microsoft.com/winfx/2006/xaml/presentation"; /> Type any text into the top field to get a preview. You can change the font, the size, and other parameters (see http://msdn.microsoft.com/en-us/library/ms745109.aspx ). The benefit of this approach is that you can enter in a text string and instantly see the output. It doesn't tell you what features a font has, but you just need to test for the ones you need, right? Hope this helps. -Andy -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] combining characters in isolation
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 glyph directly by the glyph ID in the
font. Or, you could do something like
base+combining\llap{\textcolor{white}{base}}.
Hope this helps,
Andy
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
[XeTeX] xunicode and TIPA
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 \;), and then the teckit mapping would be able to catch them. A problem you might run into is the handling of the small caps characters. Fonts like Charis SIL have the glyphs at the proper Unicode addresses (and they're actually different from the small caps you get if you use the OpenType small caps feature), but for other fonts, you may need to fake them. I think there's a way to check the presence of a glyph in a font, and from there choose the appropriate behaviour, but this will also require support from outside the teckit mapping. -Andy -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] pstricks and dvi output in xelatex
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 that you will be limited to LaTeX fonts and symbols. On the other hand, (pdf)LaTeX is a lot faster than XeLaTeX, which is a good thing if you're still fine-tuning your diagrams. Hope this helps -Andy -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Japanese Characters in PDF do not match thosein source file.
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}
\fontspec{IPAMincho}住民基本台帳ネットワーク
\end{document}
Hope this helps,
Andy
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Japanese Characters in PDF do not match thosein source file.
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.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Invalid fontname
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
Description: Adobe PDF document
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] PDF minor version
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 CIDFontType2 requires at least version 1.3. Transparent imaging %% model requires version 1.4. So if you want soft-masking support for %% PNG image with alpha channels, you should set version to 4 or higher. -Andy On Thu, Sep 16, 2010 at 12:08, Heiko Oberdiek wrote: > On Thu, Sep 16, 2010 at 05:15:34PM +0200, Peter Dyballa wrote: > >> Am 16.09.2010 um 15:44 schrieb Heiko Oberdiek: >> >> >* The only way I know is using >> > "xetex -no-pdf", followed by "xdvipdfmx -V ". >> > "xdvipdfmx --help" shows: >> >> >> This is more efficient: >> >> xetex -output-driver='xdvipdfmx -V ' >> >> The xdvipdfmx binaries in TL '09 and '10 pretest work fine... (even >> different PDF file sizes) > > Thanks. > > Yours sincerely > Heiko Oberdiek > > > -- > Subscriptions, Archive, and List information, etc.: > http://tug.org/mailman/listinfo/xetex > -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] PDF minor version
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 with XeLaTeX" and it's from Dec 26, 2009. I'm still a little shocked that there's something to do with LaTeX that Heiko doesn't know ;-) AFAIK, it should be bug-free, considering that's how all the parameters are set for dvipdfmx unless you override them using the command line. -Andy On Thu, Sep 16, 2010 at 16:48, Peter Dyballa wrote: > > Am 16.09.2010 um 22:01 schrieb Heiko Oberdiek: > >>> I thought you could simply edit dvipdfmx.cfg? >> >> If I would have known it ;-) >> I couldn't find any docu about it. > > And this route is bug-free? > > -- > Mit friedvollen Grüßen > > Pete > > We are usually convinced more easily by reasons we have found ourselves than > by those which have occurred to others. > – Blaise Pascal > > > > > -- > Subscriptions, Archive, and List information, etc.: > http://tug.org/mailman/listinfo/xetex > -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Extra trailing space in IPA font with xltxtra
\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} %or xunicode
\usepackage{linguex}
\setmainfont{Charis SIL}
\begin{document}
\ex. \textipa{DOES THIS WORK?} %would give DOES THIS WORK? instead of
the textipa replacements
\end{document}
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
uppercase and numeric input into their textipa forms.
-Andy
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Extra trailing space in IPA font with xltxtra
It's fairly basic. It just maps the capital letters, numbers, and some symbols. For \*,\;,\:, and \! I'd have to add commands to map them to an unused symbol, maybe & (so you'd get something convoluted like &*& > &, and &;B > U+0299 ; small capital B)*. If you think this should be submitted to CTAN, I can certainly do it, but it seems somewhat incomplete as is. -Andy *Charis SIL actually has two sets of small capitals. Its \textsc forms resemble the kind of small caps you get from work, but it also has a full set of IPA extension small caps which 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 >> uppercase and numeric input into their textipa forms. > > Hi Andy, it would be great if you could upload a TECkit mapping to CTAN. > Is it complete, or are there other things that would need to be added to it? > > Alan > > > -- > Alan Munn > am...@gmx.com > > > > > > > -- > Subscriptions, Archive, and List information, etc.: > http://tug.org/mailman/listinfo/xetex > xetex-textipa.map Description: Binary data xetex-textipa.tec Description: Binary data xetex-textipa-sample.tex Description: TeX document xetex-textipa-sample.pdf Description: Adobe PDF document -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] XeTeX in lshort
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 important document, I'm not convinced that
it's necessarily the right place to go into a detailed explanation
about XeTeX or Unicode. Considering the usage that lshort assumes
(math), XeTeX and Unicode introduce relatively little improvement (and
indeed, even with Unicode math support, I can see reasons why you'd
stay with LaTeX for the time being).
The attractiveness to using LaTeX to exchange documents (in the past,
and to a large extent, even now) is that you can be sure that the
source file can be read by your computer, even if you don't have the
same fonts or language support (EOL and codepage issues aside). XeTeX
introduces many stumbling blocks to this portability, even as it
solves others. Although the switch to Unicode ensures that you don't
run into codepage problems, you now have problems with individual
computer not being able to display certain scripts because the system
fonts don't support it. And although OpenType fonts provide you with
real small caps and fancy contextual alternates, you can only compile
the document on another computer if it also has the fonts you use.
These are all things which I think are outside of the scope of lshort
and concern a different audience (people who need multilingual
support, OpenType feature support, not to mention people who should
probably be using ConTeXT instead).
A short introduction to XeTeX should include discussion of editors,
because not all popular editors support Unicode. TeXworks and TeXmaker
are very good candidates for inclusion because they're easy to use and
are cross-platform. (Regarding Windows UI design, the concept of
separated parent-child windows is not at all unique to TeXworks, just
look at the various incarnations of Windows/MSN Messenger. It even
commits the crime of a program staying active even though you've
closed all windows: you can only quit it from the notification area
icon.)
I honestly think that XeTeX is LaTeX's best bet of going mainstream.
And by that, I mean, actually convert some university students from
using Microsoft Word. The new headaches it introduces into LaTeX are
nothing new in Microsoft Word, and what it gives them is a way to
interact with a document that they last saw (if ever) with WordPerfect
and its Reveal Codes feature. I've described it as HTML+CSS for
documents and strangely enough, it actually attracts some people.
I've run several LaTeX workshops for the linguistics department at my
university, and most people go straight back to Word because seeing
\emph{} makes them physically uncomfortable. The few that stay with
it, they need a little guidance and a lot of information. This is
where a document like an xshort would come in.
BTW, I don't see any benefit to telling people how to enter characters
in their documents. Chances are, if they need them, they know how to
get them. The more important thing is to re-educate those who're
entering characters *the wrong way*, e.g. using a symbol font for
Greek letters.
A few suggestions
-I would like to see mention of RTL and CJK support in the XeTeX
section, the is the main reason why I use XeTeX over (pdf)LaTeX. I'd
also change "in the past" to "in regular LaTeX" or something similar.
A current user of LaTeX is unlikely to read lshort.
-I don't think the section on old style numerals or historical
ligatures is necessary, but I would keep the Polish ligature example.
-under "How do I get OpenType fonts", I would add "OpenType fonts are
included with Windows (XP or newer), and all versions of OS X."
-I would also mention AAT fonts for OS X
The tl;dr version: I agree with the brevity of the current proposed
extension to lshort, but not some of its contents. I do like that it
links to an external resource rather than try to cover a range of
topics which readers of lshort may not be interested in.
-Andy
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] fontspec smcp bug
\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 OCT 2010 11:56 entering extended mode **keplertest.tex (D:\Personal\LaTeX\fonttest\keplertest.tex Requested font "Kepler Std" at 8.0pt -> D:/MIKTEXP/fonts/opentype/adobe/Kepler Std/KeplerStd-Capt.otf Requested font "Kepler Std" at 12.0pt -> D:/MIKTEXP/fonts/opentype/adobe/Kepler Std/KeplerStd-Regular.otf Requested font "Kepler Std" at 14.0pt -> D:/MIKTEXP/fonts/opentype/adobe/Kepler Std/KeplerStd-Subh.otf Requested font "Kepler Std" at 24.0pt -> D:/MIKTEXP/fonts/opentype/adobe/Kepler Std/KeplerStd-Disp.otf [1] ) Output written on keplertest.pdf (1 page). Works for me, I get cmr and all four optical size of Kepler Std. I'm on a Windows machine though, could it be an ICU/AAT thing? -Andy -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] parallel lines for multiple text versions
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 a box... and so on. In this way, long lines will break at the same word/group for all 3 lines. The way you could adapt it for your use is to enter the lines normally, but group each of them with curly brackets. That will prevent the package from separating it into individual words. For long lines, make two groups, starting the second group where you want the line break to occur. -Andy On Tue, Oct 5, 2010 at 22:18, Adam McCollum wrote: > Dear list members, > > I have a formatting question. What I would like to do is give line by line > three versions of a certain text (in this case, different recensions of the > Gospel of Matthew in Ge'ez, i.e. classical Ethiopic). In a WYSIWYG program, > I can of course just eyeball where the line breaks need to be and make them > manually. The process is somewhat more complicated by the fact that I'd like > to have each verse somewhat separated from other verses, and this means that > when the verse extends more than one line, the breaks still have to coincide > for each version. I'm not sure if I've done a good job explaining what I'm > hoping to do, so I attach a PDF sample written in a WYSIWYG program. > > Many thanks in advance for any help! > > Best wishes, > > Adam > > Adam McCollum, Ph.D. > Lead Cataloger, Eastern Christian Manuscripts > Hill Museum & Manuscript Library > Saint John's University > P.O. Box 7300 > Collegeville, MN 56321 > > (320) 363-2075 (phone) > (320) 363-3222 (fax) > www.hmml.org > > > > -- > Subscriptions, Archive, and List information, etc.: > http://tug.org/mailman/listinfo/xetex > > -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] parallel lines for multiple text versions
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 Wed, Oct 6, 2010 at 15:32, Alan Munn wrote: > On Oct 6, 2010, at 1:16 PM, Gareth Hughes wrote: > >> James Crippen wrote:> >>> >>> A newer and more flexible system is John Frampton’s expex. >>> >>> http://www.math.neu.edu/ling/tex/ >>> >>> It works quite well and is very well documented. It uses only TeX, but >>> works fine in a LaTeX environment. >> >> This looks nice. Is there a reason why it's not on CTAN? > > > I think it's officially still beta (although many are using it.) John will > put it up on CTAN when it's relatively unchanging in terms of actual > features and functionality. > > I would also recommend it for Adam's requirements, since it would probably > allow for easy line numbering as well. > > With respect to gb4e (actually the relevant part is cgloss4e, which is > loaded by gb4e) I would generally recommend gb4e over covington, since > covington doesn't interact nicely with various things. However, if you are > using gb4e, make sure you turn off the \automath function, which allows you > to use _ and ^ in text mode by changing their catcodes. This causes many > things to break if you don't know what you're doing, and it induces a > particularly nasty interaction with fontspec. > > Alan > > > -- > Alan Munn > am...@gmx.com > > > > > > > > -- > Subscriptions, Archive, and List information, etc.: > http://tug.org/mailman/listinfo/xetex > -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] parallel lines for multiple text versions
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 2010 14:03:57 -0500, "McCollum, Adam" > wrote: >> Many thanks for the recommendations. I've been looking at Covington and >> will also take a look at gb4e too. I actually changed Covington to allow >> more than 3 lines to be lined up, but I'm not sure how it will do with >> Ethiopic script (this is actually the first time I've done anything with >> Ethiopic in LaTeX). > > FYI, we've used the Covington macros with two Arabic script languages: > Pashto (which uses more or less the standard Naskh version of the Arabic > script) and Urdu (which uses the Nasta'liq script, much more difficult to > typeset). Since these are written right-to-left, we do the Arabic script > in a line by itself at the top of the interlinear, then repeat the > utterance in a left-to-right roman script on the next line. The roman > script line is what the gloss line is aligned off of. We've had no problem > with this. Since Ge'ez is written left-to-right, this is something you > probably don't need to deal with. But by the same token, we haven't dealt > with the case of exotic scripts in the aligned lines. > > BTW, the Covington macros deal nicely with lines that are too long to fit > on the page--both unaligned lines, and aligned lines. If I'm reading the > documentation of some of these other packages right, this is not something > they do. So with the other packages, if a line is too long to fit, you > have to manually break it. Maybe someone can confirm that I'm not > mis-reading the documentation. > > We slightly modified the covington.sty file, e.g. removing the italic font > command. Perhaps more importantly, we added a "strut" so as to add extra > vertical space between successive pairs of interlinear lines--i.e. in the > situation where the macro has split a long line. This seems to me at least > to make such interlinears easier to read. We've tested this for two-line > interlinears (that is, two aligned lines--not counting the free translation > or the Arabic script line); we've implemented this for three line > interlinears, but haven't really tested it. > > Mike Maxwell > > > > -- > Subscriptions, Archive, and List information, etc.: > http://tug.org/mailman/listinfo/xetex > -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Font nuisances
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 the following?
>>>
>>> \fontspec[BoldFont={Bergamo Std},ItalicFont={Bergamo
>>> Std},BoldItalicFont={Bergamo Std}]{Cardo}
>>
>> Yeah, you just declared the medium, upright font as bold and italic.
>> What you need is
>>
>> \fontspec[BoldFont={Bergamo Std-Bold}, ItalicFont={Bergamo Std-Italic},
>> BoldItalicFont={Bergamo St-BoldItalic}]{Cardo}
>>
> I don't think so. See example 4 in the most recent fontspec manual, from
> which I copied this:
>
> \fontspec[BoldFont={Helvetica Neue}]{Helvetica Neue UltraLight}
>
> which makes Helvetica Neue act as the "bold" for Helvetica Neue Ultralight.
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] new use of alternate glyphs and how to turn them off
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 output using MiKTeX2.8 \font\gab="Gabriola:+ss04" at 60pt %+ss04,+calt for MiKTeX \gab flying dogstarman \bye These are the version lines from each log file. This is XeTeX, Version 3.1415926-2.2-0.9997.4 (Web2C 2010) (format=xetex 2010.10.17) This is XeTeX, Version 3.1415926-2.2-0.9995.1 (MiKTeX 2.8) (preloaded format=xetex 2010.10.17) Any thoughts as to how this would happen? -Andy <><> -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] new use of alternate glyphs and how to turn them off
Just to follow up, something really weird happens when using stylistic sets 6 and 7: "dogstarman" becomes "doaaarrman". The two PDFs demonstrate the difference between MiKTeX 2.8 and tl2010. Also see http://gabriolan.ca/gabriola-font-variants/ for reference (MiKTeX stumbles on 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've attached 2 images: > tl2010gabriola shows the behaviour with tl2010 (I just installed > today), miktex28gabriola shows the correct output using MiKTeX2.8 > > \font\gab="Gabriola:+ss04" at 60pt %+ss04,+calt for MiKTeX > \gab flying dogstarman > \bye > > These are the version lines from each log file. > This is XeTeX, Version 3.1415926-2.2-0.9997.4 (Web2C 2010) > (format=xetex 2010.10.17) > This is XeTeX, Version 3.1415926-2.2-0.9995.1 (MiKTeX 2.8) (preloaded > format=xetex 2010.10.17) > > Any thoughts as to how this would happen? > > -Andy > miktex28gabtest.pdf Description: Adobe PDF document tl2010gabtest.pdf Description: Adobe PDF document -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Bug between unicode-math and expex
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 commands to be more
familiar.
-Andy
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Accessing ligatures from FontForge
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 teckitcompile.exe to generate the .tec that XeTeX uses. ;U+0066 U+0066 <> U+FB00 ; ff -> ff ligature U+0066 U+0069 <> U+FB01 ; fi -> fi ligature U+0066 U+006C <> U+FB02 ; fl -> fl ligature ;U+0066 U+0066 U+0069 <> U+FB03 ; ffi -> ffi ligature ;U+0066 U+0066 U+006C <> U+FB04 ; ffl -> ffl ligature On Tue, Feb 22, 2011 at 17:36, John Was wrote: > Hello > > Forgive the puzzlement of a new recruit to FontForge (which is installed via > Cygwin on a Windows XP machine). And apologies if this isn't the right > forum - though frequent discussion of font-related issues here gives me > hope. > > I edited a font which had just the fi and fl ligatures (in their true > Unicode positions at FB01 and FB02) and I managed to create tolerable > versions of the other three standard ligatures (ff, ffi, ffl). Using > FontForge I have added these in the slots FB00, FB03, and FB04. But > "mapping=tex-text" in the font call (in plain XeTeX) doesn't access any of > them, neither the two that were there already nor the three that I created; > however, the standard ` ' `` and '' for opening and closing quotations do > work so the mapping call is basically functioning as normal. The glyphs are > accessible to TeX if I give them manually as \char"FB00 etc. but I obviously > would like to have them delivered automatically as usual. > > I have tinkered with various FontForge menus and had hoped that adding > 'liga' to the GSUB window would be sufficient, but there is clearly > something I am not doing right. Can anyone advise? > > Many thanks > > > John > > > > -- > Subscriptions, Archive, and List information, etc.: > http://tug.org/mailman/listinfo/xetex > > -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Accessing ligatures from FontForge
I agree, it's not a good solution. I've seen it break small caps (so
\textsc{first} yields fiRST, where RST is small caps, but fi is the
lowercase ligature), and do other strange things. It is, however, a
relatively painless way to enable such ligatures in TrueType fonts or
OpenType 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 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 teckitcompile.exe to generate the
>> .tec that XeTeX uses.
>>
>> ;U+0066 U+0066 <> U+FB00 ; ff -> ff ligature
>> U+0066 U+0069 <> U+FB01 ; fi -> fi ligature
>> U+0066 U+006C <> U+FB02 ; fl -> fl ligature
>> ;U+0066 U+0066 U+0069 <> U+FB03 ; ffi -> ffi ligature
>> ;U+0066 U+0066 U+006C <> U+FB04 ; ffl -> ffl ligature
>>
>
> Although you _could_ do this, I wouldn't advise it. Much better to learn how
> to set up the ligatures you want as 'liga' substitutions in the OpenType font.
>
> JK
>
>
>> On Tue, Feb 22, 2011 at 17:36, John Was wrote:
>>> Hello
>>>
>>> Forgive the puzzlement of a new recruit to FontForge (which is installed via
>>> Cygwin on a Windows XP machine). And apologies if this isn't the right
>>> forum - though frequent discussion of font-related issues here gives me
>>> hope.
>>>
>>> I edited a font which had just the fi and fl ligatures (in their true
>>> Unicode positions at FB01 and FB02) and I managed to create tolerable
>>> versions of the other three standard ligatures (ff, ffi, ffl). Using
>>> FontForge I have added these in the slots FB00, FB03, and FB04. But
>>> "mapping=tex-text" in the font call (in plain XeTeX) doesn't access any of
>>> them, neither the two that were there already nor the three that I created;
>>> however, the standard ` ' `` and '' for opening and closing quotations do
>>> work so the mapping call is basically functioning as normal. The glyphs are
>>> accessible to TeX if I give them manually as \char"FB00 etc. but I obviously
>>> would like to have them delivered automatically as usual.
>>>
>>> I have tinkered with various FontForge menus and had hoped that adding
>>> 'liga' to the GSUB window would be sufficient, but there is clearly
>>> something I am not doing right. Can anyone advise?
>>>
>>> Many thanks
>>>
>>>
>>> John
>>>
>>>
>>>
>>> --
>>> Subscriptions, Archive, and List information, etc.:
>>> http://tug.org/mailman/listinfo/xetex
>>>
>>>
>>
>>
>>
>> --
>> Subscriptions, Archive, and List information, etc.:
>> http://tug.org/mailman/listinfo/xetex
>
>
>
>
> --
> Subscriptions, Archive, and List information, etc.:
> http://tug.org/mailman/listinfo/xetex
>
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Character Variants
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
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Character Variants
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 to CJK characters.
I'm not sure which variant you're looking for. E0100 selects the first
variant offered for that glyph by the font. In this case, the
difference is that it has a single dot on the left hand side instead
of two.
I'm not sure how to access glyphs by their variant index. However,
where multiple variants exist, you should be able to access them the
"normal" way, i.e. by selecting the character set to which the variant
belongs. Kozuka Mincho Pr6N supports the following sets: regular,
expert, hojo, jis78, jis83, jis90, nlc kanji, traditional.
The following code should allow you to test for variants of a
character and how to access them. I've attached a sample output. In
addition to the sets that KMPr6N supports, I've also included
traditional naming and simplified in case you have other fonts that
use them.
\documentclass{article}
\usepackage{fontspec}
\newcommand\varchar{辻}
\begin{document}
\fontspec{Kozuka Mincho Pr6N}辻
{\addfontfeature{RawFeature=+expt}\varchar} %Single Dot Variant
{\addfontfeature{RawFeature=+hojo}\varchar}
{\addfontfeature{RawFeature=+jp78}\varchar}
{\addfontfeature{RawFeature=+jp83}\varchar} %Single Dot Variant
{\addfontfeature{RawFeature=+jp90}\varchar} %Single Dot Variant
{\addfontfeature{RawFeature=+nlck}\varchar}
{\addfontfeature{RawFeature=+trad}\varchar}
{\addfontfeature{RawFeature=+tnam}\varchar}
{\addfontfeature{RawFeature=+simp}\varchar}
\end{document}
HTH
-Andy
KMinTest.pdf
Description: Adobe PDF document
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Character Variants
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
Re: [XeTeX] Character Variants
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 variant
You can select any variant the font offers, just change the number in
the optional argument.
There is another command \kmz, which has the same syntax, except it
selects the annotation form (if it exists in the font).
HTH
-Andy
On Mon, Mar 28, 2011 at 22:18, Bob Beckett wrote:
> I tried your method of RawFeature=+expt, but it didn't work. Finally, I
> discovered that the package genzi.sty (by Kazuomi Kuniyoshi), somehow
> interfered. After disabling genzi.sty, your code worked perfectly, producing
> the alternate glyph I wanted.
>
> Analyzing the genzi.sty code is way beyond me, so I guess I'll forgo the
> alternates until XeTeX incorporates the variant selector feature.
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] XeTeX + Helvetica Condensed Light
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 Condensed,Regular
Which means in order to use this font, I'd have to type in:
\setmainfont[Mapping=tex-text]{Helvetica Neue LT Std 47 Light Condensed}
Which is the first name given, and the style, up to the first comma.
HTH
-Andy
On Tue, Apr 12, 2011 at 20:24, André Bellaïche wrote:
> Hi !
>
> Does anybody understand why
>
> \usepackage{xunicode,fontspec}
> \setromanfont[Mapping=tex-text]{Helvetica Narrow}
>
> works while
>
> \usepackage{xunicode,fontspec}
> \setromanfont[Mapping=tex-text]{Helvetica Condensed Light}
>
> gives an error :
>
> ** ERROR ** Invalid font: -1 (0)
>
> Output file removed.
> )
> (see the transcript file for additional information)
> Error 256 (driver return code) generating output;
>
> ?
>
> The log file says:
>
> LaTeX Font Info: Try loading font information for
> OT1+HelveticaCondensedLigh
> t(0) on input line 34.
> LaTeX Font Info: No file OT1HelveticaCondensedLight(0).fd. on input line
> 34.
>
> LaTeX Font Info: Font shape `OT1/HelveticaCondensedLight(0)/m/n' undefined
> (Font) using `OT1/cmr/m/n' instead on input line 34.
>
> The Font book says I have both Helvetica Narrow and Helvetica Condensed Light
> on my Mac.
>
> I use TeXShop + pdftex.
>
> André Bellaïche
>
> P.S. Helvetica Narrow doesn't work so well. If I type 'é', I get the accent
> in white on the top-left stroke of the 'e', so I must type \'{e}instead,
> which gives a rather big accent: when typing Tél. (for Téléphone), the accent
> rises higher than the capital T.
>
>
>
>
> --
> Subscriptions, Archive, and List information, etc.:
> http://tug.org/mailman/listinfo/xetex
>
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Problem with preview, xelatex and shading in TikZ-PGF
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}
> \usepackage[active,tightpage]{preview} % Optionally comment out
> \begin{document}
> \begin{preview} % Optionally comment out
> \begin{tikzpicture}
> \shade [left color=blue, right color=green] (0,0) rectangle
> (10,10);
> \end{tikzpicture}
> \end{preview} % Optionally comment out
> \end{document}
> ---
>
> Commenting out the preview package and environment allows successful
> compilation under xelatex but the graphic is not cropped.
>
> Short of using pdfcrop, is there any workaround for this problem under
> xelatex?
>
> I have written directly to the author of the preview package and on CTT
>
> https://groups.google.com/group/comp.text.tex/browse_thread/thread/ab4125017113f167?hl=en
>
> without eliciting any replies. Any help given by this forum is greatly
> appreciated.
>
> Thank you.
>
> Chandra
>
>
> --
> Subscriptions, Archive, and List information, etc.:
> http://tug.org/mailman/listinfo/xetex
>
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Oldstyle figures in seperate file
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 feeling adventurous, you can try the below:
You can edit the ucharclasses sty file, and hijack one of the unicode
class entries (found at lines 696-877) to reflect the unicode range
you want (decimal 48-57), so let's say you have:
\newcommand{\@loadNumberForms}{\@defineUnicodeClass{\NumberFormsClass}{8528}{8591}}
You want to change this to:
\newcommand{\@loadNumberForms}{\@defineUnicodeClass{\NumberFormsClass}{48}{57}}
And then you put this in your preamble (I made up the font names):
\usepackage{fontspec}
\usepackage[NumberForms]{ucharclasses}
\setDefaultTransitions{\fontspec{Times New Roman}}{}
\setTransitionTo{NumberForms}{\fontspec{Times New Roman Expert}}
And... it should work. Or it might make xelatex very unhappy. One of the two.
Hope this helps,
Andy
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Problem with preview, xelatex and shading in TikZ-PGF
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, but I'm not sure how to tackle it. Sorry I can't give you more help than that. -Andy -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] "Options for all fonts" : colo[u]r, and the transparency byte
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/xetex
Re: [XeTeX] Polyglossia: Support for romanization of CJK
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. For Cantonese, Hokkien, etc, syllable boundaries are not quite as easy to determine because they retain non-nasal codas. -Andy -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Polyglossia: Support for romanization of CJK
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 contrast, Горбачёв is written Gorbatschow in German, > Gorbachev in English and Gorbatchev in French. If you have stuff like this, > you cannot really create hyphenation rules for only the language you want to > transcribe (e.g. Russian), but you have to create a transcription system for > every target language (German, English, French etc). But actually, I guess > that would also be possible: Create specific hyphenation patters for these > surrounding languages and then let Polyglossia automatically select the > hyphenation patter according to the environment, where the e.g. Russian text > is appearing in. Do you have examples of this outside of proper names? I haven't come across such a case and it'd be interesting to see. But wouldn't such variation defeat the purpose of romanization? I mean, consider the confusion that the Taiwanese government has caused by variously supporting Hanyu pinyin, Tongyong pinyin, and Wade-Giles (you can see all three in use on the Taipei metro system). > > But I am not sure if in literature about these countries, there is not used > a more scientific transcription, which is universal for all surrounding > languages. There's IPA, but that's only for phonetic/phonemic transcription in linguistics papers, and you wouldn't want to hyphenate it anyway. I am curious about the necessity of hyphenating romanization. Is it desirable? I would have thought that foreign words should be treated like proper nouns in running text. -Andy -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Polyglossia: Support for romanization of CJK
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 necessarily affect hyphenation. On Mon, Jun 20, 2011 at 22:46, Mike "Pomax" Kamermans wrote: > Thus, for German audiences, you would use something like "dzjanai" to make > sure that even if the meaning is unknown, the correct pronunciation is > conveyed. This refers to a situation where you want to demonstrate the pronunciation. That takes you away from romanization, the primary purpose of which is to map the script/phonemes. With pronunciation, you're venturing into very muddy waters. Consider this article discussing the pronunciation of Toronto place names: http://www.metronews.ca/toronto/local/article/811715--tarawna-where-the-streets-have-mispronounced-names . Its transcriptions are wildly inconsistent and not what you would expect to be hyphenating. Or take the example of Chinese romanization, I can't think of a language off-hand that uses q in the same way (although I remember reading about one). But people use "q" nonetheless when they talk about romanization. They don't use "ch" or "tch" or "cz", even though it might be closer in pronunciation in their language. That's not to say that a pronunciation guide or a newspaper might choose to transcribe it in such a way, but that is not romanization, that is transcription. At that point, you might as well hyphenate it using the target language's patterns because that's essentially what it's transformed into. My original thought was that if romanization is dependent on the target language and not the source language, then it becomes useless for people who only know the source language and not the target language. Romanization is supposed to provide scholars access to a language which they would otherwise be unable to describe due to a writing system that they can't use. It doesn't make sense to then restrict the scholarship to a particular target language through the use of a unique romanization system. Or, to use an analogy, if I'm going to rip a CD for my friends, I'm going to rip it to mp3, not to ogg, because I'm the only person who knows what an ogg file is. If my ultimate goal is to ensure broad dissemination and adoption, I'm not going to base my decision on my preferences but on what's most accepted. I don't disagree that variation exists in the wild. But conceptually, there's something wrong about different hyphenation patterns for romanization based on surrounding text. -Andy -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] epsdice package.
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
Re: [XeTeX] Trouble with the new 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 your question (and I > have no idea of an answer myself), I thought I'd ask whether there's > some feature of Palatino Linotype that makes it so appealing you don't > want to switch to a font that includes the character? There are a lot > of them out there, including Charis SIL, Gentium (and GentiumPlus), > Linux Libertine, Junicode, DejaVu, Old Standard, and Theano, just to > mention a few I recognize as free fonts I've downloaded, besides > whatever system fonts you might already have that include it. I'm > using GentiumPlus in my edition of Hyginus' _Fabulae_ in part because > of its inclusion of the macron-y. > > John > > On Wed, Aug 10, 2011 at 2:07 PM, Andrew Gollan > wrote in part: >> I am using the Palatino Linotype font which does not have a native ȳ glyph. >> >> I had been entering my ȳ letters as \=y which was working fine until I >> upgraded to TeXLive2011 (from 2009/2010 depending on machine). Now I get the >> error message... > -- > John McChesney-Young ** Berkeley, California, U.S.A. > JMcCYoung~at~gmail.com ** http://twitter.com/jmccyoung ** > http://jmccyoung.blogspot.com/ > > > > -- > Subscriptions, Archive, and List information, etc.: > http://tug.org/mailman/listinfo/xetex > -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Superscript and Small Caps problem
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 work for Linux Libertine is because it does
support OpenType superscripts, so the feature is enabled, but the font
doesn't actually contain superscript glyphs for 'lú'. To fix this:
Change
\newcommand{\dtm}[1]{{\textsuperscript{\sffamily#1}}}
to
\newcommand{\dtm}[1]{{\rmfamily\fakesuperscript{#1}}} %\sffamily was a
typo, right? I've reversed the order out of personal preference; it's
less likely to break this way.
Small caps: Charis SIL is one of the rare fonts that has a small
capital version of the h breve. I forget if there's any official
support for fake small caps like with LaTeX, but you can fake the
small caps version by using the capital version by using the following
code (adjust the parameters FakeStretch, FakeBold, and Scale for
appearance).
Add
\newcommand{\fakesc}[1]{{\addfontfeatures{FakeStretch=1.1,FakeBold=1.1,Scale=0.8}\MakeUppercase{#1}}}
Change
\newcommand{\smn}[1]{{\sffamily\scshape#1}}
to
\newcommand{\smn}[1]{{\sffamily\fakesc{#1}}}
The downside to using either of these codes is that it will always
fake the superscript/small caps, even if the font has the proper
glyph. I'm sure someone can hack together a fix that will swap the
definitions(between fake and real) based on the Unicode range, but I'm
not quite there.
HTH,
Andy
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] IPA characters
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 \setmainfont or \newfontfamily, you'll need
to manually define families that use numbers as part of their name
(Helvetica Neue, Frutiger, Univers), e.g.:
Helvetica Neue LT Std,HelveticaNeueLT Std Extended:style=73 Bold
Extended Oblique,Bold Italic
In order to use this font you'll need to enter:
\fontspec{Helvetica Neue LT Std 73 Bold Extended Oblique}
As for STIX, if you're getting STIX through its tex package, it should
accessible as "STIXGeneral" as Tobias mentioned, or "STIXGeneral
Regular".
You might also consider Heuristica, which is based on Utopia but
includes additional characters for language support and IPA.
http://code.google.com/p/evristika/
BTW, you can use many tipa shorthands by loading the xunicode package.
-Andy
On Mon, Oct 17, 2011 at 04:44, Joachim Trinkwitz wrote:
> Am 16.10.2011 um 20:33 schrieb Hendrik Maryns:
>
>> I installed stix fonts, but how do I call it in fontspec?
>
> Try 'otfinfo -i' on the font file, best bet is the "PostScript name".
>
> Joachim
>
> --
> Dr. Joachim Trinkwitz E-Mail: j...@uni-bonn.de
> Institut für Germanistik, Tel.: 0228-737565
> Vergleichende Literatur- www.germanistik.uni-bonn.de
> und Kulturwissenschaft www.comicforschung.uni-bonn.de
> der Universität Bonn 53012 Bonn
>
>
>
>
>
>
> --
> Subscriptions, Archive, and List information, etc.:
> http://tug.org/mailman/listinfo/xetex
>
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] ascii to unicode map for Hebrew
> 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. IIRC, they have mapping for all of their legacy (non-Unicode) fonts. -Andy -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] traditional to simplified Chinese character conversion utility or data base
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, Zdenek Wagner > wrote: >> you can just use tr, ... if you supply the map. > > I don't know what "tr" is, but this comes back to one of my original > problems; and that is, I don't have a map. Does anyone know of a > publicly available map? Such a map very likely exists. For example, > Google Translate can translate from traditional to simplified. But > even if they use a map for this service, that map may be proprietary. > >> If you wish to do it on the fly in XeTeX, you can write a TECkit map. >> Having the TECkit map you can also run txtconv from the command line. > > I like these solutions. However, again, I would still need a map. SIL > has a collection of maps available here: > http://scripts.sil.org/cms/scripts/page.php?site_id=nrsi&cat_id=ConversionMaps > But I didn't see a Chinese traditional-->simplified character map. > > Dan > > > > > On Tue, Oct 18, 2011 at 2:53 PM, Zdenek Wagner > wrote: >> 2011/10/17 Daniel Greenhoe : >>> I know that this is not really the right mailing list for this >>> question, but I have so far not found the answer by any other means >>> ... >>> >>> I would like to find or write some a utility that would take an >>> unicode encoded file and map Chinese traditional characters to >>> simplified, while leaving all other code points (such as those in the >>> Latin and IPA code spaces) untouched. For example, the traditional >>> character for horse (馬) is at unicode U+99AC, the simplified one (马) >>> is at unicode U+9A6C, and the Latin character for "A" is at U+0041. So >>> I want a utility that would change the 99AC to 9A6C, but leave the >>> 0041 unchanged. >>> >> If it is really that simple 1:1 mapping, you can just use tr, it does >> exactly that if you supply the map. If you wish to do it on the fly in >> XeTeX, you can write a TECkit map. Having the TECkit map you can also >> run txtconv from the command line. >> >>> Does anyone know of such a utility? Does anyone know of any data base >>> with a traditional to simplified character mapping such that I could >>> maybe write the utility myself? >>> >>> Many thanks in advance, >>> Dan >>> >>> >>> >>> -- >>> Subscriptions, Archive, and List information, etc.: >>> http://tug.org/mailman/listinfo/xetex >>> >> >> >> >> -- >> Zdeněk Wagner >> http://hroch486.icpf.cas.cz/wagner/ >> http://icebearsoft.euweb.cz >> >> >> >> -- >> Subscriptions, Archive, and List information, etc.: >> http://tug.org/mailman/listinfo/xetex >> > > > > -- > Subscriptions, Archive, and List information, etc.: > http://tug.org/mailman/listinfo/xetex > -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] TECkit map for Latin alphabet to Unicode IPA
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 manual are not defined, among others). -Andy On Sun, Oct 23, 2011 at 09:12, Daniel Greenhoe wrote: > Is there already a TECkit map available to map the Latin alphabet > (abc...) to Unicode IPA code points, > where the Latin symbols are defined by tipa 1.3 > (http://www.ctan.org/pkg/tipa) and > where the Unicode IPA code points are as defined by the Unicode > standard (http://unicode.org/charts/PDF/U0250.pdf)? > > Many thanks in advance, > Dan > > > -- > Subscriptions, Archive, and List information, etc.: > http://tug.org/mailman/listinfo/xetex > -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] TECkit map for Latin alphabet to Unicode IPA
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
\setTIPAcatcodes\activatetipa
\csname useTIPAfont\endcsname
\implementTIPAtextx
}
\def\implementTIPAtextx#1{#1\egroup}
\def\implementTIPAtextxx#1{\endlinechar=-1 \scantokens{#1}\egroup}
\AtBeginDocument{\let\textipa\implementTIPAtext}
\expandafter\ifx\csname scantokens\endcsname\relax
\else
\AtBeginDocument{\@ifpackageloaded{linguex}{%
\let\implementTIPAtextx\implementTIPAtextxx}}
\fi
Theoretically, you could add the following lines to your document to
add the textipaEnvironment. But I haven't tested it. And it's longer
than it needs to be.
\expandafter\ifx\csname scantokens\endcsname%
\newenvironment{textipaEnvironment}%
{\bgroup
\let\stone\TIPAstonebar
\let\tone\TIPAtonebar
\setTIPAcatcodes\activatetipa
\csname useTIPAfont\endcsname}%
{\egroup}
\else
\AtBeginDocument{\@ifpackageloaded{linguex}{%
\newenvironment{textipaEnvironment}%
{\bgroup
\let\stone\TIPAstonebar
\let\tone\TIPAtonebar
\setTIPAcatcodes\activatetipa
\csname useTIPAfont\endcsname
\endlinechar=-1 \scantokens}%
{\egroup}}}
\fi
Hope this helps,
Andy
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] TECkit map for Latin alphabet to Unicode IPA
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{textipaeEnvironment}} in
> the document.
> But I was told that textipaEnvironment is undefined. With an error
> message like that, it is quite possible that I did something wrong.
>
> But I think at this point, I would like to pursue the TECkit map
> solution. At least in my mind (and maybe in my mind only) it could
> lead to a possibly more "elegant" solution...and it would probably be
> easier for me to maintain (since in part I am not really a Tex
> programmer).
>
> Thank you again,
> Dan
>
> On Mon, Oct 24, 2011 at 5:23 PM, Peter Dyballa wrote:
>>
>> Am 24.10.2011 um 00:57 schrieb Daniel Greenhoe:
>>
>>> I am talking about these for example ...
>>> T ==> theta ('124)
>>> A ==> script A ('101)
>>> @ ==> schwa ('100)
>>> 2 ==> turned V ('062)
>>> D ==> Eth ('104)
>>> E ==> epsilon ('105)
>>> N ==> right-tail n ('357)
>>> S ==> Esh ('123)
>>> U ==> upsilon ('125)
>>> " ==> vertical stroke superior ('042)
>>
>> Something like this mapping can be achieved. Normal text could be set with
>> an "unmodified" version of GNU Freefont, while you could create \textipa{}
>> as using the same font with the ASCII2tipa mapping. So your document would
>> use kind of two fonts. A "textipaEnvironment" seems not useful. When inside
>> it only IPA characters would be used you could switch to the mapped font,
>> when normal and mapped characters are used there is no means to distinguish
>> between them, so you would need to use \textipa{}.
>>
>> --
>> Greetings
>>
>> Pete
>>
>> Well begun is half done.
>> – Optimist.
>> Half done is well begun.
>> – Realist.
>> Half begun is well done.
>> – Australian.
>>
>>
>>
>>
>>
>> --
>> Subscriptions, Archive, and List information, etc.:
>> http://tug.org/mailman/listinfo/xetex
>>
>
>
>
> --
> Subscriptions, Archive, and List information, etc.:
> http://tug.org/mailman/listinfo/xetex
>
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] TECkit map for Latin alphabet to Unicode IPA
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 any errors in the mapping, the timestamp on this
says it's from November 2009.
In any case, you'd use it like this:
%These two lines are for xunicode, if you use it instead
%\newfontface\doulos{Doulos SIL}
%\def\useTIPAfont{\doulos}
\newfontface\tipafont[Mapping=xetex-textipa]{Doulos SIL}
So in your tabular example
\begin{tabular}{r>{\tipafont}l}
1. & TA@2"DENSU \\
2. & TA@2"DENSU
\end{tabular}
It's not an environment though, just a font switch.
Hope this helps,
-Andy
xetex-textipa.map
Description: Binary data
xetex-textipa.tec
Description: Binary data
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Performance of ucharclasses
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 prohibit a wrapper package. -Andy -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] TECkit map for Latin alphabet to Unicode IPA
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 because I haven't encountered
them in the wild and I can't imagine someone entering these in by hand
(as opposed to using a font's OpenType small caps feature).
\def\;\char"FE51 %Ditto
%etc...
}
Change your mapping definitions like the following
U+FE51 latin_small_letter_t > latin_small_letter_t_with_retroflex_hook
(I've used the unicode here, but you can redefine it, maybe semicolon_operator?)
(Also, I've changed the bidirectional assignment to one-way... I seem
to recall the bidirectional assignment was for things like ligatures
in connected scripts, or contextual reassignments, where you're trying
to assign a semantic equivalency between the two sides. Which is not
what we're trying to hack here. Is it an important distinction? Not
that I've seen. But then again, I have never tried searching for a
retroflex t in Acrobat, so I couldn't tell you.)
NB: The tipa manual mentions that these commands are not 100% safe.
Keep that in mind if your code begins breaking in magical ways.
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] TECkit map for Latin alphabet to Unicode IPA
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:
> \addfontfeatures{Mapping=tipa2uni}.
> And that's it --- just one support file: a TECkit map file.
This is actually the reason I abandoned developing the map file
further. I had started based on the textipa replacements that I knew,
and then I discovered all the additional commands and realized that
they could not be implemented by TECkit along (don't get me wrong,
TECkit maps are very powerful, I've written one to convert
arabtex-like romanization into Persian). After tipa support was added
to xunicode, I just used that instead.
If this "single line" solution is important to you, you could write a
wrapper package that calls xunicode, adding whichever redefinitions
you need.
-Andy
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] TECkit map for Latin alphabet to Unicode IPA
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 command has been assigned to an alternate character. Once you find the commands you want, you can use TexMaker and create a palette of characters that you use most often. Or you can create a custom keyboard layout with dead keys to input the characters (we distributed one such keyboard for a project once, aside from Windows throwing a security dialogue, we didn't have much trouble with it). -Andy -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] TECkit map for Latin alphabet to Unicode IPA
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 particular). Anyhow, these are the fonts I use most often if I have uncommon diacritics in my document: Charis SIL (derived from Charter) Doulos SIL (matches Times New Roman) Heuristica (derived from Utopia) A lot of OpenType fonts with a "Pro" suffix will also have decent diacritic support, but it really varies from font to font. You might also want to look up \XeTeXinputnormalization on this mailing list. There was a discussion a while back about how it affects diacritic placement (although I think it had more to do with Indic languages rather than IPA). -Andy -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] TECkit map for Latin alphabet to Unicode IPA
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 that the characters aren't incorporated into the built files (it's still a work in progress). You can file a ticket with the developers at their google code site. -Andy -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Wacky behavior of XeLaTeX in TeXLive 2011
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 be OK because the font files are otherwise identical, but you'll likely notice problems if you had different versions of the same font. As for the other problem with SyncTeX... I can only imagine it's somehow related. Possibly a PATH error? HTH, Andy -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Wacky behavior of XeLaTeX in TeXLive 2011
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 you further with this, as I don't have an Ubuntu box to test on. Hopefully someone else will come up with a solution. -Andy -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Wacky behavior of XeLaTeX in TeXLive 2011
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. It ultimately comes down to using them properly. But to actually answer your question, fontspec tries to load it because the command exists. It's designed to provide a working font setup, which means populating all the font commands. -Andy -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] cmyk encoded files
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 see their sample book, which should show the stocks and inks and treatments that they have available. Colour printing in Asia is significantly cheaper than elsewhere in the world. You may find it easier to just request a proof before you commit to a larger order. Or, failing that, compile a swatch card composed of all the colours that are in your document and ask them to print that. Between process (cmyk) or Pantone, just remember that Pantone colours are much more expensive, but they do offer a wide range of possible colours. HTH, Andy -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Chinese hyphenation
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 hyphenate Chinese > text. At the moment it will only ever hyphenate where there is a space or > some punctuation. It treats any continuous block of characters as a single > word that cannot be broken up. > > Is there a package I can use, or do I have to specify the hyphenation > manually? > > Thanks a lot > > Matthew > > > > -- > Subscriptions, Archive, and List information, etc.: > http://tug.org/mailman/listinfo/xetex > -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] (Xe)TeX Live after update: Upright font found, but not italic - Huh?
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 using \usepackage with \makeatletter
> I assume this will cause problems.
>
> 3) I would use polyglossia instead of babel, yet for german it is not
> a must.
>
> Am 04.12.2011 um 14:46 schrieb Wolfgang Keller:
>
>> Hello,
>>
>> since last week, some update seems to have wrecked something in my TeX
>> Live installation. The example document (fo testing, you need the
>> Libertine typeface) below:
>>
>> %% LyX 2.0.2 created this file. For more info, see http://www.lyx.org/.
>> %% Do not edit unless you really know what you are doing.
>> \documentclass[10pt,ngerman]{scrartcl}
>> \usepackage[T1]{fontenc}
> [1] remove above line
>
>> \usepackage{geometry}
>> \geometry{verbose,tmargin=3cm,lmargin=5.5cm}
>> \usepackage{fancyhdr}
>> \pagestyle{fancy}
>> \setlength{\parskip}{0pt}
>> \setlength{\parindent}{0pt}
>>
>> \makeatletter
>> %% User specified LaTeX commands.
>> \usepackage{fontspec}
> [2] did you forget \makeatother before the above line?
> I believe, also, that font spec should be loaded after babel!!
>
>> \usepackage{xltxtra}
>> \setmainfont[Mapping=tex-text, ExternalLocation,
>> UprightFont=LinLibertine_R.otf, BoldFont=LinLibertine_RB.otf,
>> ItalicFont=LinLibertine_RI.otf, BoldItalicFont=LinLibertine_RBI.otf,
>> Numbers={Proportional,OldStyle}]{Libertine} \setsansfont
>> [Mapping=tex-text, ExternalLocation, UprightFont=LinBiolinum_R.otf,
>> BoldFont=LinBiolinum_RB.otf, ItalicFont=LinBiolinum_RI.otf,
>> BoldItalicFont=LinBiolinum_RI.otf, Numbers={Proportional,OldStyle},
>> Scale=MatchLowercase]{Biolinum} \usepackage{textcase} \usepackage
>> {scrpage} \renewcommand{\headrulewidth}{0pt} \usepackage{xkeyval}
>> \usepackage{polyglossia} \usepackage{marginnote} \reversemarginpar
>> \renewcommand*{\marginfont}{\rmfamily\itshape} \setlength
>> {\marginparwidth}{1.67\marginparwidth}
>>
>> \AtBeginDocument{
>> \def\labelitemi{\Libertine{\namedglyph{bullet}}}
>> \def\labelitemii{\(\circ\)}
>> \def\labelitemiii{\(\diamond\)}
>> }
>>
>> \makeatother
>>
>> \usepackage{babel}
> [3] I would use polyglossia
>
>
>> \usepackage{xunicode}
>> \begin{document}
>> \marginpar{Randnotiz}Text
>> \end{document}
>>
>> generates this warning:
>>
>> LaTeX Warning: Marginpar on page 1 moved.
>>
>>
>> LaTeX Font Warning: Font shape `EU1/Libertine(0)/m/sl' undefined
>> (Font) using `EU1/Libertine(0)/m/n' instead on input line
>> 41.
>>
>> [1
>>
>> ] (./Test202.aux)
>>
>> LaTeX Font Warning: Some font shapes were not available, defaults
>> substituted.
>>
>> and the attached PDF output. The marginnote text should be
>> vertically aligned with the body text and in italic.
>>
>> Could anyone give me a hint what might be broken?
>>
>> TIA,
>>
>> Sincerely,
>
>
>
> --
> Subscriptions, Archive, and List information, etc.:
> http://tug.org/mailman/listinfo/xetex
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] (Xe)TeX Live after update: Upright font found, but not italic - Huh?
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 through LyX (and this was years ago, before I'd even heard of XeTeX), and because it didn't support the packages I was using, almost everything I did was in ERT (evil red text). So I ended up just editing the tex files by hand. Which was fine, until someone else edited it using LyX and added other packages... I forget what xltxtra loads, but I think it loads fontspec, xunicode at least, so those two package calls can also be deleted. -Andy -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] tabular in footnote
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
>> modes you cannot understand why the table behaves differently in the
>> footnote. It is documented in the TeXbook.
>
> Then if that is the current state of the platform, as a LaTeX/XeLaTeX
> user it is not reasonable for me to make the demands on the system
> such as I originally sought (e.g. keeping text completely within the
> text area); that is, absolute precision is beyond the reach of one
> who only codes at the LaTeX/XeLaTeX level, and is only within the
> reach of one who codes at the TeX level.
>
> This is not a complaint, it is only an observation. I actually have a
> copy of the TeX Book, I just need to open it. ^___^
>
> Thank you for the clarification,
> Dan
>
>
> 2011/12/8 Zdenek Wagner :
>> 2011/12/8 Daniel Greenhoe :
>>> Hello Heiko,
>>> ...
>>> In my mind (and maybe in my mind only) if I code something (e.g. a
>>> tabular in a footnote) in accordance with documented syntax and then
>>> the result of that code violates a parameter (e.g. a lower text area
>>> boundary) defined in the same documentation, then that by definition
>>> is a bug. Secondly, if a 32 line section of code is required to
>>> prevent my correctly coded (as defined by documented syntax) code from
>>> violating such a parameter, then such a violation is by definition a
>>> bug and the 32 lines of additional code is by definition a "patch".
>>>
>> No, I do not agree. I can only agree that the LaTeX user
>> documentatioin is incomplete. Consider the expression "my text". You
>> would certainly be disapointed if the word "text" were verticaly
>> aligned so that its baseline matched with the bottom of "y". That's
>> why boxes have height and depth and are aligned to baselines, not to
>> bottom. The truth is that the documentation of tabular is incomplete.
>> It does not say that it has zero width and the whole table extends
>> below baseline. Thus in your original sample file you aske LaTeX to
>> put the table below the baseline and LaTeX did exactly what you asked
>> for. Incomplete documentation is unfortunately a feature of LaTeX.
>> Normal users do not know that \vspace is expanded to \vskip in the
>> vertical mode but to \vadjust{...} in the horizontal mode and the
>> starred variant is esentially \vglue. I am afraid that the LaTeX
>> documentation does not even mention the 5 modes so that the vertical
>> and horizontal modes may be strange for you. Without knowledge of the
>> modes you cannot understand why the table behaves differently in the
>> footnote. It is documented in the TeXbook.
>>
>>> Having said that, let me make these additional comments:
>>> 1. I am embarrassed by my own lack of knowledge with respect to TeX coding.
>>> 2. I realize that I take a lot from this email list but contribute
>>> nothing or next to nothing
>>> 3. I very much appreciate all the help that I have and do receive
>>> from this mailing list
>>> 4. I know that beggars can't be choosers.
>>> 5. TeX and it's derivatives has to be one of the greatest
>>> developments of all time --- like unto the Gutenberg Press --- many
>>> many thanks to everyone who has and continues to work so hard to
>>> develop it.
>>>
>>> Dan
>>>
>>>
>>> On Wed, Dec 7, 2011 at 7:51 AM, Heiko Oberdiek
>>> wrote:
On Wed, Dec 07, 2011 at 06:30:39AM +0800, Daniel Greenhoe wrote:
> On Wed, Dec 7, 2011 at 5:46 AM, Heiko Oberdiek
> wrote:
> > You have to compile twice at least.
>
> I compiled at least 8 times using "xelatex Heiko.tex". I still get the
> same error: the text extends below the text area (see attachment). You
> don't get this result on your system?
And I had written:
| The following example addresses calculates the shift to align
| the baseline of the footnote line with the first line of
| the tabular. No time for looking at the problem with the overfull \vbox.
I have seen two problems with your example and one of them solved,
the other remained unsolved. No more, no less.
Taking more time, I see now, that the overfull \vbox is caused
by something different: The header is set to zero (see options
for geometry), but the page number is printed causing the
overfull \vbox. Changing the options of geometry or \pagestyle{empty}
solves the problem.
The exceeding part of the second footnote text is correct behaviour:
TeX tries to align the top and bottom lines of a page in order to
get the baselines at the same position:
* At the top vertical space is added up to \topskip unless
the height of the first element is larger than \topskip.
* At the bottom the bottom element might have a depth up to
\maxdepth. The defa
Re: [XeTeX] no small caps in GNU FreeSerif font?
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 with the developers. I can't check the OT features on the font right now on this machine, but if you run otfinfo, it should tell you if the smcp feature is present in the font (although it's not a sure test, considering Charis SIL had, for older versions, the smcp flag, but no actual implementation). -Andy -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] arabic
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 everyone needs this kind of functionality (I was
making vocabulary sheets for class), but one of the strengths of LaTeX
is that you have the option of doing things in different ways, no?
But to address the original posts:
There's actually a typo in the second example, which is why it doesn't
run. There's no problem with arabxetex.
\begin{tabular}[l] % should read \begin{tabular}{l}
\textarab[voc]{`arabI}
\end{tabular}
Also, I have bidi version 1.2.6, and the original example actually
works fine and in fact bidi refers to xltxtra specifically and asks
that it (xltxtra) be loaded first.
Hope this helps,
Andy
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Problem displaying Chinese font with \newfontfamily
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
-Andy
On Thu, Apr 26, 2012 at 14:05, Haines Brown wrote:
> I'm migrating from LaTeX to XeLaTeX on Debian Squeeze with TL2100,
> but having trouble with XeLaTeX display of Chinese characters:
>
> \documentclass[12pt]{article}
> \usepackage{xltxtra}
> \setmainfont[Mapping=tex-text]{Linux Libertine O}
> \usepackage{xeCJK}
> \setCJKmainfont{AR PL KaitiM GB}
> \newfontfamily\sungtiGB{AR PL SungtiL GB}
>
> \begin{document}
>
> Main font:
>
> Sung font: {\sungtiGB ??}
>
> \end{document}
>
> The chinese characters are all displayed with main font "AR PL KaitiM
> GB" but the \newfontfamily only displays the main font, not the font
> it specifies. I do have access to the font because if I set "AR PL
> SungtiL GB" as main font, it displays properly.
>
> Haines Brown
>
>
>
>
> --
> Subscriptions, Archive, and List information, etc.:
> http://tug.org/mailman/listinfo/xetex
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] fontspec and pinyin.sty conflict
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 write a document using pinyin or are you migrating documents over from a non-xetex setup? If the former, you might want to consider just using the unicode/extended latin characters for pinyin, use a package like xpinyin, or see if someone's made a teckit map for pinyin. If the latter, you could redefine the problematic commands locally and see what breaks and work from there. -Andy On Wed, Jun 6, 2012 at 12:17 AM, Danyll Wills wrote: > I have looked at the archives and Googled for hours but can find nothing that > resolves the problem between fontspec and pinyin. What am I missing? Has > anybody got an answer to this? It seems to me extremely odd that such a > solution has not been worked on. The obvious issues are with things like > '\Pi' and '\Xi' as well as '\Mu' because they are used with other packages. > > Cheers, > Danyll > > > -- > Subscriptions, Archive, and List information, etc.: > http://tug.org/mailman/listinfo/xetex -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] fontspec and pinyin.sty conflict
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: 1. Start by placing tone marker on final vowel. 2. Move tone marker to non-final a, e, or o. 3. Tone 0/5 is indicated by placing a dot in front of the syllable (possibly buggy) Use it as you would any other teckit mapping. It takes input like: ni3chi1fan4le3ma5 and outputs: nǐchīfànlě·ma Hope someone finds it useful. If not, at least it was an interesting exercise. -Andy pinyin.map Description: Binary data pinyin.tec Description: Binary data -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Multilingual verbatim
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 information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] horizontal alignment
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 Crusca wrote:
> **
>
> In data lunedì 19 novembre 2012 18:39:55, Tobias Schoel ha scritto:
>
> > Hello,
>
> >
>
> > I'm not sure if I understood you correctly, but what you want to do
>
> > seems to me to structurally be a table, so you should also tex it that
> way:
>
>
>
> I forgot to specify that there are unforeseeable (at coding time)
> exceptions to that layout, so that it doesn't really fit in a table. I do
> have several other commands defined in my real xetex source and those get
> called when such exceptions arise.
>
>
>
> Even planning a little table for the "content intervals" without
> exceptions is problematic: the last two of the three rows of text in the
> minipage would span over different columns of a table, then it should be
> possible to indent them independently of the table columns, and so on.
>
>
>
>
>
> --
> Subscriptions, Archive, and List information, etc.:
> http://tug.org/mailman/listinfo/xetex
>
>
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] redefining Unicode characters
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 layout engine), will try to > > >position the accents using their bounding boxes if the font does not > > >have a GPOS table, so it should produce better results in this case > > >(unless the font in question does have a GPOS table). > > > > Wow, I'm impressed! When will this new XeTeX be coming out? Do I > > need to wait for TeXLive 2013? > > We don't usually make separate releases, so, unless you are welling to > build from git[1], the answer is yes. > > [1] https://sourceforge.net/p/xetex/code > > Regards, > Khaled > > > -- > Subscriptions, Archive, and List information, etc.: > http://tug.org/mailman/listinfo/xetex > -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] XeLaTeX, xeCJK, Japanese: some general questions
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 part you probably need most is this:
3.1 Package Options
PunctStyle = {⟨quanjiao|banjiao|kaiming|hangmobanjiao|CCT|plain|...⟩}
quanjiao - full-width, adjacent punctuation takes up 1.5 character widths
banjiao - half-width
kaiming - full-width full stop(period), others half-width
hangmobanjiao - full-width, no exceptions
CCT - CCT style (there's no explanation of it in the documentation)
plain - no width adjustment
CheckFullRight = ⟨true|false⟩
False allows linebreaks to occur before certain marks (even footnote marks).
NoBreakCS = { \footnote \footnotemark \nobreak }
Used in conjunction with CheckFullRight to prevent linebreaks preceding
certain commands. Alternatively, use \xeCJKnobreak before the command
(intended for specific instances).
Also, 3.5 describes how to set your own punctuation spacing rules. It's a
little long, so if you need it, let me know.
There was an experimental polyglossia file sent to the list a while ago, if
you search for platex, you should be able to find it.
Hope this helps,
Andy
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
[XeTeX] Fontspec Optical Size support for new OS/2 table spec
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-specific-design-selection-mechanism
).
Technical grumbling aside, the font itself is quite nice, looking like a
book version of Cambria (similar to how Kepler is like a book version of
Utopia).
Only problem is, fontspec doesn't (yet) support the new OS/2 table format.
So I've tried terrible, hack-y things to get it to work, such as nesting
SizeFeatures within BoldFeatures, and vice versa. For example, the
following code yields the correct upright font for the size, but with the
default-sized bold/italic:
\setmainfont[SizeFeatures={%
{Size={-9.7},Font={* Small},BoldFont={* Small Bold},ItalicFont={* Small
Italic},BoldItalicFont={* Small Bold Italic}},
{Size={9.7-13.5},Font={* Text},BoldFont={* Text Bold},ItalicFont={* Text
Italic},BoldItalicFont={* Text Bold Italic}},
{Size={13.5-18.5}, Font={* Subheading}, BoldFont={* Subheading
Bold},ItalicFont={* Subheading Italic},BoldItalicFont={* Subheading Bold
Italic}},
{Size={18.5-23.5}, Font={* Heading}, BoldFont={* Heading
Bold},ItalicFont={* Heading Italic},BoldItalicFont={* Heading Bold Italic}},
{Size={23.5-27.5}, Font={* Display}, BoldFont={* Display
Bold},ItalicFont={* Display Italic},BoldItalicFont={* Display Bold Italic}},
{Size={27.5-}, Font={* Banner}, BoldFont={* Banner Bold},ItalicFont={*
Banner Italic},BoldItalicFont={* Banner Bold Italic}}%
}]{Sitka}
While other combinations result in no effect at all.
Anyone have any experience with specifying bold/italic fonts with optical
sizes?
Thank you!
Andy
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
