ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Rudolf Bahr <quasi@quasi.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \quotation with yfrak-font?
Date: Fri, 27 Dec 2013 08:13:20 +0100	[thread overview]
Message-ID: <20131227071320.GA14748@mini> (raw)
In-Reply-To: <37930365-0702-4C6C-94E1-CC61BC9B6215@gmail.com>


> > On Thu, Dec 26, 2013 at 08:49:30PM +0100, Wolfgang Schuster wrote:
> > 
> > 
> > This is the answer of my context (version: 2013.05.28 00:36):
> > 
> > l.2 \definefontfamily
> >                   [mainface][rm][Unifraktur Maguntia]
> > ? h
> > The control sequence at the end of the top line
> > of your error message was never \def'ed. If you have …

> 
> Replace the \definefontfamily line with
> 
>   \definetypeface [mainface] [rm] [specserif] [Unifraktur Maguntia] [default]
> 
> because the new font command was added last autumn and your TeXLive installation
> uses a older context version (not sure if the \feature command exists there).
> 

Yes, your suggested replacement works well! Thank you.


> > I don't know, whether there apply in English texts the same rules as in German ones with respect 
> > to Fraktur or similar fonts.
> > The written Knuth text (in the .pdf-file) would contain some right "s" at end of words and syllabs 
> > as in "Thus", "components", "activities" or the third "s" in successfull, but the rest of all the 
> > other "s" would be wrong. 
> 
> What do you expect from a text with doesn’t contain any long s in the input.
> 
> Maybe your expecting from context to make the right choice for the s but there
> are cases where you won’t get the correct output and manual correction
> is necessary.

No, I don't expect contex to make the right choice for me instead! That won't be possible, 
of course: It ought to know, where syllables end. But then ... I'm asking me, why did you 
send me this Knuth-text with many wrong "s"es and without any quotation at all?

Let's finish the discussion here. The subject was: "\quotation with yfrak-font?" and
we went off course. I thank you, Wolfgang and Hraban, for having answered!

Happy New Year to all contexters in the world!

Rudolf
___________________________________________________________________________________
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-12-27  7:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-22 10:26 Rudolf Bahr
2013-12-22 11:38 ` Wolfgang Schuster
2013-12-25 11:25   ` Rudolf Bahr
2013-12-26  8:27     ` Henning Hraban Ramm
2013-12-26 18:56       ` Rudolf Bahr
2013-12-26 19:49         ` Wolfgang Schuster
2013-12-26 22:18           ` Rudolf Bahr
2013-12-27  3:34             ` Henning Hraban Ramm
2013-12-27  3:48             ` Wolfgang Schuster
2013-12-27  7:13               ` Rudolf Bahr [this message]

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=20131227071320.GA14748@mini \
    --to=quasi@quasi.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).