From: "Ville Voipio" <Ville.Voipio@kpatents.com>
Subject: Re: Uppercase headings
Date: Fri, 31 Mar 2006 20:06:00 +0300 [thread overview]
Message-ID: <B8B26F211A66434887C806A8DEE3577BFD36@kpsrv1.kpatents.local> (raw)
[-- Attachment #1: Type: text/plain, Size: 1209 bytes --]
> it's nearly impossible to get this working for all features
> (keep in mind that tex has no real feature to map font chars
> to other font chars) esp those with special chars.
I know this is not a trivial question due to the number
of encodings and languages. However, what makes me a bit
puzzled is that the following works fine:
\title{\WORD{Text with åäö etc.} }
So, the mechanism behind \WORD works well. It is just that
I cannot figure out how to use it. I emphasize that it used
to work fine even in the \setuphead definition, but that
was with an old version (April '05).
---
> works ok here (can you try the latest version - beta?)
The version I am trying to use is rather a fresh one:
TeXExec 5.4.3 - ConTeXt / PRAGMA ADE 1997-2005
texexec : TeXExec 5.4.3 - ConTeXt / PRAGMA ADE 1997-2005
texutil : TeXUtil 9.0.1 - ConTeXt / PRAGMA ADE 1992-2006
tex : unknown
context : ver: 2006.03.25 13:21
cont-en : unknown
cont-nl : unknown
Has there been any change after that? If not, I could brew up a
minimal example to illustrate the problem.
BR,
- Ville
[-- Attachment #2: winmail.dat --]
[-- Type: application/ms-tnef, Size: 3017 bytes --]
[-- Attachment #3: Type: text/plain, Size: 139 bytes --]
_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
next reply other threads:[~2006-03-31 17:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-31 17:06 Ville Voipio [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-31 17:25 Ville Voipio
2006-03-31 21:31 ` Hans Hagen
2006-03-31 21:49 ` Hans Hagen
2006-03-31 15:55 Ville Voipio
2006-03-31 16:48 ` Hans Hagen
2006-03-31 16:51 ` Hans Hagen
2006-03-31 17:16 ` Taco Hoekwater
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=B8B26F211A66434887C806A8DEE3577BFD36@kpsrv1.kpatents.local \
--to=ville.voipio@kpatents.com \
--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).