OT: cestina v nazvech priloh

[Petr Prazak]

Dobry den,

7.12.2000, Jaroslav Cibulka wrote on subject `OT: cestina v nazvech priloh':

> ...nemuzu naji v RFC jak je to s kodovanim jmen priloh. Je to, co
> produkuje MS opravdu to spravne orechove ???

Puvodne jsem chtel napsat ze ano, ale pak jsem se zacetl do RFCecek a uz si tak
jisty nejsem.

Zakodovani ne-ASCII textu resi RFC 2047, coz je cast definice MIME (RFC
2045-2049). RFC 2047 definuje, kde se muze zakodovany text objevit. Uvadi take
priklady, kde se nesmi objevit.

   + An 'encoded-word' MUST NOT be used in parameter of a MIME
     Content-Type or Content-Disposition field, or in any structured
     field body except within a 'comment' or 'phrase'.

V RFC2045 je definice:

  content := "Content-Type" ":" type "/" subtype
             *(";" parameter)
  parameter := attribute "=" value
  value := token / quoted-string

v RFC822 se definuje:

  qtext       =  <any CHAR excepting <">,     ; => may be folded
                  "\" & CR, and including
                  linear-white-space>
  quoted-pair =  "\" CHAR                     ; may quote any char
  quoted-string = <"> *(qtext/quoted-pair) <">; Regular qtext or


Obavam se tudiz, ze spravne by v parametru mel byt pouze ascii text a kodovany
text by mel byt v komentari v zavorce.
Pokud se pletu, budu rad, kdyz me nekdo vyvede z omylu.

--
S pozdravem,
     Petr Prazak

-------------------------------
developer @ GRISOFT(c) SOFTWARE
mailto:prazak na grisoft.cz
$ whois PP2717
ICQ# 10467674
-------------------------------

idiot trap : Content-Type: application/msword :-)))