From: "Ch. B." <metan0r@gmx.de>
To: ntg-context@ntg.nl
Subject: Re: Using Bold SmallCaps in LuaTeX - typescript
Date: Mon, 29 Nov 2010 13:27:25 +0100 [thread overview]
Message-ID: <201011291327.26307.metan0r@gmx.de> (raw)
In-Reply-To: <A2E1FD23-AB15-4FE2-8FBA-692926A5F8AF@awi.de>
[-- Attachment #1: Type: Text/Plain, Size: 2750 bytes --]
Am Montag, 29. November 2010, um 12:50:01 schrieb Florian Wobbe:
> On Nov 29, 2010, at 12:40 , Ch. B. wrote:
> > Am Montag, 29. November 2010, um 09:17:10 schrieb Florian Wobbe:
> >> On Nov 29, 2010, at 00:29 , ... wrote:
> >>> Good evening!
> >>>
> >>> First of all, I'm new to this list and also a context/luatex newbe. I
> >>> have some experience with LaTeX.
> >>> I want to use a font (Neutraface2) in my documents and I'm struggeling
> >>> with the typescript. I'm not able to get bold SmallCaps working (the
> >>> bold face .otf file has the feature smcp, I checked).
> >>> I tried various combinations and variations of \bf \sc in my document.
> >>> It gives me bold OR smallcaps, but not bold AND smallcaps. Whats wrong
> >>> here? Can someone give me an example typescript that I could modify to
> >>> fit the Neutraface2 font? My attempt to make one is attached.
> >>>
> >>> Greetings,
> >>> Chris
> >>
> >> Hi Chris,
> >>
> >> it does not work for pagella either. Did you try \setff{smallcaps} \bf
> >> instead?
> >>
> >> \usetypescript[pagella]
> >> \setupbodyfont[pagella]
> >>
> >> \starttext
> >> {\setff{smallcaps} This is in {\bf bold} SmallCaps} (works).
> >> {\sc This is in {\bf bold} SmallCaps} (does not).
> >> \stoptext
> >>
> >> Florian
> >
> > Hi Florian,
> >
> > that does work, thank you very much.
> > I assume the \setff means something like set font feature. If so, I
> > could shorten my typescript and only specify the 4 main font faces
> > (regular, bold italic, bold-italic) since the fonts all have all the
> > opentype features i need (onum & smcp etc.) And these can be accessed
> > via \setff{feature}, I guess.
>
> Yes, you can define for instance
>
> \definefontfeature[dlig][default][dlig=yes] % Discretionary Ligatures:
> Activates uncommon ligatures
> \definefontfeature[frac][default][frac=yes,numr=yes] % Fractions e.g. 3/4
> \definefontfeature[sups][default][sups=yes] % Superscript
> \definefontfeature[subs][default][subs=yes] % Subscript
>
> and access the font features with \setff{dlig}, \setff{subs} etc.
>
> Florian
Wonderfull!
I'm starting to get the hang of it. Even the stylistic sets work like a charm.
I've attached the output file in case you want to have a look at what I'm doing
here.
Now one last question would be: How can I insert a certain character with its
opentype name? For example \insertopentypecharacter{f_f_h.alt}. That would be
cool because otfinfo -g shows all the glyph names and one must not fiddle arount
with hex numbers or char-stuff.
In XeTeX it is possible to do so with \XeTeXglyph\XeTeXglyphindex"Q.alt1" (or
Q.alt2). That would access the first (or second) alternate glyph for the letter
Q.
You really helped a lot here. Thank you!
Chris
[-- Attachment #2: test.pdf --]
[-- Type: application/pdf, Size: 20125 bytes --]
[-- Attachment #3: Type: text/plain, Size: 486 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2010-11-29 12:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-28 23:29 ...
2010-11-29 8:17 ` Florian Wobbe
2010-11-29 11:40 ` Ch. B.
2010-11-29 11:50 ` Florian Wobbe
2010-11-29 12:27 ` Ch. B. [this message]
2010-11-29 12:41 ` Khaled Hosny
2010-11-29 13:38 ` Ch. B.
2010-11-29 13:42 ` Wolfgang Schuster
2010-11-29 14:20 ` Khaled Hosny
2010-11-29 14:36 ` Ch. B.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201011291327.26307.metan0r@gmx.de \
--to=metan0r@gmx.de \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).