Branch: Tag:

2000-09-19

2000-09-19 13:24:04 by Andreas Lange <andreas@lange.cx>

Strings now coherent with the source, various updates and some added translations

Rev: server/translations/ces/admin_tasks.xml:1.3
Rev: server/translations/ces/roxen_config.xml:1.6
Rev: server/translations/deu/admin_tasks.xml:1.2
Rev: server/translations/deu/roxen_config.xml:1.3
Rev: server/translations/eng/admin_tasks.xml:1.2
Rev: server/translations/eng/roxen_config.xml:1.6
Rev: server/translations/eng/roxen_message.xml:1.5
Rev: server/translations/eng/roxen_start.xml:1.6
Rev: server/translations/hun/admin_tasks.xml:1.2
Rev: server/translations/hun/roxen_config.xml:1.3
Rev: server/translations/jpn/admin_tasks.xml:1.2
Rev: server/translations/jpn/roxen_config.xml:1.3
Rev: server/translations/nld/admin_tasks.xml:1.2
Rev: server/translations/nld/roxen_config.xml:1.6
Rev: server/translations/swe/admin_tasks.xml:1.2
Rev: server/translations/swe/roxen_config.xml:1.9
Rev: server/translations/swe/roxen_message.xml:1.4
Rev: server/translations/swe/roxen_start.xml:1.6

2:   <locale version="1.0"/>   <project>roxen_config</project>   <language>eng</language> - <dumped>968472146</dumped> + <dumped>969369615</dumped>   <file>../base_server/configuration.pike</file> -  + <file>../base_server/config_userdb.pike</file>   <file>../base_server/global_variables.pike</file>   <file>../etc/modules/Variable.pmod/module.pmod</file>   <file>../modules/configuration/config_tags.pike</file>   <file>../modules/configuration/config_userdb.pike</file>   <file>../modules/configuration/config_filesystem.pike</file> - <file>../config_interface/standard/template</file> + <file>../config_interface/standard/cv_startpage_tabs.pike</file>   <file>../config_interface/standard/logutil.pike</file>   <file>../config_interface/standard/statusinfo.pike</file> -  + <file>../config_interface/standard/template</file>   <file>../config_interface/standard/topmenu.pike</file> - <file>../config_interface/standard/cv_startpage_tabs.pike</file> +    <file>../config_interface/standard/users.html</file> - <file>../config_interface/standard/user_form.pike</file> +    <file>../config_interface/standard/user_delete.pike</file> -  + <file>../config_interface/standard/user_form.pike</file>   <file>../config_interface/standard/actions/index.html</file> -  + <file>../config_interface/standard/event_log/clear_log.pike</file>   <file>../config_interface/standard/event_log/index.html</file>   <file>../config_interface/standard/event_log/log.pike</file> - <file>../config_interface/standard/event_log/clear_log.pike</file> + <file>../config_interface/standard/sites/add_module.pike</file> + <file>../config_interface/standard/sites/config_left_item.pike</file> + <file>../config_interface/standard/sites/create_site.pike</file> + <file>../config_interface/standard/sites/drop_module.pike</file> + <file>../config_interface/standard/sites/drop_site.html</file> + <file>../config_interface/standard/sites/drop_site.pike</file>   <file>../config_interface/standard/sites/index.html</file>   <file>../config_interface/standard/sites/log.pike</file> -  + <file>../config_interface/standard/sites/new_site.html</file>   <file>../config_interface/standard/sites/site_content.pike</file>   <file>../config_interface/standard/sites/site_header.pike</file> - <file>../config_interface/standard/sites/new_site.html</file> - <file>../config_interface/standard/sites/create_site.pike</file> - <file>../config_interface/standard/sites/drop_site.pike</file> - <file>../config_interface/standard/sites/drop_site.html</file> - <file>../config_interface/standard/sites/add_module.pike</file> - <file>../config_interface/standard/sites/drop_module.pike</file> - <file>../config_interface/standard/sites/config_left_item.pike</file> +    <file>../config_interface/standard/sites/site_templates/common.pike</file>      
82:   </str>      <str id="11"> - <o>Reloaded %s. - </o> + <o>Reloaded %s.</o>   <t></t>   </str>   
143:   </str>      <str id="22"> - <o>Virtual server comment</o> + <o>Site comment</o>   <t></t>   </str>   
153:   </str>      <str id="24"> - <o>Virtual server name</o> + <o>Site name</o>   <t></t>   </str>      <str id="25"> - <o>This is the name that will be used in the configuration interface. If this is left empty, the actual name of the virtual server will be used.</o> + <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>   
245:   </str>      <str id="35"> - <o>The domainname of the server. The domainname is used to generate default URLs, and to generate email addresses.</o> + <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>   
285:   </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 Virtual Server.&lt;br /&gt;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> + <o>If set, per-server bandwidth throttling will be enabled. It will allow you to limit the total available bandwidth for this site.&lt;br /&gt;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>   
295:   </str>      <str id="45"> - <o>This is the average bandwidth available to this Virtual Server in bytes/sec (the bucket "fill rate").</o> + <o>This is the average bandwidth available to this site in bytes/sec (the bucket "fill rate").</o>   <t></t>   </str>   
525:   </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. &lt;p&gt;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 continue being correct.</o> + <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. &lt;p&gt;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>   
555:   </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 virtual server.</o> + <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>   
696:   </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.&lt;br /&gt;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 draft 03:&lt;p&gt;&lt;blockquote&gt;&lt;i&gt;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.&lt;/i&gt;&lt;/blockquote&gt;&lt;/p&gt;</o> + <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.&lt;br /&gt;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:&lt;p&gt;&lt;blockquote&gt;&lt;i&gt;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.&lt;/i&gt;&lt;/blockquote&gt;&lt;/p&gt;</o>   <t></t>   </str>   
716:   </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].</o> + <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].</o>   <t></t>   </str>   
726:   </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' fetures for CGI, and also access files as user in the filesystems, but it gives better security.</o> + <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>   
762:   </str>      <str id="138"> - <o>Logging: Logging method</o> + <o>Logging: Debug log method</o>   <t></t>   </str>      <str id="139"> - <o>What method to use for logging, 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> + <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>   
869:   </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> + <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>   
1260:   </str>      <str id="255"> - <o>Disabling old configuration %s - </o> + <o>Disabling old configuration %s</o>   <t></t>   </str>   
1316:   </str>      <str id="dt"> - <o>Administrator logged on as %s from %s. - </o> + <o>Administrator logged on as %s from %s.</o>   <t></t>   </str>   
1545:   <o>Initial variables for the site</o>   <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="231"> + <o>Preferred language</o> + <t></t> + </str> +  + <str id="232"> + <o>Which one of the completed translations of the administration interface to use.</o> + <t></t> + </str> +  + <str id="233"> + <o>Failed login attempt %s from %s</o> + <t></t> + </str> +  + <str id="234"> + <o>Requests:</o> + <t></t> + </str> +  + <str id="235"> + <o>Are you sure you want to disable the site %s?</o> + <t></t> + </str>