1998
DOI: 10.17487/rfc2277
|View full text |Cite
|
Sign up to set email alerts
|

IETF Policy on Character Sets and Languages

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
18
0

Year Published

2001
2001
2014
2014

Publication Types

Select...
5
3
2

Relationship

0
10

Authors

Journals

citations
Cited by 46 publications
(18 citation statements)
references
References 6 publications
0
18
0
Order By: Relevance
“…This decision can be based on any available knowledge, such as the location of the user, the Accept-Language field in a request, or the Content-Language field in a response. The default language is idefault [21].…”
Section: Warningmentioning
confidence: 99%
“…This decision can be based on any available knowledge, such as the location of the user, the Accept-Language field in a request, or the Content-Language field in a response. The default language is idefault [21].…”
Section: Warningmentioning
confidence: 99%
“…All RFCs that deal with internationalization issues should have a section describing those issues; see "IETF Policy on Character Sets and Languages" [BCP18], Section 6, for more information.…”
Section: Internationalization Considerations Sectionmentioning
confidence: 99%
“…The specification allows multiple occurrences of these elements so that the presentity can convey <note> and <other> elements in multiple scripts and languages. If no 'xml:lang' attribute is provided, the default value is "i-default" [3].…”
Section: Xml Schema Definitionsmentioning
confidence: 99%