| 287 | | Django does support localising your application into a locale for which |
|---|
| 288 | | Django itself has not been translated -- it will ignore your translation |
|---|
| 289 | | files. If you were to try this and Django supported it, you would |
|---|
| 290 | | inevitably see a mixture of translated strings (from your application) and |
|---|
| 291 | | English strings (from Django itself). If you are wanting to support a |
|---|
| 292 | | locale for your application that is not already part of Django, you will |
|---|
| 293 | | need to make at least a minimal translation of the Django core. |
|---|
| | 287 | Django does not support localising your application into a locale for |
|---|
| | 288 | which Django itself has not been translated -- it will ignore your |
|---|
| | 289 | translation files. If you were to try this and Django supported it, you |
|---|
| | 290 | would inevitably see a mixture of translated strings (from your |
|---|
| | 291 | application) and English strings (from Django itself). If you are wanting |
|---|
| | 292 | to support a locale for your application that is not already part of |
|---|
| | 293 | Django, you will need to make at least a minimal translation of the Django |
|---|
| | 294 | core. |
|---|
