Re: Automated Translation Management -- Surely someone has already done this?

[ville]

The django-rosetta app might help you: http://code.google.com/p/django-rosetta/
It allows easy online editing of the po/mo files.

-ville

On Feb 16, 9:47 am, DrMeers  wrote:
> I have developed a Django site for an open source project, with
> contributors around the globe.
>
> A brief aside/background: I have used django-cms to store the majority
> of the content for the site, but rather than adopting its usual tactic
> of translating a whole page at a time, have used {% trans %} and {%
> blocktrans %} tags within the content, and written a script to dump
> the database content into dummy HTML files so they get picked up by
> django-admin.py's makemessages utility. This way translators don't
> have to hunt for which line/paragraph within a large page has been
> changed, nor worry about messing up the layout of the page when
> translating.
>
> Back to the point: this website will be translated into over a dozen
> languages, and undergo regular content updates. I have written code
> that runs django-admin.py makemessages (via subprocess.Popen, though I
> suspect there is a better way to run it within python?) and allows the
> download of the latest .po file for any given language. I would also
> like registered/authenticated users to be able to easily upload their
> updated translation files and have them automatically update the
> website (using compilemessages). So when I make a change to the
> website, I'd like the registered translators to be automatically
> emailed, and asked to update their translations (again, simply
> download and upload the new .po file via the website). This is easy
> enough to do, and saves me a HUGE amount of work over the next few
> years.
>
> But the reason I am posting this: this is such a common procedure,
> surely someone has written this stuff before? But I cannot find it
> anywhere online. Isn't there a django-translation-management package
> already written? Or should I create it once I finish coding? How have
> other people streamlined this process?

--~--~-~--~~~---~--~~
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 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
-~--~~~~--~~--~--~---

Re: Automated Translation Management -- Surely someone has already done this?

[Marco Bazzani]

so seems that the answer is no, and If you would share your work I
(and probably many other) will appreciate it very much :)
regards

On Mon, Feb 16, 2009 at 8:47 AM, DrMeers  wrote:
>
> I have developed a Django site for an open source project, with
> contributors around the globe.
>
> A brief aside/background: I have used django-cms to store the majority
> of the content for the site, but rather than adopting its usual tactic
> of translating a whole page at a time, have used {% trans %} and {%
> blocktrans %} tags within the content, and written a script to dump
> the database content into dummy HTML files so they get picked up by
> django-admin.py's makemessages utility. This way translators don't
> have to hunt for which line/paragraph within a large page has been
> changed, nor worry about messing up the layout of the page when
> translating.
>
> Back to the point: this website will be translated into over a dozen
> languages, and undergo regular content updates. I have written code
> that runs django-admin.py makemessages (via subprocess.Popen, though I
> suspect there is a better way to run it within python?) and allows the
> download of the latest .po file for any given language. I would also
> like registered/authenticated users to be able to easily upload their
> updated translation files and have them automatically update the
> website (using compilemessages). So when I make a change to the
> website, I'd like the registered translators to be automatically
> emailed, and asked to update their translations (again, simply
> download and upload the new .po file via the website). This is easy
> enough to do, and saves me a HUGE amount of work over the next few
> years.
>
> But the reason I am posting this: this is such a common procedure,
> surely someone has written this stuff before? But I cannot find it
> anywhere online. Isn't there a django-translation-management package
> already written? Or should I create it once I finish coding? How have
> other people streamlined this process?
> >
>

--~--~-~--~~~---~--~~
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 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
-~--~~~~--~~--~--~---

Re: Automated Translation Management -- Surely someone has already done this?

[Torsten Bronger]

Hallöchen!

DrMeers writes:

> [...]
>
> Back to the point: this website will be translated into over a
> dozen languages, and undergo regular content updates. I have
> written code that runs django-admin.py makemessages (via
> subprocess.Popen, though I suspect there is a better way to run it
> within python?) and allows the download of the latest .po file for
> any given language. I would also like registered/authenticated
> users to be able to easily upload their updated translation files
> and have them automatically update the website (using
> compilemessages).

We use http://translate.sourceforge.net/wiki/pootle/index for this.
It's not really easy to set up, and it doesn't integrate with
Django, but it works.

Tschö,
Torsten.

-- 
Torsten Bronger, aquisgrana, europa vetus
   Jabber ID: torsten.bron...@jabber.rwth-aachen.de


--~--~-~--~~~---~--~~
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 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
-~--~~~~--~~--~--~---

Re: Automated Translation Management -- Surely someone has already done this?

[DrMeers]

Thanks for the prompt response Alex.

> You really want to be storing the translations at the DB level to that
> effect check out:http://code.google.com/p/django-multilingual/
> orhttp://code.google.com/p/transdb/

I've checked these out before, however don't see how they solve my
problem. They seem to only operate on entire fields of a model, which
is not what I want. I could use django-cms' own translation framework
if I was happy to translate an entire field at once. Unless I'm
missing something in the somewhat minimal documentation?
--~--~-~--~~~---~--~~
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 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
-~--~~~~--~~--~--~---

Re: Automated Translation Management -- Surely someone has already done this?

[Alex Gaynor]

On Mon, Feb 16, 2009 at 2:47 AM, DrMeers  wrote:

>
> I have developed a Django site for an open source project, with
> contributors around the globe.
>
> A brief aside/background: I have used django-cms to store the majority
> of the content for the site, but rather than adopting its usual tactic
> of translating a whole page at a time, have used {% trans %} and {%
> blocktrans %} tags within the content, and written a script to dump
> the database content into dummy HTML files so they get picked up by
> django-admin.py's makemessages utility. This way translators don't
> have to hunt for which line/paragraph within a large page has been
> changed, nor worry about messing up the layout of the page when
> translating.
>
> Back to the point: this website will be translated into over a dozen
> languages, and undergo regular content updates. I have written code
> that runs django-admin.py makemessages (via subprocess.Popen, though I
> suspect there is a better way to run it within python?) and allows the
> download of the latest .po file for any given language. I would also
> like registered/authenticated users to be able to easily upload their
> updated translation files and have them automatically update the
> website (using compilemessages). So when I make a change to the
> website, I'd like the registered translators to be automatically
> emailed, and asked to update their translations (again, simply
> download and upload the new .po file via the website). This is easy
> enough to do, and saves me a HUGE amount of work over the next few
> years.
>
> But the reason I am posting this: this is such a common procedure,
> surely someone has written this stuff before? But I cannot find it
> anywhere online. Isn't there a django-translation-management package
> already written? Or should I create it once I finish coding? How have
> other people streamlined this process?
> >
>
You really want to be storing the translations at the DB level to that
effect check out:
http://code.google.com/p/django-multilingual/
or
http://code.google.com/p/transdb/

Alex

-- 
"I disapprove of what you say, but I will defend to the death your right to
say it." --Voltaire
"The people's good is the highest law."--Cicero

--~--~-~--~~~---~--~~
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 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
-~--~~~~--~~--~--~---

Automated Translation Management -- Surely someone has already done this?

[DrMeers]

I have developed a Django site for an open source project, with
contributors around the globe.

A brief aside/background: I have used django-cms to store the majority
of the content for the site, but rather than adopting its usual tactic
of translating a whole page at a time, have used {% trans %} and {%
blocktrans %} tags within the content, and written a script to dump
the database content into dummy HTML files so they get picked up by
django-admin.py's makemessages utility. This way translators don't
have to hunt for which line/paragraph within a large page has been
changed, nor worry about messing up the layout of the page when
translating.

Back to the point: this website will be translated into over a dozen
languages, and undergo regular content updates. I have written code
that runs django-admin.py makemessages (via subprocess.Popen, though I
suspect there is a better way to run it within python?) and allows the
download of the latest .po file for any given language. I would also
like registered/authenticated users to be able to easily upload their
updated translation files and have them automatically update the
website (using compilemessages). So when I make a change to the
website, I'd like the registered translators to be automatically
emailed, and asked to update their translations (again, simply
download and upload the new .po file via the website). This is easy
enough to do, and saves me a HUGE amount of work over the next few
years.

But the reason I am posting this: this is such a common procedure,
surely someone has written this stuff before? But I cannot find it
anywhere online. Isn't there a django-translation-management package
already written? Or should I create it once I finish coding? How have
other people streamlined this process?
--~--~-~--~~~---~--~~
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 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
-~--~~~~--~~--~--~---