Am 20.02.2011 um 02:12 schrieb msk...@ansuz.sooke.bc.ca:
However, if I use XeTeX's default Computer Modern typewriter font by
means
of the \ttfamily macro, without loading fontspec, then the spaces
scale
and are not stretchable by default; it's resetting the fontdimens on
every
size
On Sun, Feb 20, 2011 at 11:49:15AM +0100, Peter Dyballa wrote:
Am 20.02.2011 um 02:12 schrieb msk...@ansuz.sooke.bc.ca:
However, if I use XeTeX's default Computer Modern typewriter font
by means
of the \ttfamily macro, without loading fontspec, then the spaces
scale
and are not
Am 20.02.2011 um 12:56 schrieb Khaled Hosny:
XeTeX' Computer Modern default is actually Latin Modern. Without
fontspec it loads the PostScript variants of Computer Modern.
I'm not sure what this means, but without fontspec (or EU1 fontenc)
XeTeX loads exactly the same computer modern fonts
On Sun, Feb 20, 2011 at 01:42:51PM +0100, Peter Dyballa wrote:
Am 20.02.2011 um 12:56 schrieb Khaled Hosny:
XeTeX' Computer Modern default is actually Latin Modern. Without
fontspec it loads the PostScript variants of Computer Modern.
I'm not sure what this means, but without fontspec
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, Feb 20, 2011 at 08:50:09AM -0600, msk...@ansuz.sooke.bc.ca wrote:
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
I decided to try to replace the sign ~ in my text on the analogue of
the Unicode (code 00a0), and the words that are connected in such a
space no longer hyphenated. Is this normal? Or a feature not yet
implemented?
--
Subscriptions, Archive,
Am Sat, 19 Feb 2011 11:21:03 -0600 (CST) schrieb
msk...@ansuz.sooke.bc.ca:
If your monospaced font has stretchable word space then simply reset
\fontdimen3 + \fontdimen4.
Like most monospace fonts, mine doesn't have stretchable word space; but
XeTeX assumes stretchable word space for all
On Fri, Feb 18, 2011 at 10:11:41PM -0600, msk...@ansuz.sooke.bc.ca wrote:
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
Am 20.02.2011 um 17:01 schrieb Khaled Hosny:
I tried testing your example with a little modification
Are you still using fontspec in your file?
Without \defaultfontfeatures{}, when Latin Modern is loaded by
fontspec, *I* don't see mono-spaced output in the \Large test case.
--
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 more
Alexander wrote:
I decided to try to replace the sign ~ in my text on the analogue of
the Unicode (code 00a0), and the words that are connected in such a
space no longer hyphenated. Is this normal? Or a feature not yet
implemented?
The problem is that U+00A0 has zero lccode and (Xe)TeX
On Sun, Feb 20, 2011 at 10:38:28AM -0600, msk...@ansuz.sooke.bc.ca wrote:
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
On 20 Feb 2011, at 18:17, Khaled Hosny wrote:
OK, checking FF code, there is an isFixedPitch entry in 'post' and 'CFF'
tables that should be non-zero in monospaced fonts, so we just need
someone to come with a patch to make use of that :)
Yes, that would be a possibility - though it's worth
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
I can't find a way to edit that flag in FontForge; it appears that
FontForge sets it behind the scenes when saving a font if and only if all
glyphs in the font have exactly the same width.
Correct. FontForge has a few conventions that are slightly bullish for
an otherwise awesome program
On Sun, Feb 20, 2011 at 01:42:28PM -0600, msk...@ansuz.sooke.bc.ca wrote:
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
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
Recently I posted a question involving OT features in a font I am
preparing to release. Ulrike's suggestion to use \XeTeXtracingfonts=1
seemed promising, but doing so has not clarified the problem; XeTeX
seems to be using the correct font file. The following just occurred to me:
I was
On 2/19/2011 12:13 AM, I wrote:
In a grammar we're writing, the transcription of a word xowunʣāy gets
hyphenated immediately after the 'x'. I thought I could prevent this by
adding the command
\hyphenation{xowunʣāy}
near the beginning of the file (before the \begin{document} command).
However,
20 matches
Mail list logo
