3 ms·
Why would your customers even need to see the log file? For general errors we have a language table that spits out the local copy to the screen. Common errors a
by yardie 17y ago
Why would your customers even need to see the log file? For general errors we have a language table that spits out the local copy to the screen. Common errors are translated (~100). Behind the scenes, the logs are in english for internal errors, and the language of the OS for everything else. We rely on .NET so exceptions are tied to the OS.
We have some older components that do spit out error codes. (like COMS, error -84413994005!) Sometimes the codes aren't specific at all and I have to install a debug version to get the information I need, or rely on a graybeard programmer to help me out.
These days programs are far too complex to rely on a limited set of error codes.
- halostatue 17y agoOur logs aren't just error messages; they're all sorts of messages that the user of our (backup) software may be interested in. I'm trying to figure out ways to reduce our messages so that our customers only see the details that they will really be interested in, but there is a large subset of our customers who want to be able to review how their backups went (and not just with the email summary that we send, which is generated from the log messages, BTW). Our tracing facility, on the other hand, is purely English.
- yardie 17y agoOkay, just a difference in semantics. In that regards our systems are similar. Our reports = your logs, our logs=your traces.
- Timothee 17y agoOne helpful company could actually publish that language table, so that with a Polish message, you can find out what is the corresponding English message and use Google with that.