diff options
| author | Hemanth V. Alluri <hdrive1999@gmail.com> | 2018-10-25 05:31:19 +0530 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2018-10-24 20:01:19 -0400 |
| commit | fd49701ab9bb9352b549ec02600af1ee35794d40 (patch) | |
| tree | 804e1a424114833382dcd9da9ddc29cf0819b30e /docs/ref/unicode.txt | |
| parent | c86a3d80a25acd1887319198ca21a84c451014ad (diff) | |
Removed a useless sentence in docs/ref/unicode.txt.
Diffstat (limited to 'docs/ref/unicode.txt')
| -rw-r--r-- | docs/ref/unicode.txt | 4 |
1 files changed, 1 insertions, 3 deletions
diff --git a/docs/ref/unicode.txt b/docs/ref/unicode.txt index 8617442318..9d0311deef 100644 --- a/docs/ref/unicode.txt +++ b/docs/ref/unicode.txt @@ -2,9 +2,7 @@ Unicode data ============ -Django natively supports Unicode data everywhere. Providing your database can -somehow store the data, you can safely pass around strings to templates, -models, and the database. +Django supports Unicode data everywhere. This document tells you what you need to know if you're writing applications that use data or templates that are encoded in something other than ASCII. |