Bug 73656 Encoding: refactoring should flush the undo stack on encoding changes
Refactoring should flush the undo stack on encoding changes. It is questionable what to do if the encoding changes since the encoding has an impact on the number of characters. Alternativly the UndoTectFileChange could remember the encoding and could compare it in isValid(...).
org.eclipse.ltk.core.refactoring/src/org/eclipse/ltk/internal/core/refactoring/RefactoringCoreMessages.java
public static String TextChanges_error_content_changed;
	public static String TextChanges_error_unsaved_changes;
	public static String TextChanges_error_read_only;
	public static String TextChanges_error_outOfSync;
	public static String TextChanges_error_document_content_changed;
	public static String CheckConditionContext_error_checker_exists;
	public static String CompositeChange_performingChangesTask_name;
	public static String ProcessorBasedRefactoring_initial_conditions;
	public static String ProcessorBasedRefactoring_final_conditions;
	public static String ProcessorBasedRefactoring_create_change;
	public static String ParticipantDescriptor_correct;
	public static String ParticipantDescriptor_error_id_missing;
	public static String ParticipantDescriptor_error_name_missing;
	public static String ParticipantDescriptor_error_class_missing;
	public static String ParticipantExtensionPoint_participant_removed;
	public static String ParticipantExtensionPoint_wrong_type;
	public static String RefactoringUndoContext_label;
	public static String Refactoring_execute_label;
	public static String Refactoring_undo_label;
	public static String Refactoring_redo_label;
	
	public static String UndoableOperation2ChangeAdapter_no_undo_available;
	public static String UndoableOperation2ChangeAdapter_no_redo_available;
	public static String UndoableOperation2ChangeAdapter_error_message;
	
	public static String UndoManager2_no_change;
	static {
		NLS.initializeMessages(BUNDLE_NAME, RefactoringCoreMessages.class);
	}
}