WINDOWFILEEDIT writes UTF-8 BOM when contents are only ASCII
A Logo programming environment for Microsoft Windows
Brought to you by:
david_costanzo
Menu
▾
▴
#560 WINDOWFILEEDIT writes UTF-8 BOM when contents are only ASCII
As of FMSLogo 8.0.0, WINDOWFILEEDIT always inserts a UTF-8 BOM at the beginning of every file it writes. As a result, programs which are saved in WINDOWFILEEDIT cannot be run by versions of FMSLogo prior to 8.0.0 or other Logo environments.
WINDOWFILEEDIT should be changed to only include a UTF-8 BOM if the contents include a non-ASCII character, following the behavior of SAVE.
How Reproducible:
Every time
Steps to Reproduce:
- Run:
WINDOWFILEEDIT "myfile.lgo []. - Type some ASCII characters, like
show 1. - Choose File -> Save and Exit.
- Examine the myfile.lgo in a hex editor.
What Happens:
myfile.lgo begins with the byte sequence EF BB BF.
Expected Result:
myfile.lgo contains begins with the ASCII characters that you typed into myfile.lgo.
I have checked in a fix for this as [r5657]. Because this is conceptually a regression in FMSLogo 8.0.0 that impacts backward-compatibility, I plan to fast-track this fix into a micro-release: FMSLogo 8.0.2.
Related
Commit: [r5657]