Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fTPOR-0004lc-7Y for pgadmin-hackers@arkaria.postgresql.org; Thu, 14 Jun 2018 10:22:15 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fTPOQ-0003yV-9W for pgadmin-hackers@arkaria.postgresql.org; Thu, 14 Jun 2018 10:22:14 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fTPN3-0002el-6j for pgadmin-hackers@lists.postgresql.org; Thu, 14 Jun 2018 10:20:49 +0000 Received: from mail-ot0-x22d.google.com ([2607:f8b0:4003:c0f::22d]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1fTPMz-0001wS-67 for pgadmin-hackers@postgresql.org; Thu, 14 Jun 2018 10:20:48 +0000 Received: by mail-ot0-x22d.google.com with SMTP id 101-v6so6453881oth.4 for ; Thu, 14 Jun 2018 03:20:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=FhyNWclriwOuqmhBXFJcay1o6TFXocBFypcb9RH12Lk=; b=ba0Wo3o2RrJLmfxEBOb9aBij6728bzPuziZFQMg3BdPg0lXTHV6F4UlZKn23QjFXW0 nJe5UIHCMi7KbMrhhO5l8tqzZ9Xyovj8y3sPe7OfrAQk+AN93OFy8fsssUJIQL8Zipnq /IjqSifSjBku2/04Tzku+4gbSpAr+88UYTaSOsCWQgb7dOShz6IdsrFvPT1KsxyCgkTc KKrBXdr85/teotlCMTqMHRXhcLx9sP185uE0mddD4G4ACGxoFZAriZ3s7/vrLdyrGgOq 9M9YOeKioRNq9qcIfAL89umQWyXuGIZrSl/T1drGzE2cfHvK0Z6FhepNJsyul4UquSMX EEMA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=FhyNWclriwOuqmhBXFJcay1o6TFXocBFypcb9RH12Lk=; b=MfdZtG0IA1U9yS0QvRn4tqv/SmaztkWfeepN5aHTVgOHbmiSI9eCV1IOFosxTk0vPy oXgfZVpwlgHHZyrfz5PnDF2m3A7lOZPPX+Hvn563yrF10J3D4INMtDqVegq+ObtEUKMQ KAUMpRtj8ESSWU2Ljiz1abmwKMTGWP/mwffKbEWTs9VHBO5xyuK52fjeky9KGKLbetGW oJhQeXKsjIlfH/NXEzXN1phyxeTbVrKDRDSLrfbjuEqkEQ9/ZoMOg8AqIlIvyS1zTQHn OXb8xC4EFdI+DMHs1eBETgl5wgjVuPqLxSwM2dr4reufzLchmlRMaJT/VjjfEJmZFlXG oMjg== X-Gm-Message-State: APt69E13wPx3FtQmxAmnlshkoNTUmsR8leNJ6F7nfjEsbMtaDCPqZo0+ gXY8ckTwrXvPoeh9zo5ZznZMI0fo9hi+wTDaz7kmdA== X-Google-Smtp-Source: ADUXVKKBVOgDERZIFWuoD78J4dzMsZ+KHczVQBtHah7IgGmua56CJ05lozGzjRfJZCrz8NEco9dmX7ePWSFzboC8Y48= X-Received: by 2002:a9d:2010:: with SMTP id n16-v6mr886143ota.275.1528971642793; Thu, 14 Jun 2018 03:20:42 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a4a:4081:0:0:0:0:0 with HTTP; Thu, 14 Jun 2018 03:20:42 -0700 (PDT) In-Reply-To: References: From: Khushboo Vashi Date: Thu, 14 Jun 2018 15:50:42 +0530 Message-ID: Subject: Re: [pgAdmin4][Patch]: RM #3411 - pgAdmin 4, Mac. The application server could not be contacted To: Dave Page Cc: pgadmin-hackers Content-Type: multipart/alternative; boundary="000000000000a40479056e977328" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --000000000000a40479056e977328 Content-Type: text/plain; charset="UTF-8" On Thu, Jun 14, 2018 at 3:48 PM, Dave Page wrote: > > > On Thu, Jun 14, 2018 at 11:11 AM, Khushboo Vashi < > khushboo.vashi@enterprisedb.com> wrote: > >> >> >> On Thu, Jun 14, 2018 at 1:20 PM, Dave Page wrote: >> >>> Hi >>> >>> On Thu, Jun 14, 2018 at 6:39 AM, Khushboo Vashi < >>> khushboo.vashi@enterprisedb.com> wrote: >>> >>>> Hi, >>>> >>>> Please find the fix for #3411 - pgAdmin 4, Mac. The application server >>>> could not be contacted >>>> >>>> The issue is with french translation which has been taken care in the >>>> attached patch. >>>> >>> >>> We've seen similar issues with translations before. How can we write a >>> test (or tests) to validate them? >>> >>> One idea that springs to mind is to generate a new template against the >>> app, then iterate through all the translation catalogs and attempt to >>> translate each string that we find in the template we generated. >>> >>> We can also use our messages.pot file as a template and attempt to >> translate each string that we find in it against all the translation >> catalogs. >> > > I suggested generating a new template for the test as we only occasionally > update messages.pot (typically prior to releases), so it may be out of date. > > Okay, we can implement this way. > -- > Dave Page > Blog: http://pgsnake.blogspot.com > Twitter: @pgsnake > > EnterpriseDB UK: http://www.enterprisedb.com > The Enterprise PostgreSQL Company > --000000000000a40479056e977328 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Thu, Jun 14, 2018 at 3:48 PM, Dave Page <dpage@pgadmin.org><= /span> wrote:


On Thu= , Jun 14, 2018 at 11:11 AM, Khushboo Vashi <khushboo.vashi@e= nterprisedb.com> wrote:


On Thu, Jun 14, 2018 at 1:20 PM, Dave Page &l= t;dpage@pgadmin.org<= /a>> wrote:
Hi=

On Thu,= Jun 14, 2018 at 6:39 AM, Khushboo Vashi <khushboo.vashi@ent= erprisedb.com> wrote:
=
Hi,

Please find the fix for #3411 -=C2= =A0pgAdmin 4, Mac. The application server could not be contacted
=
The issue is with french translation which has been taken ca= re in the attached patch.

We've seen similar issues with translations before. How can we write = a test (or tests) to validate them?

One idea that = springs to mind is to generate a new template against the app, then iterate= through all the translation catalogs and attempt to translate each string = that we find in the template we generated.

=
We can also use our messages.pot file as a t= emplate and attempt to translate each string that we find in it against all= the translation catalogs.=C2=A0
<= br>
I suggested generating a new template for the test as = we only occasionally update messages.pot (typically prior to releases), so = it may be out of date.

Okay, we can implement this way.=C2=A0

--000000000000a40479056e977328--