Charles Millar <millarc <at> verizon.net> writes: > This may be related to the problem or is the same that I reported in > April and May and again earlier this month when Bastien's requested > details in his August 4th message.
Have you (or anyone else) been able to reproduce the problem given the example which I provided? Is this indeed a bug, or am I misunderstanding something?
