ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re:  [OT] − RobotoSlab Italics… or not
Date: Sun, 24 Nov 2013 12:53:05 +0100	[thread overview]
Message-ID: <5291E8A1.3080408@wxs.nl> (raw)
In-Reply-To: <52910113.7000503@renaud.io>

On 11/23/2013 8:25 PM, Renaud Aubin wrote:
> Le 23/11/2013 19:08, Wolfgang Schuster a écrit :
>> Am 23.11.2013 um 18:51 schrieb Renaud Aubin <root@renaud.io>:
>>
>>> Hi folks,
>>>
>>> I'm working on a Roboto typescript and starting from the work done by
>>> Zen Lima back in last July, I would like to push things further.
>>> Since I work on some Android projects and use Google Keep mostly on a
>>> daily basis, I was surprised to not find italics for the RobotoSlab
>>> (either on the web or by extracting the assets of the Keep package).
>>>
>>> Why am I surprised: Keep do have serif title placeholders for the new
>>> note EditText and I see it everyday!
>>>
>>> $ mtxrun --script font --list --all --pattern=robotoslab
>>>
>>> robotoslab          robotoslabbold      RobotoSlab-Bold.ttf
>>> robotoslabbold      robotoslabbold      RobotoSlab-Bold.ttf
>>> robotoslablight     robotoslablight     RobotoSlab-Light.ttf
>>> robotoslabregular   robotoslabregular   RobotoSlab-Regular.ttf
>>> robotoslabthin      robotoslabthin      RobotoSlab-Thin.ttf
>>>
>>> OK, RobotoSlab fonts are accessible and I have a working typescript to
>>> use RobotoSlab with ConTeXt MkIV (I'll made the git repo public soon).
>>> At first, my thoughts are: nevermind the Slab italics but now, I'm
>>> curious since Inkscape, LibreOffice, … propose the italic and bolditalic
>>> features of the RobotoSlab (check out the attached font-manager screenshot).
>>> I've worked with different kind of fonts'family (more or less complete)
>>> and used and modified many typescripts in my ConTeXter's life but there
>>> I should be missing something obvious. Where are the RobotoSlab
>>> Italics??? My experience is that italic and bolditalic should correspond
>>> to files… First guess: no files so the RobotoSlab Italic and BoldItalic
>>> features are just faked ones composed by my GNU/Linux Debian system. No,
>>> I must be wrong here too…
>>>
>>> Any thoughts on "The Quest of the Hidden Italics of the RobotoSlab fonts!“?
>>
>> The font has no italic but inkscape slants the regular and bold styles to get them,
>> you can do the same in context with the slant key from \definefontfeature.
>>
>> \definefontfeature[slanted][default][mode=base,slant=.25]
>>
>> \definefontfamily[roboto][rm][Roboto Slab][it=features:slanted,bi=features:slanted]
>>
>> \setupbodyfont[roboto]
>>
>> \starttext
>> Regular {\it Italic} {\bf Bold} {\bi BoldItalic}
>> \stoptext
>>
>> Wolfgang
>> ___________________________________________________________________________________
>> 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
>> ___________________________________________________________________________________
>
> Thank you Wolfgang,
>
> I've made a repo: https://github.com/nibua-r/roboto-context
> Reviews are always welcome!
>
> Any chance that this typescript could find a way to the main ConTeXt distro?

normally typescripts like that end up in tex/context/third (maybe at 
some point we can collect extra typescripts in one package)

a few suggestions:

\definefontfeature[slanted][default][mode=base,slant=.25]

best define "roboto-slanted" as you don't want to overload other 
definitions of slanted and this is rather font specific .. and are you 
sure you want base mode here?

\definefontfeature[roboto-slanted][slant=.25]

\definefontsynonym [\s!SerifItalic] [\s!Serif] 
[\s!features={default,roboto-slanted}]

should also work and delays default

also, name type typescript type-imp-roboto.tex (or .mkiv)

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2013-11-24 11:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-23 17:51 Renaud Aubin
2013-11-23 18:08 ` Wolfgang Schuster
2013-11-23 19:25   ` Renaud Aubin
2013-11-24 11:53     ` Hans Hagen [this message]
2013-11-24 14:51       ` Renaud Aubin
2013-11-24 14:53       ` Wolfgang Schuster

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=5291E8A1.3080408@wxs.nl \
    --to=pragma@wxs.nl \
    --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).