From: luigi scarso <luigi.scarso@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: (fake) bold as font feature
Date: Wed, 28 Mar 2018 11:32:52 +0200 [thread overview]
Message-ID: <CAG5iGsDPnAAYfVwgoj_Jahjp=3=9WM5yie0ngqxCcsBJ_cdfhg@mail.gmail.com> (raw)
In-Reply-To: <cfcf84f3-e7e5-2dbb-daef-d78baf63c035@gmx.es>
On Mon, Mar 26, 2018 at 11:02 PM, Pablo Rodriguez <oinos@gmx.es> wrote:
> On 03/26/2018 07:24 PM, Hans Hagen wrote:
>> On 3/26/2018 4:55 PM, Hans Hagen wrote:
>>> On 3/26/2018 1:40 PM, Pablo Rodriguez wrote:
>>>> Hans,
>>>>
>>>> would it be possible to add a embold feature (similar to the slanted
>>>> font feature) that fakes the bold font with
>>>> \starteffect[both]...\stopeffect and it doesn’t strecht the font?
>>>
>>> much is possible if i can motivate myself
>
> Good to know in order to propose new features :-).
Hm.
Fake bold / slanted / small caps /<what ever> of a base font
are dangerous, there is an high risk to compromise the
legibility of the text (this is especially true nowadays with user
consumer tablets 10" full hd ).
A font is not only glyphs, but also kernings and hints and all these
things must match.
As Knuth shown , the right way is to design from the beginning how
each glyph should be transformed
instead of apply to all the glyphs the same transformation (which is
faster, this is sure).
This is the key concept of metafont --- in my opinion better than the
variable fonts .
I am not saying that this impossible to do in context-mkiv ( *it is*
possible: just see 5.3 Virtual fonts of the luatex reference)
but in the end the result is the same of write the correct
bold/slanted/small caps/<whatever> version of the base font .
--
luigi
___________________________________________________________________________________
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2018-03-28 9:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-26 11:40 Pablo Rodriguez
2018-03-26 14:55 ` Hans Hagen
2018-03-26 17:24 ` Hans Hagen
2018-03-26 21:02 ` Pablo Rodriguez
2018-03-27 7:01 ` Hans Hagen
2018-03-27 16:59 ` Pablo Rodriguez
2018-03-28 9:32 ` luigi scarso [this message]
2018-03-28 10:29 ` Hans Hagen
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='CAG5iGsDPnAAYfVwgoj_Jahjp=3=9WM5yie0ngqxCcsBJ_cdfhg@mail.gmail.com' \
--to=luigi.scarso@gmail.com \
--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).