HEX
Server: Apache
System: Linux s198.coreserver.jp 5.15.0-151-generic #161-Ubuntu SMP Tue Jul 22 14:25:40 UTC 2025 x86_64
User: nagasaki (10062)
PHP: 7.1.33
Disabled: NONE
Upload Files
File: //usr/local/rvm/gems/default/doc/mail-2.7.1/ri/Mail/StructuredField/cdesc-StructuredField.ri
U:RDoc::NormalClass[iI"StructuredField:ETI"Mail::StructuredField;TI"Object;To:RDoc::Markup::Document:@parts[o;;[	o:RDoc::Markup::Paragraph;[I"1Provides access to a structured header field;To:RDoc::Markup::BlankLineS:RDoc::Markup::Heading:
leveli:	textI"Per RFC 2822:;To:RDoc::Markup::Verbatim;[I"+2.2.2. Structured Header Field Bodies
;TI"
;TI"E   Some field bodies in this standard have specific syntactical
;TI"F   structure more restrictive than the unstructured field bodies
;TI"M   described above. These are referred to as "structured" field bodies.
;TI"L   Structured field bodies are sequences of specific lexical tokens as
;TI"N   described in sections 3 and 4 of this standard.  Many of these tokens
;TI"M   are allowed (according to their syntax) to be introduced or end with
;TI"K   comments (as described in section 3.2.3) as well as the space (SP,
;TI"L   ASCII value 32) and horizontal tab (HTAB, ASCII value 9) characters
;TI"K   (together known as the white space characters, WSP), and those WSP
;TI"F   characters are subject to header "folding" and "unfolding" as
;TI"K   described in section 2.2.3.  Semantic analysis of structured field
;TI"0   bodies is given along with their syntax.;T:@format0:
@fileI"(lib/mail/fields/structured_field.rb;T:0@omit_headings_from_table_of_contents_below0;0;0[[[[I"Mail::CommonField;To;;[;@$;0I"(lib/mail/fields/structured_field.rb;T[I"Mail::Utilities;To;;[;@$;0@,[[I"
class;T[[:public[[I"new;T@,[:protected[[:private[[I"
instance;T[[;[	[I"charset;T@,[I"
charset=;T@,[I"default;T@,[I"errors;T@,[;[[;[[[U:RDoc::Context::Section[i0o;;[;0;0[@$I"	Mail;TcRDoc::NormalModule