On Nov 27, 11:10 am, Tim <[EMAIL PROTECTED]> wrote:
> For multilingual sites, is it not easier to maintain and keep all the
> translations in .po files? The idea of splitting up the required
> translations would mean that translators must use two different
> interfaces.
Well, those are two differ
For multilingual sites, is it not easier to maintain and keep all the
translations in .po files? The idea of splitting up the required
translations would mean that translators must use two different
interfaces. There are frameworks for translating .po files that keep
revisions, suggestions etc. Th
That's what i am about to do, but if guys from the development team
agree we could implement it in the official django code
On Nov 9, 3:34 pm, Eugene Morozov <[EMAIL PROTECTED]> wrote:
> I've implemented similar system. Only I have used MyFlatPage and
> MyFlatPageTranslation models, because it ma
I've implemented similar system. Only I have used MyFlatPage and
MyFlatPageTranslation models, because it makes easier to locate and
translate pages in the admin interface.
On 9 нояб, 15:25, DvD <[EMAIL PROTECTED]> wrote:
> Hi everyone,
> lately i was trying to internationalize a wesite which had
Sorry, that shouldn't be MyFlatPage but just FlatPage...
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from t
Hi everyone,
lately i was trying to internationalize a wesite which had flatpages,
but i also needed to translate those pages so i came up with this idea
to get site specific AND language specific flatpages.
I put on the FlatPage class this attribute:
language= models.CharField(maxlengt
6 matches
Mail list logo
