Malcolm Tredinnick wrote: > I'm not so much worried about the one-off conversion (after all, it's > for those peoples' benefit that we're doing this) as much as filesystems > that store in a particular encoding by default. There's no reliable, > non-expensive way to automatically detect the file encoding, so it > probably has to be done with a setting. > > TEMPLATE_CHARSET is not the right name, though. Templates aren't the > problem: the filesystem encoding is. So maybe FILESYSTEM_ENCODING or > something explicit like that. We'll need to graft it into each > filesystem-based template loader and it defaults to utf-8.
But filesystem doesn't control the encoding of file's content. It may do some things to file names but it's another story. The default encoding in which a file is saved depends on locale and on a text editor's abilities and settings (Notepad.exe saves in Windows' system single-byte encoding by default but may easily save in utf-8 if told so). So if we're talking about file's content then it's only templates we should worry about since Python sources have their own way to deal with it that must be used to correctly deal with u'...' things. So I'm still +1 on TEMPLATE_CHARSET. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
