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: Thu, 26 Dec 2013 19:56:46 +0100	[thread overview]
Message-ID: <20131226185646.GB23702@mini> (raw)
In-Reply-To: <3E01A401-AD75-4BBD-8392-4402F13BD938@fiee.net>


Hello Hraban,

thank you for answering!

The Fraktur fonts differ in many things from each other. I forgot to mention
the feature of automatic choice of ligatures when they appear in the text. So it's a matter of
not to be forced to change too much in a given text. I solved my problem within 10 minutes by
creating my own \glqq and \grqq. Next time I will strive for a solution with \quotation{...}.

Greetings, Rudolf

On Thu, Dec 26, 2013 at 02:27:10PM +0600, Henning Hraban Ramm wrote:
> Am 2013-12-25 um 17:25 schrieb Rudolf Bahr <quasi@quasi.de>:
> 
> > Nearly all of the hundreds of fraktur-fonts in the world have problems, as reported by the
> > program "fontforge". But even worse, mostly there is a lack of umlauts, 2 of 3 needed 
> > different "s" and a lack of ligatures. And only very, very few of them have in addition to 
> > the normal umlauts written with double points umlauts with a small "e" above instead.
> 
> Usable fraktur fonts with e-umlauts, long s and a set of ligatures I found in my collection only:
> 
> - Bastarda-K, probably by Manfred Klein
> - Unifraktur Maguntia, see http://unifraktur.sourceforge.net/maguntia.html
> 
> (Without e-umlauts there are a lot more.)
> 
> Perhaps you should try to fix the y fonts with Fontforge.
> 
> 
> Greetlings, Hraban
> ---
> http://www.fiee.net/texnique/
> http://wiki.contextgarden.net
> https://www.cacert.org (I'm an assurer)
> 
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
> 
___________________________________________________________________________________
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-26 18:56 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 [this message]
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

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=20131226185646.GB23702@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).