How to change LXTerminal's character encoding?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
0
down vote

favorite












The default character encoding on LXTerminal (on Lubuntu 18.04) is UTF-8.



Can I change it to UTF-16 Little Endian?







share|improve this question



















  • Why do you need this?
    – Ignacio Vazquez-Abrams
    May 27 at 21:25










  • @Ignacio Vazquez-Abrams I don't need it to fix a problem, I'm just learning about character encodings, and how to make the Terminal change its character encoding, etc.
    – user292805
    May 27 at 21:32










  • First run locale -a and see if that's even an option.
    – Ignacio Vazquez-Abrams
    May 27 at 22:18










  • @Ignacio Vazquez-Abrams No UTF-16 is not an option on LXTerminal. But on Konsole, UTF-16 is also not an option in the result of locale -a, but I can still set UTF-16 as the character encoding in the Konsole settings.
    – user292805
    May 28 at 16:09










  • Yes, because Konsole lets you explicitly set the encoding.
    – Ignacio Vazquez-Abrams
    May 28 at 16:14














up vote
0
down vote

favorite












The default character encoding on LXTerminal (on Lubuntu 18.04) is UTF-8.



Can I change it to UTF-16 Little Endian?







share|improve this question



















  • Why do you need this?
    – Ignacio Vazquez-Abrams
    May 27 at 21:25










  • @Ignacio Vazquez-Abrams I don't need it to fix a problem, I'm just learning about character encodings, and how to make the Terminal change its character encoding, etc.
    – user292805
    May 27 at 21:32










  • First run locale -a and see if that's even an option.
    – Ignacio Vazquez-Abrams
    May 27 at 22:18










  • @Ignacio Vazquez-Abrams No UTF-16 is not an option on LXTerminal. But on Konsole, UTF-16 is also not an option in the result of locale -a, but I can still set UTF-16 as the character encoding in the Konsole settings.
    – user292805
    May 28 at 16:09










  • Yes, because Konsole lets you explicitly set the encoding.
    – Ignacio Vazquez-Abrams
    May 28 at 16:14












up vote
0
down vote

favorite









up vote
0
down vote

favorite











The default character encoding on LXTerminal (on Lubuntu 18.04) is UTF-8.



Can I change it to UTF-16 Little Endian?







share|improve this question











The default character encoding on LXTerminal (on Lubuntu 18.04) is UTF-8.



Can I change it to UTF-16 Little Endian?









share|improve this question










share|improve this question




share|improve this question









asked May 27 at 21:18









user292805

61




61











  • Why do you need this?
    – Ignacio Vazquez-Abrams
    May 27 at 21:25










  • @Ignacio Vazquez-Abrams I don't need it to fix a problem, I'm just learning about character encodings, and how to make the Terminal change its character encoding, etc.
    – user292805
    May 27 at 21:32










  • First run locale -a and see if that's even an option.
    – Ignacio Vazquez-Abrams
    May 27 at 22:18










  • @Ignacio Vazquez-Abrams No UTF-16 is not an option on LXTerminal. But on Konsole, UTF-16 is also not an option in the result of locale -a, but I can still set UTF-16 as the character encoding in the Konsole settings.
    – user292805
    May 28 at 16:09










  • Yes, because Konsole lets you explicitly set the encoding.
    – Ignacio Vazquez-Abrams
    May 28 at 16:14
















  • Why do you need this?
    – Ignacio Vazquez-Abrams
    May 27 at 21:25










  • @Ignacio Vazquez-Abrams I don't need it to fix a problem, I'm just learning about character encodings, and how to make the Terminal change its character encoding, etc.
    – user292805
    May 27 at 21:32










  • First run locale -a and see if that's even an option.
    – Ignacio Vazquez-Abrams
    May 27 at 22:18










  • @Ignacio Vazquez-Abrams No UTF-16 is not an option on LXTerminal. But on Konsole, UTF-16 is also not an option in the result of locale -a, but I can still set UTF-16 as the character encoding in the Konsole settings.
    – user292805
    May 28 at 16:09










  • Yes, because Konsole lets you explicitly set the encoding.
    – Ignacio Vazquez-Abrams
    May 28 at 16:14















Why do you need this?
– Ignacio Vazquez-Abrams
May 27 at 21:25




Why do you need this?
– Ignacio Vazquez-Abrams
May 27 at 21:25












@Ignacio Vazquez-Abrams I don't need it to fix a problem, I'm just learning about character encodings, and how to make the Terminal change its character encoding, etc.
– user292805
May 27 at 21:32




@Ignacio Vazquez-Abrams I don't need it to fix a problem, I'm just learning about character encodings, and how to make the Terminal change its character encoding, etc.
– user292805
May 27 at 21:32












First run locale -a and see if that's even an option.
– Ignacio Vazquez-Abrams
May 27 at 22:18




First run locale -a and see if that's even an option.
– Ignacio Vazquez-Abrams
May 27 at 22:18












@Ignacio Vazquez-Abrams No UTF-16 is not an option on LXTerminal. But on Konsole, UTF-16 is also not an option in the result of locale -a, but I can still set UTF-16 as the character encoding in the Konsole settings.
– user292805
May 28 at 16:09




@Ignacio Vazquez-Abrams No UTF-16 is not an option on LXTerminal. But on Konsole, UTF-16 is also not an option in the result of locale -a, but I can still set UTF-16 as the character encoding in the Konsole settings.
– user292805
May 28 at 16:09












Yes, because Konsole lets you explicitly set the encoding.
– Ignacio Vazquez-Abrams
May 28 at 16:14




Yes, because Konsole lets you explicitly set the encoding.
– Ignacio Vazquez-Abrams
May 28 at 16:14















active

oldest

votes











Your Answer







StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);








 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f446355%2fhow-to-change-lxterminals-character-encoding%23new-answer', 'question_page');

);

Post as a guest



































active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes










 

draft saved


draft discarded


























 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f446355%2fhow-to-change-lxterminals-character-encoding%23new-answer', 'question_page');

);

Post as a guest













































































Popular posts from this blog

How to check contact read email or not when send email to Individual?

Displaying single band from multi-band raster using QGIS

How many registers does an x86_64 CPU actually have?