@FreelanceReinh wrote: In a sense, it is regular expression language. First, the macro processor resolves the %SYSFUNC call to a character string (consisting of the carriage return and line feed characters). Then PRXCHANGE works as usual and uses this character string as replacement text. The need for macro language comes from the fact that the replacement text is largely treated as just characters, so that the possibilities of providing '0D0A'x as replacement text are quite limited. Thanks again for the explanation, but actually I was willing to use the \r\n metacharacters instead… It’d be much more simple to use regular expressions both in the search part and in the replace part… But it seems to me that this is not an option...
... View more