[APP_BAD_SHAPEFILE_QUERY] The DBASE attribute file cannot be queried. Check that the file is NOT read-only and that it has an 8.3 filename format
[APP_BDY_OUTDTM] Boundary string is outside DTM {0}.
[APP_BLANK] {0}
[APP_DATAMINE_DM_EXTENSION] Using a .dm extension for {0} may cause problems importing into DATAMINE.
[APP_DATAMINE_ERROR_WRITING_POINT] Error writing point {0} to Datamine file {1}
[APP_DATAMINE_ERROR_WRITING_TRIANGLE] Error writing triangle {0} to Datamine file {1}
[APP_DATAMINE_LOST_FIELD] Field {0} for Datamine file not saved due to overlength record
[APP_DATAMINE_PRECISION_LOSS] A loss of precision will occur as coordinate values for this data set, \nxmin={0} xmax={1} ymin={2} ymax={3} zmin={4} zmax={5}, \nexceed 10,000. Values greater than this cannot be represented in Datamine without losing \nprecision. The only way to resolve this is to subtract a datum value from the \nX, Y or Z values to ensure they are in the range -10,000 to 10,000
[APP_DATAMINE_TRUNCATED_FIELD] One or more values were truncated as the plugin currently only supports 20 characters for description fields
[APP_DTMBDY_MISSING] The DTM boundary string is missing - Cannot continue without the boundary
[APP_INTERP_Z] Interpolated {0} {1} values for new data points
[APP_NO_CMN_PT] Adjacent triangles do not have a common point
[APP_NOTADJ] Fatal DTM error - Triangles are not adjacent
[APP_NUM_TRI] Number of triangles now {0}
[APP_OUTSIDE_DTM] A point is outside the DTM - cannot proceed
[APP_PNT_OUTBDY] Boundary point is outside DTM {0}
[APP_PTNOTCMN] No triangle point is common with the breakline at Y={0}, X={1}
[APP_REMOVING_DUPLICATES] Removing redundant duplicate points
[APP_RESULTS_IN] Results are in the file {0}
[APP_SHP_FILE_OPEN] Shape file opened
[APP_SPLIT_TRI] Splitting triangles crossing boundary
[APP_TOOFEW_PTS] Not enough points in boundary after filtering
[APP_TRI_SPLIT_INFLOOP] Geometry problem found near y={0} x={1}, cannot recover
[APP_TRI_ZERO_AREA] Triangle with zero area created\nData point geometry is causing problems in DTM\nLook in string {0} segment {1} offset {2} for the problem
[APP_VERT_NOT_CMN] Triangle vertex is not common with the boundary string
[ARCINFO_ATTRIBUTE_CREATED] Created "{0} attribute in shape file
[ARCINFO_DBASE_FIELD_TO_DFIELD] Attribute "{0}" output to {1} field
[ARCINFO_FAILED_TO_OPEN_FILE] Failed to open shape file {0}
[BOUNDARY_STRING_CREATION_FAILED] Unable to create DTM boundary string.
[Can't load a surpac 1 string file as a part of a DTM] Can't load a Surpac 1 string file as a part of a DTM
[CARVE_DTMDTM_NOINT] Nothing was output by the function. Ensure the specified surfaces intersect and try again.
[CARVE_NO_TRIANGULATOR] Cannot convert the input polygon into triangles as no triangulation algorithm was specified.
[CARVE_UNKNOWN_TRIANGULATOR] The triangulation algorithm {0} is not valid. Available algorithms are 'FIST', 'Carve' and 'Triangle'. Defaulting to FIST.
[CNV_NOT_NUMERIC_FOR_CENTROID_MEAN] Value " {0} " in description field of point {1} in segment {2} of string {3} is not numeric.
[DATAMINE_DRILLHOLE_FILE] {0} is a Drillhole file
[DATAMINE_EXPLICIT_FIELD_TO_DFIELD] Explicit "{0}" field output to {1} field
[DATAMINE_FILE_VERSION_ERROR] This Datamine file was saved by a later version of Surpac Vision, and cannot be opened.
[DATAMINE_IMPLICIT_FIELD_TO_DFIELD] Implicit "{0}" field output to {1} field with a value of {2}
[DATAMINE_INVALID_DRILLHOLE_FILE] {0} is an invalid Datamine drillhole file
[DATAMINE_INVALID_MODEL_FILE] {0} is an invalid Datamine model file
[DATAMINE_INVALID_POINT_FILE] {0} is an invalid Datamine point file
[DATAMINE_INVALID_STRING_FILE] {0} is an invalid Datamine string file
[DATAMINE_INVALID_WIREFRAME_POINT_FILE] {0} is an invalid Datamine wireframe point file
[DATAMINE_INVALID_WIREFRAME_TRIANGLE_FILE] {0} is an invalid Datamine wireframe triangle file
[DATAMINE_MODEL_FILE] {0} is a Model file
[DATAMINE_OPEN_FAIL] Unable to open file {0}
[DATAMINE_OVERRIDE_PREFERRED_PREC] Surpac has overridden the current default setting and saved the file as double precision in order to fit all attributes in the file.
[DATAMINE_POINT_FILE] {0} is a Point file
[DATAMINE_STRING_FILE] {0} is a String file
[DATAMINE_UNKNOWN_FILE] {0} is an unknown or unsupported Datamine file
[DATAMINE_WIREFRAME_CANT_OPEN_POINT_FILE] Can''t open wireframe point file "{0}"
[DATAMINE_WIREFRAME_MISSING_VERTEX] Missing vertex {0} for Datamine wireframe
[DATAMINE_WIREFRAME_POINT_FILE] {0} is a Wireframe Point file
[DATAMINE_WIREFRAME_TRIANGLE_FILE] {0} is a Wireframe triangle file
[DATAMINE_WIREFRAME_USING_GROUP_FIELD] Using the "{0}" grouping field to identify triobjects
[DATAMINE_WIREFRAME_USING_POINT_FILE] Using {0} as wireframe points file
[DATAMINE_WIREFRAME_USING_SURFACE_FIELD] Using the "{0}" surface field to identify trisolations
[DTM_BDYERR] The DTM boundary string could not be created. This will only cause problems with functions like DTM SECTION, STRINGS OVER DTM, etc. that require a valid DTM as created by the CREATE DTM function.
[DTM_INVALID_BOUND] Calculation of a unique boundary string is not possible, due to multiple possibilities.  The boundary string included with the DTM may not match the DTM, causing some DTM functions to work incorrectly.
[DTM_SEED_OUTBND] Seed triangle is out of bounds. The DTM may be invalid for this function.
[DTM_TRIANGLE_VERTICAL] The trisolation contains vertical triangles which is invalid for DTMs. These invalid triangles must be removed in order to proceed with the calculation.
[DTM_VALID_FOLDBACK_CHECK] Checking for foldbacks
[DTM_VALID_TRISOL_CLOSED] The trisolation is closed. Closed solids or voids cannot be valid DTM surfaces. 
[Error closing files] Error closing files
[Expected EOF] End of file not found
[Expected zero byte] Expected zero byte not found
[File format incorrect] File format incorrect
[FIO_AUTOCAD_FILE_OPEN_ERROR] AutoCAD: Error opening file {0}.
[FIO_AUTOCAD_LOADING] Importing AutoCAD file...
[FIO_DATAMINE_LOAD_AS_POINTS] Loading points from Datamine file...
[FIO_DATAMINE_LOAD_POINTS_FILE] Loading Datamine wireframe points file...
[FIO_DATAMINE_LOAD_STRING_FILE] Loading Datamine string file...
[FIO_DATAMINE_LOAD_TRIANGLE_FILE] Loading Datamine wireframe triangle file...
[FIO_FILE_PRE_SAVE] Analysing data to save...
[FIO_GEMCOM_OUTPUT_POLYLINE] Outputting polyline data...
[FIO_INIT_FILES] Initialising file properties...
[FIO_LOAD_ARCINFO] Loading Arcinfo file...
[FIO_LOAD_DTM] Loading DTM file...
[FIO_LOAD_GEMCOM_POLYLINE] Loading GEMS polyline...
[FIO_LOAD_GEMCOM_TRIOBJECTS] Loading GEMS triangulation file...
[FIO_LOAD_MEDS] Loading Meds file...
[FIO_LOAD_MICROSTATION] Loading Microstation file...
[FIO_LOAD_MINEX_GEOMETRY] Loading Minex geometry file
[FIO_LOAD_MM] Loading Micromine file
[FIO_SAVE_MINEX_GEOMETRY] Saving Minex geometry file
[FIO_SAVE_POINTS] Saving point data...
[FIO_SAVE_TRIOBJECT] Saving triangles...
[FIO_SURPAC_LOAD_POINTS] Loading string data...
[FIO_SURPAC_SAVE_DTM] Saving DTM...
[FIO_SURPAC_SAVE_STRING] Saving string data...
[FIO_VULCAN_CONVERT_DATABASE] Processing Vulcan records...
[FIO_VULCAN_LOAD] Loading Vulcan Objects...
[FIO_VULCAN_PRE_READ] Reading Vulcan file...
[FIO_VULCAN_READ] Processing Vulcan records...
[FIO_VULCAN_SAVE_RECORDS_TO_FILE] Saving records to Vulcan Database...
[GEMCOM_POLYLINE_INVALID_LINE] Line {0} invalid in GEMS polyline file
[GEMCOM_POLYLINE_PLANE_CODE_TO_DFIELD] Polyline plane code put into the {0} field
[GEMCOM_POLYLINE_TYPE_CODE_TO_DFIELD] Polyline type code put into the {0} field
[GENERAL_ERROR_READING_FILE] Error reading file {0}
[GENERAL_EXCEPTION_WHILE_READING_FILE] {0}
[GENERAL_EXCEPTION_WHILE_WRITING_FILE] {0}
[GENERAL_FAILED_TO_CREATE_FILE] Could not create the file to output
[GENERAL_INVALID_RANGE] Invalid range specifier {0}
[GENERAL_INVALID_RANGE_VALUE] Invalid range value {0}
[GENERAL_NUMBER_OF_TRIANGLES_LOADED] {0} triangles loaded
[Incorrect File Extension] Incorrect File Extension
[INVALID_NUMERIC_DESC_FIELD] The "{0}" field contains "{1}" which is non-numeric which cannot be used by this function. Inspect String {2}, Segment {3}, Point {4} for the problem.
[LPS_ERROR_SAVING_DEFAULTS] An error occurred while opening a file for writing
[MAPINFO_COLLECTION_IGNORED] Collection entity ignored
[MAPINFO_COLUMN_TO_DFIELD] "{0}" field, of type {1} output to {2} field
[MAPINFO_CUSTOM_POINT_IGNORED] Custom point entity ignored
[MAPINFO_ELEVATION_ATTRIBUTE_USED] Using attribute "{0}" for elevation
[MAPINFO_ENTITIES_LOADED] {0} MapInfo entities processed
[MAPINFO_GENERAL_ERROR_READING_FILE] An error occurred when reading the MapInfo file
[MAPINFO_GENERAL_ERROR_WRITING_FILE] An error occurred when writing the MapInfo file
[MAPINFO_LOAD_FILE] Loading MapInfo file...
[MAPINFO_LOADING_FILE_TYPE] MapInfo "{0}" file opened
[MAPINFO_NO_GEOM_FEATURE_IGNORED] No geometry entity ignored
[MAPINFO_UNKNOWN_ENTITY_IGNORED] Unknown entity ignored
[MEDS_DUPLICATE_CLASS_ID] Duplicate class ID : {0}
[MEDS_DUPLICATE_FIELD_NAME] Duplicate field name : {0}
[MEDS_DUPLICATE_STRING_INDEX] Duplicate string index : {0}
[MEDS_FIELD_DEFINITION_EXTENDS_PAST_CLASS_DEFINITION] Field definition extends past class definition : {0}
[MEDS_INVALID_CLASS_INDEX] Invalid class index : {0}
[MEDS_INVALID_INSTANCE] Invalid instance : {0}
[MEDS_INVALID_INSTANCE_INDEX] Invalid instance index : {0}
[MEDS_INVALID_INTEGER_LENGTH] Invalid integer length : {0}
[MEDS_INVALID_INTEGER_OFFSET] Invalid integer offset : {0}
[MEDS_INVALID_RECORD_LENGTH] Invalid record length : {0}
[MEDS_INVALID_RECORD_LENGTH_FLAG] Invalid record length flag : {0}
[MEDS_INVALID_RECORD_OFFSET] Invalid record offset : {0}
[MEDS_INVALID_STRING_FIELD] Invalid string field : {0}
[MEDS_INVALID_STRING_INDEX] Invalid string index : {0}
[MEDS_INVALID_STRING_LENGTH] Invalid string length : {0}
[MEDS_INVALID_STRING_PREFIX_LENGTH] Invalid string prefix length : {0}
[MEDS_INVALID_VALUE_RECORD_INDEX] Invalid value record index : {0}
[MEDS_INVALID_VERTEX_INDEX] Invalid vertex index : {0}
[MEDS_NON_NUMERIC_FILE_NAME] The file name {0} is not an integer and so cannot be used to number strings or objects.
[MEDS_NON_NUMERIC_NAME] The element name {0} is not an integer and so cannot be used to number the trisolation. The trisolation will be numbered {1}.
[MEDS_UNRECOGNISED_FILE_HEADER] Unrecognised MEDS file header
[MEDS_UNRECOGNISED_STANDARD_RECORD_HEADER] Unrecognised standard record header at {0}
[MICROMINE_IMPORT_POINTS] Outline {0} has {1} points to import.
[MICROMINE_MISSING_FIELD] A required field (Northing or Easting value) is missing from this file.   The field names that Surpac looks for are all listed in the reference manual information on the Micromine plugin.\nYou can specify site specific field names for the Northing, Easting and Elevation fields by using PLUGIN DEFAULTS or OPEN FILE and then setting the appropriate fields for Micromine.
[MICROMINE_OPEN_FAIL] Unable to open file {0}
[MICROMINE_OPEN_SEGMENTS_NOT_WRITTEN] Some segments were not written to the .out file because they are not closed.
[MICROSTATION_ERROR_READING_FILE] Error reading Microstation file {0}
[MINEXGM3_BAD_WORD_SIZE] Invalid word size is present in the Minex geometry file
[MINEXGM3_LOG_FILE_HEADER] String No, Group, Map, Ident, Class, Data Type, String Type, Red, Green, Blue, Line Style, Line Weight, Symbol
[Missing Z coordinate. Z is set to 0] Missing Z coordinate. Z is set to 0
[MSC_NOT_ENOUGH_POINTS_ERR] The specified string range contains less than three points
[MSC_NOT_SPACED_ENOUGH] Data extent is too small for plane calculations
[PLANES_DYNAMIC] Dynamic
[PLANES_ERROR_BAD_XML] Error reading plane definition.
[PLANES_ERROR_BAD_XML_CREATION] Error writing plane definition.
[PLANES_ERROR_WRITING] An error occurred writing the plane definition. The full path to the plane must be less than 256 characters long.
[PLUGIN_IGNORING_INVALID_TRIANGLE] Ignoring invalid triangle {0}. At least one of the triangle vertices tried to use a non-existent vertex.
[SOL_FATAL_ERROR] Error in calculations module
[SOL_NOTRANS_RETRY] Redoing the triangulation without transforming the segments
[SOL_TRIANGULATION_ERROR] Fatal retriangulation error
[SOLID_FAILED_TO_VALIDATE] Validation of triangulation failed, unable to process further.
[SPECIFIED_FIELD_DOES_NOT_EXISTS] Description field "{0}" does not exist. Inspect String {1}, Segment {2}, Point {3} for the problem.
[STR_SOME_SEGS_OPEN] Some segments of string {0} are open
[SURPAC_DTM_CANT_LOAD_DTM_FILE] Failed to load the file {0}.
[SURPAC_DTM_CANT_LOAD_STRING_FILE] Failed to load string file {0} specified by dtm
[SURPAC_DTM_NO_MATCHING_STRING_FILE] String file does not match DTM file
[SURPAC_INVALID_DTM_FILE_LINE] Invalid line in Surpac dtm file
[SURPAC_INVALID_STRING_FILE_LINE] Invalid Surpac string file line
[SURPAC_INVALID_VERTEX_IN_DTM_FILE] Invalid vertex information in Surpac dtm file
[SURPAC_MISSING_LINE_FROM_FILE_HEADER] Header line {0} missing from Surpac file
[SURPAC_NOT_VERSION_0_BINARY_FILE] Not a version 0 binary Surpac file
[SURPAC_PLUGIN_TOO_MANY_DFIELDS] More than {0} description fields have been found, and any description field past {0} will be ignored.
[The Minex Grid plugin can only save Grid data types.] The Minex Grid plugin can only save Grid data types.
[The Minex Tri5 plugin can only save triangle data types.] The Minex Tri5 plugin can only save triangle data types.
[Unexpected EOF] Unexpected end of file
[Unexpected IO Error] Unexpected file error encountered
[user] user
[USER_ABORTED_PROCESS] User aborted the process
[VULCAN_ERROR_LOADING_GRAPHICS_OBJECT] Error loading string entity "{0}" from the "{1}" layer
[VULCAN_ERROR_LOADING_LAYER] Error loading the "{0}" layer
[VULCAN_ERROR_LOADING_TEXT_OBJECT] Error loading text entity "{0}" from the "{1}" layer
[VULCAN_GRAPHICS_OBJECT_TO_STRING] Graphics entity "{0}" from the "{1}" layer is in string {2}
[VULCAN_INVALID_FILE_HEADER] Invalid file header in Vulcan file
[VULCAN_INVALID_NUMBER_OF_RECORDS] Invalid number of records in Vulcan file
[VULCAN_TEXT_OBJECT_TO_STRING] Text entity "{0}" from the {1} layer is in string {2}
[VULCAN_UNEXPECTED_RECORD] Unexpected record in Vulcan file