Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rDHeX-001Wuc-9q for pgsql-general@arkaria.postgresql.org; Wed, 13 Dec 2023 05:19:25 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rDHeV-00BNGB-Uf for pgsql-general@arkaria.postgresql.org; Wed, 13 Dec 2023 05:19:23 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rDHeU-00BNDc-5L for pgsql-general@lists.postgresql.org; Wed, 13 Dec 2023 05:19:23 +0000 Received: from out2-smtp.messagingengine.com ([66.111.4.26]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rDHeQ-00Bjne-6E for pgsql-general@postgresql.org; Wed, 13 Dec 2023 05:19:21 +0000 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 765EC5C0189; Wed, 13 Dec 2023 00:19:15 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Wed, 13 Dec 2023 00:19:15 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm3; t=1702444755; x=1702531155; bh=RwKmqt90jgHsE+XUUvRiXurtuvvVoaygGEQ8IFFI69I=; b= tp+MK7Ly/EeJ8y7+XG8uXAtY+M/E5Onvv054IojYG3EOcumcKedgOOPrkXfVy1n0 Sb3j8DVOccw26dE5XRc7Pt9JhT6qXCLmfrOINSiqAhioxngN0Cqfta4g/+tYBnnX +xfOo1Y0atfdMU7eCxlBffndOIfWhu/PmjGWEIVn1wyG95chpUA4rsLIc/r4ZL8c 3+1vTUT3UJcz/8cnJBfezc8HOpHLZg1ttACRuIJoQucMEjIH67YoNHE+R7AFkuRF eNM2nSliKRlZLpMTeIv093nBJ6VMnVeXUZen/VtVReS0iXFIW6NAiBMKjQ9Bqd74 cB8Xvxy6Cn1DLGYbBk6FVQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1702444755; x= 1702531155; bh=RwKmqt90jgHsE+XUUvRiXurtuvvVoaygGEQ8IFFI69I=; b=E uU0S5ueJj7Sg1FzAyFjkImnvGKUMJckfN+qi0sctTNlPBABBt+hzbSQXCXc+JYYe pFkBSZOo5xSoieEAG5GRnioGHg4OrUyJ6IIYhhIO3R4iz5jaiLoP0+276q7i7ALL 6p4i6Fbfi54uqy+RNywthd6uA6Cf87EVD0oSu3Ypg6vXN/N8AEgTIwZ4W67n1eXo 3xOq843Vn6+/b2zD1+S2wh1G3Duxyl9HDYwSkcTFjx7KwRBpBLCm1+izhKHfGK8N +mABkabfziQudkUJyN0ryF1LcLs3cR0f08O4I2httM3DpHLSTJplfzrctMTjr7vG liPU7oov/W7Vew0mW0l/g== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrudelhedgkedvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvvehfhfgjtgfgsehtkeertddtvdejnecuhfhrohhmpeetughr ihgrnhcumfhlrghvvghruceorggurhhirghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtg homheqnecuggftrfgrthhtvghrnhepfeegfeeiuedtgffgteeggfehkeejheetieeliefg teeikeejvdeiveeigfehvedtnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpe hmrghilhhfrhhomheprggurhhirghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtghomh X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 13 Dec 2023 00:19:14 -0500 (EST) Message-ID: Date: Tue, 12 Dec 2023 21:19:13 -0800 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: how can I fix my accent issues? Content-Language: en-US To: Igniris Valdivia Baez Cc: pgsql-general References: <5ee6b669-f85d-4464-903f-e6556a06536c@manitou-mail.org> <14d8be16-155f-43dd-af26-21f6b1f9e717@aklaver.com> <2fecae7e-5912-4368-86b7-0d01989b05ce@aklaver.com> From: Adrian Klaver In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 12/12/23 16:09, Igniris Valdivia Baez wrote: > Hello to all, to clarify the data is moving this way: > 1. The data is extracted from a database in postgres using Pentaho(Kettle) > 2. Here is there is a bifurcation some data is loaded into the destiny > database and behaves fine the other scenario the data is saved in xls > files to be reviewed How is saved to xls files? > 3. After the revision the data is loaded to the destiny database and > here is were I believe the issue is, because the data is reviewed in > Windows and somehow Pentaho is not understanding correctly the > interaction between both operating systems. Defined reviewed, on particular is the data changed? How is transferred from xls to to the database? Is the data reviewed in Excel only on one machine or many? What the locales/encodings/character sets involved? > > PD: when the hole operation is executed in Windows it never fails Define what you mean by whole operation done in Windows. > Thank you all -- Adrian Klaver adrian.klaver@aklaver.com