使用fprintf实现单词倒序写入后，output.txt无法正常打开的问题

Hey there! Let's figure out why your output.txt is being stubborn when you double-click it, even though gedit can handle it just fine.

What's causing the error? #

The "Byte sequence invalid in the conversion's input" error almost always boils down to encoding mismatch. Xubuntu's default text viewer (like Mousepad) is strict about expecting UTF-8 encoding (the standard for most modern systems), but your program might have written the file using a different encoding, or accidentally included invalid byte sequences that don't fit UTF-8 rules. Gedit is more forgiving—it automatically detects and handles different encodings, which is why it works there.

Step-by-step fixes #

1. First, check what encoding your file is using

Open a terminal and run this command to get details about output.txt:

file output.txt

You'll see output like output.txt: UTF-8 text or something like output.txt: ISO-8859-1 text—this tells you exactly what encoding the file is using, which is key to fixing it.

2. Fix your program to write proper UTF-8

Depending on the language you're using, make sure you explicitly set UTF-8 when reading and writing files. Here are examples for common languages:

• Python:

  # Read input.txt with UTF-8 encoding
  with open("input.txt", "r", encoding="utf-8") as infile:
      words = infile.read().split()
  # Write reversed words to output.txt with UTF-8 encoding
  with open("output.txt", "w", encoding="utf-8") as outfile:
      outfile.write("\n".join(reversed(words)))
  

• C:
  Make sure you're using text mode (not binary mode) for file operations, and if your input has non-ASCII characters, ensure you're handling them as UTF-8. Avoid writing raw bytes that don't correspond to valid UTF-8 characters.

3. Fix the existing problematic file

If you don't want to re-run your program, you can convert the existing output.txt to UTF-8 using the iconv command. Replace OLD_ENCODING with the encoding you found from the file command (like ISO-8859-1 or GBK):

iconv -f OLD_ENCODING -t UTF-8 output.txt > fixed_output.txt

Now fixed_output.txt should open without errors when you double-click it.

4. Check your input file's encoding

If input.txt itself uses a non-UTF-8 encoding, reading it without specifying that encoding can lead to garbled text being written to output.txt. Use the same file input.txt command to check, and adjust your program's reading code to match that encoding.

内容的提问来源于stack exchange，提问作者Giuliolio93