On Wed, 28 Mar 2007, Alain Bench wrote:
some terminals (Rxvt?) can display simultaneously Latin-1 and UTF-8.
Something has to provide the mode-switch between UTF-8 and Latin-1.
I meant *without* mode switch. Something that would print (fake):
| $ printf "\0351 \0303\0251\n"
Hello Thomas,
On Tuesday, March 27, 2007 at 18:10:22 -0400, Thomas E. Dickey wrote:
> On Tue, 27 Mar 2007, Alain Bench wrote:
>> some terminals (Rxvt?) can display simultaneously Latin-1 and UTF-8.
> Something has to provide the mode-switch between UTF-8 and Latin-1.
I meant *without* mode
On Tue, 27 Mar 2007, Alain Bench wrote:
On Monday, March 26, 2007 at 16:39:36 +0200, Vincent Lefèvre wrote:
about files that contain both ISO-8859-1 and UTF-8, to let the user
decide. [...] it can happen in diffs where some files are encoded in
ISO-8859-1 and others in UTF-8.
That's defin
On Monday, March 26, 2007 at 16:39:36 +0200, Vincent Lefèvre wrote:
> about files that contain both ISO-8859-1 and UTF-8, to let the user
> decide. [...] it can happen in diffs where some files are encoded in
> ISO-8859-1 and others in UTF-8.
That's definitely undecidable by the $assumed_cha
Salut Alain,
On 2007-03-25 20:21:35 +0200, Alain Bench wrote:
> Bonjour Vincent,
>
> On Sunday, March 25, 2007 at 4:28:36 +0200, Vincent Lefèvre wrote:
>
> > On 2007-03-24 16:05:08 +0100, Alain Bench wrote:
> >> Setting UTF-8 after ISO-8859-1 is useless. Any string is always
> >> valid Latin-1.
On Sun, 25 Mar 2007, Alain Bench wrote:
Hello Christoph!
On Sunday, March 25, 2007 at 13:30:12 +0200, Christoph Berg wrote:
CP1251 (iirc, the last digit could be different) is what windows
usually uses. It is a superset of latin1, with characters in the
128-159 range, mainly some quotes. That
Bonjour Vincent,
On Sunday, March 25, 2007 at 4:28:36 +0200, Vincent Lefèvre wrote:
> On 2007-03-24 16:05:08 +0100, Alain Bench wrote:
>> Setting UTF-8 after ISO-8859-1 is useless. Any string is always
>> valid Latin-1.
> Shouldn't characters 128-159 be regarded as invalid?
No, I don't thin
Hello Christoph!
On Sunday, March 25, 2007 at 13:30:12 +0200, Christoph Berg wrote:
> CP1251 (iirc, the last digit could be different) is what windows
> usually uses. It is a superset of latin1, with characters in the
> 128-159 range, mainly some quotes. That could also be a good guess.
Rig
Re: Vincent Lefevre 2007-03-25 <[EMAIL PROTECTED]>
> > Setting UTF-8 after ISO-8859-1 is useless. Any string is always
> > valid Latin-1. UTF-8 will never be tried nor selected.
>
> Shouldn't characters 128-159 be regarded as invalid? Text should
> contain only printable characters and some re
On 2007-03-24 16:05:08 +0100, Alain Bench wrote:
> On Monday, March 19, 2007 at 10:10:40 +0900, Tamotsu Takahashi wrote:
>
> > you can set "assumed_charset=iso-8859-1:utf-8"
>
> Setting UTF-8 after ISO-8859-1 is useless. Any string is always
> valid Latin-1. UTF-8 will never be tried nor sel
On Monday, March 19, 2007 at 10:10:40 +0900, Tamotsu Takahashi wrote:
> you can set "assumed_charset=iso-8859-1:utf-8"
Setting UTF-8 after ISO-8859-1 is useless. Any string is always
valid Latin-1. UTF-8 will never be tried nor selected.
The reversed order, $assumed_charset="utf-8:iso-8
On Mon, 19 Mar 2007 the mental interface of
Elimar Riesebieter told:
[...]
Yeah babe, I've had:
iconv-hook ISO-8859-1 ANSI_X3.4-1968
for an uncommented reason. Unset solved the prob ;)
For a test:
ae ä
ue ü
oe ö
sz ß
Heheheheh, it works ;)
Elimar
--
Planung:
Ersatz des Zufalls d
piled a today's hg clone. Mutt doesn't show special chars
> >>like the `German Umlauts' -> ae_?_ ue_?_ oe_?_ sz_?_ anymore. Plain
> >>1.5.14 does. No changes to muttrc.
> >>Any hints?
(snip)
> The locale should be ok since vim console and friends are d
Hi,
* Thomas Roessler [07-03-19 11:54:36 +0100] wrote:
I'd hope that this is a documentation bug (but haven't bothered to
check), and that the documentation is meant to say "plain text".
Yepp, I sent a patch to fix it.
There is no reason why format=flowed can't work with any character
set t
* Mon Mar 19 2007 TAKAHASHI Tamotsu <[EMAIL PROTECTED]>
> * Mon Mar 19 2007 Elimar Riesebieter <[EMAIL PROTECTED]>
> > >* Sun Mar 18 2007 Elimar Riesebieter <[EMAIL PROTECTED]>
> > >>I've compiled a today's hg clone. Mutt doesn't show s
On 2007-03-19 15:52:27 +0900, TAKAHASHI Tamotsu wrote:
> The manual tells that "format=flowed" messages are _plain ASCII
> messages_
I'd hope that this is a documentation bug (but haven't bothered to
check), and that the documentation is meant to say "plain text".
There is no reason why format=f
* Mon Mar 19 2007 Elimar Riesebieter <[EMAIL PROTECTED]>
> >* Sun Mar 18 2007 Elimar Riesebieter <[EMAIL PROTECTED]>
> >>I've compiled a today's hg clone. Mutt doesn't show special chars
> >>like the `German Umlauts' -> ae_?_ ue_?_ oe_?_
On Mon, 19 Mar 2007 the mental interface of
TAKAHASHI Tamotsu told:
* Sun Mar 18 2007 Elimar Riesebieter <[EMAIL PROTECTED]>
I've compiled a today's hg clone. Mutt doesn't show special chars
like the `German Umlauts' -> ae_?_ ue_?_ oe_?_ sz_?_ anymore. Plain
1.5.1
* Sun Mar 18 2007 Elimar Riesebieter <[EMAIL PROTECTED]>
> I've compiled a today's hg clone. Mutt doesn't show special chars
> like the `German Umlauts' -> ae_?_ ue_?_ oe_?_ sz_?_ anymore. Plain
> 1.5.14 does. No changes to muttrc.
>
> Any hints?
Wh
Hi all,
I've compiled a today's hg clone. Mutt doesn't show special chars
like the `German Umlauts' -> ae_?_ ue_?_ oe_?_ sz_?_ anymore. Plain
1.5.14 does. No changes to muttrc.
Any hints?
Elimar
--
Experience is something you don't get until
just after you need it!
Synopsis: Subject containing special chars causes mutt to not refresh the screen
State-Changed-From-To: open->closed
State-Changed-By: cb
State-Changed-When: Tue, 27 Feb 2007 15:42:28 +0100
State-Changed-Why:
unreproducible
Comment added by cb on Tue, 27 Feb 2007 15:42:28 +0100
J
21 matches
Mail list logo
