Path: csiph.com!feeder.erje.net!1.eu.feeder.erje.net!news.roellig-ltd.de!news.mb-net.net!open-news-network.org!.POSTED.59.236.197.178.dynamic.wless.lssmb00p-cgnat.res.cust.swisscom.ch!not-for-mail
From: Thomas 'PointedEars' Lahn <PointedEars@web.de>
Newsgroups: comp.lang.javascript
Subject: Re: Base64 encode using using windows-1250 encoding
Date: Sat, 09 Jun 2018 12:07:03 +0200
Organization: PointedEars Software (PES)
Lines: 22
Message-ID: <1933241.8CYMbNPUb9@PointedEars.de>
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> <pfg1j0$5f5$1@sunce.iskon.hr> <3956723.jocM3bjZqr@PointedEars.de> <pfg36b$6mp$1@sunce.iskon.hr>
Reply-To: Thomas 'PointedEars' Lahn <cljs@PointedEars.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8Bit
Injection-Info: gwaiyur.mb-net.net; posting-host="59.236.197.178.dynamic.wless.lssmb00p-cgnat.res.cust.swisscom.ch:178.197.236.59"; logging-data="3714"; mail-complaints-to="abuse@open-news-network.org"
User-Agent: KNode/4.14.2
Cancel-Lock: sha1:tHZ7npx9sN3yei/1ddKz89zgB4g=
Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAGFBMVEXTxa4RFk5dUWANED8PFEfy7+MGBiW+n3ZNF/QuAAACaElEQVQ4jVXUwVOcMBQG8Dc7Rc4PUntdWV2uxjDpGaGeozOp1woar4jd5t/v9wLstMwsA/ntlxdCAgUc1hjTc9/JCZfGoo3wG3HdmdAWrIJRHe7GM/TmpY5VFefuVcAkkPbLIaN8rmPmjloyZxgyR3GuJ4K0AGtJ2htz8o7yqikm759fldQXaMpbDzjKAG+8v+AugVTOPO5DOjLvGtUYQwh0CPjnVMyGd+8/GfUB5nLKJDD2aLDh5HYyMDJGDwQIo2ZmZcKbowNmAdB/AzyFhrmF2MHRb0QJJfaAnwGB6orZhoykLzJtGwF/xpYxI1dswomiUj3gTuAIqCn/4C7cULwGNBtwMTk3Y4LfKB5YUaOKBKYtpplm7u0vip8tU1NWWyI/7XdcSuIDoMt6rVHMWT0DbjHPGqDqZVSa6zleLcUTcIKLoMv3ueJluALtAo9B302zPPlrtiVScRdCjXvVh3e3JpYa/jjkuC9N+LrBMlz/eAN4eQijX2EdLo6c5tGGHwLyHFtXk89dDGHwCVhG9T0S/j55AhRZgkMCmUQXJ49TnS1wnQDvw0eAh9ICeMmEFbCnPMFzjAvsWoEWEFdYEx+S0MoUZ1gT1wId8+AF3Bl2OoEu906AUHx5VLw/gXYg/x84loOah/2UYNrgiwSwGO7RfUzVBbx/kgpckumGOi6QirtD6gkLTitbnxNol47S2jVc2vsN5kPqaAHT8uUdAJM4v/DanjYOwmUjWznGfwB7sGtAtor5BgofDuzaRj4kSQAqDakTsKORa3Q3xKi3gE1fhl71KRMqrdZ2AWNNg/YOhQyrVBnb+i+nEg4bsDA+egAAAABJRU5ErkJggg==
X-Face: %i>XG-yXR'\"2P/C_aO%~;2o~?g0pPKmbOw^=NT`tprDEf++D.m7"}HW6.#=U:?2GGctkL,f89@H46O$ASoW&?s}.k+&.<b';Md8`dH6iqhT)6C^.Px|[=M@7=Ik[_w<%n1Up"LPQNu2m8|L!/3iby{-]A+#YE}Kl{Cw$\U!kD%K}\2jz"QQP6Uqr],./"?;=4v
X-User-ID: U2FsdGVkX1/k5555x2Pb1nIyBkzIZ+K0zm+IwBztyaQLWzTasxWlTQ==
Xref: csiph.com comp.lang.javascript:35207

Jupi Krem wrote:

> OK I have (for example) UGVyaZpp5g== in database which is written by
> other software/developer. Now I need to encode Perišić to get same
> result as I see in database.

And how did the Base64-encoded data get into the database in the first 
place?

I can think of no good reason to store Base64-encoded strings in a database.
Which database engine and DBMS?

If possible, permanently decode and convert the database field instead.

There is also no good reason anymore to use Windows-1250.  In a Web 
application, use UTF-8 instead.  If it is not for a Web application,
you should have said so from the start; see the FAQ.

-- 
PointedEars
FAQ: <http://PointedEars.de/faq> | <http://PointedEars.de/es-matrix>
<https://github.com/PointedEars> | <http://PointedEars.de/wsvn/>
Twitter: @PointedEars2 | Please do not cc me./Bitte keine Kopien per E-Mail.