And you can see the ISO 2022 "plain-text" encoding also as a multipart container format trasporting multiple document fragments which could have their own local encoding (the encoding is specified by the ISO 2022 container that structures the text contents and their encodings.
You an also have container fomats containing streams that are themselves containers for other internal streams (examples: an object database storage format, or ZIP archives). On the web the MIME multipart format is widely used not just for emails, but may also apply to a single "web page" (which can embed subdocuments instead of just referencing them by external references, the final redering of the document being an assembly of multiple text streams parse separately before being assembed). 2013/8/28 Markus Scherer <[email protected]> > A common example is multi-part MIME email where each part can have its own > charset and transfer encoding. > > More generally, a container format can mix parts of different types and > encodings; examples see Philippe's email. > > For single-"document" formats, I don't think it would be useful to use > multiple text encodings. > > markus >
