Tìm kiếm hỗ trợ

Tránh các lừa đảo về hỗ trợ. Chúng tôi sẽ không bao giờ yêu cầu bạn gọi hoặc nhắn tin đến số điện thoại hoặc chia sẻ thông tin cá nhân. Vui lòng báo cáo hoạt động đáng ngờ bằng cách sử dụng tùy chọn "Báo cáo lạm dụng".

Learn More

How to set the DEFAULT encoding to UTF8 for RAW *.txt files

  • 2 trả lời
  • 1 gặp vấn đề này
  • 2 lượt xem
  • Trả lời mới nhất được viết bởi cor-el

more options

Quite often it is needed to use non local plain text files WITHOUT BYTE ORDER MARK, but containing a few utf8 encoding national characters, just like: http://math.bme.hu/~prohlep/i3/i3anyag06.txt

Firefox is the only mainstream browser what is not set up as factory default to use utf8.

We can not assume, that the readers of the raw text files, all of them will correctly adjust the locale for fall back, or each time to click view encoding etc ... the result of which goes away as soon as the reader wants to refresh the text file with F5.

Is there a cultural solution of this problem? I can not force hundreds of university students to uncomfortable non persistent solution!

Due to important developing tools DO NOT tolerate the presence of BOM, they consider it as a language syntax error, therefore we can not disregard of using BOM-less raw text C/C++ source files CONTAINING comments in UTF8 national languages.

Quite often it is needed to use non local plain text files WITHOUT BYTE ORDER MARK, but containing a few utf8 encoding national characters, just like: http://math.bme.hu/~prohlep/i3/i3anyag06.txt Firefox is the only mainstream browser what is not set up as factory default to use utf8. We can not assume, that the readers of the raw text files, all of them will correctly adjust the locale for fall back, or each time to click view encoding etc ... the result of which goes away as soon as the reader wants to refresh the text file with F5. Is there a cultural solution of this problem? I can not force hundreds of university students to uncomfortable non persistent solution! Due to important developing tools DO NOT tolerate the presence of BOM, they consider it as a language syntax error, therefore we can not disregard of using BOM-less raw text C/C++ source files CONTAINING comments in UTF8 national languages.

Tất cả các câu trả lời (2)

more options

Hi, you explain a lot but are not saying if these are pages you are making for students to view. If you are making pages in HTML5 then use the <meta charset="UTF-8"> in your header as per https://www.w3schools.com/charsets/ref_html_utf8.asp

If this has to do with page encoding built in as you mention : To submit suggestions for new or changed features, may I suggest: Feedback: https://qsurvey.mozilla.com/s3/FirefoxInput/

Please let us know if this solved your issue or if need further assistance.

more options

Firefox 59+ has a pref that you can set to true on the about:config page.

  • intl.charset.fallback.utf8_for_file = true

You can open the about:config page via the location/address bar. You can accept the warning and click "I accept the risk!" to continue.