| | 1 | = String Encoding In Django = |
| | 2 | |
| | 3 | == Introduction == |
| | 4 | |
| | 5 | Django accepts and sends data to and from a number of external entities: databases, web browsers (form input, HTML output), XML syndication feeds, PDF documents... the list is quite long. Since we would like Django to be able to offer all these features to people in all locations, we need to pay particular attention to our internationalization support. |
| | 6 | |
| | 7 | An important part of internationalization is how we handle strings inside Django and at the interfaces between Django and other applications. |
| | 8 | |
| | 9 | This page tries to capture both what we are aiming to do internally and what we are currently doing (which might be different from the eventual goal). It is partly an attempt to get my (Malcolm Tredinnick's) thoughts down in a logical form. This stuff is very tricky and it's easy to become confused when working on the code. That happens to me regularly, so I need notes like this. |
| | 10 | |
| | 11 | == The Big Picture == |
| | 12 | |
| | 13 | == HTTP Input Handling == |
| | 14 | |
| | 15 | === Form Input Handing === |
| | 16 | |
| | 17 | == Passing Strings Between Django and the Developer's Code == |
| | 18 | |
| | 19 | == Database Interaction == |
| | 20 | |
| | 21 | == Talking To External Processes == |
| | 22 | |
| | 23 | == HTTP Output == |
| | 24 | |
| | 25 | === Template Output === |
| | 26 | |
| | 27 | == Current Problems and Solution Outline == |