src/share/classes/javax/swing/text/JTextComponent.java

Print this page

        

@@ -1,7 +1,7 @@
 /*
- * Copyright (c) 1997, 2011, Oracle and/or its affiliates. All rights reserved.
+ * Copyright (c) 1997, 2013, Oracle and/or its affiliates. All rights reserved.
  * DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.
  *
  * This code is free software; you can redistribute it and/or modify it
  * under the terms of the GNU General Public License version 2 only, as
  * published by the Free Software Foundation.  Oracle designates this

@@ -86,11 +86,11 @@
  * this class provides in
  * <a href="http://docs.oracle.com/javase/tutorial/uiswing/components/generaltext.html">General Rules for Using Text Components</a>,
  * a section in <em>The Java Tutorial.</em>
  *
  * <dl>
- * <dt><b><font size=+1>Caret Changes</font></b>
+ * <dt><b>Caret Changes</b>
  * <dd>
  * The caret is a pluggable object in swing text components.
  * Notification of changes to the caret position and the selection
  * are sent to implementations of the <code>CaretListener</code>
  * interface that have been registered with the text component.

@@ -105,22 +105,22 @@
  * behavior can be changed by the {@link DefaultCaret#setUpdatePolicy} method.
  * <br>
  * <b>Note</b>: Non-editable text components also have a caret though
  * it may not be painted.
  *
- * <dt><b><font size=+1>Commands</font></b>
+ * <dt><b>Commands</b>
  * <dd>
  * Text components provide a number of commands that can be used
  * to manipulate the component.  This is essentially the way that
  * the component expresses its capabilities.  These are expressed
  * in terms of the swing <code>Action</code> interface,
  * using the <code>TextAction</code> implementation.
  * The set of commands supported by the text component can be
  * found with the {@link #getActions} method.  These actions
  * can be bound to key events, fired from buttons, etc.
  *
- * <dt><b><font size=+1>Text Input</font></b>
+ * <dt><b>Text Input</b>
  * <dd>
  * The text components support flexible and internationalized text input, using
  * keymaps and the input method framework, while maintaining compatibility with
  * the AWT listener model.
  * <p>

@@ -201,11 +201,11 @@
  * <li>removing content with the backspace and del
  *  keys.
  * <li>caret movement forward and backward
  * </ul>
  *
- * <dt><b><font size=+1>Model/View Split</font></b>
+ * <dt><b>Model/View Split</b>
  * <dd>
  * The text components have a model-view split.  A text component pulls
  * together the objects used to represent the model, view, and controller.
  * The text document model may be shared by other views which act as observers
  * of the model (e.g. a document may be shared by multiple components).

@@ -225,44 +225,44 @@
  * {@link DocumentEvent} which allows the views to stay up to date with the model.
  * This event is sent to observers that have implemented the
  * {@link DocumentListener}
  * interface and registered interest with the model being observed.
  *
- * <dt><b><font size=+1>Location Information</font></b>
+ * <dt><b>Location Information</b>
  * <dd>
  * The capability of determining the location of text in
  * the view is provided.  There are two methods, {@link #modelToView}
  * and {@link #viewToModel} for determining this information.
  *
- * <dt><b><font size=+1>Undo/Redo support</font></b>
+ * <dt><b>Undo/Redo support</b>
  * <dd>
  * Support for an edit history mechanism is provided to allow
  * undo/redo operations.  The text component does not itself
  * provide the history buffer by default, but does provide
  * the <code>UndoableEdit</code> records that can be used in conjunction
  * with a history buffer to provide the undo/redo support.
  * The support is provided by the Document model, which allows
  * one to attach UndoableEditListener implementations.
  *
- * <dt><b><font size=+1>Thread Safety</font></b>
+ * <dt><b>Thread Safety</b>
  * <dd>
  * The swing text components provide some support of thread
  * safe operations.  Because of the high level of configurability
  * of the text components, it is possible to circumvent the
  * protection provided.  The protection primarily comes from
  * the model, so the documentation of <code>AbstractDocument</code>
  * describes the assumptions of the protection provided.
  * The methods that are safe to call asynchronously are marked
  * with comments.
  *
- * <dt><b><font size=+1>Newlines</font></b>
+ * <dt><b>Newlines</b>
  * <dd>
  * For a discussion on how newlines are handled, see
  * <a href="DefaultEditorKit.html">DefaultEditorKit</a>.
  *
  *
- * <dt><b><font size=+1>Printing support</font></b>
+ * <dt><b>Printing support</b>
  * <dd>
  * Several {@link #print print} methods are provided for basic
  * document printing.  If more advanced printing is needed, use the
  * {@link #getPrintable} method.
  * </dl>