Blame Documentation/Manuals/Docbook/Tcar-ug/Repository/Convenctions/filenames.docbook
|
|
3c5068 |
<sect1 id="repo-convs-filenames">
|
|
|
054a7b |
|
|
|
3c5068 |
<title>Repository 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>,
|
|
|
a936bc |
etc.). In the very specific case of repository documentation
|
|
|
a936bc |
entries, file names follow the directory naming convenction.
|
|
|
a936bc |
This is because they are documenting directories and that is
|
|
|
a936bc |
something we want to remark. So, to better describe what we
|
|
|
a936bc |
are documenting, documentation entries follow the name
|
|
|
a936bc |
convenction used by the item they document.
|
|
|
054a7b |
</para>
|
|
|
054a7b |
|
|
|
33f520 |
</sect1>
|