> I have problems with gpreconv on Windows (GNUWin32 Groff). Whenever
> I want to use it, I have to con- vert the end-of-line symbols:
>
> tr -d \015 < [infile]|groff -U -Kcp1251 ...
>
> which makes the use of soelim much less convenient, because I have
> to preconvert my files to the '\n'
Keith Marshall:
> Actually, preconv opens its input stream in "bina-
> ry" mode, rather than in Window's special "text"
> mode. Thus, it does see the \r\n EOL sequence,
> which it then explicitly interprets as the line
> terminator, so explicitly emulating the behaviour
> which would hav
On 05/08/12 18:57, Anton Shepelev wrote:
> I wrote:
>
>> Is it reasonable to modify gpreconv or its Windows
>> port so that on Windows it will expect '\r\n'?
As a software developer, writing code primarily for Windows, I feel
obliged to chime in with an emphatic "no" here.
> preconv(1) says:
>
