* CT: text/plain; charset=us-ascii, CTE: 8bit
@ 1998-10-25 19:53 Bjørn Mork
1998-10-25 22:38 ` Lars Magne Ingebrigtsen
0 siblings, 1 reply; 8+ messages in thread
From: Bjørn Mork @ 1998-10-25 19:53 UTC (permalink / raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 201 bytes --]
Doesn't look good, does it? pgnus has suddenly started using us-ascii
instead of iso-8859-1. Is there some new variable I should be setting
or is this a bug?
Bjørn <- 8bit "encoded" iso-8859-1
.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: CT: text/plain; charset=us-ascii, CTE: 8bit
1998-10-25 19:53 CT: text/plain; charset=us-ascii, CTE: 8bit Bjørn Mork
@ 1998-10-25 22:38 ` Lars Magne Ingebrigtsen
1998-10-26 19:17 ` Dave Love
0 siblings, 1 reply; 8+ messages in thread
From: Lars Magne Ingebrigtsen @ 1998-10-25 22:38 UTC (permalink / raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 648 bytes --]
"Bjørn Mork" <bmork@dod.no> writes:
> Doesn't look good, does it? pgnus has suddenly started using us-ascii
> instead of iso-8859-1.
Sweet brother of Festus.
(find-charset-region (point-min) (point-max))
in --unibyte mode returns `(ascii)', no matter how many æøå's you put
into the buffer.
*gack*
Er...
Ok, if one runs in unibyte mode, and there are characters that are not
in the \000-\177 range, then the characters must be the result of
current-language-environment. How does one go from
current-language-environment to a charset?
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: CT: text/plain; charset=us-ascii, CTE: 8bit
1998-10-25 22:38 ` Lars Magne Ingebrigtsen
@ 1998-10-26 19:17 ` Dave Love
1998-10-26 21:31 ` Lars Magne Ingebrigtsen
0 siblings, 1 reply; 8+ messages in thread
From: Dave Love @ 1998-10-26 19:17 UTC (permalink / raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 876 bytes --]
>>>>> "Lars" == Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
Lars> Ok, if one runs in unibyte mode, and there are characters that
Lars> are not in the \000-\177 range, then the characters must be the
Lars> result of current-language-environment.
I don't think there's anything to stop you typing ça in an `English'
current-language-environment which claims only to know about `ascii'.
Lars> How does one go from current-language-environment to a charset?
I don't think you do. I think the unibytten need a default non-ASCII
Emacs charset, related to (instead of?) the MIME one. That's what I
did with TM for MBSK Emacs (though I may have confused the two sorts
of charsets). Perhaps it could be defvar'ed from `charset' in
`language-info-alist' if `unibyte-display' is defined? (Not that I
claim to understand this stuff.)
Hurrah for sanctioning of unibyte!
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: CT: text/plain; charset=us-ascii, CTE: 8bit
1998-10-26 19:17 ` Dave Love
@ 1998-10-26 21:31 ` Lars Magne Ingebrigtsen
1998-10-27 18:50 ` Dave Love
0 siblings, 1 reply; 8+ messages in thread
From: Lars Magne Ingebrigtsen @ 1998-10-26 21:31 UTC (permalink / raw)
Dave Love <d.love@dl.ac.uk> writes:
> I don't think there's anything to stop you typing ça in an `English'
> current-language-environment which claims only to know about `ascii'.
Hm. How should this be handled, then? Well, I guess I could just ask
the user. Is there a special function to prompt for a charset?
> Perhaps it could be defvar'ed from `charset' in
> `language-info-alist' if `unibyte-display' is defined? (Not that I
> claim to understand this stuff.)
I didn't know about `language-info-alist'. I've now hacked up an
mm-find-charset-region that should work under unibyte as well.
Áß ßhòülð pròbáblÿ bé ßhòwñ ïñ þhïß á®þïçlé.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: CT: text/plain; charset=us-ascii, CTE: 8bit
1998-10-26 21:31 ` Lars Magne Ingebrigtsen
@ 1998-10-27 18:50 ` Dave Love
1998-10-27 20:06 ` Hrvoje Niksic
0 siblings, 1 reply; 8+ messages in thread
From: Dave Love @ 1998-10-27 18:50 UTC (permalink / raw)
>>>>> "Lars" == Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
Lars> Is there a special function to prompt for a charset?
Not obviously. `(interactive "z")' for a coding system, of course...
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: CT: text/plain; charset=us-ascii, CTE: 8bit
1998-10-27 18:50 ` Dave Love
@ 1998-10-27 20:06 ` Hrvoje Niksic
1998-10-28 19:38 ` Dave Love
0 siblings, 1 reply; 8+ messages in thread
From: Hrvoje Niksic @ 1998-10-27 20:06 UTC (permalink / raw)
Dave Love <d.love@dl.ac.uk> writes:
> >>>>> "Lars" == Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
>
> Lars> Is there a special function to prompt for a charset?
>
> Not obviously. `(interactive "z")' for a coding system, of
> course...
`read-coding-system' is the workhorse behind `(interactive "z")',
FWIW.
--
Hrvoje Niksic <hniksic@srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
I luv the smell of nature in the morning. Smells like manure!
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: CT: text/plain; charset=us-ascii, CTE: 8bit
1998-10-27 20:06 ` Hrvoje Niksic
@ 1998-10-28 19:38 ` Dave Love
1998-11-07 17:07 ` Lars Magne Ingebrigtsen
0 siblings, 1 reply; 8+ messages in thread
From: Dave Love @ 1998-10-28 19:38 UTC (permalink / raw)
>>>>> "HN" == Hrvoje Niksic <hniksic@srce.hr> writes:
HN> `read-coding-system' is the workhorse behind `(interactive "z")',
HN> FWIW.
But coding systems aren't charsets, of course. OTOH, how are you
supposed to MIME multiple MULE charsets in a region anyway? Is the
buffer's coding system (for write?) actually the relevant thing?
BTW, has the doc for `coding-system-get' been noticed in this
connexion?
- Function: coding-system-get CODING-SYSTEM PROPERTY
This function returns the specified property of the coding system
CODING-SYSTEM. Most coding system properties exist for internal
purposes, but one that you might find useful is `mime-charset'.
That property's value is the name used in MIME for the character
coding which this coding system can read and write. Examples:
(coding-system-get 'iso-latin-1 'mime-charset)
=> iso-8859-1
(coding-system-get 'iso-2022-cn 'mime-charset)
=> iso-2022-cn
(coding-system-get 'cyrillic-koi8 'mime-charset)
=> koi8-r
The value of the `mime-charset' property is also defined as an
alias for the coding system.
--
MULE's Upping Lars's Exasperation?
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: CT: text/plain; charset=us-ascii, CTE: 8bit
1998-10-28 19:38 ` Dave Love
@ 1998-11-07 17:07 ` Lars Magne Ingebrigtsen
0 siblings, 0 replies; 8+ messages in thread
From: Lars Magne Ingebrigtsen @ 1998-11-07 17:07 UTC (permalink / raw)
Dave Love <d.love@dl.ac.uk> writes:
> But coding systems aren't charsets, of course. OTOH, how are you
> supposed to MIME multiple MULE charsets in a region anyway?
One has to create a multipart/mixed message with different MIME
charsets in each part.
> Is the buffer's coding system (for write?) actually the relevant
> thing?
Perhaps not...
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~1998-11-07 17:07 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1998-10-25 19:53 CT: text/plain; charset=us-ascii, CTE: 8bit Bjørn Mork
1998-10-25 22:38 ` Lars Magne Ingebrigtsen
1998-10-26 19:17 ` Dave Love
1998-10-26 21:31 ` Lars Magne Ingebrigtsen
1998-10-27 18:50 ` Dave Love
1998-10-27 20:06 ` Hrvoje Niksic
1998-10-28 19:38 ` Dave Love
1998-11-07 17:07 ` Lars Magne Ingebrigtsen
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).