GNU MediaGoblin Wiki - User contributions [en]

Translations

2011-09-10T15:07:00Z

Jidm: /* Spanish */

= For translators =

You can translate our tools at Transifex:

https://www.transifex.net/projects/p/mediagoblin/resource/mediagoblin/

Note: please don't translate the words "MediaGoblin" or "GNU" into your native language. Those words should be retained as-is for branding reasons. :)

* Currently not needed: You have to join a language team to start translating. The language teams are here: https://www.transifex.net/projects/p/mediagoblin/teams/

== Notes for some language teams ==
=== German ===

Interessante Hinweise zur Übersetzung finden sich bei Gnome:
* http://live.gnome.org/de/UebersetzungsRichtlinien

In Abweichung von diesen Richtlinien wird momentan "du" für die Anrede benutzt.

=== Spanish ===

Se está adoptando la siguiente convención para la traducción al español. Si crees que alguna traducción se puede mejorar, sugiérela en la página de de discusión de este artículo.

{|
!Inglés
!Español
!Comentarios
|-
|you
|tú
|(segunda persona del singular, expresión informal)
|-
|media
|contenido
|-
|slug
|ficha
|}

= For developers =
== Marking strings for translation ==
=== In Jinja2 ===

See: http://jinja.pocoo.org/docs/templates/#i18n

Mostly like Django template i18n support, if you have any experience with that.

=== In python code ===

Usually, like this:

<pre>
from mediagoblin.util import pass_to_ugettext as _

def some_func(something):
return _(u'This string would tooootally be translatable now.')
</pre>

Except, in form modules we don't actually want to translate things because for various reasons that doesn't work, so we do the translation call template-side. So write the module to use the fake ugettext passthrough (which doesn't do any translation but still wraps things in _() so that Babel will know to extract these strings):

<pre>
from mediagoblin.util import fake_ugettext_passthrough as _

class FunkyMonkeyForm(wtforms.Form):
funky = wtforms.TextAreaField(
_('Funkiness description'))
</pre>

== Extracting translations ==

If you run buildout it should create a script called 'pybabel'. Use it to extract translations like so:

<pre>
./bin/pybabel extract -F babel.ini -o mediagoblin/i18n/en/LC_MESSAGES/mediagoblin.po .
</pre>

== Compiling translations ==

<pre>
./bin/pybabel compile -D mediagoblin -d mediagoblin/i18n/
</pre>

== Pulling translations from Transifex ==

Unfortunately until the next release of transifex-client which has been patched to have proper entry points, you have to run transifex-client from a virtualenv or from site-packages. But assuming that's done, pulling translations is easy:

<pre>
tx pull -a
</pre>

== Pushing new translations to Transifex ==

<pre>
tx push -s
</pre>

Translations

2011-09-10T14:57:34Z

Jidm:

= For translators =

You can translate our tools at Transifex:

https://www.transifex.net/projects/p/mediagoblin/resource/mediagoblin/

Note: please don't translate the words "MediaGoblin" or "GNU" into your native language. Those words should be retained as-is for branding reasons. :)

* Currently not needed: You have to join a language team to start translating. The language teams are here: https://www.transifex.net/projects/p/mediagoblin/teams/

== Notes for some language teams ==
=== German ===

Interessante Hinweise zur Übersetzung finden sich bei Gnome:
* http://live.gnome.org/de/UebersetzungsRichtlinien

In Abweichung von diesen Richtlinien wird momentan "du" für die Anrede benutzt.

=== Spanish ===

Se está adoptando la siguiente convención para la traducción al español. Si crees que alguna traducción se puede mejorar, sugiérela en la página de de discusión de este artículo.

"you" > "tú" (segunda persona del singular, expresión informal)
"media" > "contenido"
"slug" > "ficha"

= For developers =
== Marking strings for translation ==
=== In Jinja2 ===

See: http://jinja.pocoo.org/docs/templates/#i18n

Mostly like Django template i18n support, if you have any experience with that.

=== In python code ===

Usually, like this:

<pre>
from mediagoblin.util import pass_to_ugettext as _

def some_func(something):
return _(u'This string would tooootally be translatable now.')
</pre>

Except, in form modules we don't actually want to translate things because for various reasons that doesn't work, so we do the translation call template-side. So write the module to use the fake ugettext passthrough (which doesn't do any translation but still wraps things in _() so that Babel will know to extract these strings):

<pre>
from mediagoblin.util import fake_ugettext_passthrough as _

class FunkyMonkeyForm(wtforms.Form):
funky = wtforms.TextAreaField(
_('Funkiness description'))
</pre>

== Extracting translations ==

If you run buildout it should create a script called 'pybabel'. Use it to extract translations like so:

<pre>
./bin/pybabel extract -F babel.ini -o mediagoblin/i18n/en/LC_MESSAGES/mediagoblin.po .
</pre>

== Compiling translations ==

<pre>
./bin/pybabel compile -D mediagoblin -d mediagoblin/i18n/
</pre>

== Pulling translations from Transifex ==

Unfortunately until the next release of transifex-client which has been patched to have proper entry points, you have to run transifex-client from a virtualenv or from site-packages. But assuming that's done, pulling translations is easy:

<pre>
tx pull -a
</pre>

== Pushing new translations to Transifex ==

<pre>
tx push -s
</pre>

Translations

2011-09-08T16:08:40Z

Jidm: /* Notes for some language teams */

= For translators =

You can translate our tools at Transifex:

https://www.transifex.net/projects/p/mediagoblin/resource/mediagoblin/

Note: please don't translate the words "MediaGoblin" or "GNU" into your native language. Those words should be retained as-is for branding reasons. :)

* Currently not needed: You have to join a language team to start translating. The language teams are here: https://www.transifex.net/projects/p/mediagoblin/teams/

== Notes for some language teams ==
=== German ===

Interessante Hinweise zur Übersetzung finden sich bei Gnome:
* http://live.gnome.org/de/UebersetzungsRichtlinien

In Abweichung von diesen Richtlinien wird momentan "du" für die Anrede benutzt.

=== Spanish ===

Utilizar "Tú" en lugar de "Usted" para la segunda persona del singular.

= For developers =
== Marking strings for translation ==
=== In Jinja2 ===

See: http://jinja.pocoo.org/docs/templates/#i18n

Mostly like Django template i18n support, if you have any experience with that.

=== In python code ===

Usually, like this:

<pre>
from mediagoblin.util import pass_to_ugettext as _

def some_func(something):
return _(u'This string would tooootally be translatable now.')
</pre>

Except, in form modules we don't actually want to translate things because for various reasons that doesn't work, so we do the translation call template-side. So write the module to use the fake ugettext passthrough (which doesn't do any translation but still wraps things in _() so that Babel will know to extract these strings):

<pre>
from mediagoblin.util import fake_ugettext_passthrough as _

class FunkyMonkeyForm(wtforms.Form):
funky = wtforms.TextAreaField(
_('Funkiness description'))
</pre>

== Extracting translations ==

If you run buildout it should create a script called 'pybabel'. Use it to extract translations like so:

<pre>
./bin/pybabel extract -F babel.ini -o mediagoblin/i18n/en/LC_MESSAGES/mediagoblin.po .
</pre>

== Compiling translations ==

<pre>
./bin/pybabel compile -D mediagoblin -d mediagoblin/i18n/
</pre>

== Pulling translations from Transifex ==

Unfortunately until the next release of transifex-client which has been patched to have proper entry points, you have to run transifex-client from a virtualenv or from site-packages. But assuming that's done, pulling translations is easy:

<pre>
tx pull -a
</pre>

== Pushing new translations to Transifex ==

<pre>
tx push -s
</pre>