![]() The PROJECT_NUMBER tag can be used to enter a project or revision number. This name is used in the title of most generated pages and in a few other places. The PROJECT_NAME tag is a single word (or a sequence of words surrounded by double-quotes, unless you are using Doxywizard) that should identify the project for which the documentation is generated. ![]() Doxygen uses libiconv (or the iconv built into libc) for the transcoding. The default is UTF-8 which is also the encoding used for all text before the first occurrence of this tag. This tag specifies the encoding used for all characters in the configuration file that follow. Below is an alphabetical index of the tags that are recognized followed by the descriptions of the tags grouped by category. The configuration options can be divided into several categories. Do this by putting a tag with these paths before the tag, e.g.: = my_config_dir You can also specify a list of directories that should be searched before looking in the current working directory. The include file is searched in the current working directory. You can also include part of a configuration file from another configuration file using a tag as follows: = config_file_name A small example: DOT_PATH = $(YOUR_DOT_PATH) Multiple lines can be concatenated by inserting a backslash ( \) as the last character of a line.Įnvironment variables can be expanded using the pattern $(ENV_VARIABLE_NAME). If the value should contain one or more blanks it must be surrounded by quotes ( "."). For tags that take a list as their argument, the += operator can be used instead of = to append new values to the list. If the same tag is assigned more than once, the last assignment overwrites any earlier assignment. Each statement consists of a TAG_NAME written in capitals, followed by the equal sign ( =) and one or more values. The file essentially consists of a list of assignment statements. Comments begin with the hash character ( #) and ends at the end of the line. Comments beginning with two hash characters ( #) at the end of the configuration file are also kept and placed at the end of the file. Comments beginning with two hash characters ( #) at the beginning of the configuration file are also kept and placed at the beginning of the file. Comments beginning with two hash characters ( #) are kept when updating the configuration file and are placed in front of the TAG they are in front of. Comments may be placed anywhere within the file (except within quotes). ![]() ![]() The statements in the file are case-sensitive. The file may contain tabs and newlines for formatting purposes. But they are now, and it didn't help.A configuration file is a free-form ASCII text file with a structure that is similar to that of a Makefile, with the default name Doxyfile. Now, I haven't read the mail, but I'm sure they didn't mean that every file and folder on the server should be 644 and 755. My father contacted our new ISP for support, and got the advice to change the permissions of every file to 644 and every folder to 755. They change every time I reload the page. Warning: imagegif() : Unable to open '/home/ewisnhtx/public_html/music/bmz_cache/d/' for writing in /home/ewisnhtx/public_html/music/includes/classes/bmz_image_ on line 642 Warning: imagegif() : Unable to open '/home/ewisnhtx/public_html/music/bmz_cache/1/' for writing in /home/ewisnhtx/public_html/music/includes/classes/bmz_image_ on line 642 Warning: imagegif() : Unable to open '/home/ewisnhtx/public_html/music/bmz_cache/7/' for writing in /home/ewisnhtx/public_html/music/includes/classes/bmz_image_ on line 642 Now we can, but on the main page of we've got lots of messages like: When we changed isp (to PRO ISP) we restored a full backup of our old server, and thus had to change some names in the configure.php files, to be able to access the stores. We have some trouble with the layout on one of our site. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |