From: Hans Hagen <pragma@wxs.nl>
Subject: Re: \uchar and italics question
Date: Thu, 19 Jan 2006 11:42:49 +0100 [thread overview]
Message-ID: <43CF6D29.9060909@wxs.nl> (raw)
In-Reply-To: <36EA006B-4A65-4204-8642-B1BD967246FD@zonnet.nl>
sjoerd siebinga wrote:
> Hi Hans,
>
> On 19 Jan 2006, at 10:43, Hans Hagen wrote:
>
>> can you test with:
>>
>>
>> \unexpanded\def\unicodeglyph#1#2% watch the double mapping
>>
>> �{\begingroup
>>
>> � \getvalue{@@\currentucharmapping\strippedcsname\uchar}{#1}{#2}%
>>
>> � \bodyfontsize\unicodescale\bodyfontsize
>>
>> � \font\unicodefont=\truefontname{\unicodestyle\unicodeone}
>>
>> � � at \currentfontscale\bodyfontsize
>>
>> � \unicodestrut
>>
>> �\unicodefont\unicodecharcommand{\char\unicodetwo\relax}%
>>
>> � \endgroup}
>>
>>
>> i'll change the handlers in not applying a strut by default
>>
>
> This seems to do the trick. The bold glyphs look fine. There is
> however one oddity �in italics�with the circumflex and caron on
> capitals and the macron in general. They are so vague that they are
> hardly visible.
that's a font characteristic
Hans
next prev parent reply other threads:[~2006-01-19 10:42 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
2006-01-19 9:43 ` Hans Hagen
2006-01-19 10:30 ` sjoerd siebinga
2006-01-19 10:42 ` Hans Hagen [this message]
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=43CF6D29.9060909@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).