Hi Jim, > > ! LC_ALL=C tr -d '\r' < t-xstrtoimax.tmp > t-xstrtoimax.xo > I hear that there really do exist systems in actual use > on which tr still does not honor backslash-escapes like \r and \n.
Which platforms, please? (I use the similar idiom in more than 200 files in gettext. So I need to know the reasons.) > So you might want to change that \r to \015, in spite of the > ASCII dependency. A few programs, like groff and IBM's ICU, are ported to platforms not based on ASCII. On the other hand, files compiled by gperf have a compile-time check for ASCII, and I've received no reports from systems where that failed. Bruno
