Examples of using Error message should in English and their translations into French
{-}
-
Colloquial
-
Official
The error message should now disappear.
PHP phpinfo. php The following error message should appear.
The error message should dissapear by now.
After the pump primes itself, the error message should go away.5.
The error message should no longer appear.
If non-UTF-8 data is received, an error message should be sent back.
The error message should not appear again.
If checks for valid values are required, andin the case of an invalid value an error message should be generated, it must be done by a trigger.
The error message should no longer appear.
After restart the error message should no longer appear.
An error message should be provided that communicates which entry is suspect and specifies what type of data is expected.
If all goes well, an error message should be displayed and the program will not launch.
The error message should be as specific as possible.
Now the error message should not appear.
The error message should give you a clue as to the problem.
A good error message should be as specific as possible.
This error message should give you a good indication of the problem.
A good error message should provide more constructive help.
The error message should provide one or more of the following navigational constructs.
The error messages should now go away.
Your error messages should clearly define what the problem was.
The error messages should be translated into Spanish, Catalan and Basque..
The wording of the error messages should be explicit.
Error messages should play less frequently.
A second key principle is that good error messages should be precise and specific.
The error messages should be resolved.
Error messages should be embedded in the input form.
Error messages should be eliminated.
Error messages should also be clear and actionable.
Error messages should be provided in the same language as the application that was being used.
