source: internationalization/trunk/TranslationSpreadsheets/WV-DIALOG-0452.txt@ 604

Last change on this file since 604 was 604, checked in by George Lilly, 14 years ago

Internationalization

File size: 11.9 KB
Line 
1English French Notes Complete/Exclude
2The following actions are also available:
3This list only contains 1 page.
4Too large. Page #
5Negative page numbers do not exist.
6Go to Page (1-
7Your selection is the current screen.
8VALM DEMO APPLICATION
9Prefix:
10 No protocols to list.
11'Expand' was last action picked.
12No Description entered.
13Package has not been changed.
14'VALM DEMO APPLICATION' List Template...
15VALM DEMO APPLICATION^1^^240^5^14^1^1^Protocol^VALM DEMO MENU^Package Protocol List^2^^1^^^
16VALM DEMO PRINT^VALM HIDDEN ACTIONS
17'VALM WORKBENCH' List Template...
18VALM WORKBENCH
19VALM WORKBENCH^1^^240^4^17^1^1^^VALM WORKBENCH^List Manager Workbench^1
20>>> Protocol file not present in this account.
21>>> Checking the version of XQOR*...
22The current version of XQOR* is
23List Manager requires version
24 or greater.
25As part of the post-init, version
26 Continue with the installation
27>>> List Manager installation will not occur.
28VALM DEMO
29>>> Will now delete demo protocols...
30>>> A new set of demo protocols will be added during the install.
31VALM OPTION DEMO
32>>> Installing XQOR* routines from VALMXQ* routines...
33>>> Will determine if package PROTOCOLS refer to 'SDUL'...
34...nothing found
35Entry Action:
36Exit Action:
37Header Code:
38Attached Protocols:
39>>> List Manager Conversion Analyzer for '
40List Manager Conversion Analyzer
41Set-up MUMPS Code
42>>> Running the '
43' List Template.
44 Select 'QUIT' action to the workbench...
45No compatiable editor for operating system.
46*** List Template Export Utility ***
47>>> Exporting LIST TEMPLATES with namespace '
48>>> Enter the Name of the Package (2-4 characters):
49>>> Enter Routine Name
50I am going to create a series of '
51>>> MAXIMUM ROUTINE SIZE(BYTES):
52Please enter the package namespace you wish to export:
53' List Template...
54 ; List Template Exporter ;
55 has been filed...
56>>> The system will create a stub routine...
57' stub routine...
58EN ; -- main entry point for
59HDR ; -- header code
60This is a test header for
61INIT ; -- init variables and list array
62HELP ; -- help code
63EXIT ; -- exit code
64EXPND ; -- expand code
65Template:
66 to the
67 List Manager WorkBench
68Template Name:
69 Entity Name:
70 Screen Title:
71 List Region
72 Top Margin:
73Bottom
74 Protocol Information
75 Type of List:
76 Protocol Menu:
77Print Protocol:
78 Hidden Menu:
79 MUMPS Code Related
80Expand:
81 Caption Line Information
82Video
83Scroll Lock
84 Other Fields
85 OK to Transport?:
86 Use Cursor Control:
87Allowable Number of Actions:
88 Date Range Limit:
89 Automatic Defaults:
90>>> LIST REGION
91Screen Title:
92Bottom Margin:
93 Entity Name:
94 # of Actions:
95Print Prot'l:
96 Array Name:
97>>> Caption Name
98XQOR WORD PROCESSING^101.11D^
99 -RAPID MODE-
100 -NORMAL MODE-
101THIS MENU SELECTION;NEXT MENU SELECTION;FINAL SELECTION
102OE/RR Software is currently being updated. Access temporarily denied.
103This item is not setup to order from OE/RR
104ADD ORDERS
105VAQ*1.5*7
106Details of this installation may be obtained from the National Patch Module
107under the entry VAQ*1.5*7 (patch # 7 for version 1.5 of PDX).
108 does not exist ***
109*** Patch 7 has not been applied to routine
110*** Installation of VAQ*1.5*7 halted ***
111Installation of patch number 7 completed
112VAQ*1.5*15
113under the entry VAQ*1.5*15 (patch #15 for version 1.5 of PDX)
114Do you want to run the inits included with this patch ?
115This patch is accompanied by a set of inits (VAQ2INIT). Running the inits
116will modify triggers on the Remote Facility field (#.01) of the VAQ - RELEASE
117GROUP file (#394.82) and the Remote Facility field (#.01) of the Remote
118Facility multiple (field #10) in the VAQ - OUTGOING GROUP file (#394.83).
119These triggers did not correctly store the external value of a pointer in the
120fields they update.
121You may skip the running of these inits if the inits included with patch
122VAQ*1.5*12 (which was entered in error) were successfully run.
123Do you want to update the VAQ - RELEASE GROUP file ?
124Enter 'YES' if you want the values stored in the Remote Domain field (#.02)
125of the VAQ - RELEASE GROUP file (#394.82) automatically re-entered. Doing
126this will ensure that the pointer values contained in this field are stored
127This step is not neccessary if the values were successfully re-entered
128during the installation of patch VAQ*1.5*12 (which was entered in error).
129Do you want to update the VAQ - OUTGOING GROUP file ?
130of the Remote Facility multiple (field #10) in the VAQ - OUTGOING GROUP file
131(#394.83) automatically re-entered. Doing this will ensure that the pointer
132values contained in this field are stored correctly.
133Installation of patch number 15
134Updating of VAQ - RELEASE GROUP file (#394.82) was not performed
135Updating of VAQ - OUTGOING GROUP file (#394.83) was not performed
136Performing update of triggered values in VAQ - RELEASE GROUP file
137VAQ-PARSE
138Local Facility
139Sending domain closed. Message ignored and deleted.
140Unable to read first line of message
141Unable to determine version of PDX used to generate transmission
142Error occurred while parsing version
143Unable to queue retransmission (IFN:
144Unable to complete automatic processing
145Unable to send results received bulletin
146Was able to file transaction (IFN:
147Unable to send Unsolicited PDX received bulletin
148Unable to acknowledge receipt of Unsolicited PDX
149Unable to queue acknowledgement for receipt of Unsolicited PDX
150-1^Error completing receipt of Unsolicited PDX
151Error occurred while filing
152(Transaction was not created)
153Transaction
154-1^Valid transaction not passed
155VAQ-XMIT
156VAQ-AUTOCHK
157Exact match on name/ssn/dob not found, process manually for potential matches
158-20^Maximum time & occurrence limits exceeded by
159PDX Server
160Unable to queue transmission of results
161-1^Did not pass reference to transaction array
162-1^Transaction array did not contain any information
163Generation of PDX transmission
164VAQTRN(
165-1^Could not queue transmission(s)
166Transaction does not exist
167Could not determine message type
168Can not transmit a transaction that is being received
169Transaction did not contain a domain to transmit message to
170Domain is closed:
171Error occurred while building transmission(1)
172Error occurred while extracting information
173PDX (V1.5) TRANSMISSION FROM
174Patient Data eXchange
175-1^Did not pass work identifier
176-1^Did not pass transaction work was done with
177-1^Did not pass a valid transaction
178-1^Did not pass a valid word identifier
179-1^Could not create entry in work-load file
180-1^Unable to create entry in work-load file
181-1^Did not pass subject of message
182-1^Did not pass sender of message
183-1^Did not pass array containing message
184-1^Did not valid array reference
185-1^Array did not contain message
186-1^Did not pass distribution list
187-1^Distributionl list was empty
188-1^Could not get stub message
189UNABLE TO SEND MESSAGES
190The following message(s) could not be transmitted ...
191) Transaction Number:
192Sent By:
193Could not be determined (Contact your PDX ADPAC)^Could not be determined (Contact your PDX ADPAC)
194PDX Request
195Results from processing an external request
196Acknowledgment (Contact your PDX ADPAC)
197Re-transmit (Contact your PDX ADPAC)
198The following error(s) occurred while generating PDX transmissions ...
199Global Location: ^VAT(394.61,
200Unknown^??
201G.VAQ PDX ERRORS
202-1^Did not pass valid transaction
203VAQ-BUL
204Not listed
205Could not be determined
206The following PDX Request requires manual processing ...
207 Transaction number:
208 Requested by:
209 Reason for manual processing:
210 Segments that were over the allowable time & occurrence limits:
211 Requested Maximum Requested Maximum
212 Segment Time Time Occurrence Occurrence
213G.VAQ MANUAL PROCESSING
214Process PDX Request for
215-1^Unable to generate and send bulletin
216-1^Transaction did not contain results of a request
217-1^Transaction did not contain a transaction number
218Uknown
219Your request for information has been
220processed and returned
221Transaction number:
222*** PATIENT WAS LISTED AS SENSITIVE AT THE REMOTE FACILITY ***
223*** PATIENT IS LISTED AS SENSITIVE IN YOUR FACILITY ***
224Requested on:
225Reason: Patient not found
226Reason: Requested patient could not be uniquely identified
227None listed
228Requested information:
229Requested data could not be included in notification
230Transaction did not contain any information
231Error occurred while getting information from PDX files
232PDX Rejection for
233PDX Results for
234The following error(s) occurred while receiving a PDX transmission ...
235General Information
236XMZ:
237Global Location: ^XMB(3.9,
238Postmaster Basket: S.VAQ-PDX-SERVER
239General Error
240Specific Error(s)
241Message Number:
242Note: Each PDX transmission can contain more than one PDX message. Message
243 number X refers to the Xth message within the transmission (not the
244UNABLE TO PROPERLY RECEIVE TRANSMISSION
245-1^Transaction was not an Unsolicited PDX
246The following Unsolicited PDX has been received ...
247Received on:
248Sent by:
249Comments: None listed
250G.VAQ UNSOLICITED RECEIVED
251Unsolicited PDX for
252-1^Did not pass reference to error array
253** Purger was stopped before completion **
254The following PDX Transaction(s) could not be purged ...
255** Please remember that PDX Transactions may also **
256** have associated data stored in file number 394.62 **
257PDX TRANSACTIONS COULD NOT BE PURGED
258-1^Did not pass reference to array of transaction pointers
259-1^Did not pass message number or reference to output array
260-1^Valid message number not passed
261-1^Did not pass a valid pointer to VAQ - TRANSACTION file
262-1^Transaction is being received, not transmitted
263-1^Subject of message not passed
264-1^Could not determine sender of message
265-1^Could not create stub message
266-1^Line number not passed
267Success
268Killing of bad PDX messages
269-1^Could not task deletion of message
270-1^Did not pass pointer to VAQ - TRANSACTION file
271-1^Could not determine status of message
272VAQ-RCVE
273-1^Could not determine message type
274-1^Could not determine remote transaction number
275-1^Did not pass message number of reference to array
276-1^Could not determine facility name
277-1^Could not determine message status or type
278-1^Could not determine return address
279-1^Could not determine destination of message
280-1^Patient information not contained in VAQ - TRANSACTION file
281-1^Did not pass segment abbreviation
282-1^Did not pass location of Extraction Array
283-1^Did not pass a valid pointer to the VAQ - TRANSACTION file
284-1^Could not determine type of message to send
285-1^Equivalent message not available in version 1.0 format
286-1^Message not required
287-1^Could not determine remote domain
288PDX (V1.0) TRANSMISSION FROM
289VAQ-10
290-1^Transaction does not require a PDX message in version 1.0
291-1^Transmission does not have a version 1.0 equivalent
292PDX*MAS
293PDX*MPS
294-1^Message type does not return data
295-1^Could not determine current domain
296Request requires user intervention
297-1^Version 1.0 does not have an equivalent message
298-1^Could not determine 1.0 status
299-1^Could not determine 1.0 parent PDX number
300-1^Transaction did not contain patient's name or SSN
301-1^Could not determine name of requestor
302-1^Could not determine current site number
303#################### #################### ####################
304#################### #################### ####################
305#################### #################### ####################
306#################### #################### ####################
307#################### #################### ####################
Note: See TracBrowser for help on using the repository browser.