Using the language files is the solution here. Even if your site only supports the English language, it still means that you can have .po files for just English. Once you understand how it all hangs together you'll be away.
http://docs.djangoproject.com/en/1.1/topics/i18n/#topics-i18n I have a site that is just English but we allow the client to choose what text they want to use. The text in templates can be descriptions, for example you could type "Home page welcome message" in a template and mark it for translation. Then in the English .po file you can see what the text is used for and input the correct English for it. On Aug 9, 4:19 pm, bobhaugen <bob.hau...@gmail.com> wrote: > I want to provide customizable vocabularies for an open-source django > project, where each deployer can use different terms for strings that > appear in templates (e.g. field names, form field descriptions, help > text, page titles, etc.) > > Would django language files work for this purpose? Everything will be > in English (at this stage), so that would involve (if I understand > correctly) customizing the English language .po file. (Right?) > > Does that smell like a reasonable solution? Any hidden rocks? > > Has anybody done anything like this, either using language files or > some other solution? If so, how did you do it, and how did it work in > practice? -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
