Bug 81140 [nls tooling] Too many false positives when navigating from a key in properties file editor to Java editor
I200412142000 Currently properties key references are determined by a text search. The text search results should be filtered, such that the final results contain only matches from string partitions.
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/propertiesfileeditor/PropertyKeyHyperlink.java
Object[] result= dialog.getResult();
			if (result != null && result.length == 1)
			 return (KeyReference)result[0];
		}
		return null;
	}
		
	private void open(KeyReference keyReference) {
		if (keyReference == null)
			return;
		
		try {	
			IEditorPart part= EditorUtility.openInEditor(keyReference.storage, true);
			EditorUtility.revealInEditor(part, keyReference.offset, keyReference.length);
		} catch (JavaModelException e) {
			JavaPlugin.log(new Status(IStatus.ERROR, JavaPlugin.getPluginId(),
				IJavaStatusConstants.INTERNAL_ERROR, PropertiesFileEditorMessages.getString("OpenAction.error.message"), e)); 
			
			ErrorDialog.openError(fShell, 
				getErrorDialogTitle(),
				PropertiesFileEditorMessages.getString("OpenAction.error.messageProblems"), 
				e.getStatus());
		
		} catch (PartInitException x) {
							
			String message= null;
			
			IWorkbenchAdapter wbAdapter= (IWorkbenchAdapter)((IAdaptable)keyReference).getAdapter(IWorkbenchAdapter.class);
			if (wbAdapter != null)
				message= PropertiesFileEditorMessages.getFormattedString("OpenAction.error.messageArgs",