CharSet
property CharSet: string read write;
Example
procedure MarkUtf8(const Part: TIdMessagePart);
begin
Part.CharSet := 'utf-8';
end;
Usage
Stores the part's raw charset label independently, with one-way updates from ContentType parameters but no validation or header synchronization.
Additional Technical Info
CharSet is an independent String field, not a live view of the internal Content-Type header. Assignment stores text exactly and performs no encoding conversion, canonicalization or supported-codepage validation.
Setting ContentType with a nonempty charset parameter removes that parameter from the stored header value and writes it here. If a later ContentType assignment omits the parameter, the old CharSet remains. Assigning CharSet directly does not add/update a header parameter; the message encoder may consult both pieces later.
Changing the label never converts TIdText.Body. A mismatch can label text with the wrong character set. Establish the actual body encoding and declared label together under the outbound mail policy.
Empty assignment clears only this field. Native Assign copies it. The operation is O(n) managed-string assignment, does no I/O and issues no explicit collection-item change notification. The part is mutable and not thread-safe.
The source-reviewed example only sets metadata; no bytes were encoded.
External references
- Indy upstream:
TIdMessagePart- field and ContentType extraction behavior. - RFC 2045 section 5.1 - Content-Type parameters.