summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorい。 <99417239+koupro0204@users.noreply.github.com>2024-05-07 14:30:17 +0900
committerSarah Boyce <42296566+sarahboyce@users.noreply.github.com>2024-05-23 12:35:20 +0200
commit718ed69751c9b3923ffa99ce000e733c8350d0a6 (patch)
tree7b47b2016786ebf43d0d6ad017b8f6d99aa84ec5 /docs
parent99273fd525129a973639044dfb12cfd732d8f1d6 (diff)
Fixed #35430 -- Corrected docs on timezone conversion in templates.
Diffstat (limited to 'docs')
-rw-r--r--docs/topics/i18n/timezones.txt5
1 files changed, 4 insertions, 1 deletions
diff --git a/docs/topics/i18n/timezones.txt b/docs/topics/i18n/timezones.txt
index c11bd03b09..0d866dac6c 100644
--- a/docs/topics/i18n/timezones.txt
+++ b/docs/topics/i18n/timezones.txt
@@ -9,7 +9,10 @@ Overview
When support for time zones is enabled, Django stores datetime information in
UTC in the database, uses time-zone-aware datetime objects internally, and
-translates them to the end user's time zone in templates and forms.
+converts them to the end user's time zone in forms. Templates will use the
+:ref:`default time zone <default-current-time-zone>`, but this can be updated
+to the end user's time zone through the use of :ref:`filters and tags
+<time-zones-in-templates>`.
This is handy if your users live in more than one time zone and you want to
display datetime information according to each user's wall clock.