| | 294 | Application message files are a bit complicated to discover - they need the |
|---|
| | 295 | i18n middleware to be found. If you don't use the middleware, only the |
|---|
| | 296 | django message files and project message files will be processed. |
|---|
| | 297 | |
|---|
| | 298 | Additionally you should think about how to structure your translation |
|---|
| | 299 | files. If your applications should be delivered to other users and should |
|---|
| | 300 | be used in other projects, you might want to use app-specific translations. |
|---|
| | 301 | But using app-specific translations and project translations could produce |
|---|
| | 302 | weird problems with make-messages: make-messages will traverse all directories |
|---|
| | 303 | below the current path and so might put message IDs into the project |
|---|
| | 304 | message file that are already in application message files. Easiest way |
|---|
| | 305 | out is to store applications that are not part of the project (and so carry |
|---|
| | 306 | their own translations) outside the project tree. That way make-messages |
|---|
| | 307 | on the project level will only translate stuff that is connected to your |
|---|
| | 308 | explicit project and not stuff that is distributed independently. |
|---|
| | 309 | |
|---|
