Hi Jonathan,
Thanks for your comments.
On 2011-02-07 22:34:05 +1030, Jonathan Kew
said:
So while I think I agree that it would be good for \XeTeXcharglyph to
respect the font's selected OT features, it's important to recognize
the limitations inherent in *any* API that tries to get glyph
On 2011-02-12 11:58:07 +1030, David Perry
said:
In one of my fonts, I'm having a hard time getting the OT features to
work correctly in XeLaTeX.
If I include the following line:
\setmainfont[Numbers=Lowercase,Ligatures={Rare,Historical}]{Cardo}
then the oldstyle numerals and ligature
On 2011-02-17 15:12:53 +1030, Vafa Khalighi
said:
This is not a problem but when preview package is used Then you get error:
! Package xkeyval Error: no key specified for value `'.
See the xkeyval package documentation for explanation.
Hi Vafa,
Sorry for the delay with this. I think I've
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
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 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
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
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 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
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 06/07/2011, at 3:41 PM, Mojca Miklavec wrote:
> I would like to know how I can use unicode-math package for mixing
> multiple fonts. (I don't mean taking a few characters from one font
> and a few symbols from the other.) I would like to display one
> character from LM Math for example and the
On 2011-07-14 16:33:59 +0930, Mojca Miklavec
said:
Wow, Ulrik, Perfect!
I will simply use your version now (not trying to learn the syntax).
Will - Maybe it makes sense to incorporate some of the changes into
your original document?
Or at least create a second copy or style file with the pur
On 2011-09-03 07:30:41 +0930, Daniel Greenhoe
said:
Thank you Ulrike --- I have started using the unicode-math package. It
works great. Your suggestion was very helpful.
Note that if you're just looking to change the font used for the italic
alphabetic characters, the mathspec package might
On 2011-09-12 06:24:38 +0930, Daniel Greenhoe
said:
Using \underbrace with the unicode-math package under XeLaTeX produces
garbage output. Here is a minimal example:
\documentclass{book}
\usepackage{unicode-math}
\setmathfont{xits-math.otf}
\begin{document}%
\[ \underbrace{xyz} \]
\end{doc
On 2011-09-13 21:05:33 +0930, CTAN Announcements said:
Name of contribution: fontspec
Author's name: Will Robertson
Package version: v2.2
Location on CTAN: macros/latex/contrib/fontspec/
Summary description: Advanced font selection in XeLaTeX and LuaLaTeX
License type: lppl
Announcement
On 2011-09-14 19:14:13 +0930, VAFA KHALIGHI
said:
Are you going to change the actual code or you will be adding backward
compatibility?
I like to use the new code for my xepersian package but I need to know if
the new code is also going to get changed?
The documented functions \fontspec_set
On 2011-09-15 02:13:15 +0930, VAFA KHALIGHI
said:
Here is my minimal example. What is the difference between \newfontfamily
and \fontspec_set_family?
Sorry, I should have added more information to that section of the
manual. Here's the new text for \fontspec_set_family:
% Defines a new NF
On 2011-09-17 18:44:48 +0930, VAFA KHALIGHI
said:
Why this always returns "non-RTL script"?
\newif\if@Latin
\fontspec_if_current_script:nTF {arab} {\@Latinfalse} {\@Latintrue}
I wondered if the documentation for this feature needed work, but it
seems okay if a little terse: "Test whether t
On 15 Apr 2014, at 9:49 am, Khaled Hosny wrote:
> On Thu, Apr 10, 2014 at 12:58:23PM +0100, Philip Taylor wrote:
>>
>> Why are these key XeTeX primitives (\XeTeXprotrudechars, \rpcode, etc)
>> not documented in /The XƎTEX reference guide/ ? Will, Khaled,
>> Jonathan : can you comment on this,
On 11 Feb 2016, at 8:06 AM, David J. Perry wrote:
>
> I looked in a font editor at the font (XITS) that was used to produce the
> sample PDF. As far as I can see, it has no support for combining marks or
> variation selectors of the sort that I would expect, based on my non-math
> experience.
On 11 Feb 2016, at 4:27 PM, Shakthi Kannan wrote:
>
> ! LaTeX Error: Command \providelength already defined.
> Or name \end... illegal, see p.192 of the manual.
How ironic… it should have been defined with \providecommand in both cases!
(If they both behave identically, which I gue
Hi all,
Some recent discussions about unicode mathematics and so on brought up the
following issue. I thought it might be good to raise here in case it sparks
anything. If not, no harm done :)
In the current unicode/OpenType maths support in XeTeX and LuaTeX, with proper
setup of \Udelcode and
Hi David,
> On 21 Feb 2016, at 11:36 AM, David J. Perry wrote:
>
> Simon kindly tested my font in the SILE editor. The script and language
> settings and the stylistic set all work as expected there. So it seems the
> font is not the source of the problems I'm experiencing. Any additional
>
On 24 Feb 2016, at 2:20 AM, Jonathan Kew wrote:
>
> For a document that wants some other kind of "ActualText", there's going to
> need to be pretty detailed markup in the source, I think. (E.g. each word, or
> similar unit, will need to be tagged to provide the desired ActualText that
> goes w
Hi Ross,
Great to hear from you.
I thought of you straight away when writing my email :)
> On 25 Feb 2016, at 11:35 AM, Ross Moore wrote:
>
> You have to be *very* careful with /ActualText, since it must be done using
> PDFdoc encoding,
> as it becomes part of the page contents stream.
> Any
On 25 Feb 2016, at 8:33 PM, Jonathan Kew wrote:
>
> I'd guess it has always been possible, in principle, to attach ActualText to
> math at the macro level, using \specials{}s to write the necessary PDF code
> directly. But I confess I haven't really looked into what this would
> involve pe
Hi David,
I think I remember intentionally omitting this feature because it’s kind of
useless for most fonts.
(It’s been a long time, though. Happy to revisit.)
I’d recommend creating your own feature option for it using something like:
\newopentypefeature{Style}{AllAlternates}{+aalt}
Hope thi
Hi Pat,
Sorry for the inconvenience.
> On 23 May 2016, at 11:41 AM, Patrick Carr wrote:
>
> Did I just miss or screw up an update or something? I tried searching
> on the errors and the best I could describe it here, on stack
> exchange, and the googles, but maybe I was searching for the wrong
On 26 Aug 2016, at 2:32 AM, Philip Taylor wrote:
>
> 2) \fontdimen 2 is not affected by the :letterspace parameter; arguably it
> should be, such that interword space is stretched in proportion to
> interletter space (and perhaps \fontdimens 3, 4 & 7 should be modified as
> well, and perhaps e
Hi all,
I'm not able to check this minute, but I wonder if lmmono is being
"special-cases" by luaotfload -- would explain the results you're seeing.
In fontspec if you load it with \setmonofont the stretch and shrink should be
forced to zero, but I can agree it would be good to get to the bott
Hi,
(Forwarding this on on behalf of a fontspec user who would like a new feature.
Not currently subscribed so please CC me directly if you have further comment.)
TL;DR: +lfbd feature works in XeTeX but +rtbd does not.
If there are further requests for fontspec OpenType feature support, please
101 - 131 of 131 matches
Mail list logo
