From: "Mikael Persson" <mickep@math.chalmers.se>
Subject: Re: special characters and \startuseMPgraphic{FunnyFrame}
Date: Mon, 3 May 2004 21:00:38 +0200 (MEST) [thread overview]
Message-ID: <33305.82.182.100.57.1083610838.squirrel@mail.medic.chalmers.se> (raw)
In-Reply-To: <4096920B.8070209@gmx.de>
> Hello,
>
> the following example does not work if the text in the
> \FrameTitle{Blockflötenspielen} contains special characters like öäßé etc.
>
> Has someone a solution for this problem?
>
> Thanks a lot,
>
> Helmut
>
>
I had a similar problem some time ago. But I used the utf regime. The
solution (I dont know if I read it on the list or where it came from) was
to put curly braces around those characters. In this case it would be
\enableregime[utf]
instead of
\enableregime[windows]
and then
These: Blockfl{ö}tenspielen macht Spa{ß}!
I tried this with your doc and it worked.
Probably someone soon comes up with a nicer solution,
Regards, Micke P
prev parent reply other threads:[~2004-05-03 19:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-03 18:40 Helmut Schwertner
2004-05-03 18:57 ` Willi Egger
2004-05-03 19:00 ` Mikael Persson [this message]
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=33305.82.182.100.57.1083610838.squirrel@mail.medic.chalmers.se \
--to=mickep@math.chalmers.se \
--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).