| java.lang.Object | |
| ↳ | android.text.util.Rfc822Tokenizer |
This class works as a Tokenizer for MultiAutoCompleteTextView for address list fields, and also provides a method for converting a string of addresses (such as might be typed into such a field) into a series of Rfc822Tokens.
| Public Constructors | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Public Methods | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
Returns the end of the token (minus trailing punctuation)
that begins at offset
cursor within text.
| |||||||||||
Returns the start of the token that ends at offset
cursor within text.
| |||||||||||
Terminates the specified address with a comma and space.
| |||||||||||
This method will try to take a string like
"Foo Bar (something) <foo\@google.com>,
blah\@google.com (something)"
and convert it into one or more Rfc822Tokens.
| |||||||||||
This constructor will try to take a string like
"Foo Bar (something) <foo\@google.com>,
blah\@google.com (something)"
and convert it into one or more Rfc822Tokens, output into the supplied
collection.
| |||||||||||
|
[Expand]
Inherited Methods | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
From class
java.lang.Object
| |||||||||||
|
From interface
android.widget.MultiAutoCompleteTextView.Tokenizer
| |||||||||||
Returns the end of the token (minus trailing punctuation)
that begins at offset cursor within text.
Returns the start of the token that ends at offset
cursor within text.
Terminates the specified address with a comma and space. This assumes that the specified text already has valid syntax. The Adapter subclass's convertToString() method must make that guarantee.
This method will try to take a string like "Foo Bar (something) <foo\@google.com>, blah\@google.com (something)" and convert it into one or more Rfc822Tokens. It does *not* decode MIME encoded-words; charset conversion must already have taken place if necessary. It will try to be tolerant of broken syntax instead of returning an error.
This constructor will try to take a string like "Foo Bar (something) <foo\@google.com>, blah\@google.com (something)" and convert it into one or more Rfc822Tokens, output into the supplied collection. It does *not* decode MIME encoded-words; charset conversion must already have taken place if necessary. It will try to be tolerant of broken syntax instead of returning an error.
Developers