FM / libXt

/usr/share/doc/libXt

Name	Size	Mode	Actions
acknowledgement.xml	8743	0644	edit dl rm
appA.xml	3644	0644	edit dl rm
appB.xml	32505	0644	edit dl rm
appC.xml	56361	0644	edit dl rm
appD.xml	28405	0644	edit dl rm
appE.xml	38698	0644	edit dl rm
appF.xml	3893	0644	edit dl rm
CH01.xml	89186	0644	edit dl rm
CH02.xml	143010	0644	edit dl rm
CH03.xml	43858	0644	edit dl rm
CH04.xml	78069	0644	edit dl rm
CH05.xml	30989	0644	edit dl rm
CH06.xml	43514	0644	edit dl rm
CH07.xml	150747	0644	edit dl rm
CH08.xml	17593	0644	edit dl rm
CH09.xml	136490	0644	edit dl rm
CH10.xml	67632	0644	edit dl rm
CH11.xml	168130	0644	edit dl rm
CH12.xml	33863	0644	edit dl rm
CH13.xml	30677	0644	edit dl rm
COPYING	5673	0644	edit dl rm
intrinsics.xml	5307	0644	edit dl rm
preface.xml	2733	0644	edit dl rm

Edit: /usr/share/doc/libXt/appA.xml (3644B)

<appendix id='Resource_File_Format'>
<title>Resource File Format</title>
<para>
A resource file contains text representing the default resource values for an
application or set of applications.
</para>

<para>
The format of resource files is defined by
<emphasis remap='I'>Xlib — C Language X Interface.</emphasis> and is reproduced here
for convenience only.
</para>

<para>The format of a resource specification is</para>
<informaltable frame='none'>
  <?dbfo keep-together="always" ?>
  <tgroup cols='2' align='left' colsep='0' rowsep='0'>
  <colspec colwidth='0.3*' colname='c1'/>
  <colspec colwidth='1.0*' colname='c2'/>
  <tbody>
    <row>
      <entry>ResourceLine</entry>
      <entry>= Comment | IncludeFile | ResourceSpec | &lt;empty line&gt;</entry>
    </row>
    <row>
      <entry>Comment</entry>
      <entry>="!" {&lt;any character except null or newline&gt;}</entry>
    </row>
    <row>
      <entry>IncludeFile</entry>
      <entry>= "#" WhiteSpace "include" WhiteSpace FileName WhiteSpace</entry>
    </row>
    <row>
      <entry>FileName</entry>
      <entry>= &lt;valid filename for operating system&gt;</entry>
    </row>
    <row>
      <entry>ResourceSpec</entry>
      <entry>= WhiteSpace ResourceName WhiteSpace ":" WhiteSpace Value</entry>
    </row>
    <row>
      <entry>ResourceName</entry>
      <entry>= [Binding] {Component Binding} ComponentName</entry>
    </row>
    <row>
      <entry>Binding</entry>
      <entry>="." | "*"</entry>
    </row>
    <row>
      <entry>WhiteSpace</entry>
      <entry>= {&lt;space> | &lt;horizontal tab&gt;}</entry>
    </row>
    <row>
      <entry>Component</entry>
      <entry>= "?" | ComponentName</entry>
    </row>
    <row>
      <entry>ComponentName</entry>
      <entry>= NameChar {NameChar}</entry>
    </row>
    <row>
      <entry>NameChar</entry>
      <entry>= "a"-"z" | "A"-"Z" | "0"-"9" | "_" | "-"</entry>
    </row>
    <row>
      <entry>Value</entry>
      <entry>={&lt;any character except null or unescaped newline&gt;}</entry>
    </row>
  </tbody>
  </tgroup>
</informaltable>

<para>
Elements separated by vertical bar (|) are alternatives.
Curly braces ({...}) indicate zero or more repetitions
of the enclosed elements.
Square brackets ([...]) indicate that the enclosed element is optional.
Quotes ("...") are used around literal characters.
</para>

<para>
If the last character on a line is a backslash (\),
that line is assumed to continue on the next line.
</para>

<para>
To allow a Value to begin with whitespace,
the two-character sequence "\<emphasis remap='I'>space</emphasis>" (backslash followed by space)
is recognized and replaced by a space character,
and the two-character sequence "\<emphasis remap='I'>tab</emphasis>"
(backslash followed by horizontal tab)
is recognized and replaced by a horizontal tab character.
</para>
<para>
To allow a Value to contain embedded newline characters,
the two-character sequence "\n" is recognized and replaced by a
newline character.
To allow a Value to be broken across multiple lines in a text file,
the two-character sequence "\<emphasis remap='I'>newline</emphasis>"
(backslash followed by newline) is
recognized and removed from the value.
</para>
<para>
To allow a Value to contain arbitrary character codes,
the four-character sequence "\<emphasis remap='I'>nnn</emphasis>",
where each <emphasis remap='I'>n</emphasis> is a digit character in the range of "0"-"7",
is recognized and replaced with a single byte that contains
the octal value specified by the sequence.
Finally, the two-character sequence "\\" is recognized
and replaced with a single backslash.
</para>
</appendix>

Resource File Format A resource file contains text representing the default resource values for an application or set of applications. The format of resource files is defined by Xlib — C Language X Interface. and is reproduced here for convenience only. The format of a resource specification is ResourceLine = Comment | IncludeFile | ResourceSpec | <empty line> Comment ="!" {<any character except null or newline>} IncludeFile = "#" WhiteSpace "include" WhiteSpace FileName WhiteSpace FileName = <valid filename for operating system> ResourceSpec = WhiteSpace ResourceName WhiteSpace ":" WhiteSpace Value ResourceName = [Binding] {Component Binding} ComponentName Binding ="." | "*" WhiteSpace = {<space> | <horizontal tab>} Component = "?" | ComponentName ComponentName = NameChar {NameChar} NameChar = "a"-"z" | "A"-"Z" | "0"-"9" | "_" | "-" Value ={<any character except null or unescaped newline>} Elements separated by vertical bar (|) are alternatives. Curly braces ({...}) indicate zero or more repetitions of the enclosed elements. Square brackets ([...]) indicate that the enclosed element is optional. Quotes ("...") are used around literal characters. If the last character on a line is a backslash (\), that line is assumed to continue on the next line. To allow a Value to begin with whitespace, the two-character sequence "\space" (backslash followed by space) is recognized and replaced by a space character, and the two-character sequence "\tab" (backslash followed by horizontal tab) is recognized and replaced by a horizontal tab character. To allow a Value to contain embedded newline characters, the two-character sequence "\n" is recognized and replaced by a newline character. To allow a Value to be broken across multiple lines in a text file, the two-character sequence "\newline" (backslash followed by newline) is recognized and removed from the value. To allow a Value to contain arbitrary character codes, the four-character sequence "\nnn", where each n is a digit character in the range of "0"-"7", is recognized and replaced with a single byte that contains the octal value specified by the sequence. Finally, the two-character sequence "\\" is recognized and replaced with a single backslash.