From: Rudolf Bahr <quasi@quasi.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \quotation with yfrak-font?
Date: Thu, 26 Dec 2013 23:18:45 +0100 [thread overview]
Message-ID: <20131226221845.GA8259@mini> (raw)
In-Reply-To: <A7B1E593-1E7F-4BA2-9F66-659E51687BA3@gmail.com>
On Thu, Dec 26, 2013 at 08:49:30PM +0100, Wolfgang Schuster wrote:
>
> Have you tried the unifraktur fonts, as you can see on the website the font has features to change
> the umlauts and also to replace the normal s with the long s.
>
> \definefontfamily[mainface][rm][Unifraktur Maguntia]
>
> \setupbodyfont[mainface]
>
> \definefontfeature [longs] [cv11=yes]
> \definefontfeature [diaeresis] [cv15=yes]
>
> \mainlanguage[de]
>
> \starttext
>
> \input knuth
>
> schönstes – {\feature[+][longs]schönstes}
>
> ſchön Üben – {\feature[+][diaeresis]ſchön Üben}
>
> \quotation{Quoted text}
>
> \stoptext
>
> Wolfgang
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 ...
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.
I know that many people write German texts in this manner, because they don't know it better, and
perhaps it's allowed in English texts, I don't know, but it's rather ugly in German ones.
In yfrak I have to describe in a special manner end "s" and umlauts with a little "e"
on top too, but its very easy and short:
middle "s" = "s", the normal one,
end "s" = "s:"
"ä" = "ä" or "*a", "ö" = "ö" or "*o" and so forth.
The only error is that \quotation{...} is not possible. Perhaps yfrak will be repaired one day.
Ok, I admit, it would be possible to write a text with the right characters in Unifraktur Maguntia,
but with what expense!
I tried Unifraktur Maguntia after having it transcoded into .otf by fontforge and saw, that
\quotation{...} worked well. As I see now the transfering into .otf wasn't necessary. I will
preserve your above example. Thanks, Wolfgang.
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
___________________________________________________________________________________
next prev parent reply other threads:[~2013-12-26 22:18 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 [this message]
2013-12-27 3:34 ` Henning Hraban Ramm
2013-12-27 3:48 ` Wolfgang Schuster
2013-12-27 7:13 ` Rudolf Bahr
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=20131226221845.GA8259@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).