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 1fTPEB-000443-7V for pgadmin-hackers@arkaria.postgresql.org; Thu, 14 Jun 2018 10:11:39 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fTPE9-0007fe-Nx for pgadmin-hackers@arkaria.postgresql.org; Thu, 14 Jun 2018 10:11:37 +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 1fTPE9-0007fU-J1 for pgadmin-hackers@lists.postgresql.org; Thu, 14 Jun 2018 10:11:37 +0000 Received: from mail-oi0-x22e.google.com ([2607:f8b0:4003:c06::22e]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1fTPE5-0001j7-6L for pgadmin-hackers@postgresql.org; Thu, 14 Jun 2018 10:11:36 +0000 Received: by mail-oi0-x22e.google.com with SMTP id t22-v6so5126671oih.6 for ; Thu, 14 Jun 2018 03:11:32 -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=Uj9w/XSRaCYM5s5tYzde8opGpG2S0RtSP97ZiRZFtw4=; b=y7gwbnmgUDVMK6Xs8YS0Loj/9++d2JKETwkXzeQkWm+oIMPwYSEMsFJE+3qzgBzI4y wnaPMz73L+tJXE5oaYWwCBstkAtasl9k0eU8c6XIt6QtRsJ6dU9a6BN16bRf2Qa2OKia TeBvQLto30Fnkvz1h7k2Bo+K8xAvPsh7Qq+1WECGEMYIYRF3IZNfdI30ICsvidiJfRSD 7cA77FUlXEDaUQcN6bRu0rE/t5rYxV5df0/mLv1dXzzOMFRUHMKIeCfqP5km8UZ85XxD Y4YA37stvDECUVaCdn2+NoXkMtys94+9uw7MppInnCguQwmyn7NSvgn0ytWCr93oxDx3 X41g== 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=Uj9w/XSRaCYM5s5tYzde8opGpG2S0RtSP97ZiRZFtw4=; b=dUZwH6zxrNUoZngqzIEQtarh63Cq7Up3X6aQWYAF2DyVYdNbQC6C9U2S9g8pi8tr8g ORQa/spK/Ck+iXcChSKOdrPHe7eVhNdRuzWGQSlEoqxWxgK8bcEK56eZ0J8ZEJP0Ty2W 7oR+/O26/56A3UFcagSzFkNNfb9AdujqyEF/uyHkxbPg7ge3BtTNEEydAqXYSYUcpMst XqutjWRWQC9Bav3ur5BqXPd6Ys6YXK1xNJSo/9ruWQ/Nvh3wFiXUBSLCeW0yvsFv8xPc hJEQ26x2P6r9ZtdSxjiw8iaz/utJgook1iUM9EtLTRcupWJxTyuQpz2vNbZVfsogj0pp 6//w== X-Gm-Message-State: APt69E3RE4002wRJTCqAkFELAqt5HYQTimpXSHBA5X/ajW9eYOp8J7U9 0Sy5N22MBTHKWAKXUL7zcoN1EH/+ydQqC1JOnIw01w== X-Google-Smtp-Source: ADUXVKKgVmc2IrSlaPMctpGE5sQLtiRAHw9t+eVhy+/zsC8f1bA+elr5IEAlJfOmZ73iHbxlUSNe9lgExgHZdNonxi4= X-Received: by 2002:aca:1701:: with SMTP id j1-v6mr928248oii.113.1528971090696; Thu, 14 Jun 2018 03:11:30 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a4a:4081:0:0:0:0:0 with HTTP; Thu, 14 Jun 2018 03:11:30 -0700 (PDT) In-Reply-To: References: From: Khushboo Vashi Date: Thu, 14 Jun 2018 15:41:30 +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="000000000000bbbbf5056e9752a5" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --000000000000bbbbf5056e9752a5 Content-Type: text/plain; charset="UTF-8" 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. > Alternatively, just iterate the catalogs, and grab each of the source > strings from them and attempt to translate using the same catalog. > > The former method would ensure that the current state of the application > can be translated, but that of course might miss some strings in the > catalogs. The latter would validate each catalog against itself, but might > miss some strings that are in the application but haven't been merged yet > (though, that doesn't seem like it would cause a problem). > > -- > Dave Page > Blog: http://pgsnake.blogspot.com > Twitter: @pgsnake > > EnterpriseDB UK: http://www.enterprisedb.com > The Enterprise PostgreSQL Company > --000000000000bbbbf5056e9752a5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


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

On T= hu, Jun 14, 2018 at 6:39 AM, Khushboo Vashi <khushboo.vash= i@enterprisedb.com> wrote:
Hi,

Please find the fix for #3411 = -=C2=A0pgAdmin 4, Mac. The application server could not be contacted
<= div>
The issue is with french translation which has been take= n care in the attached patch.

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

One idea t= hat springs to mind is to generate a new template against the app, then ite= rate through all the translation catalogs and attempt to translate each str= ing that we find in the template we generated.

We can also use our messages.pot file as a temp= late and attempt to translate each string that we find in it against all th= e translation catalogs.=C2=A0
<= div>Alternatively, just iterate the catalogs, and grab each of the source s= trings from them and attempt to translate using the same catalog.

The former method would ensure that the current state of th= e application can be translated, but that of course might miss some strings= in the catalogs. The latter would validate each catalog against itself, bu= t might miss some strings that are in the application but haven't been = merged yet (though, that doesn't seem like it would cause a problem).

-- =
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
<= br>EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
=

--000000000000bbbbf5056e9752a5--