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

Groups > comp.lang.javascript > #35210

Re: Base64 encode using using windows-1250 encoding

Show all headers | View raw

Jupi Krem <nomail@gmail.com> wrote on 09 Jun 2018 in comp.lang.javascript:

> Evertjan. formulated the question :
>> Jupi <nomail@gmail.com> wrote on 09 Jun 2018 in comp.lang.javascript:
>>
>>> Thomas 'PointedEars' Lahn expressed precisely :
>>>> Jupi wrote:
>>>> ^^^^
>>>> Your real name belongs there.
>>> 
>>> Mr. Jupi Krem
>>> 
>>>>> I need to encode string using Central European Windows-1250
>>>>> encoding. 
>>>> 
>>>> Why?
>>> 
>>> Because I need it.
>>> 
>>>>> I know how to use simple base64 but it is utf-8 encoded and I need
>>>>> windows-1250.
>>>> 
>>>> Base64 is a transfer encoding.  UTF-8 and Windows-1250 are character 
>>>> encodings.  They have nothing to do with each other.
>>>> 
>>>> One uses character encodings to encode code points of characters of 
>>>> character sets.
>>>> 
>>>> One uses a transfer encoding to transfer (character) codes that
>>>> cannot be handled verbatim by a protocol or network connection.
>>>> 
>>>> <https://en.wikipedia.org/wiki/Base64>
>>> 
>>> I do not understand all this. I just need to encode some string which 
>>> contains Easteuropean characters to base64 string. Curently, when I 
>>> encode string, it is encoded using utf-8.
>>> Thank you.
>>
>> IMHO:
>>
>> base64 translates ["encodes"] any string
>> into a human-readable string.
>>
>> It should[!] not matter what is in the input string,
>> or what encoding is used.
>>
>> =======================
>>
>> <script type='text/javascript'> 
>> 'use strict';
>>
>> // Define the string
>> let str = 'Hello World!';
>>
>> // Encode the String
>> let encodedString = btoa(str);
>> console.log(encodedString); // Outputs: "SGVsbG8gV29ybGQh"
>>
>> // Decode the String
>> let decodedString = atob(encodedString);
>> console.log(decodedString); // Outputs: "Hello World!"
>>
>> </script>
>>
>> However please read these first:
>>
>> <https://developer.mozilla.org/en-US/docs/Web/API/WindowBase64/Base64
>> _encoding_and_decoding#The_Unicode_Problem>
>>
>> <https://stackoverflow.com/questions/30106476/using-javascripts-atob-to-
>> decode-base64-doesnt-properly-decode-utf-8-strings>
>>
>> https://caniuse.com/#search=btoa
>>
>> https://caniuse.com/#search=atob

[please do not toppost]

> Than you but your code works with English language - but not with 
> EastEuropean.

Nonsense, the language has nothing to do with it, as long as the letters are 
coded an you include the specific corrections on my code as shown in the 
links, I trust.

I expect a minimum of Javascript knowledge or experimenting joy on your 
part, as a Usenet NG is not a paid helpdesk.

-- 
Evertjan.
The Netherlands.
(Please change the x'es to dots in my emailaddress)

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