> If I'm not mistaken, this was bug 3118 

yes, it seems as the same bug.

> which is supposedly already fixed.

no i can reproduce the problem even for the attached file there
(with 1.5.0).

pavel

Reply via email to