Log of Roxen.git/server/translations/eng/roxen

2002-06-13

2002-06-13 22:54:23 by Martin Nilsson <mani@lysator.liu.se>

e4202bf4e639c7a64c23ecc62a6bf255387c0aa5 (1532 lines) (+132/-1400) ^{[

Show
| Annotate

]}
Branch: Aphoto_2.0_beta3

Automated update

Rev: server/translations/Makefile:1.5
Rev: server/translations/ces/roxen_config.xml:1.32
Rev: server/translations/configs/roxen_config.xml:1.30
Rev: server/translations/configs/roxen_message.xml:1.16
Rev: server/translations/deu/roxen_config.xml:1.40
Rev: server/translations/deu/roxen_message.xml:1.10
Rev: server/translations/eng/mod_filesystem.xml:1.8
Rev: server/translations/eng/mod_webapp.xml:1.3(DEAD)
Rev: server/translations/eng/roxen_config.xml:1.37
Rev: server/translations/eng/roxen_message.xml:1.21
Rev: server/translations/hun/roxen_config.xml:1.28
Rev: server/translations/jpn/roxen_config.xml:1.28
Rev: server/translations/nld/roxen_config.xml:1.32
Rev: server/translations/swe/roxen_config.xml:1.41
Rev: server/translations/swe/roxen_message.xml:1.20

2: <locale version="1.0"/> <project>roxen_config</project> <language>eng</language> - <file>../base_server/config_userdb.pike</file> - <file>../base_server/configuration.pike</file> - <file>../base_server/global_variables.pike</file> - <file>../base_server/module_support.pike</file> - <file>../config_interface/actions/index.html</file> + <file>../config_interface/boxes/Box.pmod</file> - <file>../config_interface/boxes/articles.pike</file> + <file>../config_interface/boxes/crunch.pike</file> <file>../config_interface/boxes/doclinks.pike</file> <file>../config_interface/boxes/megatokyo.pike</file> - <file>../config_interface/boxes/ris_news.pike</file> + <file>../config_interface/boxes/server_status.pike</file> <file>../config_interface/boxes/welcome.pike</file> <file>../config_interface/cv_startpage_tabs.pike</file>
44: <file>../config_interface/sites/index.html</file> <file>../config_interface/sites/log.pike</file> <file>../config_interface/sites/new_site.html</file> - <file>../config_interface/sites/site.html</file> + <file>../config_interface/sites/site_content.pike</file> <file>../config_interface/sites/site_header.pike</file> - + <file>../config_interface/sites/site.html</file> <file>../config_interface/statusinfo.pike</file> - + <file>../config_interface/tasks/index.html</file> <file>../config_interface/template</file> <file>../config_interface/topmenu.pike</file> <file>../config_interface/user_delete.pike</file> <file>../config_interface/user_form.pike</file> <file>../config_interface/users.html</file> - <file>../etc/modules/Variable.pmod/Date.pike</file> - <file>../etc/modules/Variable.pmod/Email.pike</file> - <file>../etc/modules/Variable.pmod/Image.pike</file> - <file>../etc/modules/Variable.pmod/Mapping.pike</file> - <file>../etc/modules/Variable.pmod/Schedule.pike</file> - <file>../etc/modules/Variable.pmod/Upload.pike</file> - <file>../etc/modules/Variable.pmod/VerifiedString.pike</file> - <file>../etc/modules/Variable.pmod/module.pmod</file> + <file>../modules/configuration/config_filesystem.pike</file> <file>../modules/configuration/config_tags.pike</file> - + <file>../pike_modules/Variable.pmod/Date.pike</file> + <file>../pike_modules/Variable.pmod/Email.pike</file> + <file>../pike_modules/Variable.pmod/Image.pike</file> + <file>../pike_modules/Variable.pmod/Mapping.pike</file> + <file>../pike_modules/Variable.pmod/module.pmod</file> + <file>../pike_modules/Variable.pmod/Schedule.pike</file> + <file>../pike_modules/Variable.pmod/Upload.pike</file> + <file>../pike_modules/Variable.pmod/VerifiedString.pike</file> <file>../site_templates/common.pike</file> <str id="2">
95: <t></t> </str> - <str id="11"> - <o>Reloaded %s.</o> - <t></t> - </str> + - <str id="12"> - <o>Priority</o> - <t></t> - </str> + - <str id="13"> - <o>The priority of the module. 9 is highest and 0 is lowest. Modules with the same priority can be assumed to be called in random order</o> - <t></t> - </str> - - <str id="16"> - <o>Security: Patterns</o> - <t></t> - </str> - - <str id="18"> - <o>Security: Security level</o> - <t></t> - </str> - - <str id="20"> - <o>Default site</o> - <t></t> - </str> - - <str id="21"> - <o>If true, this site will be selected in preference of other sites when virtual hosting is used and no host header is supplied, or the supplied host header does not match the address of any of the other servers.</o> - <t></t> - </str> - - <str id="22"> - <o>Site comment</o> - <t></t> - </str> - - <str id="23"> - <o>This text will be visible in the administration interface, it can be quite useful to use as a memory helper.</o> - <t></t> - </str> - - <str id="24"> - <o>Site name</o> - <t></t> - </str> - - <str id="25"> - <o>This is the name that will be used in the administration interface. If this is left empty, the actual name of the site will be used.</o> - <t></t> - </str> - - <str id="26"> - <o>Logging: Format</o> - <t></t> - </str> - - <str id="27"> - <o>What format to use for logging. The syntax is: - <pre>response-code or *: Log format for that response code - - Log format is normal characters, or one or more of the variables below: - - \n \t \r -- As in C, newline, tab and linefeed - $char(int) -- Insert the (1 byte) character specified by the integer. - $wchar(int) -- Insert the (2 byte) word specified by the integer. - $int(int) -- Insert the (4 byte) word specified by the integer. - $^ -- Supress newline at the end of the logentry - $host -- The remote host name, or ip number. - $vhost -- The Host request-header sent by the client, or - if none - $ip_number -- The remote ip number. - $bin-ip_number -- The remote host id as a binary integer number. - $cern_date -- Cern Common Log file format date. - $bin-date -- Time, but as an 32 bit integer in network byteorder - $method -- Request method - $resource -- Resource identifier - $full_resource -- Full requested resource, including any query fields - $protocol -- The protocol used (normally HTTP/1.0) - $response -- The response code sent - $bin-response -- The response code sent as a binary short number - $length -- The length of the data section of the reply - $bin-length -- Same, but as an 32 bit integer in network byteorder - $request-time -- The time the request took (seconds) - $referer -- the header 'referer' from the request, or '-'. - $user_agent -- the header 'User-Agent' from the request, or '-'. - - $user -- the name of the auth user used, if any - $user_id -- A unique user ID, if cookies are supported, - by the client, otherwise '0' - $cache-status -- A comma separated list of words (containing no - whitespace) that describes which cache(s) the page - was delivered from: - protcache -- The low-level cache in the HTTP - protocol module. - xsltcache -- The XSLT cache. - pcoderam -- RXML parse tree RAM cache. - pcodedisk -- RXML parse tree persistent cache. - cachetag -- No RXML &lt;cache&gt; tag misses. - nocache -- No hit in any known cache. - </pre></o> - <t></t> - </str> - - <str id="28"> - <o>Logging: Enabled</o> - <t></t> - </str> - - <str id="29"> - <o>Log requests</o> - <t></t> - </str> - - <str id="30"> - <o>Logging: Log file</o> - <t></t> - </str> - - <str id="31"> - <o>The log file. <pre>%y Year (e.g. '1997') - %m Month (e.g. '08') - %d Date (e.g. '10' for the tenth) - %h Hour (e.g. '00') - %H Hostname - </pre></o> - <t></t> - </str> - - <str id="32"> - <o>Logging: No Logging for</o> - <t></t> - </str> - - <str id="33"> - <o>Don't log requests from hosts with an IP number which matches any of the patterns in this list. This also affects the access counter log.</o> - <t></t> - </str> - - <str id="34"> - <o>Domain</o> - <t></t> - </str> - - <str id="35"> - <o>The domain name of the server. The domain name is used to generate default URLs, and to generate email addresses.</o> - <t></t> - </str> - - <str id="36"> - <o>Ports: Primary Server URL</o> - <t></t> - </str> - - <str id="37"> - <o>This is the main server URL, where your start page is located. This - setting is for instance used as fallback to generate absolute URLs to - the server, but in most circumstances the URLs sent by the clients are - used. A URL is deduced from the first entry in 'URLs' if this is left - blank. - - Note that setting this doesn't make the server accessible; you must - also set 'URLs'.</o> - <t></t> - </str> - - <str id="38"> - <o>Ports: URLs</o> - <t></t> - </str> - - <str id="40"> - <o>Internal module resource mountpoint</o> - <t></t> - </str> - - <str id="41"> - <o>Some modules may want to create links to internal resources. This setting configures an internally handled location that can be used for such purposes. Simply select a location that you are not likely to use for regular resources.</o> - <t></t> - </str> - - <str id="42"> - <o>Throttling: Server; Enabled</o> - <t></t> - </str> - - <str id="43"> - <o>If set, per-server bandwidth throttling will be enabled. It will allow you to limit the total available bandwidth for this site. Bandwidth is assigned using a Token Bucket. The principle under which it works is: for each byte we send we use a token. Tokens are added to a repository at a constant rate. When there's not enough, we can't transmit. When there's too many, they "spill" and are lost.</o> - <t></t> - </str> - - <str id="44"> - <o>Throttling: Server; Average available bandwidth</o> - <t></t> - </str> - - <str id="45"> - <o>This is the average bandwidth available to this site in bytes/sec (the bucket "fill rate").</o> - <t></t> - </str> - - <str id="46"> - <o>Throttling: Server; Bucket Depth</o> - <t></t> - </str> - - <str id="47"> - <o>This is the maximum depth of the bucket. After a long enough period of inactivity, a request will get this many unthrottled bytes of data, before throttling kicks back in. Set equal to the Fill Rate in order not to allow any data bursts. This value determines the length of the time over which the bandwidth is averaged.</o> - <t></t> - </str> - - <str id="48"> - <o>Throttling: Server; Minimum Grant</o> - <t></t> - </str> - - <str id="49"> - <o>When the bandwidth availability is below this value, connections will be delayed rather than granted minimal amounts of bandwidth. The purpose is to avoid sending too small packets (which would increase the IP overhead).</o> - <t></t> - </str> - - <str id="50"> - <o>Throttling: Server; Maximum Grant</o> - <t></t> - </str> - - <str id="51"> - <o>This is the maximum number of bytes assigned in a single request to a connection. Keeping this number low will share bandwidth more evenly among the pending connections, but keeping it too low will increase IP overhead and (marginally) CPU usage. You'll want to set it just a tiny bit lower than any integer multiple of your network's MTU (typically 1500 for ethernet).</o> - <t></t> - </str> - - <str id="52"> - <o>Throttling: Request; Enabled</o> - <t></t> - </str> - - <str id="53"> - <o>If set, per-request bandwidth throttling will be enabled.</o> - <t></t> - </str> - - <str id="54"> - <o>Throttling: Request; Minimum guarranteed bandwidth</o> - <t></t> - </str> - - <str id="55"> - <o>The maximum bandwidth each connection (in bytes/sec) can use is determined combining a number of modules. But doing so can lead to too small or even negative bandwidths for particularly unlucky requests. This variable guarantees a minimum bandwidth for each request.</o> - <t></t> - </str> - - <str id="56"> - <o>Throttling: Request; Bucket Depth Multiplier</o> - <t></t> - </str> - - <str id="57"> - <o>The average bandwidth available for each request will be determined by the modules combination. The bucket depth will be determined multiplying the rate by this factor.</o> - <t></t> - </str> - - <str id="58"> - <o>No such file message</o> - <t></t> - </str> - - <str id="59"> - <o>What to return when there is no resource or file available at a certain location.</o> - <t></t> - </str> - - <str id="60"> - <o>Welcome text</o> - <t></t> - </str> - - <str id="61"> - <o>The text shown to the user on connect</o> - <t></t> - </str> - - <str id="62"> - <o>User session limit</o> - <t></t> - </str> - - <str id="63"> - <o>The maximum number of times a user can connect at once. 0 means unlimited.</o> - <t></t> - </str> - - <str id="64"> - <o>Allow named ftp</o> - <t></t> - </str> - - <str id="65"> - <o>If yes, non-anonymous users can connect</o> - <t></t> - </str> - - <str id="66"> - <o>Allow login with incorrect password/user</o> - <t></t> - </str> - - <str id="67"> - <o>If yes, users can connect with the wrong password and/or username. This is useful since things like .htaccess files can later on authenticate the user.</o> - <t></t> - </str> - - <str id="68"> - <o>Allow anonymous ftp</o> - <t></t> - </str> - - <str id="69"> - <o>If yes, anonymous users is allowed to connect.</o> - <t></t> - </str> - - <str id="70"> - <o>Shell database</o> - <t></t> - </str> - - <str id="71"> - <o>If this string is set to anything but the empty string, it should point to a file containing a list of valid shells. Users with shells that does not figure in this list will not be allowed to log in.</o> - <t></t> - </str> - - <str id="72"> - <o>Show internal errors</o> - <t></t> - </str> - - <str id="73"> - <o>Show 'Internal server error' messages to the user. This is very useful if you are debugging your own modules or writing Pike scripts.</o> - <t></t> - </str> - - <str id="74"> - <o>Logging: Set unique browser id cookies</o> - <t></t> - </str> - - <str id="75"> - <o>If set to Yes, all clients that accepts cookies will get a unique 'user-id-cookie', which can then be used in the log and in scripts to track individual users.</o> - <t></t> - </str> - - <str id="76"> - <o>Logging: Set ID cookies only once</o> - <t></t> - </str> - - <str id="77"> - <o>If set to Yes, Roxen will attempt to set unique browser ID cookies only upon receiving the first request (and again after some minutes). Thus, if the user doesn't allow the cookie to be set, she won't be bothered with multiple requests.</o> - <t></t> - </str> - - <str id="86"> - <o>SSL certificate file</o> - <t></t> - </str> - - <str id="87"> - <o>The SSL certificate file to use. The path is relative to %s</o> - <t></t> - </str> - - <str id="88"> - <o>SSL key file</o> - <t></t> - </str> - - <str id="89"> - <o>The SSL key file to use. The path is relative to %s, you do not have to specify a key file, leave this field empty to use the certificate file only</o> - <t></t> - </str> - - <str id="90"> - <o>Logging: Log entire file length in restored connections</o> - <t></t> - </str> - - <str id="91"> - <o>If this toggle is enabled log entries for restored connections will log the amount of sent data plus the restoration location. Ie if a user has downloaded 100 bytes of a file already, and makes a Range request fetching the remaining 900 bytes, the log entry will log it as if the entire 1000 bytes were downloaded. This is useful if you want to know if downloads were successful (the user has the complete file downloaded). The drawback is that bandwidth statistics on the log file will be incorrect. The statistics in Roxen will still be correct.</o> - <t></t> - </str> - - <str id="92"> - <o>Default font</o> - <t></t> - </str> - - <str id="93"> - <o>The default font to use when modules request a font.</o> - <t></t> - </str> - - <str id="94"> - <o>Font directories</o> - <t></t> - </str> - - <str id="95"> - <o>This is where the fonts are located.</o> - <t></t> - </str> - - <str id="96"> - <o>Logging: Log directory prefix</o> - <t></t> - </str> - - <str id="97"> - <o>This is the default file path that will be prepended to the log file path in all the default modules and the site.</o> - <t></t> - </str> - - <str id="98"> - <o>Cache: Proxy Disk Cache Enabled</o> - <t></t> - </str> - - <str id="99"> - <o>If set to Yes, caching will be enabled.</o> - <t></t> - </str> - - <str id="100"> - <o>Cache: Proxy Disk Cache Clean size</o> - <t></t> - </str> - - <str id="101"> - <o>Minimum number of Megabytes removed when a garbage collect is done.</o> - <t></t> - </str> - - <str id="102"> - <o>Cache: Proxy Disk Cache Minimum available free space and inodes (in %)</o> - <t></t> - </str> - - <str id="103"> - <o>If less than this amount of disk space or inodes (in %) is left, the cache will remove a few files. This check may work half-hearted if the diskcache is spread over several filesystems.</o> - <t></t> - </str> - - <str id="104"> - <o>Cache: Proxy Disk Cache Size</o> - <t></t> - </str> - - <str id="105"> - <o>How many MB may the cache grow to before a garbage collect is done?</o> - <t></t> - </str> - - <str id="106"> - <o>Cache: Proxy Disk Cache Maximum number of files</o> - <t></t> - </str> - - <str id="107"> - <o>How many cache files (inodes) may be on disk before a garbage collect is done ? May be left zero to disable this check.</o> - <t></t> - </str> - - <str id="108"> - <o>Cache: Proxy Disk Cache bytes per second</o> - <t></t> - </str> - - <str id="109"> - <o>How file size should be treated during garbage collect. Each X bytes counts as a second, so that larger files will be removed first.</o> - <t></t> - </str> - - <str id="110"> - <o>Cache: Proxy Disk Cache Base Cache Dir</o> - <t></t> - </str> - - <str id="111"> - <o>This is the base directory where cached files will reside. To avoid mishaps, 'roxen_cache/' is always prepended to this variable.</o> - <t></t> - </str> - - <str id="112"> - <o>Cache: Proxy Disk Cache Number of hash directories</o> - <t></t> - </str> - - <str id="113"> - <o>This is the number of directories to hash the contents of the disk cache into. Changing this value currently invalidates the whole cache, since the cache cannot find the old files. In the future, the cache will be recalculated when this value is changed.</o> - <t></t> - </str> - - <str id="114"> - <o>Cache: Proxy Disk Cache Keep without Content-Length</o> - <t></t> - </str> - - <str id="115"> - <o>Keep files without Content-Length header information in the cache?</o> - <t></t> - </str> - - <str id="116"> - <o>Cache: Proxy Disk Cache Refreshes on Last-Modified</o> - <t></t> - </str> - - <str id="117"> - <o>If set, refreshes files without Expire header information when they have reached double the age they had when they got cached. This may be useful for some regularly updated docs as online newspapers.</o> - <t></t> - </str> - - <str id="118"> - <o>Cache: Proxy Disk Cache Last resort (in days)</o> - <t></t> - </str> - - <str id="119"> - <o>How many days shall files without Expires and without Last-Modified header information be kept?</o> - <t></t> - </str> - - <str id="120"> - <o>Cache: Proxy Disk Cache Garbage collector logfile</o> - <t></t> - </str> - - <str id="121"> - <o>Information about garbage collector runs, removed and refreshed files, cache and disk status goes here.</o> - <t></t> - </str> - - <str id="124"> - <o>Identify, Use default identification string</o> - <t></t> - </str> - - <str id="125"> - <o>Setting this variable to No will display the "Identify as" node where you can state what Roxen should call itself when talking to clients. It is possible to disable this so that you can enter an identification-string that does not include the actual version of Roxen, as recommended by the HTTP/1.0 and HTTP/1.1 RFCs:<blockquote>Note: Revealing the specific software version of the server may allow the server machine to become more vulnerable to attacks against software that is known to contain security holes. Server implementors are encouraged to make this field a configurable option.</blockquote></o> - <t></t> - </str> - - <str id="126"> - <o>Identify, Identify as</o> - <t></t> - </str> - - <str id="127"> - <o>Enter the name that Roxen should use when talking to clients. </o> - <t></t> - </str> - - <str id="128"> - <o>Change uid and gid to</o> - <t></t> - </str> - - <str id="129"> - <o>When Roxen is run as root, to be able to open port 80 for listening, - change to this user-id and group-id when the port has been opened. If - you specify a symbolic username, the default group of that user will - be used. The syntax is user[:group]. - - A server restart is necessary for a change of this variable to take - effect. Note that it also can lead to file permission errors if the - Roxen process no longer can read files it previously has written, - although the start script fixes this for the standard file locations.</o> - <t></t> - </str> - - <str id="130"> - <o>Change uid and gid permanently</o> - <t></t> - </str> - - <str id="131"> - <o>If this variable is set, Roxen will set it's uid and gid permanently. This disables the 'exec script as user' features for CGI, and also 'access files as user' in the filesystems, but it gives better security.</o> - <t></t> - </str> - - <str id="132"> - <o>Module directories</o> - <t></t> - </str> - - <str id="133"> - <o>This is a list of directories where Roxen should look for modules. Can be relative paths, from the directory you started Roxen. The directories are searched in order for modules.</o> - <t></t> - </str> - - <str id="134"> - <o>Client supports regexps</o> - <t></t> - </str> - - <str id="135"> - <o>What do the different clients support? - The default information is normally fetched from the file server/etc/supports in your Roxen directory.</o> - <t></t> - </str> - - <str id="136"> - <o>Logging: Audit trail</o> - <t></t> - </str> - - <str id="137"> - <o>If Audit trail is set to Yes, all changes of uid will be logged in the Event log.</o> - <t></t> - </str> - - <str id="138"> - <o>Logging: Debug log method</o> - <t></t> - </str> - - <str id="139"> - <o>What method to use for the debug log, default is file, but syslog is also available. When using file, the output is really sent to stdout and stderr, but this is handled by the start script.</o> - <t></t> - </str> - - <str id="140"> - <o>Logging: Log PID</o> - <t></t> - </str> - - <str id="141"> - <o>If set, the PID will be included in the syslog.</o> - <t></t> - </str> - - <str id="142"> - <o>Logging: Log to system console</o> - <t></t> - </str> - - <str id="143"> - <o>If set and syslog is used, the error/debug message will be printed to the system console as well as to the system log.</o> - <t></t> - </str> - - <str id="144"> - <o>Logging: Syslog type</o> - <t></t> - </str> - - <str id="145"> - <o>When using SYSLOG, which log type should be used.</o> - <t></t> - </str> - - <str id="146"> - <o>Logging: Log what to syslog</o> - <t></t> - </str> - - <str id="147"> - <o>When syslog is used, how much should be sent to it? <hr />Fatal: Only messages about fatal errors Errors: Only error or fatal messages Warning: Warning messages as well Debug: Debug messager as well All: Everything </o> - <t></t> - </str> - - <str id="148"> - <o>Logging: Log as</o> - <t></t> - </str> - - <str id="149"> - <o>When syslog is used, this will be the identification of the Roxen daemon. The entered value will be appended to all logs.</o> - <t></t> - </str> - - <str id="150"> - <o>Number of threads to run</o> - <t></t> - </str> - - <str id="151"> - <o>The number of simultaneous threads Roxen will use. - Please note that even if this is one, Roxen will still be able to serve multiple requests, using a select loop based system. - This is quite useful if you have more than one CPU in your machine, or if you have a lot of slow NFS accesses.Do not increase this over 20 unless you have a very good reason to do so.</o> - <t></t> - </str> - - <str id="154"> - <o>Auto Restart: Enable Anti-Block-System</o> - <t></t> - </str> - - <str id="155"> - <o>If set, the anti-block-system will be enabled. This will restart the server after a configurable number of minutes if it locks up. If you are running in a single threaded environment heavy calculations will also halt the server. In multi-threaded mode bugs such as eternal loops will not cause the server to reboot, since only one thread is blocked. In general there is no harm in having this option enabled. </o> - <t></t> - </str> - - <str id="156"> - <o>Auto Restart: ABS Timeout</o> - <t></t> - </str> - - <str id="157"> - <o>If the server is unable to accept connection for this many minutes, it will be restarted. You need to find a balance: if set too low, the server will be restarted even if it's doing legal things (like generating many images), if set too high you might get a long downtime if the server for some reason locks up.</o> - <t></t> - </str> - - <str id="158"> - <o>Default language</o> - <t></t> - </str> - - <str id="159"> - <o>Locale, used to localize all messages in Roxen. Standard means using the default locale, which varies according to the value of the 'LANG' environment variable.</o> - <t></t> - </str> - - <str id="160"> - <o>Auto Restart: Enable Automatic Restart</o> - <t></t> - </str> - - <str id="161"> - <o>If set, Roxen will automatically restart after a configurable number of days. Since Roxen uses a monolith, non-forking server model the process tends to grow in size over time. This is mainly due to heap fragmentation but also because of memory leaks.</o> - <t></t> - </str> - - <str id="170"> - <o>Cache: Memory Cache Garbage Collect Interval</o> - <t></t> - </str> - - <str id="171"> - <o>The number of seconds between every garbage collect (removal of old content) from the memory cache. The memory cache is used for various tasks like remembering what supports flags matches what client.</o> - <t></t> - </str> - - <str id="172"> - <o>Commented config files</o> - <t></t> - </str> - - <str id="173"> - <o>Save the variable documentation strings as comments in the configuration files. Only useful if you read or edit the config files directly.</o> - <t></t> - </str> - - <str id="174"> - <o>Show documentation</o> - <t></t> - </str> - - <str id="175"> - <o>Show the variable documentation.</o> - <t></t> - </str> - - <str id="176"> - <o>Show advanced configuration options</o> - <t></t> - </str> - - <str id="177"> - <o>Show all possible configuration options, not only the ones that are most often changed.</o> - <t></t> - </str> - - <str id="180"> - <o>Show developer options and actions</o> - <t></t> - </str> - - <str id="181"> - <o>Show settings and actions that are not normaly useful for non-developer users. If you develop your own Roxen modules, this option is for you.</o> - <t></t> - </str> - - <str id="182"> - <o>Background color</o> - <t></t> - </str> - - <str id="183"> - <o>Administration interface background color.</o> - <t></t> - </str> - - <str id="184"> - <o>Text color</o> - <t></t> - </str> - - <str id="185"> - <o>Administration interface text color.</o> - <t></t> - </str> - - <str id="186"> - <o>Link color</o> - <t></t> - </str> - - <str id="187"> - <o>Font</o> - <t></t> - </str> - - <str id="188"> - <o>Administration interface font.</o> - <t></t> - </str> - - <str id="189"> - <o>Add/Delete module page type</o> - <t></t> - </str> - - <str id="191"> - <o>All Permissions</o> - <t></t> - </str> - + <str id="192"> <o>View Settings</o> <t></t>
1169: <t></t> </str> - <str id="274"> - <o>Cache:Cache size</o> - <t></t> - </str> - - <str id="275"> - <o>The size of the data cache used to speed up requests for commonly requested files, in KBytes</o> - <t></t> - </str> - - <str id="276"> - <o>Cache:Max file size</o> - <t></t> - </str> - - <str id="277"> - <o>The maximum size of a file that is to be considered for the cache</o> - <t></t> - </str> - - <str id="278"> - <o>Compact site list</o> - <t></t> - </str> - - <str id="279"> - <o>If true, the list of sites will be presented in a compact format suitable for servers with many sites.</o> - <t></t> - </str> - - <str id="280"> - <o>normal</o> - <t></t> - </str> - - <str id="282"> - <o>fast</o> - <t></t> - </str> - - <str id="284"> - <o>faster</o> - <t></t> - </str> - - <str id="286"> - <o>compact</o> - <t></t> - </str> - - <str id="288"> - <o>really compact</o> - <t></t> - </str> - + <str id="290"> <o>Module event log for '%s' cleared by %s (%s) from %s</o> <t></t>
1284: <t></t> </str> - <str id="229"> - <o>Page charset</o> - <t></t> - </str> - - <str id="230"> - <o>The charset to use when rendering configuration interface pages.</o> - <t></t> - </str> - + <str id="234"> <o>Requests</o> <t></t>
1304: <t></t> </str> - <str id="236"> - <o>Default variable sort order</o> - <t></t> - </str> - - <str id="237"> - <o>The default order variables are sorted in</o> - <t></t> - </str> - - <str id="238"> - <o>alphabetical</o> - <t></t> - </str> - - <str id="239"> - <o>as defined</o> - <t></t> - </str> - - <str id="240"> - <o>alphabetical, changed first</o> - <t></t> - </str> - - <str id="241"> - <o>as defined, changed first</o> - <t></t> - </str> - - <str id="242"> - <o>Changed variables are highlighted</o> - <t></t> - </str> - - <str id="243"> - <o>How to highlight variables that does not have their default value</o> - <t></t> - </str> - - <str id="244"> - <o>Not at all</o> - <t></t> - </str> - - <str id="268"> - <o>Different background color</o> - <t></t> - </str> - - <str id="302"> - <o>Add a header</o> - <t></t> - </str> - - <str id="303"> - <o>Group Tasks</o> - <t></t> - </str> - - <str id="304"> - <o>If true, tasks are grouped acording to type, otherwise all tasks will be listed on one page</o> - <t></t> - </str> - - <str id="305"> - <o>The modules security level is used to determine if a request should be handled by the module. - <h2>Security level vs Trust level</h2> Each module has a configurable security level. Each request has an assigned trust level. Higher trust levels grants access to modules with higher security levels. - <h2>Definitions</h2><ul> <li>A requests initial Trust level is infinitely high.</li> <li> A request will only be handled by a module if its trust level is higher or equal to the security level of the module.</li> <li> Each time the request is handled by a module the trust level of the module will be set to the lower of its trust level and the modules security level, unless the security level of the module is 0, which is a special case and means that no change should be made.</li> </ul> - <h2>Example</h2> Modules:<ul> <li> User filesystem, security level 1</li> <li> Filesystem module, security level 3</li> <li> CGI module, security level 2</li> </ul> - A request handled by "User filesystem" is assigned a trust level of one after the security level of that module. That request can then not be handled by the "CGI module" since that module has a higher security level than the requests trust level. - On the other hand, a request handled by the the "Filsystem module" could later be handled by the "CGI module".</o> - <t></t> - </str> - - <str id="306"> - <o>Site</o> - <t></t> - </str> - - <str id="307"> - <o>No such file message override files</o> - <t></t> - </str> - - <str id="308"> - <o>If no file match a given resource all directories above the wanted file is searched for one of the files in this list. - As an example, if the file /foo/bar/not_there.html is wanted, and this list contains the default value of 404.inc, these files will be searched for, in this order: /foo/bar/404.inc, /foo/404.inc and /404.inc.</o> - <t></t> - </str> - - <str id="309"> - <o>Require user with the 'hilfe' permission</o> - <t></t> - </str> - - <str id="310"> - <o>If yes, require a user with the hilfe permission set, otherwise, any configuration interface user will work, even one with only the view settings permission</o> - <t></t> - </str> - + <str id="311"> <o>Site event log for '%s' cleared by %s (%s) from %s</o> <t></t> </str> - <str id="312"> - <o>Could not interpret the date</o> - <t></t> - </str> - + <str id="313"> <o>An email address must contain "@".</o> <t></t>
1545: <t></t> </str> - <str id="349"> - <o>Update Client</o> - <t></t> - </str> - - <str id="350"> - <o>Load of %s (%s) failed</o> - <t></t> - </str> - - <str id="351"> - <o>The module %s (%s) could not be loaded.</o> - <t></t> - </str> - - <str id="352"> - <o>Found trailing data after the date. </o> - <t></t> - </str> - - <str id="353"> - <o>Month must be at least 1. </o> - <t></t> - </str> - - <str id="354"> - <o>Month must be 12 or less. </o> - <t></t> - </str> - - <str id="355"> - <o>Day must be at least 1.</o> - <t></t> - </str> - - <str id="356"> - <o>%s does not appear to be a valid date.</o> - <t></t> - </str> - - <str id="357"> - <o>Day must be %d or less.</o> - <t></t> - </str> - - <str id="5"> - <o>Interface language</o> - <t></t> - </str> - - <str id="19"> - <o>Select the Administration interface language.</o> - <t></t> - </str> - + <str id="152"> <o>%O is not an integer</o> <t></t> </str> - <str id="153"> - <o><dl> - <dt>normal</dt><dd>Show module name and documentation with images.</dd> - <dt>fast</dt><dd>Like normal, but no type images.</dd> - <dt>faster</dt><dd>Like normal, but allows selecting multiple modules at once.</dd> - <dt>compact</dt><dd>Only show the names of modules, and allow addition/deletion of multiple modules at once.</dd> - <dt>really compact</dt><dd>Like compact, but no module classes.</dd> - </dl></o> - <t></t> - </str> - + <str id="222"> <o>Create new user</o> <t></t>
1671: <t></t> </str> - <str id="195"> - <o>Community articles</o> - <t></t> - </str> - - <str id="231"> - <o>Most recently published community articles</o> - <t></t> - </str> - + <str id="232"> <o>Crunch activity</o> <t></t>
1691: <t></t> </str> - <str id="263"> - <o>News from www.roxen.com</o> - <t></t> - </str> - - <str id="281"> - <o>The news headlines from www.roxen.com</o> - <t></t> - </str> - - <str id="283"> - <o>Unknown box %s</o> - <t></t> - </str> - - <str id="285"> - <o>Large Content Boxes</o> - <t></t> - </str> - - <str id="287"> - <o>Content boxes on the Startpage</o> - <t></t> - </str> - - <str id="289"> - <o>Small Content Boxes</o> - <t></t> - </str> - - <str id="327"> - <o>Theme</o> - <t></t> - </str> - - <str id="343"> - <o>The theme to use</o> - <t></t> - </str> - + <str id="358"> <o>Changed</o> <t></t>
1801: <t></t> </str> - <str id="8"> - <o>Server secret</o> - <t></t> - </str> - - <str id="9"> - <o>The server secret is a string used in some cryptographic functions, such as calculating unique, non-guessable session id's. Change this value into something that is hard to guess, unless you are satisfied with what your computers random generator has produced</o> - <t></t> - </str> - + <str id="164"> <o>Databases</o> <t></t>
1836: <t></t> </str> - <str id="167"> - <o>Form font size</o> - <t></t> - </str> - - <str id="178"> - <o>The fontsize of the variables in the configuration interface</o> - <t></t> - </str> - - <str id="179"> - <o>Documentation font size</o> - <t></t> - </str> - - <str id="193"> - <o>The fontsize of the documentation in the configuration interface</o> - <t></t> - </str> - - <str id="205"> - <o>Minimum allowed bitrate</o> - <t></t> - </str> - - <str id="215"> - <o>The minimum allowed bitrate, in bits/second. If the client is slower than this set bitrate, it will be disconnected (after a timeout). Setting this higher than 14000 is not recommended if you have modem users.</o> - <t></t> - </str> - + <str id="233"> <o>bytecode data</o> <t></t>
1921: <t></t> </str> - <str id="245"> - <o>The syntax is: - - <dl> <dt>userdb userdatabase module</dt> - <dd> Select a non-default userdatabase module. The default is to search all modules. The userdatabase module config_userdb is always present, and contains the configuration users</dd> - <dt>authmethod authentication module</dt> - <dd>Select a non-default authentication method.</dd><dt>realm realm name</dt> - <dd>The realm is used when user authentication info is requested</dd></dl> - Below, CMD is one of 'allow' and 'deny' - <dl> - <dt>CMD ip=ip/bits [return] - CMD ip=ip:mask [return] - CMD ip=pattern[,pattern,...] [return] </dt> - <dd>Match the remote IP-address.</dd> - - <dt>CMD user=name[,name,...] [return]</dt> - <dd>Requires a authenticated user. If the user name 'any' is used, any valid user will be OK. Otherwise, one of the listed users are required.</dd> <dt>CMD group=name[,name,...] [return]</dt> - <dd>Requires a authenticated user with a group. If the group name 'any' is used, any valid group will be OK. Otherwise, one of the listed groups are required.</dd> - - <dt>CMD dns=pattern[,pattern,...] [return]</dt> - <dd>Require one of the specified DNS domain-names</dd> - <dt>CMD time=HH:mm-HH:mm [return]</dt> - <dd>Only allow access to the module from the first time to the second each day. Both times should be specified in 24-hour HH:mm format.</dd> - <dt>CMD day=day[,day,...] [return]</dt> - <dd>Only allow access during certain days. Day is either a numerical value (monday=1, sunday=7) or a string (monday, thuesday etc)</dd></dl> - pattern is always a glob pattern (* = any characters, ? = any character). - - return means that reaching this command results in immediate - return, only useful for 'allow'. - - 'deny' always implies a return, no futher testing is done if a - 'deny' match. - </o> - <t></t> - </str> - - <str id="246"> - <o>Compatibility level</o> - <t></t> - </str> - - <str id="257"> - <o>Passive port minimum</o> - <t></t> - </str> - - <str id="320"> - <o>Minimum port number to use in the PASV/EPSV response.</o> - <t></t> - </str> - - <str id="321"> - <o>Passive port maximum</o> - <t></t> - </str> - - <str id="322"> - <o>Maximum port number to use in the PASV/EPSV response.</o> - <t></t> - </str> - + <str id="323"> <o>Shared with </o> <t></t> </str> - <str id="14"> - <o>Module list mode</o> - <t></t> - </str> - - <str id="15"> - <o>The module list mode. One of <dl><dt>Folded</dt><dd>Modules in the same group are folded</dd><dt>UnFolded</dt><dd>Like the 'old' Roxen 2.1 list</dd><dt>JavaScript Popup</dt><dd>Like Folded, but when you move the mouse over a folded group, a menu with the folded modules will popup</dd></dl></o> - <t></t> - </str> - - <str id="17"> - <o>Folded with javascript popup</o> - <t></t> - </str> - - <str id="122"> - <o>Folded</o> - <t></t> - </str> - - <str id="123"> - <o>Unfolded (old style)</o> - <t></t> - </str> - + <str id="219"> <o>Authentication method</o> <t></t>
2032: <t></t> </str> - <str id="384"> - <o>Warning: The theme %s no longer exists, using default. - </o> - <t></t> - </str> - - <str id="385"> - <o>Reload failed</o> - <t></t> - </str> - - <str id="386"> - <o>The compatibility level is used by different modules to select the right behavior to remain compatible with earlier Roxen versions. When a server configuration is created, this variable is set to the latest version. After that it's never changed automatically, thereby ensuring that server configurations migrated from earlier Roxen versions is kept at the right compatibility level. - - This variable may be changed manually, but it's advisable to test the site carefully afterwards. A reload of the whole server configuration is required to propagate the change properly to all modules.</o> - <t></t> - </str> - - <str id="387"> - <o>Auto Restart: Schedule</o> - <t></t> - </str> - - <str id="388"> - <o>Automatically restart the server according to this schedule.</o> - <t></t> - </str> - - <str id="999"> - <o>SNMP: Enable SNMP agent</o> - <t></t> - </str> - + <str id="389"> <o>Fetching data from %s...</o> <t></t> </str> - <str id="390"> - <o>Release notes</o> - <t></t> - </str> - + <str id="391"> <o>Web Site Creator</o> <t></t>
2120: <t></t> </str> - <str id="400"> - <o>Update</o> - <t></t> - </str> - + <str id="401"> <o>Copy or move database</o> <t></t>
2240: </str> <str id="424"> - <o>The database %s was deleted by b%s</o> + <o>The database %s was deleted by %s</o> <t></t> </str>
2681: <t></t> </str> - <str id="85"> - <o>Default module tab</o> - <t></t> - </str> - - <str id="162"> - <o>The tab that will be selected by default when you select a module.</o> - <t></t> - </str> - - <str id="163"> - <o>Enable replication system</o> - <t></t> - </str> - - <str id="337"> - <o>If enabled, Roxen will enable various replication systems needed to set up multiple frontend systems. You will need a database named 'replicate' that recides in a shared mysql server for this to work. Also, all servers has to have this flag set. Roxen must be restarted before changes to this variable takes effect </o> - <t></t> - </str> - + <str id="361"> <o>Are you sure you want to delete the database %s and the data?</o> <t></t>
2756: <t></t> </str> - <str id="373"> - <o>Bind to these URLs. You can use '*' and '?' to perform globbing (using any of these will default to binding to all IP-numbers on your machine). If you specify a IP# in the field it will take precedence over the hostname.</o> - <t></t> - </str> - + <str id="508"> <o>Ports</o> <t></t>
2775: <o>Bind this port: </o> <t></t> </str> + + <str id="1000"> + <o>Content Editor (Instant Edition)</o> + <t></t> + </str> + + <str id="1001"> + <o>Content Editor (Advanced Edition)</o> + <t></t> + </str> + + <str id="1002"> + <o>Web Developer</o> + <t></t> + </str> + + <str id="1003"> + <o>System Developer</o> + <t></t> + </str> + + <str id="1004"> + <o>Administrator</o> + <t></t> + </str> + + <str id="1005"> + <o>Forms And Response Module</o> + <t></t> + </str> + + <str id="1006"> + <o>Categorization Module</o> + <t></t> + </str> + + <str id="1007"> + <o>Tutorials</o> + <t></t> + </str> + + <str id="1008"> + <o>Refresh</o> + <t></t> + </str>

Roxen.git/ server/ translations/ eng/ roxen_config.xml

2002-06-13

2002-06-13 22:54:23 by Martin Nilsson <mani@lysator.liu.se>