Re: Bilingual Content Creation

That really depends on what you want to do with it. 

We are using both dbgettext with Rosetta and transmeta in our application. 

Transmeta creates extra database fields with _en and _es (or other language-codes). You then edit the fields in django admin, like regular fields. It is an easy way to create a multi-lingual application. However the problem with it is when you want external translators to edit the fields, the django admin interface is not good. You wouldn't want them to login and edit there.

The best thing about using dbgettext and Rosetta is that you can send the PO files to translators and they can use there regular software to do the translations. Then you can just import the po file in the project. You can then use rosetta to handle updates thereafter.

So in summary, either is good as long as you are doing the translations yourself or you are doing it as you go along, however if you have alot of translations that need to be translated at once, Rosetta and dbgettext is probably a better solution.

Regards,

Andréas

2014-04-23 18:48 GMT+02:00 Nate <broinjc@gmail.com>:

I'm making a Django site that will have Spanish and English content.

I know I will be using i18n. I want users to be able to create and translate content easily from the django admin. 

I am wondering how I should implement this.

I've looked at these apps:

• Rosetta
  
• transdb
• multi-lingual

And I've also read that one option would be to create duplicate model fields renamed with _en and _es suffixes accordingly.

What's the slickest route to go?

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/1422c693-2dc2-4f3a-b358-be8886d6718b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CALXYUb%3DBRg2jB7tuptcj_n4o8qVYJzYB-ykZ1gKGDDV4sU%2Bh%2Bw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.