Initial import of the CDE 2.1.30 sources from the Open Group.

cde/programs/dthelp/dthelpview/nlsMsgChk.txt

@@ -0,0 +1,386 @@
+# $XConsortium: nlsMsgChk.txt /main/2 1996/11/11 11:29:19 drk $
+#############################################################################
+#
+# Component:  helpview (e.g $(TOP)/hp/rivers/cachecreek/helpview/helpview)
+#
+############################################################################
+
+# NOTE: Some of the dialogs exercise messages which are in different
+#       message sets.  The syntax used to specify this is:
+#
+#                (set #, msg#)
+#
+
+
+1. Screendump file name:  < 1.Z > 
+
+   _DtMessage catalog set number: 2, and 9
+
+   _DtMessage number(s):  (Set 2, messages 1 - 28), (Set 9, message 1)
+
+   Instructions: 
+
+   From a terminal window type the following command to start
+   helpview: 
+
+   /usr/hphelp/bin/helpview -helpVolume HelpOnHelp.hv
+
+   By selecting each of the helpveiw pulldown menus, you can see each of the 
+   menu labels covered in the messages.  The screen dump given here just shows
+   the main helpview dialog and top level menu items.
+   
+   Set 9, message 1 is displayed in the main window under the menubar.
+
+
+
+
+2. Screendump file name:  < 2.Z >
+
+   _DtMessage catalog set number: 2 
+
+   _DtMessage number(s): 31
+
+   Instructions: 
+
+   From a terminal window type the following command to start
+   helpview: 
+
+   /usr/hphelp/bin/helpview -man
+
+   Type "foo" inside the 'Man Page:' text field and select the 'Show Man Page'
+   button.  A quick help dialog will appear displaying the proper error
+   message (e.g. "Man Page could not be formatted").
+   Select the Exit button to exit the Man Page viewer.
+
+
+
+
+3. Screendump file name:  < 3.Z >
+
+   _DtMessage catalog set number: 7
+
+   _DtMessage number(s): 11, 12, 13, 16
+
+   Instructions: 
+
+   From a terminal window type the following command to start
+   helpview: 
+
+   /usr/hphelp/bin/helpview -man
+
+   The Man Page dialog that shows up contains all of the above messages.
+   Select the Exit button to exit the Man Page viewer.
+
+
+
+
+4. Screendump file name:  < 4.Z >
+
+   _DtMessage catalog set number: 2
+
+   _DtMessage number(s): 34
+
+   Instructions: 
+
+   From a terminal window type the following command to start
+   helpview: 
+
+   /usr/hphelp/bin/helpview -helpVolume HelpOnHelp.hv -locationId foobar
+
+   'foobar' is not a valid locationId for the HelpOnHelp help volume, thus the
+   error message "Nonexistent location ID" is generated within the helpview
+   main window.  This error message is also sent to Standard Error (e.g. the 
+   terminal window you ran helpveiw from), however, this version of the error
+   message is not localized.  Only the version that goes comes from the 
+   (Set 2, _DtMessage 34), and is displayed in the helpviw main window is 
+   localized.
+
+
+
+
+5. Screendump file name:  < 5.Z >
+
+   _DtMessage catalog set number: 2
+
+   _DtMessage number(s): 37
+
+   Instructions: 
+
+   From a terminal window type the following command to start
+   helpview: 
+
+   /usr/hphelp/bin/helpview -helpVolume foobar
+
+   'foobar' is not a valid helpVolume, thus the error message "Could not find 
+   help volume." is generated within the helpview main window.
+   This error message is also sent to Standard Error (e.g. the 
+   terminal window you ran helpveiw from), however, this version of the error
+   message is not localized.   Only the version that goes comes from the 
+   (Set 2, _DtMessage 37), and is displayed in the helpviw main window is 
+   localized.
+
+
+
+
+6. Screendump file name:  < 6.Z >
+
+   _DtMessage catalog set number: 2
+
+   _DtMessage number(s): 39
+
+   Instructions: 
+
+   From a terminal window type the following command to start
+   helpview: 
+
+   /usr/hphelp/bin/helpview 
+
+   Because you did not give any helpVolume resource to the helpview 
+   application it will generate the error message: "No help volume specified".
+
+
+
+
+7. Screendump file name:  < 7.Z >
+
+   _DtMessage catalog set number: 3
+
+   _DtMessage number(s): 1, 2, 3, 4
+
+   Instructions: 
+
+   From a terminal window type the following command to start
+   helpview: 
+
+   /usr/hphelp/bin/helpview -helpVolume HelpOnHelp.hv
+
+   From the main Helpview window select the History... menu item under the
+   Search menu.  The History dialog contains all the messages used in set 3.
+
+
+
+
+8. Screendump file name:  < 8.Z >
+
+   _DtMessage catalog set number: 4
+
+   _DtMessage number(s): 1, 2, 3, 4, 5, 6, and 7.
+
+   Instructions: 
+
+   From a terminal window type the following command to start
+   helpview: 
+
+   /usr/hphelp/bin/helpview -helpVolume HelpOnHelp.hv
+
+   From the main Helpview window select the Print... menu item under the
+   File menu.  The Print dialog contains all the messages used in set 4.
+
+
+
+
+9. Screendump file name:  < 9.Z >
+
+   _DtMessage catalog set number: 5
+
+   _DtMessage number(s): 1, 2, 3, 4, 5, and 6.
+
+   Instructions: 
+
+   From a terminal window type the following command to start
+   helpview: 
+
+   /usr/hphelp/bin/helpview -helpVolume HelpOnHelp.hv
+
+   From the main Helpview window select the Keyword... menu item under the
+   Search menu. This dialog contains messages 1 through 6.
+
+
+
+
+10. Screendump file name:  < 10.Z >
+
+   _DtMessage catalog set number: 5 and 8
+
+   _DtMessage number(s): (Set 5, message 10), (Set 8, messages 2, and 5)
+
+   Instructions: 
+
+   From a terminal window type the following command to start
+   helpview: 
+
+   /usr/hphelp/bin/helpview -helpVolume HelpOnHelp.hv
+
+   From the main Helpview window select the Keyword... menu item under the
+   Search menu. Type foo in the "Keyword Filter (Optional):" field and hit
+   <return>.  An error dialog will be posted.
+
+
+
+
+11. Screendump file name:  < 11.Z >
+
+   _DtMessage catalog set number: 5 
+
+   _DtMessage number(s): 9
+
+   Instructions: 
+
+   As root move the file "/usr/hphelp/help/%L/onhelp/HelpOnHelp.hvk" to 
+   "/usr/hphelp/help/%L/onhelp/HelpOnHelp.sav". 
+
+   From a terminal window type the following command to start
+   helpview: 
+
+   /usr/hphelp/bin/helpview -helpVolume HelpOnHelp.hv
+
+   From the main Helpview window select the Keyword... menu item under the
+   Search menu. An error dialog will be posted stating: "Keyword index not 
+   available!".
+
+   Be sure to restore the HelpOnHelp.sav file back to HelpOnHelp.hvk.
+
+
+
+
+12. Screendump file name:  < 12.Z >
+
+   _DtMessage catalog set number: 6
+
+   _DtMessage number(s): 1, 2, 3, and 5.
+
+   Instructions: 
+
+   From a terminal window type the following command to start
+   helpview: 
+
+   /usr/hphelp/bin/helpview -helpVolume HelpOnHelp.hv
+
+   From the main Helpview window select the Using Help... menu item under the
+   Help menu.  The Help On Help dialog will be posted.
+
+
+
+
+13. Screendump file name:  < 13.Z >
+
+   _DtMessage catalog set number: 6
+
+   _DtMessage number(s): 4
+
+   Instructions: 
+
+   Make a copy of the /usr/hphelp/app-defaults/%L/Helpview file in your 
+   home directory.  Comment out the following line in that file:
+   "Helpview*helpOnHelpVolume: HelpOnHelp.hv".  
+
+   From a terminal window type the following command to start
+   helpview: 
+
+   /usr/hphelp/bin/helpview -helpVolume HelpOnHelp.hv
+
+   From the main Helpview window select the Using Help... menu item under the
+   Help menu.  An error dialog will be posted with the proper error message
+   in it.
+
+   Make sure to un-comment the HelpOnHelpVolume resource in your Helpview 
+   app-defaults file before you continue.
+
+
+
+
+14. Screendump file name:  < 14.Z >
+
+   _DtMessage catalog set number: 2 
+
+   _DtMessage number(s): 32
+
+   Instructions: 
+
+   From a terminal window type the following command to start
+   helpview: 
+
+   /usr/hphelp/bin/helpview -file foobar
+
+   Note: foobar must not exist in your current working directory.
+
+  'foobar' is not a valid file, thus the error message "Text file data could
+   not be formatted." is generated within the quick help  window.
+   This error message is also sent to Standard Error (e.g. the terminal
+   window you ran helpveiw from), however, this version of the error
+   message is not localized.   Only the version that goes comes from the 
+   (Set 2, _DtMessage 32), and is displayed in the helpviw main window is 
+   localized.
+
+  
+
+
+15. Screendump file name:  < 15.Z >
+
+   _DtMessage catalog set number: 7 
+
+   _DtMessage number(s): 7, and 16
+
+   Instructions: 
+
+   From a terminal window type the following command to start
+   helpview: 
+
+   /usr/hphelp/bin/helpview -manPage grep
+
+   Note: If you do not have the grep man page on your system just use any 
+         man page that you have on the current system.
+
+   The quick help dialog that is displayed will show the above listed messages.
+
+
+
+
+16. Screendump file name:  <None>
+
+   _DtMessage catalog set number: 7
+
+   _DtMessage number(s): 1, 2, 3, 4, 5, 6, and 13.
+
+   Instructions: 
+
+   From a terminal window type the following command to start
+   helpview: 
+
+   /usr/hphelp/bin/helpview -foobar
+
+   Because 'foobar' is not a valid command line option, the following 
+   Usage message is produced:
+
+   Usage: helpview...
+
+        -helpVolume <Help Volume File>
+        -locationId  <Cache Creek LocationId>
+        -file  <ASCII Text File>
+        -man
+        -manPage  <Unix Man Page>
+
+
+
+
+17. The following messages and corresponding message sets are used only when
+    specific error conditions are hit.  Their is no easy way for a localizer
+    to display these messages, thus, their are no screen dumps or explanations
+    on how to display them.  
+
+    The bottom line is that they need to be localized, however, they cannot be
+    viewed by the localizers.
+
+
+  
+    a) _DtMessage catalog set number: 2
+       _DtMessage number(s): 29, 30, 33, and 38.
+    
+
+    b) _DtMessage catalog set number: 7
+       _DtMessage number(s): 14, and 15.
+
+   
+    c) _DtMessage catalog set number: 8
+       _DtMessage number(s): 3, and 4.
+