On 2011-03-01 00:58:45 +1030,
msk...@ansuz.sooke.bc.ca said:
It's important not to override the widths of glyphs because of the common
case I described earlier of a font that is in some meaningful way
monospaced, but doesn't have all characters exactly the same width.
Also note that XeTeX cur
On 01/03/2011, at 1:28 AM, Vadim Radionov wrote:
> one side-effect of your patch is that now, afaics, WordSpace multipliers work
> cumulatively in
>
> \newfontfamily\russianfont[Mapping=tex-text,Script=Cyrillic,WordSpace={1.4,.9,.8},
> SmallCapsFeatures={LetterSpace=5,WordSpace={1.5,1,1}}]{Char
Hi, Will
one side-effect of your patch is that now, afaics, WordSpace multipliers
work cumulatively in
\newfontfamily\russianfont[Mapping=tex-text,Script=Cyrillic,WordSpace={1.4,.9,.8},
SmallCapsFeatures={LetterSpace=5,WordSpace={1.5,1,1}}]{CharterITC}
while they were unrelated before.
Vadim
O
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
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?
mmm
mim
ciao
Toscho
Am 27.02.2011 17:32, schrieb Peter Dyballa:
Am 27.02.2011 um 06:32 schrieb Will Robertson:
Could we measur
On 28/02/2011, at 10:11 AM, msk...@ansuz.sooke.bc.ca wrote:
>> http://github.com/wspr/fontspec/issues/99
>>
>> Have I missed anything?
>
> On issue 99: you mention "an option to add two ‘spaces’ instead of one
> might be a nice customisation." That calls for some caution - does it
> mean "add
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 28/02/2011, at 12:56 AM, msk...@ansuz.sooke.bc.ca wrote:
> If I edit the fontspec.sty file to include the above definition instead of
> the existing one, then inter-word spaces scale correctly. Inter-sentence
> spaces don't. Ideally there would be similar code addressing \fontdimen7
> in rela
Am 27.02.2011 um 06:32 schrieb Will Robertson:
Could we measure the width of an "i" and an "m", and if they're the
same we'd be 99% sure it's a monospace font?
You could also allow to set a mono(space) or fixed option to the
options when declaring a font. (Which might allow to set monospa
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
Hi Will,
Yes, the patch works in my tests. Concerning changing of WordSpace locally:
i can do in a line with some other "change": consider
some context {\addfontfeature{LetterSpace={0},WordSpace={5}} way too
stretched} some context again.
Probably that's because invoking other feature uses anot
On 27/02/2011, at 8:12 PM, Vadim Radionov wrote:
> But still there are things to be improved. If i want to change WordSpace
> locally, I have to add
> some other dummy feature (say, LetterSpace=0), or this change of inter-word
> space will be applied globally to the current font.
Hi Vadim,
Th
But still there are things to be improved. If i want to change WordSpace
locally, I have to add
some other dummy feature (say, LetterSpace=0), or this change of inter-word
space will be applied globally to the current font.
Vadim
On Sun, Feb 27, 2011 at 12:10 PM, Vadim Radionov
wrote:
> Will,
>
Will,
Thank you for this patch, i've been waiting for it since months ago.
Yours,
Vadim
On Sun, Feb 27, 2011 at 8:28 AM, Will Robertson wrote:
> On 2011-02-20 03:51:03 +1030, msk...@ansuz.sooke.bc.ca said:
>
> Manually setting \fontdimen3 and \fontdimen4 seems to correctly change the
>> spa
On 2011-02-20 11:42:30 +1030,
msk...@ansuz.sooke.bc.ca said:
* Ideally the fact that the font is monospace is auto-detected, but if
that is difficult or impossible, it would be reasonable that I set some
option to let the system know that spaces should not stretch.
Could we measure the wi
On 2011-02-20 03:51:03 +1030,
msk...@ansuz.sooke.bc.ca said:
Manually setting \fontdimen3 and \fontdimen4 seems to correctly change the
space stretchability - and in fact is the workaround I'm using for the
time being - but it must be repeated after every size change and so it
breaks semantic m
Am Tue, 22 Feb 2011 10:57:12 -0600 (CST) schrieb
msk...@ansuz.sooke.bc.ca:
>>>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,
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 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, 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 a
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 (for
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 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 wor
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 m
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
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.
--
Greeting
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
> b
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 f
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
> >
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 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
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 as
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 n
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 chang
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:
> 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,
Am 19.02.2011 um 23:50 schrieb msk...@ansuz.sooke.bc.ca:
Ulrike Fischer says
that WordSpace should not be used as a "default" feature; but since it
fails whenever the standard font-size commands are used, the practical
effect is that WordSpace cannot be used at all.
You can use WordSpace as
Am 19.02.2011 um 19:57 schrieb msk...@ansuz.sooke.bc.ca:
Instead of exotic fonts you can use from TeX Live 2010 the GNU
Freefonts in:
No, I can't. The document in question is a type specimen, and
written in
a mixture of English and Japanese. Using a different font would
defeat
the e
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 Sat, Feb 19, 2011 at 04:14:36PM -0600, msk...@ansuz.sooke.bc.ca wrote:
> I still think that XeTeX or fontspec are buggy in their handling of
> monospace fonts, but this is a better workaround.
The question is how to know if the font is monospaced or not, what if
one wants a monospaced font but
Martin Schröder wrote:
Why do you ask anyway? Since when are you using LaTeX?
There are many things that I don't use in which I continue
to maintain an interest.
** Phil.
--
Not sent from my i-Pad, i-Phone, Blackberry, Blueberry, or any
such similar poseurs' toy, none of which would I be se
Mike "Pomax" Kamermans wrote:
Philip,
And if one wants full justification as well as monospaced spaces with
a monospaced font ?
Wait, I'm confused; is that even logically possible?
Good point : I hadn't considered that !
** Phil.
--
Not sent from my i-Pad, i-Phone, Blackberry, Blueberry,
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 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
Philip,
And if one wants full justification as well as monospaced spaces with
a monospaced font ?
Wait, I'm confused; is that even logically possible?
A monospaced font has letters and symbols all of equal width, including
interpunctions like "space" (the one you type with a space bar, not t
2011/2/19 Philip Taylor (Webmaster, Ret'd) :>
> Martin Schröder wrote:
>> Methinks the ragged2e package offers a solution.
>
> And if one wants full justification as well as monospaced spaces
> with a monospaced font ?
untested:
\usepackage{ragged2e}
...
\justifying
foo bar\par
\RaggedRight
foo ba
Martin Schröder wrote:
2011/2/19:
it goes. The problem is that XeTeX also adds stretchability and
shrinkability to the word space, which is an inappropriate thing to do
when the font is monospace, and there doesn't seem to be a way to remove
the stretchability and shrinkability in a way that
2011/2/19 :
> it goes. The problem is that XeTeX also adds stretchability and
> shrinkability to the word space, which is an inappropriate thing to do
> when the font is monospace, and there doesn't seem to be a way to remove
> the stretchability and shrinkability in a way that will survive the L
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
Am 19.02.2011 um 05:11 schrieb msk...@ansuz.sooke.bc.ca:
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.
Matthew,
XeTeX (and orig
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
Am Sat, 19 Feb 2011 10:48:51 -0600 (CST) schrieb
msk...@ansuz.sooke.bc.ca:
> 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
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
Am Fri, 18 Feb 2011 22:11:41 -0600 (CST) schrieb
msk...@ansuz.sooke.bc.ca:
> 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
>
54 matches
Mail list logo
