From: rf@cl.cam.ac.uk (Robin Fairbairns)
Subject: Re: Pitfalls of switching to {ucs} and [utf8x]{inputenc} ?
Date: 1 Jul 2005 08:57:17 GMT [thread overview]
Message-ID: <da30hd$fc$3@gemini.csx.cam.ac.uk> (raw)
In-Reply-To: 1120206233.651633.41540@g49g2000cwa.googlegroups.com
"Adam Funk" <a24061@yahoo.com> writes:
>Pascal Bourguignon wrote:
>> > But before I do this to my thesis, I'd like to know if it's really that
>> > simple or if there are any pitfalls? If it matters, my thesis contains
>> > a lot of occurrences of Swedish special characters in \text{...}
>> > commands in math mode.
>>
>> Not at all. Before you do this on your thesis, you want to learn
>> about the command cp(1).
>
>:-)
>
>It's on CVS.
oh, goodie. can we all contribute?
--
Robin (http://www.tex.ac.uk/faq) Fairbairns, Cambridge
next prev parent reply other threads:[~2005-07-01 8:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-30 14:51 Pitfalls of switching to {ucs} and [utf8x]{inputenc} ? Adam Funk
2005-06-30 15:23 ` Peter Dyballa
2005-06-30 18:44 ` Pascal Bourguignon
2005-07-01 8:00 ` Markus Kuhn
2005-07-01 8:26 ` Adam Funk
2005-07-01 8:23 ` Adam Funk
2005-07-01 8:57 ` Robin Fairbairns [this message]
2005-07-01 18:20 ` Adam Funk
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='da30hd$fc$3@gemini.csx.cam.ac.uk' \
--to=rf@cl.cam.ac.uk \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).