|
From: Simon W. <sim...@ma...> - 2011-05-14 17:06:58
|
Paul,
This feature was introduced by Keith Harwood. It seems odd to me, perhaps Keith will tell us what it's for.
--S
On 10 May 2011, at 13:07, Paul Huygen wrote:
> Dear Simon,
> On Mon, 09 May 2011 18:10:13 +0100, Simon Wright wrote
>> Paul,
>>
>> I've had a go, attached to this message. It involved a recursive
>> call to source_get(), not I think a problem on modern machines but
>> with nuweb you never know!
>>
>> It works fine with nuweb itself, my web that used the feature, and a
>> test case 631095.w (also attached).
>>
>> Can you have a try and see how you get on?
>
> Great!
>
> It works on my computer. However, when I tried it on my own project, I
> discovered another "for-me" problem, that probably betrays my sloppiness. I
> have multiple scrap placeholders that refer to nothing. The older nuweb
> versions respond on this with a warning only, but nuweb-1.55 writes the
> placeholder in the output. E.g. when nuweb-1.01 processes the following file
>
> ---testit.w-----------------------
> \documentclass{article}
> \begin{document}
> @o test.out @{@%
> Some text.
> @< a placeholder that refers to nothing @>
> @| @}
> \end{document}
> ----------------------------------
>
> , it produces the following "test.out":
>
> ---test.out----------------------
> Some text.
>
> ---------------------------------.
>
> However, nuweb 1.55 produces:
>
> ---test.out----------------------
> Some text.
> @<a placeholder that refers to nothing@>
> ---------------------------------.
>
> Thanks,
>
> Paul.
>
>
>
>
|