transfer parts from the wiki to the dev-manual

Author: jakoch

developer-manual/en/chapter02-engine-internals.adoc

@@ -170,6 +170,23 @@ Levels: `LOG_DEBUG`, `LOG_INFO`, `LOG_WARNING`, `LOG_ERROR`
 
 Modules can be filtered at runtime via `Log::setModuleLogLevel()`.
 
+===== C++ Logging Macros
+
+When writing C++ code, always use the provided log macros defined in
+`engine/core/modules.h`:
+
+[source,cpp]
+----
+FL_DBG(module, msg)   // Debug level
+FL_LOG(module, msg)   // Informational level
+FL_WARN(module, msg)  // Warning level
+FL_ERR(module, msg)   // Error level
+FL_PANIC(module, msg) // Panic level (causes abort)
+----
+
+Modules are defined in `<FIFE>/engine/core/modules.h`. Always use the correct
+log module when writing to the log.
+
 ==== XML Settings to EngineSettings
 
 The XML settings file maps directly to `EngineSettings`:

developer-manual/en/chapter04_coding-standards.adoc

@@ -2,6 +2,12 @@
 
 We have a set of quite detailed coding standards that have been followed for some time.
 
+=== Input file formats
+
+FIFE's accepted input file format is XML. The XML format should be used when
+describing data (metadata). Any new or existing functionality (like font file
+definitions) should also use the XML format.
+
 include::chapter04-cpp-coding-standard.adoc[]
 
 include::chapter04-python-coding-standard.adoc[]