It's not OK to interpret a \n as a line break.
It is.
That would mean storing program specific data into the description.
It would not.
Program specific data should be behind a <Ctrl-D><ID> mark.
There is a difference between program specific data and a user's choice to have \n interpreted as a line break in the common descript.ion area.
\n are normal characters. To interpret them differently means changing the format.
The format isn't changed by the way how printable characters are interpreted by programs.
What would happen if more programs would add special characters (for instance $,#,etc.) with special meaning?
Besides that Mother Earth would collapse, it would mean that these descript.ion files could be edited normally in all apps with descript.ion support.
If this is allowed there's no need to use the <Ctrl-D><ID> method.
You haven't understood the ID concept, just like ghisler, who has totally fucked up this descript.ion implementation.
He doesn't set the ID when comments reach the limit of 511 chars, but instead he sets the ID only when line breaks are used, but instead of IN FRONT of the first occurence he puts the ID at THE END of descript.ion. This will of course lead to data loss in descript.ion files when edited in other applications.
FAIL!
How is it possible that this has not been discovered during the beta tests? Really, not even by tosbsas? Impressive!
Icfu