Op 13-07-2020 om 01:56 schreef Nils König:
> Basically, I imagined this just like:
> 
>> If nano were to handle a BOM properly, it must remove a BOM whenever
>> a file is read, and add it back when it is written.  But that would
>> make it impossible to delete an unwanted BOM with a simple backspace.
>> Then the user would need to fall back to a tool like dos2unix.
> 
> But without the need for an external tool to remove a BOM, instead this could 
> be toggled in the save dialog.

You want to have it both ways.  1) You want nano to hide the BOM from the
user -- because the BOM is part of the file format and must of course stay
where it is.  And 2) you want to be able to remove the BOM in some way.

But... in what circumstances would you want to remove the BOM?

Another question.  These *.ass files, are they in DOS format?
Or do you also have Unix files that start with a BOM?

Benno

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to