|
It's not for external editors sake, but for being able to file-in non-ascii .st's generated in 7+ in older Pharos. These older versions have always used the presence/absence of a BOM to decide whether to use utf8 or macroman to read the file; omit it, and all of a sudden, the perfectly encoded utf8 gets interpreted as macroman.
|
|
|
Priority: 5 – Fix If Time
|
|
Status: Resolved (Fix Review Needed)
|
|
Assigned to: hilaire
|
|
Milestone: Pharo7.0
|
Go to Case
|
|