OT format mailu

[Pavel Hudecek]

Kdyz vymyslite nejake jine reseni, aby vysledek fungoval vsem,
urcite jej napiste.

Me reseni umoznuje, abyste mohl prispivat do ceskych i zahranicnich
konferenci zaroven a nevznikaly pri tom problemy se ctenim Vasich
prispevku, ani odpovedi na ne, prestoze odpoved nekdo napsal
s diakritikou a pouzil klient, ktery kodovani automaticky nezmenil.

O RFC jsem psal jen ve vztahu k tomu, ze text bez diakritiky
neni 8859-1, ale US-ASCII, coz s Vasim citatem
naprosto souhlasi.

Pavel Hudecek
----------------------------------------------------
http://www.diametral.cz

Od: "Petr Simek" <psimek@jcu.cz>
> On Sun, 19 Jan 2003, Pavel Hudecek wrote:
> 
> > Tady prave jde o to, aby kodovani nebylo podle obsahu, ale podle ciloveho
> > uctu, nebo cilove adresy. Kdyz na tento mail totiz nekdo odpovi ?esky
> > a nebude mit zaple automaticke prekodovani, z ?e?tiny se stane ?e?tina...
> 
> To je hezke, ohanite se tu RFC a pritom vymyslite nesmysly oznacovani
> charsetu dokumentu podle odesilatele, prijemce, lokality a podobne
> nesmysly. RFC 2046 k tomu pomerne jasne pise :
> 
> 
>    In general, composition software should always use the "lowest common
>    denominator" character set possible.  For example, if a body contains
>    only US-ASCII characters, it SHOULD be marked as being in the US-
>    ASCII character set, not ISO-8859-1, which, like all the ISO-8859
>    family of character sets, is a superset of US-ASCII. More generally,
>    if a widely-used character set is a subset of another character set,
>    and a body contains only characters in the widely-used subset, it
>    should be labelled as being in that subset.  This will increase the
>    chances that the recipient will be able to view the resulting entity
>    correctly.