From: Khaled Hosny <khaledhosny@eglug.org>
To: ntg-context@ntg.nl
Subject: Re: Fraktur fonts
Date: Thu, 13 Jun 2013 09:36:40 +0200 [thread overview]
Message-ID: <20130613073639.GA20619@khaled-laptop> (raw)
In-Reply-To: <20130612092603.GA1090@mini>
On Wed, Jun 12, 2013 at 11:28:12AM +0200, Rudolf Bahr wrote:
> both with "context" and "texexec", but I don't achieve the desired result.
> "texexec" displays a font somehow similar to Fraktur, but not a very nice one and
> much to broad; and it seems to have no different "s" (one inner-word and one word-end
> or syllable-end "s") as needed in Fraktur. And, my "texexec" doesn't know anything
> about umlauts and sharp s.
> Whereas my "context" (translating the same program), dosn't know Fraktur, but knows
> umlauts.
For "context" (ConTeXt MkIV), you may want to try an OpenType Fraktur
font, like:
http://unifraktur.sourceforge.net/
The long s versus rounded s distinction is a text input issue, you have
to inter the correct s according the position in the word (the rules are
complex, different from a country to country and from a period to
another).
Regards,
Khaled
___________________________________________________________________________________
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-06-13 7:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-12 9:28 Rudolf Bahr
2013-06-13 7:19 ` luigi scarso
2013-06-13 7:36 ` Khaled Hosny [this message]
2013-06-13 22:55 ` Hans Hagen
2013-06-21 16:53 ` Rudolf Bahr
2013-06-21 19:01 ` Pablo Rodríguez
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=20130613073639.GA20619@khaled-laptop \
--to=khaledhosny@eglug.org \
--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).