Changeset 10666

Timestamp:

2005-09-30T10:07:08+12:00 (18 years ago)

Author:

mdewsnip

Message:

Updated/added some strings for the remote Greenstone collection building.

File:

• trunk/gli/classes/dictionary.properties (modified) (2 diffs)

trunk/gli/classes/dictionary.properties

@@ -775 +775 @@
 #
 #***** Missing EXEC *****
-MissingEXEC.Message:Warning! You will not be able to view your new collections within the Librarian Interface unless you specify the path to the locally running Greenstone Library Webserver. You can enter this now in the text field below, or later by going to Preferences and choosing the Connection tab. Remember that a valid url must start with the protocol "http://", and will probably end with the executable name ("gsdl" for Greenstone local library server, "library" for other web servers).
+MissingEXEC.Message:Warning! You will not be able to view your new collections within the Librarian Interface unless you specify the path to the Greenstone Library Webserver. You can enter this now in the text field below, or later by going to Preferences and choosing the Connection tab. Remember that a valid url must start with the protocol "http://", and will probably end with the executable name ("gsdl" for Greenstone local library server, "library" for other web servers).
 MissingEXEC.Title:Missing Greenstone Library Address
 #***** Missing EXEC_GS3 *****
@@ -929 +929 @@
 #
 #***** Remote Greenstone Server *****
-RemoteGreenstoneServer.Error:An error has occurred while performing this operation:\n{0-Error message}
+RemoteGreenstoneServer.Authentication_Message:Please enter your Greenstone username and password:
+RemoteGreenstoneServer.Error:An error has occurred on the remote Greenstone server while performing this operation:\n{0-Error message}
 RemoteGreenstoneServer.Error_Title:Remote Greenstone Server Error
 RemoteGreenstoneServer.Progress:Remote Greenstone Server Progress: 
+RemoteGreenstoneServer.Steal_Lock_Message:This collection is currently locked by user '{0-User name}'.\nDo you want to steal control of this lock file (not recommended, as work may be lost)?
 #**********************
 #