- Timestamp:
- 04/11/10 08:16:27 (12 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis-content-disp/latest/draft-ietf-httpbis-content-disp.xml
r1074 r1075 544 544 <seriesInfo name="RFC" value="2231"/> 545 545 </reference> 546 546 <!-- 547 547 <reference anchor="RFC3629"> 548 548 <front> … … 556 556 <seriesInfo name="STD" value="63"/> 557 557 <seriesInfo name="RFC" value="3629"/> 558 </reference> 558 </reference>--> 559 559 560 560 <reference anchor="RFC3864"> … … 693 693 <t> 694 694 Some user agents accept percent encoded (<xref target="RFC3986" x:fmt="," x:sec="2.1"/>) 695 sequences of characters encoded using the UTF-8 (<xref target="RFC3629"/>) character encoding.696 </t> 697 <t> 698 In practice, this is hard to use because those user agents699 that do not support it will display the escaped character sequence to the user. 700 < /t>701 <t> 702 Furthermore, the first user agent to implement this did choose the encoding703 based on local settings; thus making it very hard to use in multi-lingual704 en vironments.695 sequences of characters. The character encoding being used for decoding 696 depends on various factors, including the encoding of the referring page, 697 the user agent's locale, it's configuration, and also the actual value of 698 the parameter. 699 </t> 700 <t> 701 In practice, this is hard to use because those user agents that do not 702 support it will display the escaped character sequence to the user. For those 703 user agents that do implement this it is difficult to predict what character 704 encoding they actually expect. 705 705 </t> 706 706 </section> … … 886 886 </t> 887 887 <t> 888 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/263"/>: 889 "text about historical percent-decoding unclear" 890 </t> 891 <t> 888 892 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/264"/>: 889 893 "add explanation of language tagging"
Note: See TracChangeset
for help on using the changeset viewer.