On Wed, 25 Jan 2012, Alexandre Julliard wrote:
Francois Gouget fgouget@free.fr writes:
You were right on both points:
- All these error messages have a trailing full stop in English, French and Japanese.
- They also tend to be much more verbose than Wine's messages and usually form a proper sentence.
I'm not going to fix point 2.
But I think point 1 can and should be fixed. The question is how to do it without spending a month in the process or fuzzying all the existing translations. It probably needs to be scripted somehow and then the patch for both winerror.mc and the po files submitted? (or just submit the patch for winerror.mc and the script?)
I'm not sure that doing 1 without 2 is all that useful. If they are supposed to be proper sentences and are not, they will look ugly with or without full stop.
I don't think the messages below are more ugly with a full stop or even ugly at all in the first place.
Invalid address.
Service not active.
Media changed.
Property set not found.
That's why I don't plan on doing 2: I consider the current messages to be terse but fine, and I'm not convinced waxing eloquent like Windows is any better.
(I'm attaching my hack for checking the Windows messages, forgot to do it before)