Re: Base64 Encoding -- RPG400-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: Base64 Encoding
From: Mihael Schmidt <mihael@xxxxxxxxxxxxxx>
Date: Fri, 17 May 2019 18:44:50 +0200
List-archive: <https://archive.midrange.com/rpg400-l/>
List-help: <mailto:rpg400-l-request@lists.midrange.com?subject=help>
List-id: RPG programming on IBM i <rpg400-l.lists.midrange.com>
List-post: <mailto:rpg400-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/rpg400-l>, <mailto:rpg400-l-request@lists.midrange.com?subject=unsubscribe>

+1

I am a little taxed atm. Sorry for my wording and it didn't reflect what I meant to say.

Glad that someone jumped in to help.

On 17.05.19 16:08, John Yeung wrote:

On Fri, May 17, 2019 at 2:41 AM Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx> wrote:

Where many people get this wrong is that they encode ASCII or
Unicode data

Scott, respectfully, referring to "Unicode" (or "UNICODE" as you later
do) as an *encoding* is just as misleading as what Mihael said.

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.