|
This diagram shows an example of how different input sources can vary their charsets.
The output may also use different charsets. The goal for the i18n system to allow a
seamless transition from one charset to another in an easy way.
TODO — Image not available in archive
Title: Charset Sources Diagram (eZ i18n)
File: /doc/images/charset.png
What this image shows:
Diagram showing the different charset input sources handled by the eZ i18n system (URL, HTTP POST, database, template files, .ts translation files, INI settings) and how they are converged to a single internal charset, then converted to the output charset for the HTTP response. Illustrates seamless multi-charset handling across the CMS pipeline.
Replacement instructions:
Redraw based on sdk/ezi18n/view/charset_sources documentation. Save as /doc/images/charset.png
See /sdk/missing.html for the full list of missing images.
|