I'm working on re-flowing the markup on each page to fix mis-matched tags,
etc. Once that's done we need to wrap every English text section with
either:
{% trans 'message' %} or {% blocktrans %}The phrase to translate.{%
endblocktrans %}.
Docs here:
https://docs.djangoproject.com/en/1.8/topics/i18n/translation/#internationalization-in-template-code
Once you've done that, run
$ cactus messages:make
that will write PO files for the messages to locale/en/ -- we then get
those translated. probably with a new transifex project?
On Wed, May 13, 2015 at 4:14 PM, S.Brandt <s.bra...@mixxx.org> wrote:
> Got any i18n docs for cactus, e.g. howto generate gettext translation
> templates, or howto display translated strings?
> Nothing@ http://cactusformac.com/docs/
>
> On May 13, 2015, at 2:44 AM, RJ Ryan <rr...@mixxx.org> wrote:
>
> It will also make translations of the website possible.
>
>
>
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Get Mixxx, the #1 Free MP3 DJ Mixing software Today
http://mixxx.org
Mixxx-devel mailing list
Mixxx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mixxx-devel
