From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: Questions/Comments
Date: Tue, 11 Sep 2001 18:36:20 +0200 [thread overview]
Message-ID: <5.1.0.14.1.20010911183140.025dee60@server-1> (raw)
In-Reply-To: <20010911132918.B1521@wimsey>
At 01:29 PM 9/11/2001 +0200, Marco Kuhlmann wrote:
>How can I play with different protrusion values? The named
>quotation marks are no single characters, but combinations, like
>
> \def\lowerleftdoubleninequote{,,}
>But the protrusion information should be assigned to
>characters, right?
there is a way out by having a font with dummy chars and put that one at
the boundary but i don't know how to make one -)
\setupsynonyms
> [acronym]
> [textstyle=versface]
>
>While this works fine in normal text, \subsection{\URL} goes
>nuts: It prints out versface instead of using it to switch to
>another font. Is this a bug or a feature? :-)
no, you can use \definealternativestyle [see font-ini and bet manual] to
define a style that acts differently in normal text and section headers
>does not yield the desired effect, though:
>
>[concerning abbreviations with colon lookahead]
>
> > This is kind of tricky because capitalizing interferes with
> > look ahead. I can consider adding a hook but this is a
> > delicate process [not quickly hackable]
>
>I think it would be worth it, though. Not only German is
>concerned, and it is much more consistent to be able to type
>
> We offer foo, bar, baz, \ETC. And gnus. than
> We offer foo, bar, baz, \ETC And gnus.
hm, i can look into it later, since using real fake caps is an option
thereby avoiding \kap
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
next prev parent reply other threads:[~2001-09-11 16:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-10 16:57 Questions/Comments Marco Kuhlmann
2001-09-11 8:27 ` Questions/Comments Hans Hagen
2001-09-11 11:29 ` Questions/Comments Marco Kuhlmann
2001-09-11 16:36 ` Hans Hagen [this message]
2001-09-12 13:58 ` Questions/Comments Marco Kuhlmann
2001-09-14 11:10 ` Questions/Comments Hans Hagen
2001-09-14 19:39 ` Questions/Comments Marco Kuhlmann
2001-09-14 20:00 ` Questions/Comments Marco Kuhlmann
2001-09-17 16:34 ` Questions/Comments Hans Hagen
2001-09-17 16:30 ` Questions/Comments 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=5.1.0.14.1.20010911183140.025dee60@server-1 \
--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).