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

Groups > comp.lang.javascript > #35198

Re: Base64 encode using using windows-1250 encoding

From Jupi Krem <nomail@gmail.com>
Newsgroups comp.lang.javascript
Subject Re: Base64 encode using using windows-1250 encoding
Date 2018-06-09 10:01 +0200
Organization Iskon Internet d.d.
Message-ID <pfg1go$5f1$1@sunce.iskon.hr> (permalink)
References <pfe3di$lvq$1@sunce.iskon.hr> <3469849.XUi3uDslzQ@PointedEars.de> <pffn0r$t08$1@sunce.iskon.hr> <16824345.heBUIXtyyW@PointedEars.de> <3701683.oWXzg6A8BD@PointedEars.de>

Show all headers | View raw

It happens that Thomas 'PointedEars' Lahn formulated :
> Thomas 'PointedEars' Lahn wrote:
>
>> Jupi wrote:
>>> Thomas 'PointedEars' Lahn expressed precisely :
>>>> Jupi wrote:
>>>>> I need to encode string using Central European Windows-1250 encoding.
>>>> Why?
>>> 
>>> Because I need it.
>> 
>> No, you just *think* you need it.
>> 
>> <http://xyproblem.info/>
>> 
>>> […]
>>> I just need to encode some string which
>>> contains Easteuropean characters to base64 string.
>> 
>>   var b64 = window.btoa("Perišić");
>
> This throws
>
>> Uncaught DOMException: Failed to execute 'btoa' on 'Window': The string to 
>> be encoded contains characters outside of the Latin1 range.
>>     at <anonymous>:1:8
>
> in Chromium "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like 
> Gecko) Chrome/57.0.2987.98 Safari/537.36".  So apparently there is no easy 
> way.
>
> Since ECMAScript implementations only use a Unicode-compatible 16-bit 
> character encoding internally, a possibility appears to be convert the 
> original string to a representation of UTF-8 first, encode the individual 
> UTF-8 code units as if each of them were an ISO-8859-1 code unit, and then 
> encode the resulting character string with Base64.  For that, we could use 
>
>   var b64 = window.btoa(
>     encodeURIComponent("Perišić").replace(
>       /%([0-9A-F]{2})|./g,
>       (m, code) => (code) ? String.fromCharCode(parseInt(code, 16)) : m)
>   );
>
> Still, the question remains: Why does Base64 have to be used in the first 
> place?

Because I need to encode Perišić with windows-1250 encoding to become 
UGVyaZpp5g== and not UGVyacWhacSH like in your examples.

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