Gnus development mailing list
 help / color / mirror / Atom feed
From: Hrvoje Niksic <hniksic@srce.hr>
Subject: Re: Non-MULE XEmacs default charset
Date: 16 Jan 1999 00:33:27 +0100	[thread overview]
Message-ID: <kign23kun5k.fsf@jagor.srce.hr> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "15 Jan 1999 23:17:36 +0100"

Lars Magne Ingebrigtsen <larsi@ifi.uio.no> writes:

> If we're running under a non-MULE XEmacs, and we find non-ascii
> chars, then what charset are those in?  Is there a locale or
> something that can be inspected?

No.

For example, I run in a non-Mule XEmacs with latin2 fonts (as set by
Xdefaults), and the non-ASCII chars are likely latin2 -- however,
XEmacs doesn't know that by default.  Under TTY's, things work so that 
I instruct my terminal (emulator) to display latin2 fonts, and XEmacs
does the (more or less) right thing by default.

I don't run in a Croatian locale, because that would be disastrous for 
other things.  Besides, not all operating systems implement a Croatian 
locale.

> I think the user should be prompted when this can't be determined.

Yes.  It would also be nice to provide a variable for this, say
`message-default-charset', which the user can set in their .gnus and
avoid the question.


  reply	other threads:[~1999-01-15 23:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-01-15 22:17 Lars Magne Ingebrigtsen
1999-01-15 23:33 ` Hrvoje Niksic [this message]
1999-01-16 16:28   ` Lars Magne Ingebrigtsen
1999-01-16 17:11     ` Hrvoje Niksic
1999-01-16 22:47       ` Lars Magne Ingebrigtsen
1999-01-20 21:20   ` Kai.Grossjohann
1999-01-21 13:53     ` Hrvoje Niksic

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=kign23kun5k.fsf@jagor.srce.hr \
    --to=hniksic@srce.hr \
    /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).