From: Hans Hagen <pragma@wxs.nl>
Subject: Re: unicode fontdefinition
Date: Fri, 25 Nov 2005 00:05:42 +0100 [thread overview]
Message-ID: <43864746.4040904@wxs.nl> (raw)
In-Reply-To: <B9D59CDC-D805-4680-A5CB-A90BB32EBFF9@zonnet.nl>
sjoerd siebinga wrote:
> Hi all,
>
> I am currently typesetting a collection of articles that use a great
> number of unicodeglyphs from 19 vectors. All the regular glyphs turn
> up fine, but I am unable to get the bold and italic versions of the
> glyphs. I have made encoding files for all the vectors using the
> xsl-scripts from Adam Lindsay and installed them via texfont.�
>
> The sourcefile is an xml-file with decimal-unicode-entities that are
> mapped to the \uchar command by the \defineXMLentity command.
>
> I have defined the unicode fontsynonyms as follows:
>
> <code>
>
> \loadmapfile[palatinolinostar_01xx-starling-linostar]
> \definefontsynonym [UnicodeRegular01]
> [palatinolinostar_01xx-PalatinoLinoStar] [encoding=palatinolinostar_01xx]
> \definefontsynonym [UnicodeBold01]
> [palatinolinostar_01xx-PalatinoLinoStarBold]�[encoding=palatinolinostar_01xx]
> \definefontsynonym [UnicodeItalic01]
> [palatinolinostar_01xx-PalatinoLinoStarItalic]�[encoding=palatinolinostar_01xx]
>
more a question for adam ...
> \starttypescript [my] [starling-linostar] [texnansi,palatinolinostar_01xx]
the texnansi,palatinolinostar_01xx will become \typescriptthree which is
a wrong encoding name
> \definetypeface [starling-linostar] [rm] [serif] [linostar] [default]
> [encoding=\typescriptthree]
> \stoptypescript
>
>
> \usetypescript [my] [starling-linostar]
>
> \setupbodyfont[starling-linostar,rm,10pt]
> </code>
>
> Could somebody tell me what I am doing wrong?�
>
you need something:
\starttypescript [map] [linostar] [texnansi]
\loadmapfile [\typescripttwo-starling-linostar.map]
\stoptypescript
\starttypescript [serif] [linostar] [texnansi]
\definefontsynonym [linostar][\typescriptthree-PalatinoLinoStar]
[encoding=\typescriptthree]
\definefontsynonym
[linostar-Italic][\typescriptthree-PalatinoLinoStarItalic]
[encoding=\typescriptthree]
\definefontsynonym
[linostar-Bold][\typescriptthree-PalatinoLinoStarBold]
[encoding=\typescriptthree]
\stoptypescript
\starttypescript [serif] [linostar] [name]
\setups[font:fallback:serif]
\definefontsynonym [Serif] [linostar]
\definefontsynonym [SerifItalic] [linostar-Italic]
\definefontsynonym [SerifBold] [linostar-Bold]
\stoptypescript�
\starttypescript[starling-linostar] [texnansi]
\definetypeface [starling-linostar] [rm][serif][linostar][default]
[encoding=\typescriptthree]
\stoptypescript
\usetypescript[starling-linostar][texnansi]
\setupbodyfont[starling-linostar,rm,10pt]
since the \typescriptthree-PalatinoLinoStarBold expands to
texnansi-PalatinoLinoStarBold ... do you have that font file?
Hans
next prev parent reply other threads:[~2005-11-24 23:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-24 8:19 sjoerd siebinga
2005-11-24 23:05 ` Hans Hagen [this message]
2005-11-25 13:17 ` sjoerd siebinga
2005-11-25 14:25 ` 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=43864746.4040904@wxs.nl \
--to=pragma@wxs.nl \
--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).