I'd like to use the commercial font "Pro Typewriter Underwood," from
http://www.vintagetype.com/, with XeLaTeX, to produce a close
approximation of old-style typewriter output. But I can't get it to
correctly recognize that the font is a monospace font for the purposes of
inter-sentence spacing.
On Thu, 13 Jan 2011, François Patte wrote:
> Who can explain (and correct if possible) this strange behaviour of the
> Linux Libertine fonts if you add the option "Fractions=On"
>
> If you put a number with more than one digit, only the last number has
> the normal size, the preceding digits are w
On Thu, 13 Jan 2011, François Patte wrote:
> > You should only turn the fractions option on where you actually want
> So no other solution that:
> {\addfontfeature{Fractions=On} 1/2}
>
> Or a macro doing the same job?
As far as I know, that's what must be done.
Fr. Michael said that Latin Modern
On Thu, 13 Jan 2011, Fr. Michael Gilmary wrote:
> > I couldn't find the source code for the OpenType features
> > in Latin Modern Roman;
> Voilà!
>
> > > > otfinfo -f lmroman10-regular.otf
I'd been hoping for the source code as such - i.e. the *.fea files.
Looking at the substitution tables aft
On Sun, 16 Jan 2011, Khaled Hosny wrote:
> It can be done to some degree, see:
> http://talleming.com/2009/10/01/fraction-fever-2/
Looks like it's simply doing fixed-length sequences, with a large fixed
length. That may be good enough in practice - who *really* needs to not
only typeset fractions
On Tue, 15 Feb 2011, Jonathan Kew wrote:
> Yes, you can't do lookups that involve , because of how xetex
> handles word spacing.
If it doesn't work in XeTeX, there will probably be other applications in
which it also doesn't work - so changing XeTeX wouldn't solve the problem.
In general, I think
I'm having trouble with monospace OTF fonts. If I load a monospace OTF
font with fontspec, it works fine at the default size, but when I change
the size with LaTeX class-provided commands such as \Large, the spaces
between words end up the wrong size. I did some digging and found
the problem seem
On Sat, 19 Feb 2011, Ulrike Fischer wrote:
> I would say WordSpace shouldn't be used in \defaultfontfeatures.
Moving the WordSpace setting to the font-loading command and eliminating
\defaultfontfeatures doesn't change the behaviour. The space still
doesn't scale when the size changes as it woul
On Sat, 19 Feb 2011, Ulrike Fischer wrote:
> Yes, as I said size changes doesn't reload a font. WordSpace
> shouldn't be used as a "default" feature.
It doesn't matter whether it's being used as a default; the problem shows
up even without \defaultfontfeatures. Are you saying that WordSpace
shoul
On Sat, 19 Feb 2011, Peter Dyballa wrote:
> XeTeX (and original TeX) do not put SPACE characters into the output, i.e., if
> a SPACE glyph would exist in a font it is not used to separate words or such.
I'm well aware of that. I explained it myself on this very list a few
days ago in answer to so
On Sat, 19 Feb 2011, Martin Schröder wrote:
> Methinks the ragged2e package offers a solution.
The ragged2e package doesn't work for me because it recognizes monospace
fonts by detecting that the value of \fontdimen3 is zero. For OTF fonts,
XeTeX sets \fontdimen3 to nonzero regardless of whether
On Sat, 19 Feb 2011, Mike "Pomax" Kamermans wrote:
> > And if one wants full justification as well as monospaced spaces with a
> > monospaced font ?
>
> Wait, I'm confused; is that even logically possible?
Full justification with monospace fonts would be very unusual. Even if
someone wants to do
On Sun, 20 Feb 2011, Khaled Hosny wrote:
> The question is how to know if the font is monospaced or not, what if
> one wants a monospaced font but with stretchable space?
Well, first of all, "a monospaced font but with stretchable space" is a
very unusual thing to want. That is not how monospace
On Sun, 20 Feb 2011, Peter Dyballa wrote:
> My suggestion was not that you change the font for productive work but that
> you (and we) can test your theory of the different behaviour of TT and OT
> fonts. Which I could not find.
I see. I'm not claiming a difference between TrueType and OpenType,
Blah, deleted a line by mistake. Please read that as:
On Sat, 19 Feb 2011, msk...@ansuz.sooke.bc.ca wrote:
> between OpenType and traditional TeX. TrueType isn't in the picture at
all. I apologize for misunderstanding your suggestion of using another
> font - what I thought you were saying wa
On Sun, 20 Feb 2011, Peter Dyballa wrote:
> > Loading fontspec causes it to use Latin Modern and we're back where we
> > started.
>
> XeTeX' Computer Modern default is actually Latin Modern. Without fontspec it
> loads the PostScript variants of Computer Modern. Latin Modern is constructed
> as an
On Sun, 20 Feb 2011, Khaled Hosny wrote:
> I lost track of what the original issue is, so I tried testing your
> example with a little modification (removing default font feature and
> using different font), and all monspaced fonts I tried are giving me,
> guess what, monospaced results. Now I'm mo
On Sun, 20 Feb 2011, Khaled Hosny wrote:
> OK, this sounds like a fontspec bug to me, can you file a bug against
> fontspec (else I'll try to do myself).
Okay, I'll file one.
> OK, checking FF code, there is an isFixedPitch entry in 'post' and 'CFF'
> tables that should be non-zero in monospaced
On Sun, 20 Feb 2011, Khaled Hosny wrote:
> OK, the inevitable luatex post (I've been resisting for long :p):
> Can you try with your font and see if it heps?
That does seem to work. I haven't checked stretchability, but it at least
gets the width right.
--
Matthew Skala
msk...@ansuz.sooke.bc.ca
On Sun, 20 Feb 2011, Ulrike Fischer wrote:
> >From the other posting I gathered that you use \raggedright anyway.
> Does the stretchability has actually any effect?
I thought I'd replied to this, but then found my intended reply in my
"unsent drafts" folder, and it doesn't seem to be in the list a
On Wed, 23 Feb 2011, Meho R. wrote:
> 4. The old problem about PDF search unfortunately still remains: only
> basic standard ligatures are recognized. I would be happy if someone
> knows a way to correct this during font creation or correcting existing
> ones.
I think the Adobe Glyph Naming Conven
On Sun, 27 Feb 2011, Will Robertson wrote:
> The code here is
> \tl_put_right:Nx \l_fontspec_postadjust_tl {
My copy of fontspec.sty actually has a \tl_set:Nx instead of \tl_put_right
at this point.
> So it seems like I should be writing something more like
>
> \tl_put_right:Nn \l_fontspec_pos
On Mon, 28 Feb 2011, Will Robertson wrote:
> How about, instead, if
>
> WordSpace={2,2,2}
>
> was a multiplier, but
>
> WordSpace={6pt,2pt,1pt}
>
> set the values explicitly? (Subject to scaling according to the font size.)
If both those are available, it should be fine. If only the point
On Sun, 27 Feb 2011, Tobias Schoel wrote:
> If the monospace option is set by hand for non-monospaced fonts, how will the
> letters be positioned in the monospaced grid? How should the following pattern
> look?
I only envision the monospace option as affecting the width of TeX's word
and sentence
On Thu, 3 Mar 2011, Philip Taylor (Webmaster, Ret'd) wrote:
> if XeTeX is predicated on the use of Unicode, it should
> "understand" the semantics of Unicode code points such
> as u2009 and u202F and just do the right thing without
> having to hack things through the use of active characters.
Ther
On Thu, 3 Mar 2011, enrico.grego...@univr.it wrote:
> > \newunicodechar{2009}{\,\hspace{0pt}}
> > \newunicodechar{202f}{\,}
>
> Of course it works.
>
> The main purpose of the package is indeed to use the "real char". Actually
> those who don't know how to input it will never use the packag
On Sun, 6 Mar 2011, Gerrit wrote:
> In this case, Polyglossia could give priority to the main language written in
> the text. If the document has main language English and second language
What is the "main language written in the text"?
> the document, that the character is ambigunous. For other
On Sun, 6 Mar 2011, Gerrit wrote:
> > > the text. If the document has main language English and second language
> > What is the "main language written in the text"?
> >
> Sorry, my English... I meant the main language, the text is written in. E.g.
> an English article with some Russian text in it.
On Tue, 22 Mar 2011, jonathan MERCIER wrote:
> it seem not!!
Open-source development occasionally occurs in places other than
SourceForge. I think XeTeX is only using the SourceForge bug tracker;
note that there doesn't seem to be any code in the repository you're
looking at, so a lack of updates
On Sun, 27 Mar 2011, David Perry wrote:
> character. You can enter characters by number in XeTeX with \char"; so
> try
>
> \char"8FBB\char"E0100
If it's just a question of getting in the characters, which the font will
then process by glyph substitution, it should work to simply include the
d
On Sun, 27 Mar 2011, Peter Dyballa wrote:
> U+8FBB exists in this and quite a few other fonts, but which font has U+E0100?
> (And since this character is outside the BMP, the Basic Multilingual Pane, it
> won't be some usual font.)
U+E0100 is not a graphic character in itself, but a "variation sel
On Sun, 27 Mar 2011, Paul Isambert wrote:
> Both, actually. The font by itself does nothing, it simply indicates what the
> rendering engine should do. I suppose (because it's seems the simplest way
> here) that this is implemented as a ligature.
By that logic it could be said that no software eve
On Mon, 11 Apr 2011, Dan Drake wrote:
> If you please, what dumb thing am I doing here?
No dumb mistakes, just a little more work needed to get the results
you want.
The quotation marks thing should be easy. Try specifying Mapping=tex-text
as an option when you choose the font, as in:
\setma
I have a large document, approximately 1800 pages, with a lot of graphics
created by PGF/TikX and heavily using transparency. I would like to use
XeTeX to generate one large XDVI file, then run xdvipdfmx several times
with different -s options to make PDFs of subranges of the pages. (See
appendix
On Mon, 16 May 2011, Heiko Oberdiek wrote:
> take some actions arising specials. But these actions might
> have effects on the whole document. Sometimes this is good
> to avoid missing object declarations and other things. But sometimes
> extra stuff or wrong stuff is added because of pages that th
On Sun, 5 Jun 2011, Philip TAYLOR (Webmaster, Ret'd) wrote:
> However, experimenting with all possible values from "00" to "FF"
> for the transparency byte seems to have zero effect, in that the
> second element laid down completely obscures whatever lies
> beneath it. What am I missing, please ?
On Sun, 5 Jun 2011, Philip TAYLOR (Webmaster, Ret'd) wrote:
> Thank you for your prompt response, Mathew. In fact, I am using the default
> driver (I am not aware how I might alter this), and was simply relying on it
> to "do the right thing". If you could tell me how to identify the driver, and
On Sun, 12 Jun 2011, Pander wrote:
> I have discovered a problem with ocrb10.otf the ligatures are not workig
> correctly in xelatex. ttx from fonttools reports only these common
> ligatures: ff-ffi-ffl-fi-fl. See example below for result. How to solve
> this?
Does this font contain ligatures at a
On Mon, 13 Jun 2011, Pander wrote:
> TeX Live 2010
>
> /usr/local/texlive/2010/texmf-dist/fonts/opentype/public/ocr-b-outline/ocrb10.otf
That is Zdeněk Wagner's auto-conversion of Norbert Schwarz's Metafont
source. It doesn't contain f-ligatures no matter what the GSUB table may
say. I took a lo
On Mon, 13 Jun 2011, Pander wrote:
> > mark, dotless i and j, and similar code points). The existence of a GSUB
> > table pointing at those points can probably be explained by defaults from
> > the auto-conversion. So in summary, yes, it's a bug in the font.
>
> Could the conversion software gene
On Mon, 13 Jun 2011, Pander wrote:
> And Ubuntu should also switch to these OCRA fonts for ttf-ocr-a? What is
> in there is from 2009 and is credited to
> "Created by Sauter,U-TOWN_HALL\Sauter,S-1-5-21-2526881554-1349 with
> FontForge 1.0 (http://fontforge.sf.net)"
OCR-A is another question. I co
On Wed, 15 Jun 2011, Mike "Pomax" Kamermans wrote:
> Since phonetic guide texts for CJKV are tied to characters, I would consider
> the most logical split one where the guide text is dictated by the character
> boundaries, and the language used. Hyphenation for guide text would be
> strongly tied t
On Sun, 19 Jun 2011, Tobias Schoel wrote:
> if I understand correctly, that way the output still shows the letters or the
> deprecated unicode codepoints. It should be analog to medieval / lowercase
> numbers. E.g. it's still the number 123 it only uses different glyphs. So when
> I copypaste it, i
On Sun, 19 Jun 2011, Tobias Schoel wrote:
> that's a good answer. is there such an opentype feature / fonts supporting it?
I don't know of a font that does Arabic->Roman numeral translation as
glyph substitution while preserving the original Arabic code points. I'm
considering building an Arabic-
On Sun, 19 Jun 2011, enrico.grego...@univr.it wrote:
> What the OP wants is that "CXV" is stored as a unique glyph representing 115.
> Maybe this can be done by reserving, say, five thousand slots in Unicode to
> contain the numbers from 1 to 5000 in Roman form that are built from the basic
If you
On Sun, 19 Jun 2011, Tobias Schoel wrote:
> Am I the OP? (I don't know that abbreviation and therefore I am confused.) But
Yes. It's an old Usenet abbreviation standing for "Original Poster."
--
Matthew Skala
msk...@ansuz.sooke.bc.ca People before principles.
http://ansuz.sooke.b
On Wed, 22 Jun 2011, Keith J. Schultz wrote:
> 2) A program can open any/retrieve any file on a server
>using http. all it needs to do is speak http!
While we're at it, let's add a spelling checker, SQL database backend, and
multilingual thesaurus to TeX. Also a Space Invaders m
On Thu, 23 Jun 2011, Keith J. Schultz wrote:
> I was not talking about implementing a full http-client.
I don't see how the system can reliably download files from http: URLs
without being or using a full HTTP client. That's the point I was
responding to. If your main point was something e
On Sat, 16 Jul 2011, Peter Dyballa wrote:
> like "hay" (or some other form of money) or different, like in German for
> example? (That's the reason IPA was invented: it's completely clear.)
I think the point Michael was making is that because Cherokee is already
written in a phonetic script, trans
On Thu, 1 Sep 2011, Peter Dyballa wrote:
> > So instead of the \setmathrm giving me the font I requested, I seem to
> > be getting a computer modern font. Why would this be???
>
> Because you don't set your maths in \mathrm! The default for maths is a
> sans-serif font, because the text usually co
On Thu, 1 Sep 2011, Daniel Greenhoe wrote:
> $abcdefgh$\\
> * The second line (in math mode) I would think should be mono-spaced
> because of the \setmathrm command; but instead it seems to be maybe a
> proportional computer modern font.
Letters inside $..$ without other markup are not set in \ma
On Fri, 23 Sep 2011, VAFA KHALIGHI wrote:
> When I started as the maintainer of bidi, I contacted some of the
> package/class authors unfortunately no one even bothered to reply back (at
> least saying, no I do not have time or I do not know how to do it) and
> indeed that is why bidi itself, suppo
On Tue, 18 Oct 2011, George N. White III wrote:
> Users also don't like to discover that the publishers' LaTeX format they
> need won't work with the distro TeX, or that a document that formats correctly
> on a co-author's Mac or Windows system won't format on their linux system.
That seems to me
On Sun, 23 Oct 2011, Philip TAYLOR (Webmaster, Ret'd) wrote:
> clearly they are -- but in terms of actual requirements. Since
> you are only "discouraged from" and not "prohibited from"
> making changes, I believe that a court of law would find that
> there is no actual inconsistency in practice.
On Wed, 26 Oct 2011, Philip TAYLOR (Webmaster, Ret'd) wrote:
> He does /not/ deny you the right to do so; he discourages
> you, which any competent native speaker of English would
> recognise as being completely different.
I'm sure any competent lawyer will tell you that if you do something that
h
On Fri, 28 Oct 2011, William Adams wrote:
> > majority of documents are created using GUI tools. What use cases
> > are better served by batch mode, and in what cases is TeX used by
> > default because of available GUI tools refuse to play.
>
> Large database publications. Variable data printing.
On Wed, 2 Nov 2011, Philip TAYLOR (Webmaster, Ret'd) wrote:
> Fortunately, FMi and others were able to convince
> him that he was wrong, whence TeX 3. Now we clearly
> need to start on Adobe (and Heiko !).
If Ross Moore's and other recent technical postings are to be believed,
this is a non-issue
On Fri, 4 Nov 2011, Mojca Miklavec wrote:
> corrections & submit PDF for printing ... and that friend has set
> French or Russian as his default/preferred language, so the printing
> house will print the document typeset with Russian hyphenation
> patterns. Wouldn't that be nice?
This kind of prob
On Fri, 4 Nov 2011, Reinhard Kotucha wrote:
> As far as paper size is concerned, as mentioned by Matthew Skala, this
> information belongs into each document too. However, there are some
> situations where default settings can be useful though, for instance
> if you exchange TeX source files with
On Sun, 13 Nov 2011, Petr Tomasek wrote:
> make ~ not active when writing my own macros because it contradicts
> the Unicode standard...)
Isn't it just as much a "contradiction" of the "standard" for \ to do
what \ does? I don't think that is a good way to decide what TeX's
input format should be
On Mon, 14 Nov 2011, Petr Tomasek wrote:
> > Not in every case. How would you visually differentiate between all the
> > white space characters (space vs. non-break space, thin space (u2009)
> Using different color.
About 8% of men have some form of colour blindness (the prevalance is much
lower,
I think this discussion is bogging down because several different
questions are getting mixed together. Here's what I see as the major
issues:
1. Does Unicode specify a single correct way of representing white space?
2. If an input file to XeTeX contains currently less common Unicode
whitespace
On Mon, 14 Nov 2011, Philip TAYLOR wrote:
> > 2. Inevitably, people will include invalid characters in TeX input; and
> > U+00A0 is an invalid character for TeX input.
>
> Firstly (as is clear from the list on which we are discussing
> this), we are not discussing TeX but XeTeX. Secondly, even
Xe
On Mon, 14 Nov 2011, Philip TAYLOR wrote:
> I think (with respect) that "some Unicode code points outside the 7-bit range"
> is a gross understatement. As far as I am aware, XeTeX permits a very
> considerable
> subset of Unicode (perhaps even all of it; I do not know) as input.
My point is that
On Mon, 14 Nov 2011, Karljurgen Feuerherm wrote:
> I use U+12000 and above regularly, as a case in point...
Do you think that basic formatting control functions should be bound to
code points in that range, as the preferred way of accessing those
functions? Let's not lose track of what this discu
Since we're having so much fun with U+00A0, what about U+00AD, which may
or may not mean the same thing as \- ?
--
Matthew Skala
msk...@ansuz.sooke.bc.ca People before principles.
http://ansuz.sooke.bc.ca/
--
Subscriptions, Archive,
On Sun, 27 Nov 2011, Aleksandr Andreev wrote:
> I figured out the issue. They work if the entire text is in black, like this:
> {\moo \Huge }
I've been watching this discussion with interest, having had similar
problems. I thought the colour thing might be an issue - very likely
XeTeX is put
On Sun, 27 Nov 2011, Aleksandr Andreev wrote:
> It appears that XeTeX colors are handled by inserting pdfliteral nodes
> around colored items, which breaks the access to GPOS.
>
> Unless there's been some work on this issue since 2007, it appears
> that I will need to look for a different way of ty
It appears to me that XeTeX doesn't handle, at all, OpenType context
substitutions that match without doing a substitution - i.e. the ones that
appear in Adobe feature files as "ignore sub" rules. When one of these
matches, the renderer is supposed to skip the remaining rules in the
lookup. XeTeX
Here's a stripped-down example of the problem. The attached OTF font
contains rules in the "clig" feature saying that "a b" should be replaced
by "a B" (i.e. the b is changed to upper case) except when it is followed
by "c". For greater clarity, the feature file is also attached. Testing
in Font
On Tue, 29 Nov 2011, Khaled Hosny wrote:
> The same here, but I get the expected result (aBa, abc) with LuaTeX as
> well as HarfBuzz. I tested with another application using ICU layout
> engine (fontmatrix) and got the same result as XeTeX, so I think it is
> an ICU bug.
On further testing, I don'
On Wed, 30 Nov 2011, Khaled Hosny wrote:
> processed by the layout engine, which would require keeping account of
> character to glyph mapping (which is doable, all text editing GUI's have
> to do it).
It will, of course, have to do something sensible (even if that just means
complain) should the
On Wed, 30 Nov 2011, msk...@ansuz.sooke.bc.ca wrote:
> In the Korean fonts I'm currently working on, some syllables are converted
> to single precomposed glyphs by ligature substitution, and others are
> built up by overlaying zero-width glyphs, and the difference between the
I was interested to t
On Wed, 30 Nov 2011, Apostolos Syropoulos wrote:
> did produce the expected results with say XeTeX that comes with
> TeXLive 2009. I will give more details later on.
The item I found in the ICU issue tracker suggests the bug was introduced
in their code base on October 28, 2008, so (given the dela
On Thu, 1 Dec 2011, Khaled Hosny wrote:
> > Suppose someone types
> >
> >f\textcolor{red}{f}
>
> In this case FireFox colourises half of resulting ff ligatures (1/3 in
> ffi etc), I'm not sure how this is done or if it is possible with PDF at
I don't think XeTeX should attempt to do that.
--
On Thu, 1 Dec 2011, Philip TAYLOR wrote:
> > ! Unable to load picture or PDF file 'Resources/Images/TAR-2.tex'.
>
> and no
>
> > ! Unable to load picture or TeX file 'Resources/Images/TAR-2.tex'.
It seems obvious to me that the command to load a PDF file and the command
to load a picture are shari
On Thu, 1 Dec 2011, Khaled Hosny wrote:
> On Thu, Dec 01, 2011 at 07:59:14AM -0600, msk...@ansuz.sooke.bc.ca wrote:
> > The item I found in the ICU issue tracker suggests the bug was introduced
> > in their code base on October 28, 2008
>
> Link?
Bug ticket:
http://bugs.icu-project.org/trac/tic
On Thu, 1 Dec 2011, Aleksandr Andreev wrote:
> cursive-type font (or even for italics). And it would most certainly
> not work for something like Korean syllables.
It appears that even a correctly filled-in ligature carets table only
specifies horizontal positions (or, only vertical positions for
On Sun, 4 Dec 2011, Zdenek Wagner wrote:
> first, as Keith wrote, as a reader I would not expect a table in a
> footnote. If the table is important, why not to put it to the main
> text? And if it is not important, why it is there at all? If it is of
I would definitely expect to see a table in a f
On Mon, 12 Dec 2011, Daniel Greenhoe wrote:
> should be at U+1D00. But in Pagella-regular, U+1D00 is empty. Where
> are the small caps being hidden? Or are they algorithmically generated
> from the Latin capital letters?
I think the officially correct way for an OpenType font to support small
caps
On Thu, 15 Dec 2011, Philip TAYLOR wrote:
> found on the ground floor", but I am not the author), the apostrophe
> of "weaver’s/weavers’" is the same Unicode character as the closing
> quotation mark of "windows’". Should it be ?
I think that's the practice recommended by the Unicode Consortium.
On Thu, 15 Dec 2011, Peter Baker wrote:
> apostophe and the closing quotation mark are the same glyph. We'd have to kern
> each instance manually.
>
> That said, it's pretty clear that we're stuck with what the Unicode Consortium
> has decreed for us.
Old style and lining numerals are generally th
On Sat, 17 Dec 2011, Tobias Schoel wrote:
> So we're back to the days, where one had to use escape sequences for quotation
> marks (\glq,\grq,"',"`,…) as though unicode had not included u2019.
>
> Even worse, because with OpenType some font designers might include
> substitution rules which include
On Sat, 21 Jan 2012, Steve White wrote:
> There is one table concerning Sanskrit. As Hindi is
> transformation-wise simpler than Sanskrit, it uses only the "default"
> tables. So there are no tables that specifically refer to Hindi.
FWIW, I've noticed a similar problem with FontForge. It has tr
On Sun, 12 Feb 2012, Zdenek Wagner wrote:
> The author has right to decide how his package can be used. If people
> are discouraged to distribute it, TL maintainers feel discouraged and
> do not distribute it. I am also discouraged, thus I only point to
> CTAN. I have tried this package with a few
On Wed, 15 Feb 2012, maxwell wrote:
> The SIL Scheherazade font covers all the characters in the Unicode Arabic
> script block (not the presentation forms). Afaik, that includes all
> Persian (Pashto, Urdu, Punjabi...) characters, in the Naskh style. There
> are a few Arabic script chars used in
I'm sorry I don't have many details because it wasn't my own system on
which the problem appeared, but: I have a PDF file generated with XeTeX
(xdvipdfm), and a Japanese font embedded in the PDF. It looks fine on my
screen (under Linux, with a couple of different viewers) and it prints
correctly
On Sat, 18 Feb 2012, Jonathan Kew wrote:
> If you're in a position to edit the font such that it has a 1000-unit em
> square, this may resolve the incompatibility.
It *is* a font with a non-1000-unit em, so that's probably the issue and
editing the font is probably the right solution. It bothers
On Wed, 14 Mar 2012, d fulano wrote:
> how do I determine what are the "standard ligatures" in a font?It is not
> obvious (especially for non-English languages), and they can also vary
> in each font. Basically what I want to do is this:I can very quicky
It will be tricky with OpenType fonts that
On Thu, 15 Mar 2012, Philip TAYLOR wrote:
> ! Undefined control sequence.
> l.4 \defaultfontfeatures
It is provided by the LaTeX fontspec package. Here we go again...
--
Matthew Skala
msk...@ansuz.sooke.bc.ca People before principles.
http://ansuz.sooke.bc.ca/
-
On Fri, 16 Mar 2012, Philip TAYLOR wrote:
> plain format, and thus any solution that is predicated on the
> use of (e.g.,) "fontspec", "LaTeX", "XeLaTeX", "ConTeXt", and
> so on, cannot be of use to me in my quest.
Even if you don't actually load the packages, it may be worthwhile to
examine the s
On Tue, 3 Apr 2012, Roel Meeuws wrote:
> some of the unicode characters are showing up as a square with a cross,
> i.e. I think xetex is not finding the right glyphs in the font. I am using
Your file contains code points U+278A through U+2793, which are "DINGBAT
NEGATIVE CIRCLED SANS-SERIF DIGIT O
On Tue, 15 May 2012, C Y wrote:
> environment wise...) If not, is there documentation anywhere of what
> constitutes the minimal set of files that will allow an average LaTeX
> document to be typeset?
That is a lot like asking for the minimal set of files that will allow an
average Linux software
On Tue, 31 Jul 2012, Joachim Trinkwitz wrote:
> exceptional cases or for certain special needs like font variants, color
> etc. (OK, speaking from the perspective of a user who don't need
> languages with non-latin scripts …)
There's the rub. Non-Latin scripts are a big part of the constituency o
On Tue, 31 Jul 2012, Jonathan Kew wrote:
> On 31/7/12 13:26, msk...@ansuz.sooke.bc.ca wrote:
> > There's the rub. Non-Latin scripts are a big part of the constituency of
> > XeTeX. I routinely have to manually activate Korean-specific OpenType
> > features that are specified to be default but tha
On Wed, 1 Aug 2012, Philip TAYLOR wrote:
> Is that not good ? Would Chinese calligraphy look anywhere near
> as beautiful if its glyph forms had been forcibly coerced into
> meeting the constraints imposed by movable type printing ?
The question is whether the machine or the human being should be
On Wed, 1 Aug 2012, Ulrike Fischer wrote:
> Perhaps (the discussion is rather long). But you obviously don't
> accept my conclusion that one possible solution is to reduce the
> complexity of the script. You are only looking for the people who
> should write all this complex code.
Language is inhe
On Wed, 1 Aug 2012, Zdenek Wagner wrote:
> > That is the line of thinking that would favour Graphite (a general system
> > for defining complex scripts inside fonts) over OpenType (which requires
> That's right but we still have a lot of non-Graphite fonts.
We also don't have much enthusiasm, as
On Wed, 1 Aug 2012, David Perry wrote:
> Yes, there are flaws in XeTeX, e.g., in connection with Hangul support. But I
I think XeTeX actually works quite well with hangul if the appropriate
features are turned on, and it sounds like their not being so was a bug
that's easy to fix. It was already
On Fri, 7 Sep 2012, Zdenek Wagner wrote:
> page breaks but will compile. If the font is loaded from a specific
> path and another user does not have the font in the very same path,
> the document will not compile. Of course, the best way would be if the
If I need a document to be portable, I'll in
1 - 100 of 155 matches
Mail list logo
