--- old/src/java.desktop/share/classes/javax/print/attribute/package-info.java 2017-07-16 16:17:45.000000000 -0700 +++ new/src/java.desktop/share/classes/javax/print/attribute/package-info.java 2017-07-16 16:17:45.000000000 -0700 @@ -39,19 +39,20 @@ * The print data and the processing instructions are separate entities. This * means that: * - *

* The processing instruction does not specify how the print job processes the * request; each processing instruction is only a description of the results of * a print job. The print job determines the manner in which it achieves the @@ -97,18 +98,18 @@ * The Java Print Service API defines these different kinds of attributes with * five subinterfaces of {@code Attribute}: *

* Each attribute class implements one or more of these tagging subinterfaces to * indicate where the attribute can be used in the API. If an attribute class @@ -123,40 +124,39 @@ * The Java Print Service API defines a group of standard attribute classes * modeled upon the attributes in the Internet Printing Protocol (IPP) version * 1.1. The standard attribute classes are in the subpackage - * javax.print.attribute.standard to keep the actual attribute classes + * {@code javax.print.attribute.standard} to keep the actual attribute classes * conceptually separate from the generic apparatus defined in package - * javax.print.attribute. + * {@code javax.print.attribute}. * *

Attribute Sets

* A client usually needs to provide more than one processing instruction when - * submitting a print job. For example, the client might need to specify a - * media size of A4 and a landscape orientation. To send more than one - * processing instruction, the client collects the attributes into an attribute - * set, which the Java Print Service API represents with the + * submitting a print job. For example, the client might need to specify a media + * size of A4 and a landscape orientation. To send more than one processing + * instruction, the client collects the attributes into an attribute set, which + * the Java Print Service API represents with the * AttributeSet interface. *

* The {@code AttributeSet} interface is similar to the * Map interface: it provides a map of * key to values, in which each key is unique and can contain no more than one * value. However, the {@code AttributeSet} interface is designed to - * specifically support the needs of the Java Print Service API. An {@code - * AttributeSet} requires that: + * specifically support the needs of the Java Print Service API. An + * {@code AttributeSet} requires that: *

    - *
  1. Each key in an {@code AttributeSet} corresponds to a category, and - * the value of the key can only be one of the attribute values that belong - * to the category represented by the key. Thus, unlike a {@code Map}, an - * {@code AttributeSet} restricts the possible values of a key: an attribute - * category cannot be set to an attribute value that does not belong to that - * category.
    2. - *
  2. No two attributes from the same category can exist in the same set. - * For example, an attribute collection must not contain both a "one-sided" - * attribute and a "two-sided" attribute because these two attributes give - * the printer conflicting instructions.
    3. - *
  3. Only attributes implementing the {@code Attribute} interface can be - * added to the set.
    4. + *
  4. Each key in an {@code AttributeSet} corresponds to a category, and the + * value of the key can only be one of the attribute values that belong to the + * category represented by the key. Thus, unlike a {@code Map}, an + * {@code AttributeSet} restricts the possible values of a key: an attribute + * category cannot be set to an attribute value that does not belong to that + * category. + *
  5. No two attributes from the same category can exist in the same set. For + * example, an attribute collection must not contain both a "one-sided" + * attribute and a "two-sided" attribute because these two attributes give the + * printer conflicting instructions. + *
  6. Only attributes implementing the {@code Attribute} interface can be + * added to the set. *
- *

- * The javax.print.attribute package includes + * The {@code javax.print.attribute} package includes * HashAttributeSet as a concrete * implementation of the attribute set interface. {@code HashAttributeSet} * provides an attribute set based on a hash map. You can use this @@ -167,18 +167,15 @@ * that are restricted to contain just one of the four kinds of attributes, as * discussed in the Attribute Roles section: *

* Notice that only four kinds of attribute sets are listed here, but there are * five kinds of attributes. Interface - * SupportedValuesAttribute - * denotes an attribute that gives the supported values for another attribute. + * SupportedValuesAttribute denotes + * an attribute that gives the supported values for another attribute. * Supported-values attributes are never aggregated into attribute sets, so * there is no attribute set subinterface defined for them. *

@@ -189,17 +186,15 @@ * For a read-only attribute set, calling a mutating operation throws an * {@code UnmodifiableSetException}. *

- * Package javax.print.attribute includes one concrete implementation of each of - * the attribute set subinterfaces: + * Package {@code javax.print.attribute} includes one concrete implementation of + * each of the attribute set subinterfaces: *

* All of these classes extend * HashAttributeSet and enforce the @@ -211,12 +206,11 @@ * enumerated value. The Java Print Service API does not use primitive data * types, such as int, to represent attribute values for these reasons: * * For type-safety and to represent all attributes uniformly, the Java Print * Service API defines each attribute category as a class, such as class @@ -240,27 +234,27 @@ * represent each abstract syntax, and these classes are used as the parent of * standard attributes whenever possible. The abstract syntax classes are: * * The abstract syntax classes are independent of the attributes that use them. * In fact, applications that have nothing to do with printing can use the @@ -304,12 +298,10 @@ *

Attribute Vendors

* The Java Print Service API is designed so that vendors can: * * To define a new value for an attribute, a client can construct instances of * such attributes with arbitrary values at runtime. However, an enumerated @@ -364,12 +356,12 @@ * } * *

- * Please note: In the javax.print APIs, a null reference parameter to methods - * is incorrect unless explicitly documented on the method as having a - * meaningful interpretation. Usage to the contrary is incorrect coding and may - * result in a run time exception either immediately or at some later time. - * IllegalArgumentException and NullPointerException are examples of typical and - * acceptable run time exceptions for such cases. + * Please note: In the {@code javax.print} APIs, a {@code null} reference + * parameter to methods is incorrect unless explicitly documented on the method + * as having a meaningful interpretation. Usage to the contrary is incorrect + * coding and may result in a run time exception either immediately or at some + * later time. {@code IllegalArgumentException} and {@code NullPointerException} + * are examples of typical and acceptable run time exceptions for such cases. * * @since 1.4 */