Help:Editing guidelines

This page describes standards, structures and techniques that are utilised in this wiki. It is recommended to conform to these in order to maintain information consistency and accessibility. However, nothing bad will happen if you do not. The standards are not tightly settled nor thoroughly thought, however they were changed many times through the page development, and are still imperfect. This means that they may changed again if there is a need for that. This also means that the rules may be broken whenever it is reasonable. Feel free to discuss the issues and ideas on the discussion pages.

Namespaces

Currently the FileInfo uses three namespaces (not counting the wiki maintenance namespaces):

• LBA1 - for LBA 1 contents
• LBA2 - for LBA 2 stuff
• Main - for common and other stuff

The rule is simple: everything that belongs to only one LBA version should go to appropriate LBA namespace, everything that belongs to both LBAs or does not belong to any of them should go to the Main namespace. Here are some examples and exceptions:

• HQR files and entries always go to LBA namespaces, because LBAs do not share files, even if some files have the same names (like ress.hqr, which has different content). This allows some entries to have identical names and still be described in different pages (like Main game palette).
• Programs always go to the Main namespace, because even if a program supports only one LBA version, it still does not belong to that version (e.g. support for the other version may be added in future).
• A File type should go to one of the LBA namespaces if it is used by one LBA version only, but it should go to the Main namespace if it is used by both LBAs. If both LBAs use a similar (but not identical) format for the same purpose (like isometric scene), it should be split into two pages with the same name, but each in its own namespace. In this case they may share the specification (that points out differences).

Categories

FileInfo categories not only organize content, but also, for HQR entries, define belonging to a specific HQR file, that's why in some cases it is important to maintain categories properly.

In automatic HQR presentation model (see below) each HQR file entry, must be in a category named identically as the HQR file it belongs to. For example, and entry (page) named Main game palette that belongs to Ress.hqr file (from LBA 1) must belog to Category:LBA1:Ress.hqr, otherwise it will not show on the LBA1:Ress.hqr page. This does not apply to manual presentation model, but existing entry pages should also follow this rule for consistency (and for easier possible switch to automatic model of that HQR file in future).

The main category structure is following:

• LBA1 - everything related to LBA 1
• LBA2 - everything related to LBA 2
• HQR files - HQR file and entry pages
  • LBA1:Anim.hqr
  • LBA1:Body.hqr
  • LBA2:Anim.hqr
  • LBA2:Body.hqr
  • ... and so on
• VOX files - same as HQR files
• ILE files
• OBL files
• File formats
• Programs

In the future there will be categories for images and other files, but there are none for now.

File format pages

The file format pages describe various file formats - all useful formats that exist in LBA installation directories (though describing some formats, like EXE, is probably pointless), and those that can be extracted from them. Infobox format template exists to provide infobox for the format pages. Example usage:

{{Infobox format
| extension = LSP
| lba1 = true
| lba2 = true
| colour = E0E000
| defaultsort = image
}}

• extension - is the commonly used extension the files of that format have when stored on a disk. Most of the extracted files extensions are made up by the LBA community.
• lba1 and lba2 - indicate occurence of files of this format in specific LBA version.
• colour = colour the extension will have in various lists (like entries list in a HQR page). The colour is in HTML notation, but without the # mark (named colours are not allowed).
• defaultsort - sets the wiki's {{DEFAULTSORT:xxx}} directive, which is used to change the way the page will be sorted in category listings. In this example, without defaultsort, the page would appear under L (because the page name is LBA image). The defaultsort param makes it appear under I.