ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <wolfgang.schuster@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Font recognition with command "context", but not with command "texexec"
Date: Sun, 29 Jul 2012 09:34:24 +0200	[thread overview]
Message-ID: <898BA0E1-27D9-4180-8436-556C2D2C3126@gmail.com> (raw)
In-Reply-To: <50143956.7040208@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1738 bytes --]


Am 28.07.2012 um 21:11 schrieb Martin Rimmler <martin.rimmler@googlemail.com>:

> Hi,
> 
> this might be a very simple problem, but I tried to figure it out for some time now without success. Reading manuals, searching with Google, etc. did not help. So if it actually is very simple, I herewith apologize. I really tried to solve it without the mailing list.
> 
> Here is the Problem:
> The command "texexec" ignores the bodyfont setup. When I process the following code
> 
>     \setupbodyfont[gentium]
> 
>     \starttext
>     This little text is enough to demonstrate the problem.
>     \stoptext
> 
> with the command "texexec filename", the default font is used. Only when i use the command "context filename.tex", context uses the font gentium. 
> The gentium font is a truetype font and stored on my system under /usr/share/fonts.
> I use Linux Mint Debian Edition 201204. My .bashrc file contains the following line:
> 
>     export OSFONTDIR="/usr/local/share/fonts;$HOME/.fonts;/usr/share/fonts"
> 
> I use the standalone version of context with pdftex. The command \contextversion returns "2012.07.27 16:41", i.e. the time I last updated it.
> 
> Using the mkiv switch did not help.
> 
>     texexec mkiv filename
> 
> 
> Any comments are welcome.

For MkII you have to load the typescript file and the typescript yourself while for MkIV these two steps are done together with the \setupbodyfont command when the name for the typeface, typescript and file is the same (e.g. gentium and type-gentium).

\usetypescriptfile[type-gentium]
\usetypescript[gentium][texnansi]
\setupbodyfont[gentium]

\starttext
This little text is enough to demonstrate the problem.
\stoptext

Wolfgang


[-- Attachment #1.2: Type: text/html, Size: 2648 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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:[~2012-07-29  7:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-28 19:11 Martin Rimmler
2012-07-29  7:34 ` Wolfgang Schuster [this message]
2012-07-29 13:39   ` Bill Meahan
2012-07-29 20:36     ` Mojca Miklavec
2012-07-29 23:05       ` Hans Hagen
2012-07-30  7:50         ` Mojca Miklavec
2012-07-30  9:06           ` Khaled Hosny
2012-07-30  9:16             ` Mojca Miklavec
2012-07-30 10:31               ` Khaled Hosny

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=898BA0E1-27D9-4180-8436-556C2D2C3126@gmail.com \
    --to=wolfgang.schuster@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).