<systemoutput>
System output is content that a computer or device generates in response to a command or situation.
Specialization hierarchy
The <systemoutput> element is specialized from
<ph>. It is defined in the software domain module.
Content model
(Text |
<data>
|
<sort-as>
|
<foreign>
|
<keyword>
|
<markupname>
|
<apiname>
|
<option>
|
<parmname>
|
<cmdname>
|
<msgnum>
|
<varname>
|
<wintitle>
|
<numcharref>
|
<parameterentity>
|
<textentity>
|
<xmlatt>
|
<xmlelement>
|
<xmlnsname>
|
<xmlpi>
|
<term>
|
<abbreviated-form>
|
<text>
)*
- Text
-
<abbreviated-form> -
<apiname> -
<cmdname> -
<data> -
<foreign> -
<keyword> -
<markupname> -
<msgnum> -
<numcharref> -
<option> -
<parameterentity> -
<parmname> -
<sort-as> -
<term> -
<text> -
<textentity> -
<varname> -
<wintitle> -
<xmlatt> -
<xmlelement> -
<xmlnsname> -
<xmlpi>
Attributes
The following attributes are
available on this element: universal
attributes and @keyref.
The following attributes are available on this element: universal attributes and the attributes defined below.
@keyref- Specifies a key
name that acts as a redirectable reference based on a key
definition within a map. See STUB CONTENT for information on using
this attribute.
For HDITA, the equivalent of
@keyrefis@data-keyref
Example
This section is non-normative.
In the following code sample, the <systemoutput> element identifies
an application response to user input:
<p>After you type <userinput>mealplan dinner</userinput>, the meal planning program
will print <systemoutput>For what day?</systemoutput>.
Reply by typing the day of the week for which you want a meal plan,
for example, <userinput>Thursday</userinput>.</p>