From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: Problems with: 1) French guillemets and Big5 in regexps, 2) QP filename MIME
Date: 23 Dec 1999 12:17:13 +0100 [thread overview]
Message-ID: <vaf7li5x5xi.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: Georges KO's message of "Thu, 23 Dec 1999 18:16:33 +0800"
Georges KO <gko@gko.net> writes:
> Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
>
> > Maybe Lars should add a -*- coding: latin1 -*- to the gnus*.el files
> > which contain non-ASCII characters?
>
> Yeah, that should be the best way...
So, could anybody with CVS access do that? (I don't have that
access.)
And what happens when you byte-compile a file with such a tag in it?
Will the *.elc file be okay for all language environments?
kai
--
A preposition is not a good thing to end a sentence with.
next prev parent reply other threads:[~1999-12-23 11:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-23 1:49 Georges KO
1999-12-23 5:45 ` Georges KO
1999-12-23 9:53 ` Kai Großjohann
1999-12-23 10:16 ` Georges KO
1999-12-23 11:17 ` Kai Großjohann [this message]
1999-12-23 19:28 ` Florian Weimer
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=vaf7li5x5xi.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--cc=ding@gnus.org \
/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).