You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
[All systems] the long options --unix and --dos have been
renamed --unix2dos and --dos2unix respectively to make it easier to
remember what it does. You can still type --unix or --dos if you like,
since you are allowed to truncate long options provided the letters
uniquely identify the option you want. Note: you do not need to use
these options if you are using the default names for the program
(todos, fromdos, unix2dos or dos2unix), since the direction of
conversion is implicit from the name.
[All systems] added long options --todos and --fromdos, which are
synonyms for --unix2dos and --dos2unix respectively, for those who
are more familiar with those names.
[All systems] now checks to make sure the program is named either
"todos", "fromdos", "dos2unix" or "unix2dos" or one of
the --todos, --fromdos, --unix2dos, --dos2unix, -u, or -d options
is specified, otherwise it will not proceed with the conversion.
Previously, if the direction of conversion was not clear from the
name of the program or from its options, it would assume the
conversion was in a particular direction depending on the operating system.
This meant that the program behaved differently on different systems
if it was given some arbitrary name (other than one of the above).
[All systems] the documentation has been updated (ie, the manual pages
and this README file). The man page and its HTML equivalent are now
generated from the same source file, making it easier to update in
the future.
[Windows] now supports the Windows' implementation of symbolic links
introduced in Vista in 2007. Note that symlinks have been supported on
Unix-type systems (eg, Linux, macOS, *BSD, etc) since 2003 (ver 1.7).
[Windows] now supports '/' as directory separators (in addition to
the usual '\') for pathnames since Windows can also handle these.
(Specifically, Windows accepts both separators at the Win32 API
level, though not all Windows programs, including Microsoft's own,
support it. Now, Tofrodos also supports it.)