Unify line ending terminology#2141
Conversation
|
We should emphasize that Macintosh actually uses LF. Maybe we could just drop the CR option? |
|
How about this? Windows (CR LF) The important part is to not trick Mac users into using CR. |
|
@Eldaw Interesting...never realized there was a PR so similar. I'm not attached to the terminology I used, it's what Visual Studio used so figured it was an OK way of doing it. I understand that VS is targeted to a more technical audience than N++ is. Presumably in the majority of cases (not all) if a user is converting line endings they have some idea what line endings they want even without terminology. I think it is important to keep the CR/LF/CRLF terminology that way if someone disagrees with the naming scheme they can at least know exactly what line endings they are converting to.
I totally agree, however most Mac users probably don't know the difference between "Mac" vs "Old Mac" (although maybe they do? I'm not a Mac person :) ). |
Agree, I just tried to get a concise result, and I got not satisfying result using "Mac OS X" or "OS X". That's why I suggested above to remove the CR mode. |
Closes #2038
Currently there are inconsistencies when using EOL terminology. I have changed occurrences to use (and maintain this order):
Windows (CR LF)Unix (LF)Macintosh (CR)I am open to suggestions but I feel this is fairly straight forward, unambiguous, and this is exactly how MSVC displays them in their menu.
Before:
After:


