From: sjoerd siebinga <sjoerdsiebinga@zonnet.nl>
Subject: Re: \uchar and italics question
Date: Thu, 19 Jan 2006 08:21:34 +0100 [thread overview]
Message-ID: <38818B77-53E9-4526-8D24-8759360B515D@zonnet.nl> (raw)
In-Reply-To: <43CECEBD.7030404@wxs.nl>
[-- Attachment #1.1: Type: text/plain, Size: 1448 bytes --]
Hi Hans,
On 19 Jan 2006, at 00:26, Hans Hagen wrote:
> did you try:
>
> \defineunicodefont [MySwitch] [MyOwnFont] % [command=
> \insertunicodeglyph]
>
> \definefontsynonym [MyOwnFontRegular] [Sans]
> \definefontsynonym [MyOwnFontItalic] [SansItalic]
>
> \MySwitch \uchar... \it ...
Yes, but still no bold or italics. Maybe there is something wrong
with my definitions.
[code]
\defineunicodefont [MySwitch] [mylinostar] % [command=
\insertunicodeglyph]
\loadmapfile[palatinolinostar_01xx-starling-linostar]
\definefontsynonym [mylinostarRegular01] [palatinolinostar_01xx-
PalatinoLinoStar]
\definefontsynonym [mylinostarBold01] [palatinolinostar_01xx-
PalatinoLinoStarBold]
\definefontsynonym [mylinostarItalic01] [palatinolinostar_01xx-
PalatinoLinoStarItalic]
\starttext
{\MySwitch \uchar{1}{1}} \\
{\MySwitch \it \uchar{1}{1}} \\
{\MySwitch \bf \uchar{1}{1}} \\
\stoptext
[/code]
I have installed the font without errors with TeXfont.
>
> The uchar command is a wrapper around a handler; currently only
> chinese and japanese handlers are defined, and you need a defaultcase.
What do you mean by defaultcase?
>
> (btw this mechanism is rather complex because it needs to handle
> (1) fake unicode, i.e. you can define remappers, (2) unicode, (3)
> utf as input encoding, (4) special handlers, (5) ..... ) Even i get
> lost in the code -)
I see what you mean. The font-uni.tex is an impressive piece of coding.
Sjoerd
[-- Attachment #1.2: Type: text/html, Size: 3552 bytes --]
[-- Attachment #2: Type: text/plain, Size: 139 bytes --]
_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
next prev parent reply other threads:[~2006-01-19 7:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-17 16:57 sjoerd siebinga
2006-01-17 22:54 ` Hans Hagen
2006-01-18 12:10 ` Mojca Miklavec
2006-01-18 14:22 ` Hans Hagen
2006-01-18 20:04 ` sjoerd siebinga
2006-01-18 23:26 ` Hans Hagen
2006-01-19 7:21 ` sjoerd siebinga [this message]
2006-01-19 9:43 ` Hans Hagen
2006-01-19 10:30 ` sjoerd siebinga
2006-01-19 10:42 ` Hans Hagen
2006-01-19 13:17 ` Henning Hraban Ramm
2006-01-19 16:35 ` sjoerd siebinga
2006-01-19 17:20 ` Hans Hagen
2006-01-19 18:50 ` Henning Hraban Ramm
2006-01-19 19:44 ` Hans Hagen
2006-01-19 20:51 ` sjoerd siebinga
2006-01-20 9:26 ` Henning Hraban Ramm
2006-01-20 17:30 ` Mojca Miklavec
-- strict thread matches above, loose matches on Subject: below --
2006-01-18 6:56 sjoerd siebinga
2006-01-17 16:57 sjoerd siebinga
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=38818B77-53E9-4526-8D24-8759360B515D@zonnet.nl \
--to=sjoerdsiebinga@zonnet.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).