Request support for viewing UTF-16

[ciscohack]

some log file when i use moor to read it. It shows the content like showing in screenshot why? whereas same file when i use bat to read it show in proper format. I noticed if you used macos textEdit app and save the log in in rich text then moor shows the log like below screenshot most of time but bat tool render properly

[walles]

Can you post the file so I can try?

And also, can you please update the screenshot so that all four window borders are clearly visible?

[ciscohack]

Can you post the file so I can try?

And also, can you please update the screenshot so that all four window borders are clearly visible?

NTP.log

i had other log file also but now not able to find it

[walles]

Your log file is UTF-16 encoded, which is currently not supported by moor.

I'll treat this as a feature request.

As a workaround until moor supports UTF-16, you might consider configuring your tool to create logs in UTF-8 instead.

UTF-16 seems like something very few people use, so a number of tools will likely have problems with it:
https://trends.google.com/trends/explore?date=all&q=%2Fm%2F07x89,%2Fm%2F0b1gl

[ciscohack]

@walles Thanks for prompt response. how did you check abou encoding. I have few other files having similar rendering issue not sure if those also have unicode issue but BAT tool work fine. Not able to find those files else would have checked it

[walles]

how did you check abou encoding.

I loaded the file in Visual Studio Code. It rendered fine in there, and the editor said "UTF-16 LE" ("Little Endian") at the bottom of the screen.

[ciscohack]

how did you check abou encoding.

I loaded the file in Visual Studio Code. It rendered fine in there, and the editor said "UTF-16 LE" ("Little Endian") at the bottom of the screen.

Can we add same in moor status baar also .btw thanks i think there is one more log i am not getting had same issue doubt that also has same issue

[0ion9]

If you have access to iconv, then you can probably pipe the output of iconv -f utf-16le -t utf-8 FILENAME into moor for the time being.

If you also have uchardet which detects character encodings, then you could completely automate it, as uchardet FILENAME will output in a format suitable for -f option of iconv, ie, in summary, iconv -f $(uchardet FILENAME) -t utf-8 FILENAME | moor (I'm assuming your shell is sh/bash-like here)