From b70beda0430fc142874999e52b451865284cd52a Mon Sep 17 00:00:00 2001 From: Georg Bauer Date: Thu, 6 Oct 2005 10:07:45 +0000 Subject: i18n: added support for the new DEFAULT_CHARSET setting in translators git-svn-id: http://code.djangoproject.com/svn/django/branches/i18n@788 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/translation.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'docs') diff --git a/docs/translation.txt b/docs/translation.txt index 5f63abdc09..e0a6531ba8 100644 --- a/docs/translation.txt +++ b/docs/translation.txt @@ -304,9 +304,9 @@ in the project library, but decided against this: with message files in the application tree, they can more easily be distributed. Another speciality is that we only use gettext and gettext_noop - that's -because django uses allways utf-8 strings internally. There isn't much use -in using ugettext or something like that, as you allways will need to produce -utf-8 anyway. +because django uses allways DEFAULT_CHARSET strings internally. There isn't +much use in using ugettext or something like that, as you allways will need to +produce utf-8 anyway. And last we don't use xgettext alone and some makefiles but use python wrappers around xgettext and msgfmt. That's mostly for convenience. -- cgit v1.3