ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Florian Wobbe <Florian.Wobbe@awi.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: MnSymbol in ConText
Date: Sun, 20 Feb 2011 20:30:53 +0100	[thread overview]
Message-ID: <DEBB36B4-71C2-4A8D-B2B1-9C44435B600B@awi.de> (raw)
In-Reply-To: <AANLkTi=_Jy74x1DaS1ci4QDVYrcZNcYPE_6VB23pe6wp@mail.gmail.com>

>> Is there any way to use MnSymbol in context?
> 
> It is, but somebody needs to write support for it. Both for MKII and MKIV.

The problem is, that luatex refuses to load any of the MnSymbol*.otf font files available from CTAN with an error message. I don't know what is broken with the fonts.

Should you just be interested in the symbols you can fix the otf font with fontforge by reencoding and saving it to a unicode font again. Glyphs with undefined unicode value will be assigned to unicode slots starting from 0xF0000.

Then you can do this:

\definefontsynonym [MnSymbol12U] [name:MnSymbol12Uni]
\starttext
\definedfont [MnSymbol12U at 16pt] ABC XYZ \char"25B7 \char"2660 \char"2720 \char"10391 \char"10393 \char"10335
\stoptext

To print a table with glyphs and unicode values do:

\usemodule[fnt-10]
\starttext
\ShowCompleteFont{name:MnSymbol12Uni}{11pt}{1} % MnSymbol12Uni.otf
\stoptext

I used the following fontforge script to re-generate the font:

#begin fontforge script

#usage: fontforge -script fontBMP2Full.ff MnSymbol12.otf

Open($1);

F1 = $fontname+"Uni" # fontname
F2 = "" # familyname
F3 = $fullname+"Uni" # fullname
F4 = "" # weight
F5 = "" # copyright
F6 = "" # fontversion

#SetFontNames(fontname[,family[,fullname[,weight[,copyright-notice[,fontversion]]]]])
#Sets various postscript names associated with a font. If a name is omitted (or is the
#empty string) it will not be changed. 
SetFontNames(F1,F2,F3,F4,F5,F6)

Reencode("unicode");
Generate($fontname+".otf");
Quit(0);

#end fontforge script

Florian

___________________________________________________________________________________
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:[~2011-02-20 19:30 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-19  0:26 C.
2011-02-19  0:57 ` Arthur Reutenauer
2011-02-19  9:30 ` Mojca Miklavec
2011-02-20 19:30   ` Florian Wobbe [this message]
2011-02-20 19:38     ` Khaled Hosny
2011-02-20 20:01       ` Florian Wobbe
2011-02-21  8:05         ` Taco Hoekwater
2011-02-23 10:59     ` C.
2011-02-23 11:37       ` Wolfgang Schuster
2011-02-23 14:04         ` C.
2011-03-07 16:51         ` Mojca Miklavec
2011-03-05 13:58       ` Steffen Wolfrum
2011-03-05 21:41         ` Hans Hagen
2011-03-07 16:31           ` C.
2011-03-07 16:44             ` Steffen Wolfrum
2011-03-07 18:32               ` Aditya Mahajan
2011-03-07 23:23                 ` Hans Hagen
2011-03-07 23:57                   ` Aditya Mahajan
2011-03-07 17:20           ` Wolfgang Schuster
2011-03-07 18:41             ` Florian Wobbe
2011-03-07 21:21               ` C.

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=DEBB36B4-71C2-4A8D-B2B1-9C44435B600B@awi.de \
    --to=florian.wobbe@awi.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).