ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Thomas Fehige <thomas@fehige.de>
To: ntg-context@ntg.nl
Subject: Re: glyph substitution
Date: Fri, 29 Apr 2016 09:44:20 +0200	[thread overview]
Message-ID: <572310D4.6030208@fehige.de> (raw)
In-Reply-To: <1cad4caa-38f3-a38a-9b09-1492dd6b2129@wxs.nl>


[-- Attachment #1.1: Type: text/plain, Size: 1827 bytes --]

Am 27.04.2016 um 17:10 schrieb Hans Hagen:
> indeed they are lots of small examples (taken from the list or 
> experiments) but they show what can be done
>
> if they crash (no sure what you mean there) it's most likely due to 
> fonts you don't have on your machine

Yes, many of the blank pages or obscure (to me) error messages seem to 
be font-related. I'll have to see to that.

> a lot has been published in articles in user group journals or for 
> meetings, there is a font manual that you can buy for nominal costs, 
> there are some manuals on the website and an extended version of the 
> more technical one that hardly anyone needs will end up in the 
> distribution some day soon, there are examples on stack exchange, in 
> the mail archive an don the wiki ... a lot of this depends on 
> voluntary work so you can hardly complain about it .. anyone is free 
> to provide more documentation and share experiences

Yes, I know, I'm sorry I let my exasperation run free. When I started 
out with LaTeX /and/ typesetting more than two decades ago, I had one 
basic book on LaTeX. Over the years my knowledge of LaTeX, typography, 
layout design and typesetting grew side by side, if somewhat organically 
and unsystematic. Nowadays there's about a metre and a half of bookshelf 
occupied by books on LaTeX, TeX and Typography.

As I make books myself, I'm obviously not averse to buying them. I guess 
the ConTeXt books on fonts and layout will do me good.

> btw, if you want to roll out your own features as in extensions-001 
> then you also need to know what the font provides (or lacks) .. open 
> type fonts can be pretty complex and there is no consistency in how 
> certain features are implemented

Yes, I learned that already. Will these home-made features only work on 
open type fonts?

Cheers -- Thomas

[-- Attachment #1.2: Type: text/html, Size: 2537 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 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
___________________________________________________________________________________

  reply	other threads:[~2016-04-29  7:44 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-19  7:10 uppercase, small caps, numerals and German capital sharp s Thomas Fehige
2016-04-19 12:05 ` Wolfgang Schuster
2016-04-19 12:46   ` Thomas Fehige
2016-04-20 14:03   ` Thomas Fehige
2016-04-20 14:25     ` Wolfgang Schuster
2016-04-20 21:25       ` Thomas Fehige
2016-04-20 21:27       ` Thomas Fehige
2016-04-22 11:35       ` glyph substitution Thomas Fehige
2016-04-22 20:28         ` Hans Hagen
2016-04-25  9:53           ` Thomas Fehige
2016-04-25 12:48           ` Thomas Fehige
2016-04-25 15:49             ` Thomas Fehige
2016-04-25 18:12             ` Thomas Fehige
2016-04-25 20:44               ` Wolfgang Schuster
2016-04-26  8:42                 ` Thomas Fehige
2016-04-27 14:27                 ` Thomas Fehige
2016-04-27 15:10                   ` Hans Hagen
2016-04-29  7:44                     ` Thomas Fehige [this message]
2016-04-29  7:56                       ` Hans Hagen
2016-04-29  8:38                     ` Test Suite Fonts "extensions-001" Thomas Fehige
2016-04-29  9:05                       ` Wolfgang Schuster
2016-05-03  9:22                         ` Setting up TeXworks Thomas Fehige
2016-05-06  8:04                           ` Mojca Miklavec
2016-05-06 11:39                             ` L.S.-Soc&Gam
2016-05-16 15:46                               ` Thomas Fehige
2016-05-16 15:55                                 ` Jean-Pierre Delange
2016-05-17 11:16                                   ` Thomas Fehige
2016-05-17 12:39                                     ` Thomas Fehige
2016-05-17 12:59                                       ` Hans Hagen
2016-05-19 14:09                                         ` Thomas Fehige
2016-05-17 13:22                                       ` Jean-Pierre Delange
2016-05-19 15:16                                         ` Thomas Fehige
2016-05-19 16:15                                           ` Jean-Pierre Delange
2016-05-07 10:49                             ` Thomas Fehige
2016-05-09 11:02                               ` Thomas Fehige
2016-05-15 19:29                                 ` Thomas Fehige
2016-05-16 14:34                                   ` ConTeXt and Scite Thomas Fehige
2016-05-03  9:51                         ` Setting up TeXworks Thomas Fehige
2016-05-03 10:21                           ` Mojca Miklavec
2016-05-03 13:01                             ` Thomas Fehige
2016-04-25 20:47             ` glyph substitution Wolfgang Schuster
2016-04-26  7:42               ` Thomas Fehige

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=572310D4.6030208@fehige.de \
    --to=thomas@fehige.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).