Linux

48685 readers

399 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

Reading .mcn files? (lemmy.world)

submitted 1 year ago* (last edited 1 year ago) by EuroNutellaMan@lemmy.world to c/linux@lemmy.ml

8 comments fedilink hide all child comments

Hello y'all,

I need to get some information out of a .mcn file that is used by the Cary WinUV program (for windows XP), I know the file contains the info we're looking for but it's not readable on a text editor as per screenshot (the same thing appears via OSS - code and cat). Same for Nano which gives me a lot of tiny amongi.

Cary WinUV for some reason doesn't display the information we want, who know what they were thinking.

Anyone know a way to read the characters missing?

EDIT: Thanks everyone, I solved by saving it into csv through Cary WinUV but that may not work for everyone so thanks for all the replies

you are viewing a single comment's thread
view the rest of the comments

[–] cerement@slrpnk.net 5 points 1 year ago* (last edited 1 year ago)

hexdump comes stock with most distros, no editing features, but hexdump -C filename will at least let you see what’s in the file
from control characters and control codes, it looks like everything is separated by a set of three NUL characters (\00 in first screenshot or ^@ in the nano screenshot)
- EDIT: so the field names are three NUL characters, text for the name, and SOH (^A) terminating the field name – then a padded line for the field values (values are probably meant to be fixed length)
if you don’t find anything more convenient, as a last resort, you can turn to perl and sed, they were originally designed for situations like this, trying to get meaningful data out of disparate file formats