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 1fTPKt-0004Uv-Cr for pgadmin-hackers@arkaria.postgresql.org; Thu, 14 Jun 2018 10:18:35 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fTPKs-0008Qc-3g for pgadmin-hackers@arkaria.postgresql.org; Thu, 14 Jun 2018 10:18:34 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fTPKr-0008QS-QW for pgadmin-hackers@lists.postgresql.org; Thu, 14 Jun 2018 10:18:33 +0000 Received: from mail-wm0-x235.google.com ([2a00:1450:400c:c09::235]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1fTPKn-00058o-Qc for pgadmin-hackers@postgresql.org; Thu, 14 Jun 2018 10:18:31 +0000 Received: by mail-wm0-x235.google.com with SMTP id x6-v6so9562460wmc.3 for ; Thu, 14 Jun 2018 03:18:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pgadmin-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=dC9MkkqptpZPQS1jZo0NYf/qpEJn/3iAyPqNT/jL6wc=; b=fQCodjJg5Xc/55xHGsCRjt+/CU2clK8q6qk37nLpIAbHh255a4maF4zL4QzkfXIFBr XiDZl7pPCuinvVZWWd6j94ekAF8rx1ZKywzhrWe+mi1z72DHgDFYMTdR4NGZq9IedzYg Lu5xGou2pqYCwShYXDsJq7ChrsHtnt127UugSY9jQX27wptabSMG2t7dYK+t6gT1nWPe ujI7VkWwHAr4sul1/2Ll4EAp7bSwM663JpGimrYF48/ZNbvgqrUjpUSCBC2ui8zmbQlw wE5QXkSuDxJ99IMc9GSM/T1BCdwHerIdRHBg/0pILZMPEBGawlWnknWQpm7MZmmU4npP aOHw== 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=dC9MkkqptpZPQS1jZo0NYf/qpEJn/3iAyPqNT/jL6wc=; b=eOVyeHS8CdyM9Cu5LCmp3PbOf3ZWk0jt2G9wLh/0/ewi4AU7rnk9t1LvHpF43ktkMf ZNv3GuCOImn+gPY6SUQXsV6sHPW3ZNAtADzJMI8CH3cT/R0rrnlKudD4L9tAs+C3t/fP 31jQVbI5V7I62jdgxa4P8QzCP7oEnCwOHv54JJgiVTwPbqfXNIrZpAqxvwal4n6281OB yzoNZ7umctr7hqqV6qkXBbdJuun8k5hgGX0VJX5kA2OhtUpb17L5aTjkXdVH1egnIPUH n4wJkiCYIz9/i+NjRw5NqR7j869tWL1e08fwXrSHNH+GIYeG20V+loxV3hCh+5XcLZc0 MkHA== X-Gm-Message-State: APt69E3YkfLSDakMMIp4JZEF66pxCJytyUuYaB78aUoFBbNnwelrj8F4 9dtV1OzYb3s8sKYJ79lqIYHXOYt/SE/64Z0cNoQ+Fw== X-Google-Smtp-Source: ADUXVKKEuKVirzRYddFKgGSTrMCMe1CdhCKE0YgAezVtMEkulLziX7ze8hxZbOfbNAWY05gkbLlWG5A4irQcwS3NYBQ= X-Received: by 2002:a1c:3ac6:: with SMTP id h189-v6mr1488192wma.64.1528971508126; Thu, 14 Jun 2018 03:18:28 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a1c:2907:0:0:0:0:0 with HTTP; Thu, 14 Jun 2018 03:18:27 -0700 (PDT) In-Reply-To: References: From: Dave Page Date: Thu, 14 Jun 2018 11:18:27 +0100 Message-ID: Subject: Re: [pgAdmin4][Patch]: RM #3411 - pgAdmin 4, Mac. The application server could not be contacted To: Khushboo Vashi Cc: pgadmin-hackers Content-Type: multipart/alternative; boundary="0000000000009d27ae056e976b44" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --0000000000009d27ae056e976b44 Content-Type: text/plain; charset="UTF-8" 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. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company --0000000000009d27ae056e976b44 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Thu, Jun 14, 2018 at 11:11 AM, Khushboo Vashi <= khushb= oo.vashi@enterprisedb.com> wrote:


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

On Thu, Jun 14, 2018 at 6:39 AM, Khushboo Vashi = <kh= ushboo.vashi@enterprisedb.com> wrote:
Hi,

Please find the fix= for #3411 -=C2=A0pgAdmin 4, Mac. The application server could not be conta= cted

The issue is with french translation which ha= s been taken care in the attached patch.

<= /div>
We've seen similar issues with translations before. Ho= w can we write a test (or tests) to validate them?

One idea that springs to mind is to generate a new template against the ap= p, then iterate through all the translation catalogs and attempt to transla= te 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.=C2=A0

I suggested generating a new template for the = test as we only occasionally update messages.pot (typically prior to releas= es), so it may be out of date.

--
Dave Page
Blog: = http://pgsnake.bl= ogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com<= br>The Enterprise PostgreSQL Company
--0000000000009d27ae056e976b44--