From acf05a45e8dbcc30f51ca1318b0da5968b430df3 Mon Sep 17 00:00:00 2001 From: esaunders Date: Tue, 10 Jan 2017 10:26:11 -0500 Subject: [PATCH] Modified message that is displayed in content viewer when we are unable to find the text associated with a keyword hit. --- .../src/org/sleuthkit/autopsy/keywordsearch/Bundle.properties | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/KeywordSearch/src/org/sleuthkit/autopsy/keywordsearch/Bundle.properties b/KeywordSearch/src/org/sleuthkit/autopsy/keywordsearch/Bundle.properties index 43ba62c3c6..576ce90aac 100644 --- a/KeywordSearch/src/org/sleuthkit/autopsy/keywordsearch/Bundle.properties +++ b/KeywordSearch/src/org/sleuthkit/autopsy/keywordsearch/Bundle.properties @@ -66,7 +66,7 @@ ExtractedContentViewer.getTitle=Indexed Text ExtractedContentViewer.getSolrContent.knownFileMsg=

{0} is a known file (based on MD5 hash) and does not have text in the index.

ExtractedContentViewer.getSolrContent.noTxtYetMsg=

{0} does not have text in the index.
It may have no text, not been analyzed yet, or keyword search was not enabled during ingest.

ExtractedContentViewer.getSolrContent.txtBodyItal={0} -HighlightedMatchesSource.getMarkup.noMatchMsg=
There were no keyword hits on this page. 
The keyword could have been in the file name. 
Advance to another page if present, or to view the original text, choose File Text 
in the drop down menu to the right...
+HighlightedMatchesSource.getMarkup.noMatchMsg=
Failed to retrieve content for keyword hit. 
The keyword could have been in the file name. 
Advance to another page if present, or to view the original text, choose File Text 
in the drop down menu to the right...
HighlightedMatchesSource.getMarkup.queryFailedMsg=
Failed to retrieve keyword hit results. 
Confirm that Autopsy can connect to the Solr server.
HighlightedMatchesSource.toString=Search Results Installer.reportPortError=Indexing server port {0} is not available. Check if your security software does not block {1} and consider changing {2} in {3} property file in the application user folder. Then try rebooting your system if another process was causing the conflict.