From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: issue with font in typing environment
Date: Sun, 2 Feb 2014 10:53:42 +0100 [thread overview]
Message-ID: <223B4711-43A8-451B-93A0-02EB93BEAEBE@gmail.com> (raw)
In-Reply-To: <52EE02C5.3040502@gmx.es>
Am 02.02.2014 um 09:33 schrieb Pablo Rodriguez <oinos@gmx.es>:
> Dear list,
>
> I converted the monospace fonts of txfonts
> (http://www.ctan.org/tex-archive/fonts/txfonts/pfb) from pbf to otf
> using FontForge. They work fine (http://www.ousia.tk/ryfonts.zip).
>
> But the issue is shown in the following sample (beta from 2014.02.01 14:22):
>
> \definefontfamily[mainface][mono][ryt1xtt][bf=ryt1xbtt]
> \setupbodyfont[mainface]
> \definetyping[TeXcode][option=TEX]
> \starttext
> \starttyping
> \ConTeXt\ is
> \stoptyping
> \startTeXcode
> \ConTeXt\ is
> \stopTeXcode
> \stoptext
>
> If option=TEX is enabled, there is no space after the backslash.
>
> I have checked the font and it seems to work fine, so it might be a bug.
I can reproduce the problem with the type1 fonts:
\starttypescript[serif][txfonts]
\setups[font:fallback:serif]
\definefontsynonym [Serif] [file:t1xtt.afm] [features=complete]
\definefontsynonym [SerifBold] [file:t1xbtt.afm] [features=complete]
\definefontsynonym [SerifCaps] [file:t1xttsc.afm] [features=complete]
\stoptypescript
\starttypescript[mono][txfonts]
\setups[font:fallback:mono]
\definefontsynonym [Mono] [file:t1xtt.afm] [features=none]
\definefontsynonym [MonoBold] [file:t1xbtt.afm] [features=none]
\stoptypescript
\definetypeface [mainface] [rm] [serif] [txfonts] [default]
\definetypeface [mainface] [tt] [mono] [txfonts] [default]
\setupbodyfont[mainface]
\starttext
Regular, {\bf Bold} and {\sc Smallcaps}.
\starttyping[option=tex]
\CONTEXT\ is wonderful!
\stoptyping
\stoptext
Even though this is something that should be fixed using a different font
in truetype/opentype format solves your problem as well. The following
two fonts are similar to the monospaced font of the txfonts package:
- http://www.fontsquirrel.com/fonts/Luxi-Mono
- http://www.fontsquirrel.com/fonts/pt-mono
Wolfgang
___________________________________________________________________________________
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:[~2014-02-02 9:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-02 8:33 Pablo Rodriguez
2014-02-02 9:53 ` Wolfgang Schuster [this message]
2014-02-02 11:34 ` Pablo Rodriguez
2014-02-02 13:14 ` Wolfgang Schuster
2014-02-02 17:20 ` Pablo Rodriguez
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=223B4711-43A8-451B-93A0-02EB93BEAEBE@gmail.com \
--to=schuster.wolfgang@gmail.com \
--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).