nlsREADME.txt 4.7 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139
  1. # $XConsortium: nlsREADME.txt /main/2 1996/11/11 11:32:25 drk $
  2. #############################################################################
  3. #
  4. # Component: types - The DT 3.0 action and filetype definitions.
  5. #
  6. ############################################################################
  7. Introduction:
  8. ------------
  9. The files in this directory contain the DT 3.0 action and
  10. filetype definitions.
  11. The syntax for the DT 3.0 definitions is much different than the
  12. DT 2.0 syntax. The most significant change is that the each
  13. field in a definition is on a separate line and each field is
  14. identified by a keyword. Other important changes are: filetype
  15. and action definitions may be in the same file; some fields are
  16. optional and each definition may have a "DESCRIPTION" field.
  17. See the file "uxstd.vf" for an example of a DT database file
  18. that has both filetype and action definitions in the same file
  19. and uses the "DESCRIPTION" field.
  20. There are NO screendumps for this component.
  21. There is NO message catalog for this component.
  22. There is NO app-defaults file for this component.
  23. This component contains a Dialog Description File (DDF). See
  24. the section on "Localizing Dtdialog DDF Files" in the NLS
  25. Cookbook for general information.
  26. Files to be localized:
  27. ---------------------
  28. File Name Target Name
  29. --------- -----------
  30. 1. laserrom.vf /usr/dt/types/%L/laserrom.vf
  31. 2. print.vf /usr/dt/types/%L/print.vf
  32. 3. printerNN.vf /usr/dt/types/%L/printerNN.vf
  33. 4. unsupported.vf /usr/dt/types/%L/unsupported.vf
  34. 5. user-prefs.vf /usr/dt/types/%L/user-prefs.vf
  35. 6. uxstd.vf /usr/dt/types/%L/uxstd.vf
  36. 7. dt.vf /usr/dt/types/%L/dt.vf
  37. 8. vhelp.vf /usr/dt/types/%L/vhelp.vf
  38. 9. dt20.vf /usr/dt/types/%L/dt20.vf
  39. 10. dtfile.vf /usr/dt/types/%L/dtfile.vf
  40. 11. dtpad.vf /usr/dt/types/%L/dtpad.vf
  41. 12. xclients.vf /usr/dt/types/%L/xclients.vf
  42. 13. actions.ddf /usr/dt/dialogs/%L/actions.ddf
  43. What to localize in the .vf files:
  44. ---------------------------------
  45. NOTE: do NOT localize action and filetype names.
  46. 1. The "DESCRIPTION" field in every action and filetype definition
  47. should be localized. The information in this field can be
  48. displayed to the user by selecting a file in the File Manager and
  49. then pressing the "F1" key.
  50. 2. Some action definitions contain "prompt strings" that ask
  51. the user for input. The prompt strings should be localized.
  52. Prompt strings are always embedded in a pair of '"' characters
  53. which are embedded in a pair of '%' characters. For example, in
  54. the following EXEC-STRING field, the prompt string is "Some
  55. String:":
  56. EXEC-STRING %(File)Arg_1"Some String:"%
  57. To change the prompt to "String Some:", use:
  58. EXEC-STRING %(File)Arg_1"String Some:"%
  59. Prompt strings are only used in the "EXEC-STRING" and "EXEC-HOST"
  60. fields of action definitions.
  61. To find the actions which contain prompts,
  62. The EXEC-STRING and EXEC-HOST field may contain "keywords" that
  63. should NOT be localized. These keywords are the same keywords
  64. that were used with DT 2.*, so for more infomation, see the
  65. reference "HP Visual User Environment User's Guide".
  66. Do NOT localize the following keywords:
  67. (File)Arg_1
  68. (File)Args
  69. %LocalHost%
  70. Arg_1
  71. Args
  72. 3. The "L-ICON" and "S-ICON" fields may be localized. These fields
  73. are for the large and small icons, respectively.
  74. How to test the localization changes:
  75. ------------------------------------
  76. 1. To test the DESCRIPTION field changes:
  77. To test the action definition changes, select the action and
  78. then press the "F1" key. The localized description should get
  79. displayed.
  80. To test the filetype definition changes, create a file of that
  81. filetype, select that file and then press the "F1" key. The
  82. localized description should get displayed.
  83. 2. To test the prompt string changes:
  84. For every action definition that was changed in step #2 above,
  85. double click the action in the File Manager. The prompt string
  86. that is displayed should be localized.
  87. 3. To test the icon changes:
  88. For every action whose icon was changed, display the action in the
  89. File Manager. The icon displayed should be the localized icon.
  90. For every filetype whose icon was changed, create a file of that
  91. filetype and display the file in the File Manager. The icon
  92. displayed should be the localized icon.
  93. #
  94. #