Idea from the VSE world: IESMSGS & Explain function. Part of the VSE systems itself, but each vendor has the ability to add to the IESMSGS file, if they follow the rules for message format and use the utility functions for adding message.
In the Linux world, doesn't the MAN function perform the same role? Isn't there a means of adding to the file that MAN accesses? Shouldn't the various vendors be able to provide, as part of their install process, the procedure to meger their MAN updates into the central MAN respository? Garry -----Original Message----- From: David Goodenough [mailto:[EMAIL PROTECTED]] Sent: Monday, February 04, 2002 2:13 PM To: [EMAIL PROTECTED] Subject: Re: Messages Manual I am not sure it is that is not warranted, rather that the code comes from such disparate places that it would be logistically very difficult to collate and maintain. At least with a single vendor changes are managed, and so documentation updates are controllable. This does make it a bad thing to want to do, just a very difficult one. Add to that the well known fact that programmers do not like witing documentation and you have the current Linux situation. Of course not only does Linux itself come from many places, but Linux is only the kernel, and all the other bits need to be considered too. Then it all needs to be NLS enabled, and we start to see why comercial software is so expensive and the documentation so out of date. I suppose what is needed is a bright idea to make it painless, and then at least there would no longer be the excuse that it is all too hard. This is really a wider question than just messages. Anyone got such an idea? Paul Kaufman <paul.kaufman@ve To: [EMAIL PROTECTED] rizon.com> cc: Sent by: Linux Subject: Re: Messages Manual on 390 Port <[EMAIL PROTECTED] RIST.EDU> 02/04/02 12:18 PM Please respond to Linux on 390 Port I supported MVS back in the days when we had source for it. I talked with a few people who supported VM when they had source for it as well. We also had messages and codes manuals. Our experiences are that using messages and codes manuals is a more efficient way to solve problems than reading the source. Many people seem to be saying that a Linux messages manual is not warranted because you can read the source. Are these statements based on experience supporting a large corporate IT department? <font size="1">Confidentiality Warning: This e-mail contains information intended only for the use of the individual or entity named above. If the reader of this e-mail is not the intended recipient or the employee or agent responsible for delivering it to the intended recipient, any dissemination, publication or copying of this e-mail is strictly prohibited. The sender does not accept any responsibility for any loss, disruption or damage to your data or computer system that may occur while using data contained in, or transmitted with, this e-mail. If you have received this e-mail in error, please immediately notify us by return e-mail. Thank you.
