> Removing a warning just because it works for you is not an option IMHO. Before
> you remove it, it is up to you to prove that it really is obsolete in all
> cases.
That's why I asked you do test this with your TeXLive installation.
If we identify the problem of beeing only a problem in xdvi, the we should
write this in the warning.
An invalid warning is nothing we can leave as it is, see the student I was talking about. More
drastically, you can compare our current behavior with this case:
You sit into your car, start the engine and get the warning that the car can
crash today.
Would you start driving?
What is really the case is that a manufacturer of tires sent a warning to your car manufacturer that
the tires of a certain type might break at high velocities. So if you would have this info, you
could look if your car has this type of tire.
So as customer you expect to get useful informations. If the car manufacturer is sure that this type
of typres cannot be on your car (as they are for examples larger tires that would not fit to your
car), you expect of not getting bothered.
>> Nevertheless the problem with incorrect warning is that it hinders people
>> from working. Yesterday I got a call from a student who had to deliver a
>> report written in LyX as TeX file. Due to the warning, he was scared that
>> the TeX output is probably corrupted and thus don't want to sent it but
>> his deadline is on Monday. I could explain him the case, but think of
>> users who don't have anybody to ask quickly.
>
> He could simply use a safer path name and be done with it.
He could not because he has about 20 images generated by a measuring device that adds the
parentheses automatically. So he would have to rename every image file manually. This is a lot of
work (Windows users normally don't know that such things can be done much faster by using the
command line), and this only because of an invalid warning.
regards Uwe
