How to Fix the Issue of `less` CLI Program Interpreting UTF-8 Text Files as Binary

Have you ever encountered the issue of the less command-line interface program interpreting UTF-8 text files as binary? This can be frustrating, especially when you're trying to view and navigate through text files using less. Luckily, there are a few simple steps you can take to fix this problem.

What is the `less` command?

Before we dive into the solution, let's quickly understand what the less command does. less is a popular program used to view the contents of a text file in a terminal window. It allows you to scroll through the file, search for specific text, and perform other useful functions.

The Issue: UTF-8 Text Files Interpreted as Binary

The problem arises when you try to view a UTF-8 encoded text file using less, but it interprets the file as binary. This means that instead of displaying the actual text content, you see a series of strange characters or symbols. This can happen due to a misconfiguration or incorrect settings.

Fixing the Issue

To resolve this problem, follow these steps:

Step 1: Check your Locale Settings

Start by checking your system's locale settings. The locale determines the character encoding used by default. Open a terminal window and run the following command:

This will display various locale-related settings. Look for the LANG variable, which specifies the default language and character encoding. Make sure it is set to a UTF-8 compatible value, such as:

If the LANG variable is not set to a UTF-8 compatible value, you can change it by modifying the appropriate configuration file. For example, if you are using the Bash shell, you can edit the .bashrc file in your home directory and add the following line:

Save the file and restart your terminal for the changes to take effect.

Step 2: Set the `LESSCHARSET` Environment Variable

If the issue persists after setting the LANG variable, you can try setting the LESSCHARSET environment variable explicitly. This variable specifies the character encoding that less should use.

To set the LESSCHARSET variable, open a terminal window and run the following command:

This will set the LESSCHARSET variable to UTF-8. You can add this command to your shell's configuration file (e.g., .bashrc) to make it persistent.

Conclusion

By following these steps, you should be able to fix the issue of less interpreting UTF-8 text files as binary. Remember to check your locale settings and set the LESSCHARSET environment variable correctly. Now you can view and navigate through UTF-8 encoded text files using less without any problems!