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
Cannot use UTF8 in rundeck #222
Comments
Hi Ujfjhz, do you mean scripts embedded in your job, or do they come from an external file? Do you mind posting a snippet or sample as a gist or to pastebin? |
Yeah, no matter which workflow step(command,script,script file) I embedded in my Job, I cannot echo Chinese Words correctly, the Chinese Words are often shown as "?????" or others strange. For example: All the cases above,I cannot use Chinese correctly. And another question, when the Rundeck Server dispatch scripts to target nodes , what enviroment configuration file will be read,~/.bash_profile, ~/.bashrc or others? Thank you very much. |
FormattedOutputStream and LogOutputStream do not correctly handle multibyte characters |
We are addressing this issue when logging system is revamped. |
i have fixd this bug ,anybody need the bugfix can email me |
Hi, can you post it as a gist if you are unable to do a pull request? Thanks Greg
|
Great!Thank you very much! |
i do prefer paste the code here,but the editor does not support code ,some spcecial chars omitted. |
hi @brightye i think this is what you were trying to paste? https://gist.github.com/gschueler/7902292 |
hi @gschueler it's exactly what i paste ,but the code is corrupt since some special html reserved chars like > < ommited by github editor. |
if there are any other changes you had, please post them in a gist from https://gist.github.com thanks |
@gschueler ,take a look at this gist: https://gist.github.com/brightye/11204119 |
Hi all, are there any news on this issue? |
There are some UTF8 or GBK words in my scripts, when I execute the job which contain the scripts , the output cannot give the correct words.
The text was updated successfully, but these errors were encountered: