Blame Manuals/Repository/Docbook/Introduction/Repoconvs/filenames.docbook
|
|
054a7b |
<sect1 id="intro-repoconvs-filenames">
|
|
|
054a7b |
|
|
|
054a7b |
<title>File Names</title>
|
|
|
054a7b |
|
|
|
054a7b |
<para>
|
|
|
978692 |
Inside &TCAR;, file names are all written in lowercase (e.g.,
|
|
|
978692 |
<filename>01-welcome.png</filename>,
|
|
|
054a7b |
<filename>splash.png</filename>,
|
|
|
054a7b |
<filename>anaconda_header.png</filename>, etc.) and directory
|
|
|
054a7b |
names are all written capitalized (e.g.,
|
|
|
054a7b |
role="directory">Identity</filename>,
|
|
|
054a7b |
role="directory">Themes</filename>,
|
|
|
054a7b |
role="directory">Motifs</filename>) and sometimes in cammel
|
|
|
054a7b |
case (e.g., <filename role="directory">TreeFlower</filename>,
|
|
|
054a7b |
etc.).
|
|
|
054a7b |
</para>
|
|
|
054a7b |
|
|
|
054a7b |
<para>
|
|
|
054a7b |
In the very specific case of repository documentation entries,
|
|
|
054a7b |
file names follow the directory naming convenction. This is
|
|
|
054a7b |
because they are documenting directories and that is something
|
|
|
054a7b |
we want to remark. So, to better describe what we are
|
|
|
054a7b |
documenting, documentation entries follow the name convenction
|
|
|
054a7b |
used by the item they document.
|
|
|
054a7b |
</para>
|
|
|
054a7b |
|
|
|
054a7b |
</sect1>
|