OptInt PmWiki : Pm Wiki / Page specific variables . ... Page variables have the form {$ variable } , and can be used in page markup or in certain formatting strings in PmWiki. ... Prefixing the variable name with an asterisk (*) means the variable reflects the value related to the target page or main page. ... Namespaced} - spaced page name, as in "Page Variables" . ... Defines new Page Variable of name $CurrentSkin, which can be used in the page with {$CurrentSkin} (also for Conditional markup ). ...

... PmWiki . ... Basic Variables | ... Page variables have the form {$ variable } , and can be used in page markup or in certain formatting strings in PmWiki . ... Note that these variables do not necessarily exist in the PHP code, because they have to be determined for a specific page. ... Prefixing the variable name with an asterisk (*) means the variable's value is related to the target page or main (body) page. ... Title} - page title (may differ from Name), as in "Page specific variables" . ...

... Apache HTTP Server Version 2.2 . Apache > HTTP Server > Documentation > Version 2.2 > Developer Documentation . ... Apache 2.0 uses Doxygen to document the APIs and global variables in the code. This will explain the basics of how to document using Doxygen. ... return description . ... foo/bar/gum" -> "gum" . ... gum" -> "gum" . ... Questions on how to manage the Apache HTTP Server should be directed at either our IRC channel, #httpd, on Freenode, or sent to our mailing lists . ...

... Apache HTTP Server Version 2.2 . Apache > HTTP Server > Documentation > Version 2.2 > Developer Documentation . ... Apache 2.0 uses Doxygen to document the APIs and global variables in the the code. This will explain the basics of how to document using Doxygen. ... return description . deffunc signature of the function . ... DoxyGen does not have a full parser in it, so any prototype that use a macro in the return type declaration is too complex for scandoc. ... foo/bar/gum" -> "gum" . ...

... ESO copyright, division, department . ... Any document produced by the DFS Department has to apply the official ESO document template: MSWORD format (ZIP compressed) , Latex format as compressed tar file (courtesy of Ralf and Pascal), or StarOffice format . ... Template for Test Plan and Test Report : as HTML page (for complete testing - to be edited with DreamWeaver, as Twiki page (for basic testing) Any HTML page produced by the DFS Department has to apply the official DFS web page template . ...

... Documentation for the Python objects defined by the project is divided into separate pages for each package, module, and class. The API documentation also includes two pages containing information about the project as a whole: a trees page, and an index page. ... A description of the package. ... A summary of the classes defined by the package. ... The module contents frame contains a list of every submodule, class, type, exception, function, and variable defined by a module or package. ...

The Call for Proposals and HST Primer are (only) available electronically in HTML and PDF formats. The HTML version is optimized for on-line browsing, and contains many links to related or more detailed information, both within the document itself and within other STScI documents. ... Please choose the format appropriate for your printer. ... Depending on your browser, you may obtain a nicer layout if you instruct your browser to use its default fonts, instead of the document-specific fonts. ...