Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix encoding issue #23

Merged
merged 1 commit into from
Jan 11, 2023
Merged

Fix encoding issue #23

merged 1 commit into from
Jan 11, 2023

Conversation

TeddyBear06
Copy link
Contributor

Fixes #7 using a Blob rather than btoa (as btoa() creates a Base64-encoded ASCII string).

Side modification, the {{VALUES}}\n substitution does not works on my environnement (even if I take care about Linux vs Windows line feeds...). Feel free to remove this modification if it's not relevant and I just missed up something along the way :-)

Fixes mprimi#7 using a Blob rather than btoa (as btoa() creates a Base64-encoded ASCII string).

Side modifiation, the {{VALUES}}\n substitution does not works on my environnement as the substituion is searching for a litteral \n in the template. Feel free to remove this modification if it's not relevant and I juste missed something along the way :-)
@TeddyBear06 TeddyBear06 reopened this Jan 10, 2023
@mprimi mprimi merged commit 3fad300 into mprimi:main Jan 11, 2023
@mprimi
Copy link
Owner

mprimi commented Jan 11, 2023

Thank you very much @TeddyBear06!

I struggled and googled a bunch regarding b64 encoding of non-ascii, but didn't come upon this. It's maybe one of those things that is so obvious to web/JS developers that there's not a lot of Q&A online.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug] The generated secret.html file does not support UTF-8 chars
2 participants