ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
Subject: Re: Using latex font-packages
Date: Tue, 9 Aug 2005 21:36:35 +0200	[thread overview]
Message-ID: <2E87DA9F-1E39-49EE-8C33-5B635B3672BE@uni-bonn.de> (raw)
In-Reply-To: <42F8F4AF.2020307@militzer.net>

It looks like you need to write an runes-enco-file for your font for  
these character names to work. I haven't followed this thread very  
closely, but maybe chapter 3 of the MyWay on Greek fonts can help  
you: http://dl.contextgarden.net/myway/GreekInContext.pdf

Best

Thomas

On Aug 9, 2005, at 8:23 PM, Kai Militzer wrote:

> Hello Hans,
>
>
>>> I'm slowly getting there, only two more problems to solve ;) The  
>>> first thing is, that to use some of the characters in the fontset  
>>> I have to use \th to display them, but I have no idea how to  
>>> accomplish that in context as everytime I use \somerunes \th, or  
>>> \somerunes{\th} ... I get an error message. If i double mascerade  
>>> it like \\th i get the symbols for the characters t and h. I am  
>>> sure there is a way to get this working.
>>>
>>> The next thing, which I guess is to search more on the font- 
>>> subsystem of context, is the fact that I only get my characters  
>>> displayed when viewing the .dvi-file with xdvi. When executing  
>>> texexec --pdf or using dvipdf (or dvips) I get nothing, or the  
>>> charaters in the standard latin-typeset (i.e. ASCII).
>>>
>>
>>
> I solved the second problem. I copied the map and type1 fonts into  
> the directories mentioned in the readme to the font (which where  
> latex-specific). After looking at the texexec output and some try  
> and error, I finaly got all working. So if I now do a texexec --pdf  
> I get a pdf-file with the font included.
>
>
>> how does your code look?
>>
>
> That is my code for testing (nothing more in there, the following  
> is the whole document)
>
> \setuppapersize[a4][a4]
> \starttext
> \startbodymatter
> \loadmapfile[allrunes.map]
> \definefont[somerunes][frumbr sa 1]
> \somerunes{\\th}  % This is where the problem lies. I need to get  
> the \th working to produce a rune
> \stopbodymatter
> \stoptext
>
>
>> can you send me a zip with the tfm files?
>>
>
> I guess you don't need it any more, as the font-inclusion is  
> working now. If you still need it drop me a line.
>
> Regards
> Kai
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context
>

  reply	other threads:[~2005-08-09 19:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-09  8:42 Kai Militzer
2005-08-09 10:39 ` Hans Hagen
2005-08-09 12:18   ` Kai Militzer
2005-08-09 15:03     ` Hans Hagen
2005-08-09 16:32       ` Kai Militzer
2005-08-09 17:51         ` Hans Hagen
2005-08-09 18:23           ` Kai Militzer
2005-08-09 19:36             ` Thomas A. Schmitz [this message]
2005-08-09 20:45               ` Kai Militzer
2005-08-09 20:48             ` Hans Hagen

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=2E87DA9F-1E39-49EE-8C33-5B635B3672BE@uni-bonn.de \
    --to=thomas.schmitz@uni-bonn.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).