
Comparing changes: https://github.com/smarty-php/smarty/compare/v4.3.1...v4.4.1 It is noticeable that Smarty 4.3.1 does not officially support PHP 8.3. Is only supported with 4.4.0. Remark: During tests with Smarty 4.5.1, it was noticed that the following warning occurs: Deprecated: Using the unregistered function "function_exists" in a template is deprecated and will be removed in a future version. Use Smarty::registerPlugin to explicitly register a custom modifier. As of Smarty 5.X.X, templates must be revised again. The Smarty release 5.0.2 is already officially available. However, integration into FlatPress is not entirely trivial.
21 lines
1.3 KiB
Markdown
21 lines
1.3 KiB
Markdown
# from_charset
|
|
|
|
`from_charset` is used to transcode a string from a given charset to the
|
|
internal charset. This is the exact opposite of the [to_charset
|
|
modifier](language-modifier-to-charset.md).
|
|
|
|
## Parameters
|
|
|
|
| Parameter Position | Type | Required | Possible Values | Default | Description |
|
|
|--------------------|--------|----------|------------------------------------------------------------------------------------------------------------------------------|--------------|---------------------------------------------------------------|
|
|
| 1 | string | No | `ISO-8859-1`, `UTF-8`, and any character set supported by [`mb_convert_encoding()`](https://www.php.net/mb_convert_encoding) | `ISO-8859-1` | The charset encoding the value is supposed to be decoded from |
|
|
|
|
> **Note**
|
|
>
|
|
> Charset encoding should be handled by the application itself. This
|
|
> modifier should only be used in cases where the application cannot
|
|
> anticipate that a certain string is required in another encoding.
|
|
|
|
See also [Charset Encoding](../../programmers/charset.md), [to_charset
|
|
modifier](language-modifier-to-charset.md).
|