956:
36:
458:
All media types should be registered using the IANA registration procedures. For the efficiency and flexibility of the media type registration process, different structures of subtypes can be registered in registration trees that are distinguished by the use of tree prefixes. Currently the following
609:
Suffix is an augmentation to the media type definition to additionally specify the underlying structure of that media type, allowing for generic processing based on that structure and independent of the exact type's particular semantics. Media types that make use of a named structured syntax should
866:
Mailcap (derived from the phrase "mail capability") is a type of meta file used to configure how MIME-aware applications such as mail clients and web browsers render files of different MIME-types. The mailcap format is defined by RFC 1524 "A User Agent
Configuration Mechanism for Multimedia Mail
517:
The terms "vendor" and "producer" are considered equivalent in the context. Industry consortia as well as non-commercial entities can register media types in the vendor tree. A registration in the vendor tree may be created by anyone who needs to interchange files associated with some software
593:) without being registered, should be, if possible, re-registered with a proper prefixed subtype. If this is not possible, the media type can, after an approval by both the media types reviewer and the IESG, be registered in the standards tree with its unprefixed subtype.
518:
product or set of products. However, the registration belongs to the vendor or organization producing the software that employs the type being registered, and that vendor or organization can at any time elect to assert ownership of a registration done by a third party.
573:
prefix, but discouraged use of the unregistered tree, as new personal and vendor trees with relaxed registration requirements are now available. The current RFC 6838 (published in
January 2013) maintains the same recommendation, but subtypes prefixed with
894:
allows one to fall back on the extension in these cases. Similarly, since many file systems do not store MIME type information, but instead rely on the filename extension, a mime.types file is frequently used by web servers to determine MIME type.
1352:
S. Rzepa, Henry; Murray-Rust, Peter; J. Whitaker, Benjamin (14 August 1998). "The
Application of Chemical Multipurpose Internet Mail Extensions (Chemical MIME) Internet Standards to Electronic Mail and World Wide Web Information Exchange".
454:
A subtype typically consists of a media format, but it may or must also contain other content, such as a tree prefix, producer, product or suffix, according to the different rules in registration trees.
614:
for that structured syntax when they are registered. Unregistered suffixes should not be used (since
January 2013). Structured syntax suffix registration procedures are defined in RFC 6838.
325:
Types, subtypes, and parameter names are case-insensitive. Parameter values are usually case-sensitive, but may be interpreted in a case-insensitive fashion depending on the intended use.
494:
Registrations in the standards tree must be either associated with IETF specifications approved directly by the IESG, or registered by an IANA recognized standards-related organization.
931:
and the format is simply that each line is a space-delimited list of a MIME type, followed by zero or more extensions. For example, the HTML type can be associated with the extensions
546:
The unregistered tree includes media types intended exclusively for use in private environments and only with the active agreement of the parties exchanging them. It uses the
197:
use the term "media type", and consider the term "MIME type" to be obsolete, since media types have become used in contexts unrelated to email, such as HTTP. By contrast, the
1127:
HTTP uses media types in the
Content-Type (Section 8.3) and Accept (Section 12.5.1) header fields in order to provide open and extensible data typing and type negotiation.
201:
continues to use the term "MIME type" and discourages use of the term "media type" as ambiguous, since it is used with a different meaning in connection with the
621:
suffix has been defined since
January 2001 (RFC 3023), and was formally included in the initial contents of the Structured Syntax Suffix Registry along with
1005:#--Netscape Communications Corporation MIME Information # Do not delete the above line. It is used to identify the file type. type=text/html exts=htm,html
471:
prefix). These registration trees were first defined in
November 1996 (obsoleted RFC 2048 - currently RFC 6838). New registration trees may be created by
526:
The personal or vanity tree includes media types associated with non publicly available products or experimental media types. It uses the
1566:
90:
136:
is the official authority for the standardization and publication of these classifications. Media types were originally defined in
1525:
886:. If the MIME type is properly set, this is unnecessary, but MIME types may be incorrectly set, or set to a generic type such as
475:
Standards Action for external registration and management by well-known permanent organizations (e.g. scientific societies).
1402:
1380:
133:
427:
1595:
1073:
specifies that Media Types (formerly known as MIME types) and Media
Subtypes will be assigned and listed by the IANA.
381:
76:
1549:
1305:
1486:
1239:
1142:
472:
1619:
1614:
186:
Different internet standards or web standards bodies differ on the preferred term for this type of identifier.
870:
Lines can be comments starting with the # character, or a mime-type followed by how to handle that mime type.
248:
1427:
443:
1639:
333:
The "type" part defines the broad use of the media type. As of
November 1996, the registered types were:
121:, in that they identify the intended data format. They are mainly used by technologies underpinning the
867:
Format
Information" but is not defined as an Internet standard. It is supported by most Unix systems.
17:
1209:
1487:"application/x-www-form-urlencoded (registered 2014-05-14, updated 2014-05-14, updated 2020-07-14)"
1184:
Standards are encouraged to consistently use the term MIME type to avoid confusion with the use of
995:
54:
1585:
1563:
1052:
118:
147:(MIME) Part One: Format of Internet Message Bodies (Nov 1996) in November 1996 as a part of the
991:
202:
1171:
1091:
502:
The vendor tree includes media types associated with publicly available products. It uses the
1282:
403:
1002:
consisting of a specific comment that identifies the file as a mime.types file, as follows:
1119:
387:
137:
1236:"Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies"
8:
1014:
391:
236:
228:
175:
46:
969:
Please expand the section to include this information. Further details may exist on the
1024:
114:
999:
1624:
1461:
1111:
561:
This type was originally defined in RFC 1590 (published in September 1993) using the
1590:
1362:
1101:
1019:
861:
140:
1261:
1435:
1410:
1388:
1214:
970:
435:
419:
232:
171:
110:
58:
1122:
1095:
144:
1634:
1629:
1608:
1570:
1465:
1115:
411:
126:
1501:
167:
597:
is an example of a widely deployed type that ended up registered with the
735:
application/vnd.openxmlformats-officedocument.presentationml.presentation
585:
Media types that have been widely deployed (with a subtype prefixed with
407:
106:
1309:
747:
application/vnd.openxmlformats-officedocument.wordprocessingml.document
1453:
1366:
1235:
1591:
The Python Standard Library | mimetypes — Map filenames to MIME types
1106:
1330:
122:
361:. By July 2024, the registered types included the foregoing, plus
1599:
910:
741:
application/vnd.openxmlformats-officedocument.spreadsheetml.sheet
683:
1303:
1260:
Nielsen, Henrik; Fielding, Roy T.; Berners-Lee, Tim (May 1996).
955:
917:
In UNIX-type systems, the mime.types file is usually located at
162:. Media types are also used by other internet protocols such as
1179:
198:
1351:
483:
The standards tree does not use any tree prefix. Examples are
618:
569:
prefix. RFC 2048 (published in November 1996) introduced the
399:
155:
322:
is an optional parameter indicating the character encoding.
1060:
212:
194:
190:
163:
149:
1259:
998:
and a comma-separated list of extensions, together with a
158:
message content and attachments; hence the original name,
1150:
1089:
645:
in January 2013 (RFC 6839). Subsequent additions include
220:
1454:"Media Type Specifications and Registration Procedures"
1573:, John McAnally, Thu, 22 Jan 1998 15:29:29 -0600 (CST)
1085:
1083:
1081:
582:
are no longer considered to be members of this tree.
1460:. RFC6838. Internet Engineering Task Force (IETF).
1165:
1163:
1090:Fielding, R.; Nottingham, M.; Reschke, J. (2022).
1078:
882:file, which associates filename extensions with a
1550:"MIME types (IANA media types) - HTTP | MDN"
558:. Media types in this tree cannot be registered.
459:trees are created: standard (no prefix), vendor (
1606:
1160:
1137:
1135:
908:associates an extension with a MIME type, while
306:As an example, an HTML file might be designated
215:response header for providing the media type is
1233:
380:An unofficial top-level type in common use is
1422:
1420:
1132:
711:application/vnd.microsoft.portable-executable
1458:IETF Request for Comments (RFC) Pages - Test
1355:Journal of Chemical Information and Modeling
994:, where it used a different format; it used
902:a file, these two work together as follows:
57:. There might be a discussion about this on
1442:
1234:Freed, N.; Borenstein, N. (November 1996).
1447:
1445:
1417:
1222:
521:
134:Internet Assigned Numbers Authority (IANA)
1361:(6). American Chemical Society: 976–982.
1304:Daniel Leidert, Egon Willighagen (2007).
1262:"Hypertext Transfer Protocol -- HTTP/1.0"
1229:
1227:
1225:
1204:
1202:
1200:
1147:XHTML Modularization 1.1 - Second Edition
1105:
91:information and communications technology
77:Learn how and when to remove this message
247:Syntax notations in this section are in
914:associates a MIME type with a program.
729:application/vnd.oasis.opendocument.text
512:application/vnd.oasis.opendocument.text
266:. A media type can optionally define a
152:(Multipurpose Internet Mail Extensions)
14:
1607:
1197:
1047:
1045:
1043:
1041:
1039:
239:continue to use the term "MIME type".
1451:
262:, which is further structured into a
1499:
1428:"Table 10: Standard MIME type icons"
949:
610:use the appropriate IANA registered
541:
235:specifications implemented by Linux
174:specifications implemented by Linux
154:specification, for denoting type of
29:
1526:"Structured Syntax Suffix Registry"
1169:
1155:ContentType: A media type, as per .
1036:
791:(.jpg, .jpeg, .jfif, .pjpeg, .pjp)
24:
664:
25:
1651:
1586:IANA list of official media types
1579:
753:application/x-www-form-urlencoded
595:application/x-www-form-urlencoded
478:
402:other than normal files, such as
394:, the unofficial top-level types
113:. Their purpose is comparable to
1403:"2.14 Content types for volumes"
1306:"The chemical-mime-data project"
954:
166:, document file formats such as
34:
1556:
1542:
1518:
1493:
1479:
1395:
1373:
1345:
1323:
1240:Internet Engineering Task Force
1172:"4.1. MIME type representation"
945:
1407:Shared MIME Info Specification
1385:Shared MIME Info Specification
1297:
1275:
1253:
497:
181:
13:
1:
1030:
990:The mime.types file dates to
873:
723:application/vnd.ms-powerpoint
463:prefix), personal or vanity (
105:is a two-part identifier for
444:office productivity software
242:
7:
1008:
506:tree prefix. Examples are:
449:
254:A media type consists of a
251:, following RFC convention.
27:Identifier for file formats
10:
1656:
1500:Kohn, Dan (January 2001).
1452:Freed, N. (January 2013).
878:An associated file is the
859:
855:
550:tree prefix. Examples are
530:tree prefix. Examples are
390:. In the context of Linux
246:
1432:Icon Naming Specification
1381:"2.13. Non-regular files"
1331:"Chemical MIME Home page"
1283:"HTML 4.01 Specification"
942:text/html htm html
936:
932:
904:
887:
848:
842:
837:
832:
827:
822:
817:
811:
805:
799:
794:
788:
783:
778:
773:
767:
762:
757:
752:
746:
740:
734:
728:
722:
716:
710:
705:
700:
695:
689:
679:
674:
658:
654:
650:
646:
642:
638:
634:
630:
626:
622:
611:
604:
598:
594:
590:
586:
579:
575:
570:
566:
562:
555:
551:
547:
535:
531:
527:
511:
507:
503:
488:
484:
468:
464:
460:
439:
431:
423:
415:
395:
382:
374:
370:
366:
362:
358:
354:
350:
346:
342:
338:
334:
319:
315:
311:
307:
249:Extended Backus–Naur form
224:
216:
205:
888:application/octet-stream
717:application/vnd.ms-excel
706:application/vnd.api+json
669:From the IANA registry:
508:application/vnd.ms-excel
328:
308:text/html; charset=UTF-8
278:
178:, for similar purposes.
119:uniform type identifiers
1210:"shared-mime-info-spec"
939:by the following line:
522:Personal or vanity tree
467:prefix), unregistered (
442:(generic categories of
231:name for a media type.
1176:MIME Sniffing Standard
1143:"4.3. Attribute Types"
965:is missing information
404:filesystem directories
1620:Computer file formats
1615:Internet architecture
388:chemical file formats
446:document) are used.
392:desktop environments
318:is the subtype, and
237:desktop environments
176:desktop environments
138:Request for Comments
47:confusing or unclear
1552:. 18 December 2023.
1170:Hemsley, Gordon P.
1100:. sec. 8.3.1.
1015:Content negotiation
818:multipart/form-data
680:application/ld+json
612:"+"suffix
428:DCF digital cameras
424:x-content/image-dcf
310:. In this example,
125:, and also used on
115:filename extensions
55:clarify the article
1640:1996 introductions
1531:. IANA. 2012-07-20
1333:. 22 December 1998
1025:Filename extension
713:(.efi, .exe, .dll)
690:application/msword
1596:Common MIME types
1502:"XML Media Types"
1367:10.1021/ci9803233
988:
987:
552:application/x.foo
542:Unregistered tree
87:
86:
79:
16:(Redirected from
1647:
1574:
1560:
1554:
1553:
1546:
1540:
1539:
1537:
1536:
1530:
1522:
1516:
1515:
1513:
1512:
1497:
1491:
1490:
1483:
1477:
1476:
1474:
1472:
1449:
1440:
1439:
1424:
1415:
1414:
1399:
1393:
1392:
1377:
1371:
1370:
1349:
1343:
1342:
1340:
1338:
1327:
1321:
1320:
1318:
1317:
1308:. Archived from
1301:
1295:
1294:
1292:
1290:
1279:
1273:
1272:
1270:
1268:
1257:
1251:
1250:
1248:
1246:
1231:
1220:
1219:
1206:
1195:
1194:
1188:as described in
1167:
1158:
1157:
1139:
1130:
1129:
1109:
1107:10.17487/rfc9110
1087:
1076:
1075:
1070:
1068:
1049:
1020:Content sniffing
983:
980:
974:
958:
950:
938:
934:
930:
923:
913:
906:
889:
862:File association
850:
844:
839:
834:
829:
824:
819:
813:
807:
801:
796:
790:
785:
780:
775:
769:
768:application/zstd
764:
759:
754:
748:
742:
736:
730:
724:
718:
712:
707:
702:
697:
691:
681:
676:
675:application/json
660:
656:
652:
648:
644:
640:
636:
632:
628:
624:
613:
600:
596:
592:
588:
581:
577:
572:
568:
564:
557:
553:
549:
537:
533:
529:
513:
509:
505:
490:
486:
470:
466:
462:
441:
433:
425:
417:
397:
384:
376:
372:
368:
364:
360:
356:
352:
348:
344:
340:
336:
321:
317:
313:
309:
300:
297:
294:
291:
288:
285:
282:
226:
218:
207:
82:
75:
71:
68:
62:
38:
37:
30:
21:
1655:
1654:
1650:
1649:
1648:
1646:
1645:
1644:
1605:
1604:
1582:
1577:
1561:
1557:
1548:
1547:
1543:
1534:
1532:
1528:
1524:
1523:
1519:
1510:
1508:
1498:
1494:
1485:
1484:
1480:
1470:
1468:
1450:
1443:
1436:freedesktop.org
1426:
1425:
1418:
1411:freedesktop.org
1401:
1400:
1396:
1389:freedesktop.org
1379:
1378:
1374:
1350:
1346:
1336:
1334:
1329:
1328:
1324:
1315:
1313:
1302:
1298:
1288:
1286:
1281:
1280:
1276:
1266:
1264:
1258:
1254:
1244:
1242:
1232:
1223:
1215:freedesktop.org
1208:
1207:
1198:
1168:
1161:
1141:
1140:
1133:
1088:
1079:
1066:
1064:
1051:
1050:
1037:
1033:
1011:
1006:
1000:standard header
996:key–value pairs
984:
978:
975:
968:
967:about Netscape.
959:
948:
943:
925:
918:
909:
876:
864:
858:
853:
843:text/javascript
763:application/zip
758:application/xml
701:application/sql
696:application/pdf
667:
665:Common examples
607:
544:
524:
500:
485:text/javascript
481:
452:
436:package manager
420:removable media
331:
302:
301:
298:
295:
292:
289:
286:
283:
280:
252:
245:
184:
111:content formats
83:
72:
66:
63:
52:
39:
35:
28:
23:
22:
15:
12:
11:
5:
1653:
1643:
1642:
1637:
1632:
1627:
1622:
1617:
1603:
1602:
1593:
1588:
1581:
1580:External links
1578:
1576:
1575:
1569:2000-12-07 at
1555:
1541:
1517:
1506:tools.ietf.org
1492:
1478:
1441:
1416:
1394:
1372:
1344:
1322:
1296:
1274:
1252:
1221:
1196:
1159:
1153:. 2010-07-29.
1131:
1118:. STD 97.
1097:HTTP Semantics
1077:
1034:
1032:
1029:
1028:
1027:
1022:
1017:
1010:
1007:
1004:
986:
985:
962:
960:
953:
947:
944:
941:
875:
872:
857:
854:
852:
851:
846:
840:
835:
830:
825:
820:
815:
809:
803:
797:
792:
786:
781:
776:
771:
765:
760:
755:
750:
744:
738:
732:
726:
720:
714:
708:
703:
698:
693:
687:
677:
671:
666:
663:
606:
603:
543:
540:
536:image/prs.btif
523:
520:
499:
496:
480:
479:Standards tree
477:
451:
448:
438:packages) and
412:symbolic links
330:
327:
304:
303:
279:
244:
241:
183:
180:
85:
84:
42:
40:
33:
26:
9:
6:
4:
3:
2:
1652:
1641:
1638:
1636:
1633:
1631:
1628:
1626:
1623:
1621:
1618:
1616:
1613:
1612:
1610:
1601:
1597:
1594:
1592:
1589:
1587:
1584:
1583:
1572:
1571:archive.today
1568:
1565:
1559:
1551:
1545:
1527:
1521:
1507:
1503:
1496:
1488:
1482:
1467:
1463:
1459:
1455:
1448:
1446:
1437:
1433:
1429:
1423:
1421:
1412:
1408:
1404:
1398:
1390:
1386:
1382:
1376:
1368:
1364:
1360:
1356:
1348:
1332:
1326:
1312:on 2016-10-08
1311:
1307:
1300:
1285:. 24 Dec 1999
1284:
1278:
1263:
1256:
1241:
1237:
1230:
1228:
1226:
1218:. 2023-09-03.
1217:
1216:
1211:
1205:
1203:
1201:
1193:
1191:
1190:Media Queries
1187:
1181:
1177:
1173:
1166:
1164:
1156:
1152:
1148:
1144:
1138:
1136:
1128:
1124:
1121:
1117:
1113:
1108:
1103:
1099:
1098:
1093:
1086:
1084:
1082:
1074:
1063:. 4 June 2018
1062:
1058:
1054:
1053:"Media Types"
1048:
1046:
1044:
1042:
1040:
1035:
1026:
1023:
1021:
1018:
1016:
1013:
1012:
1003:
1001:
997:
993:
982:
979:November 2019
972:
966:
963:This section
961:
957:
952:
951:
940:
929:
922:
915:
912:
907:
901:
896:
893:
885:
881:
871:
868:
863:
847:
841:
836:
831:
826:
821:
816:
810:
804:
800:image/svg+xml
798:
793:
787:
782:
777:
772:
766:
761:
756:
751:
745:
739:
733:
727:
721:
715:
709:
704:
699:
694:
688:
685:
678:
673:
672:
670:
662:
620:
615:
602:
583:
559:
539:
532:audio/prs.sid
519:
515:
495:
492:
476:
474:
456:
447:
445:
437:
429:
421:
413:
409:
405:
401:
393:
389:
385:
378:
326:
323:
320:charset=UTF-8
314:is the type,
290:"/"
277:
276:
275:
273:
269:
265:
261:
257:
250:
240:
238:
234:
230:
229:XML data-type
222:
214:
209:
204:
200:
196:
192:
187:
179:
177:
173:
169:
165:
161:
157:
153:
151:
146:
142:
139:
135:
130:
128:
127:Linux desktop
124:
120:
116:
112:
108:
104:
100:
96:
92:
81:
78:
70:
60:
59:the talk page
56:
50:
48:
43:This article
41:
32:
31:
19:
1562:WEBMASTERS:
1558:
1544:
1533:. Retrieved
1520:
1509:. Retrieved
1505:
1495:
1481:
1469:. Retrieved
1457:
1431:
1406:
1397:
1384:
1375:
1358:
1354:
1347:
1335:. Retrieved
1325:
1314:. Retrieved
1310:the original
1299:
1287:. Retrieved
1277:
1265:. Retrieved
1255:
1243:. Retrieved
1213:
1189:
1185:
1183:
1175:
1154:
1146:
1126:
1096:
1092:"Media Type"
1072:
1065:. Retrieved
1056:
989:
976:
964:
946:Netscape use
927:
920:
916:
903:
899:
897:
891:
883:
879:
877:
869:
865:
668:
635:+fastinfoset
616:
608:
584:
560:
545:
525:
516:
501:
493:
482:
457:
453:
408:device files
379:
332:
324:
305:
271:
267:
263:
259:
255:
253:
217:Content-Type
210:
188:
185:
159:
148:
131:
107:file formats
102:
99:content type
98:
94:
88:
73:
64:
53:Please help
44:
1600:Mozilla MDN
928:.mime.types
556:video/x.bar
498:Vendor tree
386:, used for
335:application
225:ContentType
182:Terminology
1609:Categories
1564:mime types
1535:2019-11-08
1511:2021-03-05
1316:2016-04-28
1186:media type
1031:References
921:mime.types
905:mime.types
892:mime.types
880:mime.types
874:mime.types
860:See also:
823:text/plain
806:image/tiff
789:image/jpeg
784:image/avif
774:audio/mpeg
422:, such as
281:mime-type
272:parameters
170:, and the
95:media type
67:April 2023
49:to readers
1466:2070-1721
1116:2070-1721
971:talk page
884:MIME type
838:text/html
812:model/obj
795:image/png
779:audio/ogg
659:+cbor-seq
655:+json-seq
489:image/png
416:x-content
351:multipart
243:Structure
223:has used
208:feature.
160:MIME type
129:systems.
103:MIME type
18:MIME type
1625:Metadata
1567:Archived
1009:See also
992:Netscape
849:text/xml
833:text/csv
828:text/css
601:prefix.
450:Subtypes
440:x-office
383:chemical
293:subtype
123:Internet
1471:15 July
1245:15 July
926:$ HOME/
924:and/or
911:mailcap
900:viewing
856:Mailcap
749:(.docx)
743:(.xlsx)
737:(.pptx)
684:JSON-LD
432:package
375:haptics
367:example
347:message
260:subtype
45:may be
1464:
1337:11 May
1180:WHATWG
1114:
1067:5 June
890:, and
814:(.obj)
808:(.tif)
802:(.svg)
770:(.zst)
731:(.odt)
725:(.ppt)
719:(.xls)
692:(.doc)
657:, and
641:, and
639:+wbxml
605:Suffix
400:inodes
373:, and
268:suffix
258:and a
227:as an
219:. The
206:@media
199:WHATWG
143:
1635:Linux
1598:from
1529:(XML)
1289:2 Feb
1267:2 Feb
937:.html
919:/etc/
898:When
845:(.js)
651:+cbor
647:+gzip
623:+json
396:inode
371:model
359:video
343:image
339:audio
329:Types
287:type
156:email
1630:MIME
1473:2015
1462:ISSN
1339:2019
1291:2017
1269:2017
1247:2015
1123:9110
1112:ISSN
1069:2018
1061:IANA
1057:IANA
935:and
933:.htm
643:+zip
631:+der
627:+ber
619:+xml
617:The
528:prs.
504:vnd.
473:IETF
465:prs.
461:vnd.
426:for
363:font
357:and
355:text
316:html
312:text
270:and
264:tree
256:type
213:HTTP
211:The
195:IETF
193:and
191:IANA
189:The
168:HTML
164:HTTP
150:MIME
145:2045
132:The
117:and
109:and
93:, a
1363:doi
1151:W3C
1120:RFC
1102:doi
589:or
578:or
565:or
430:),
414:),
410:or
233:XDG
221:W3C
203:CSS
172:XDG
141:RFC
101:or
89:In
1611::
1504:.
1456:.
1444:^
1434:.
1430:.
1419:^
1409:.
1405:.
1387:.
1383:.
1359:38
1357:.
1238:.
1224:^
1212:.
1199:^
1182:.
1178:.
1174:.
1162:^
1149:.
1145:.
1134:^
1125:.
1110:.
1094:.
1080:^
1071:.
1059:.
1055:.
1038:^
661:.
653:,
649:,
637:,
633:,
629:,
625:,
599:x-
591:X-
587:x-
580:X-
576:x-
571:x.
567:X-
563:x-
554:,
548:x.
538:.
534:,
514:.
510:,
491:.
487:,
469:x.
406:,
377:.
369:,
365:,
353:,
349:,
345:,
337:,
274::
97:,
1538:.
1514:.
1489:.
1475:.
1438:.
1413:.
1391:.
1369:.
1365::
1341:.
1319:.
1293:.
1271:.
1249:.
1192:.
1104::
981:)
977:(
973:.
686:)
682:(
434:(
418:(
398:(
341:,
299:;
296:*
284:=
80:)
74:(
69:)
65:(
61:.
51:.
20:)
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.