ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: "Gour D." <gour@atmarama.net>
Subject: Re: simplefonts or Typecripts
Date: Fri, 13 Aug 2010 17:58:55 +0200	[thread overview]
Message-ID: <4C656BBF.2080601@wxs.nl> (raw)
In-Reply-To: <20100813130348.7af18ec9@atmarama.noip.me>

On 13-8-2010 1:03, Gour D. wrote:
> Hello!
>
> I'd like to (finally) dive into ConTeXt (MkIV) using it for everything
> and stop using LyX/LaTeX...ConText is installed via
> context-minimals-git package on Archlinux (thank you Aditya).
>
> The 'Using fonts' section on wiki says:
>
> Handling fonts in LuaTeX can be done
>
>      * in a simple but limited way, using the simplefonts module;
>      * in the standard way, using TypeScripts
>
> and I've tried example with Delicious font (too bad there is no
> Croatian characters available) and it works.
>
> Considering I never learnt TypeScripts mechanism (and managed to
> forget most of ConteXr I knew when fiddling with it some years ago), I
> wonder if 'simplefonts' is THE way to go with fonts in MkIV and/or is
> there something one may miss by not using TypeScripts mechanism?

it depends ... simplefonts uses some heuristics and therefore can make 
it easier but not all fonts fit into a systematic approach

for a long time project making a few typescripts (just use those defined 
at the end of type-otf.mkiv as template) and using file: is more robust 
esp as it will nicely fail when something fundamental has changed (names 
or so)

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:[~2010-08-13 15:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-13 11:03 Gour D.
2010-08-13 15:58 ` Hans Hagen [this message]
2010-08-13 16:50   ` Gour D.
2010-08-13 19:11   ` Gour D.
2010-08-13 20:35     ` other markup to ConTeXt (was: simplefonts or Typecripts) Henning Hraban Ramm
2010-08-13 22:56       ` John Haltiwanger
2010-08-14  5:19       ` other markup to ConTeXt Gour D.
2010-08-14  9:23         ` Philipp Gesang
2010-08-14  9:31           ` John Haltiwanger
2010-08-14  9:50             ` Khaled Hosny
2010-08-14  9:52           ` Hans Hagen
2010-08-14 10:23             ` Philipp Gesang
2010-08-14 12:47           ` Henning Hraban Ramm

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=4C656BBF.2080601@wxs.nl \
    --to=pragma@wxs.nl \
    --cc=gour@atmarama.net \
    --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).