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

can you add supports for makensis INPUTCHARSET OUTPUTCHARSET? #4898

Closed
hdfeng265 opened this issue Apr 25, 2020 · 4 comments
Closed

can you add supports for makensis INPUTCHARSET OUTPUTCHARSET? #4898

hdfeng265 opened this issue Apr 25, 2020 · 4 comments
Assignees

Comments

@hdfeng265
Copy link

My windows charset is gbk, when i use makensis.exe to compile utf-8 nsis script, i got a "Bad text encoding" error.
image
Makensis.exe has option to specify input charset, but electron-builder seem doesn't have this option.
Can you add supports for makensis INPUTCHARSET OUTPUTCHARSET? Thanks!!

Temporarily, i modified "node_modules/electron-builder/node_modules/app-builder-lib/out/targets/nsis/NsisTarget.js" and "NsisTarget.js.map" by insert " args.push("-INPUTCHARSET", "UTF8", "-OUTPUTCHARSET", "UTF8");" into line 724, to support utf-8 nsis script.
image
image

@stale
Copy link

stale bot commented Jun 24, 2020

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@stale stale bot added the backlog label Jun 24, 2020
@stale stale bot closed this as completed Jul 1, 2020
@woxixiulayin
Copy link

same problem here.We have to use custom nsis script in electorn-builder, but got "Bad text encoding" error.We have to use INPUTCHARSET option with makensis. Any fix for that?

@sohobloo
Copy link
Contributor

These is useful to fix custom scripts encoding issues. Why closed.

@mmaietta mmaietta reopened this Sep 16, 2021
@stale stale bot removed the backlog label Sep 16, 2021
@mmaietta
Copy link
Collaborator

mmaietta commented Sep 16, 2021

Is there a particular reason why we wouldn't want the input and output charsets to be utf8? Seems like those args would be beneficial to just use by default.

Any reason to not use utf16 instead btw?

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

No branches or pull requests

4 participants