> He might benefit from a .eo before the text of his file to > turn off backslash as the escape character? And there's > prefixing each line with \& in case one of them starts with > either of the control characters, . or '.
Ugh. You're right. However, then the "\&" won't be understood anymore either. But we can use, e.g., BEL and ACK as control and escape characters. Also, troffrc-end is included after all macro files and its backslashes won't be understood anymore. We can work around this by just including the macro file as the first file to be processed, without a "-m" argument. So it's possible, but I think it's easier just filtering the input text with sed and doubling all backslashes (you need to filter anyway to prepend "\&" to all lines).
