Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.javascript > #35236

Re: Base64 encode using using windows-1250 encoding

Path csiph.com!aioe.org!.POSTED!not-for-mail
From Mickey Finn <mfinn@gmail.com>
Newsgroups comp.lang.javascript
Subject Re: Base64 encode using using windows-1250 encoding
Date Thu, 14 Jun 2018 19:22:17 -0300
Organization Aioe.org NNTP Server
Lines 34
Message-ID <pfupqo$1fio$1@gioia.aioe.org> (permalink)
References <pfe3di$lvq$1@sunce.iskon.hr> <3469849.XUi3uDslzQ@PointedEars.de> <pffn0r$t08$1@sunce.iskon.hr> <XnsA8FC60AA57528eejj99@194.109.6.166> <pfgb4v$2mb$1@solani.org> <pfgcpb$e3b$1@sunce.iskon.hr>
NNTP-Posting-Host B6md3aArm4BKZkzYoct3UA.user.gioia.aioe.org
Mime-Version 1.0
Content-Type text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding 8bit
X-Complaints-To abuse@aioe.org
User-Agent Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
X-Notice Filtered by postfilter v. 0.8.3
Content-Language en-GB
Xref csiph.com comp.lang.javascript:35236

Show key headers only | View raw


Jupi Krem wrote:
> on 09.06.2018, Frank Kozuschnik supposed :
>>
>> Base64 does not encode "strings" (= sequences of characters); it 
>> encodes sequences of octets (bytes).
>>
>> To "base64-encode a string", you actually perform two steps:
>>
>> 1. Apply a character encoding to transform the string into a sequence 
>> of bytes.
>> 2. Base64-encode the result to get a sequence of base64 characters.
>>
>> I guess Jupi just wants to use Windows-1250 encoding for step 1.
>>
>> He could use this code on node.js:
>>
>>    var windows1250 = require("windows-1250");
>>    var btoa = require('btoa');
>>    var bytes = windows1250.encode("Perišić");
>>    var b64 = btoa(bytes);
>>
>> <https://runkit.com/embed/tqtkt1s6ik5n>
>>
>> Result: b64 == "UGVyaZpp5g=="
> 
> Awesome. Thank you so much for this. It works perfect. :-)
>>
>>> It should[!] not matter what is in the input string,
>>> or what encoding is used.
>>
>> It actually does matter which encoding is used for step 1.

Thomas Lahn is always playing the role of Court Jester, except it is not 
fun.

Back to comp.lang.javascript | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Base64 encode using using windows-1250 encoding Jupi <nomail@gmail.com> - 2018-06-08 16:21 +0200
  Re: Base64 encode using using windows-1250 encoding Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2018-06-08 20:26 +0200
    Re: Base64 encode using using windows-1250 encoding Jupi <nomail@gmail.com> - 2018-06-08 22:09 +0200
      Re: Base64 encode using using windows-1250 encoding Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2018-06-08 22:57 +0200
    Re: Base64 encode using using windows-1250 encoding Jupi <nomail@gmail.com> - 2018-06-09 07:02 +0200
      Re: Base64 encode using using windows-1250 encoding Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2018-06-09 09:25 +0200
        Re: Base64 encode using using windows-1250 encoding Jupi Krem <nomail@gmail.com> - 2018-06-09 09:52 +0200
          Re: Base64 encode using using windows-1250 encoding Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2018-06-09 10:12 +0200
            Re: Base64 encode using using windows-1250 encoding Jupi Krem <nomail@gmail.com> - 2018-06-09 10:25 +0200
        Re: Base64 encode using using windows-1250 encoding Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2018-06-09 09:53 +0200
          Re: Base64 encode using using windows-1250 encoding Jupi Krem <nomail@gmail.com> - 2018-06-09 10:01 +0200
            Re: Base64 encode using using windows-1250 encoding Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2018-06-09 10:17 +0200
              Re: Base64 encode using using windows-1250 encoding Jupi Krem <nomail@gmail.com> - 2018-06-09 10:32 +0200
          Re: Base64 encode using using windows-1250 encoding Jupi Krem <nomail@gmail.com> - 2018-06-09 10:02 +0200
            Re: Base64 encode using using windows-1250 encoding Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2018-06-09 10:20 +0200
              Re: Base64 encode using using windows-1250 encoding Jupi Krem <nomail@gmail.com> - 2018-06-09 10:29 +0200
                Re: Base64 encode using using windows-1250 encoding Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2018-06-09 12:07 +0200
      Re: Base64 encode using using windows-1250 encoding "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2018-06-09 09:30 +0200
        Re: Base64 encode using using windows-1250 encoding Jupi Krem <nomail@gmail.com> - 2018-06-09 09:55 +0200
          Re: Base64 encode using using windows-1250 encoding "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2018-06-09 13:11 +0200
        Re: Base64 encode using using windows-1250 encoding Frank Kozuschnik <franko@nurfuerspam.de> - 2018-06-09 12:45 +0200
          Re: Base64 encode using using windows-1250 encoding Jupi Krem <nomail@gmail.com> - 2018-06-09 13:13 +0200
            Re: Base64 encode using using windows-1250 encoding Mickey Finn <mfinn@gmail.com> - 2018-06-14 19:22 -0300
  Re: Base64 encode using using windows-1250 encoding "Christoph M. Becker" <cmbecker69@arcor.de> - 2018-06-09 12:30 +0200
    Re: Base64 encode using using windows-1250 encoding Jupi Krem <nomail@gmail.com> - 2018-06-09 13:14 +0200
    Re: Base64 encode using using windows-1250 encoding Yappi <nomail@gmail.com> - 2018-06-09 13:33 +0200

csiph-web