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

Print this page

        

@@ -1,7 +1,7 @@
 /*
- * Copyright (c) 1997, 2003, 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

@@ -31,11 +31,11 @@
  * The <code>Document</code> is a container for text that serves
  * as the model for swing text components.  The goal for this
  * interface is to scale from very simple needs (a plain text textfield)
  * to complex needs (an HTML or XML document, for example).
  *
- * <p><b><font size=+1>Content</font></b>
+ * <p><b>Content</b>
  * <p>
  * At the simplest level, text can be
  * modeled as a linear sequence of characters. To support
  * internationalization, the Swing text model uses
  * <a href="http://www.unicode.org/">unicode</a> characters.

@@ -60,11 +60,11 @@
  * <ul>
  * <li>{@link #getLength()}
  * <li>{@link #getText(int, int)}
  * <li>{@link #getText(int, int, javax.swing.text.Segment)}
  * </ul>
- * <p><b><font size=+1>Structure</font></b>
+ * <p><b>Structure</b>
  * <p>
  * Text is rarely represented simply as featureless content. Rather,
  * text typically has some sort of structure associated with it.
  * Exactly what structure is modeled is up to a particular Document
  * implementation.  It might be as simple as no structure (i.e. a

@@ -81,11 +81,11 @@
  * <ul>
  * <li>{@link #getDefaultRootElement()}
  * <li>{@link #getRootElements()}
  * </ul>
  *
- * <p><b><font size=+1>Mutations</font></b>
+ * <p><b>Mutations</b>
  * <p>
  * All documents need to be able to add and remove simple text.
  * Typically, text is inserted and removed via gestures from
  * a keyboard or a mouse.  What effect the insertion or removal
  * has upon the document structure is entirely up to the

@@ -96,11 +96,11 @@
  * <li>{@link #insertString(int, java.lang.String, javax.swing.text.AttributeSet)}
  * <li>{@link #remove(int, int)}
  * <li>{@link #createPosition(int)}
  * </ul>
  *
- * <p><b><font size=+1>Notification</font></b>
+ * <p><b>Notification</b>
  * <p>
  * Mutations to the <code>Document</code> must be communicated to
  * interested observers.  The notification of change follows the event model
  * guidelines that are specified for JavaBeans.  In the JavaBeans
  * event model, once an event notification is dispatched, all listeners

@@ -150,11 +150,11 @@
  * <li><a href="#removeDocumentListener(javax.swing.event.DocumentListener)">removeDocumentListener(DocumentListener)</a>
  * <li><a href="#addUndoableEditListener(javax.swing.event.UndoableEditListener)">addUndoableEditListener(UndoableEditListener)</a>
  * <li><a href="#removeUndoableEditListener(javax.swing.event.UndoableEditListener)">removeUndoableEditListener(UndoableEditListener)</a>
  * </ul>
  *
- * <p><b><font size=+1>Properties</font></b>
+ * <p><b>Properties</b>
  * <p>
  * Document implementations will generally have some set of properties
  * associated with them at runtime.  Two well known properties are the
  * <a href="#StreamDescriptionProperty">StreamDescriptionProperty</a>,
  * which can be used to describe where the <code>Document</code> came from,