Thread: [pgadmin-hackers] Process for Creating Translations
Hi Hackers,
In the patches we sent recently, we added text to the User Interface. We know that calling getText translates it but currently we don't have translations for any of the new text.
Is there a process for getting these text translated to other languages?
Thanks,
Shruti & Joao
Hi On Thu, Jun 1, 2017 at 4:40 PM, Shruti B Iyer <siyer@pivotal.io> wrote: > Hi Hackers, > > In the patches we sent recently, we added text to the User Interface. We > know that calling getText translates it but currently we don't have > translations for any of the new text. > > Is there a process for getting these text translated to other languages? I periodically update the translation templates, and then put a shout out to the translators. I try to minimise that though - I don't want to be pinging them every other commit for obvious reasons. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
I periodically update the translation templates, and then put a shout
out to the translators. I try to minimise that though - I don't want
to be pinging them every other commit for obvious reasons.
Thanks for the response, Dave. To clarify, we should continue to wrap English text in the get_text function and you will be able to generate a list of newly needed translations periodically? I just want to understand whether we need to keep track of all the new phrases from each story we complete.
Thanks,
Matt
On Thu, Jun 1, 2017 at 1:05 PM, Dave Page <dpage@pgadmin.org> wrote:
Hi
On Thu, Jun 1, 2017 at 4:40 PM, Shruti B Iyer <siyer@pivotal.io> wrote:
> Hi Hackers,
>
> In the patches we sent recently, we added text to the User Interface. We
> know that calling getText translates it but currently we don't have
> translations for any of the new text.
>
> Is there a process for getting these text translated to other languages?
I periodically update the translation templates, and then put a shout
out to the translators. I try to minimise that though - I don't want
to be pinging them every other commit for obvious reasons.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-hackers
Right, you don't need to do anything except wrap strings in the appropriate macros/functions.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK:http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK:http://www.enterprisedb.com
The Enterprise PostgreSQL Company
I periodically update the translation templates, and then put a shout
out to the translators. I try to minimise that though - I don't want
to be pinging them every other commit for obvious reasons.Thanks for the response, Dave. To clarify, we should continue to wrap English text in the get_text function and you will be able to generate a list of newly needed translations periodically? I just want to understand whether we need to keep track of all the new phrases from each story we complete.Thanks,MattOn Thu, Jun 1, 2017 at 1:05 PM, Dave Page <dpage@pgadmin.org> wrote:Hi
On Thu, Jun 1, 2017 at 4:40 PM, Shruti B Iyer <siyer@pivotal.io> wrote:
> Hi Hackers,
>
> In the patches we sent recently, we added text to the User Interface. We
> know that calling getText translates it but currently we don't have
> translations for any of the new text.
>
> Is there a process for getting these text translated to other languages?
I periodically update the translation templates, and then put a shout
out to the translators. I try to minimise that though - I don't want
to be pinging them every other commit for obvious reasons.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-hackers