Javascript translations

From: Dave Page <dpage(at)pgadmin(dot)org>
To: Atira Odhner <aodhner(at)pivotal(dot)io>
Cc: pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>
Subject: Javascript translations
Date: 2017-03-23 12:37:16
Message-ID: CA+OCxoxmG_9ZEumosoDgyUZ6nNGwHDkW2COAgNKRCJLS1=Mr8Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

Hi Tira,

I've been spending spare minutes starting to move the JS translations
to use your new mechanism with an aim to minimising the Jinja
rendering. Unfortunately, I found a couple of issues; can you look
into them please?

1) String extraction no longer picks up strings in JS files. I guess
we may need a custom extractor for babel?

2) The docs were never updated to reflect the changes, e.g.
https://www.pgadmin.org/docs4/dev/translations.html

Thanks!

--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Responses

Browse pgadmin-hackers by date

  From Date Subject
Next Message Navnath Gadakh 2017-03-23 12:45:49 Re: pgAdmin 4 commit: Re-organised the regression directory now we have mul
Previous Message Dave Page 2017-03-23 12:35:32 pgAdmin 4 commit: Client side translation.