> You'd better write: > > If you choose /var/www, which is Apache's default document root, all > files hosted in that directory MAY become publicly accessible. It is > therefore recommended to change your apache main DocumentRoot > configured in /etc/apache/httpd.conf or /etc/apache2/apache.conf > after the setup of DTC of you choose /var/www here.
OK. New attempt: Template: dtc/conf_hostingpath Type: string Default: /var/www/sites _Description: Path for hosted domains: Please enter the directory to be used by DTC to store files for all hosted domains. . If you choose /var/www, which is Apache's default document root, all files hosted in that directory may become publicly accessible. It is therefore recommended to change the DocumentRoot setting in Apache configuration if you choose /var/www as path for hosted domains. > > Template: dtc/conf_use_nated_vhosts > > Type: boolean > > Default: false > > _Description: Use "NATed" vhosts? > > DTC can configure Apache to use one of your IP addresses. If the > > server is firewalled with NAT and port redirections of public IP(s) > > address(es), a "NATed" vhost configuration can be generated. > > . > > This option should be chosen only if the server is directly connected > > to the Internet and uses a dynamic public IP addres. In such cases, > > NAT and port forwarding are mandatory for DTC. > > No, this is not right! This option should NOT be choosen if the server > is connected directly to the internet. So I would rather write this: All this clearly shows that the whole thing is everythign but clear, I'm afraid..:-| New proposal: Template: dtc/conf_use_nated_vhosts Type: boolean Default: false _Description: Use "NATed" vhosts? DTC can configure Apache to use one of your IP addresses. If the server is firewalled with NAT and port redirections of public IP(s) address(es), a "NATed" vhost configuration can be generated. . This option should be chosen only if the server is not connected to the Internet directly, but through a firewall doing network address translation (NAT). If the server uses a dynamic public IP address, NAT and port forwarding are mandatory for DTC. > I can't wait to have this new template ready, as I have corrected bugs > in the current version in SID, and that I want to have it uploaded asap > to remove them. > > Last thing, before you send this new english template so it can be > translated, I'll rewrap it to 80 cols as my sponsor seems to insist on > this (which I also think is not a bad thing). I also think translators > should be warned to take care of this (little) issue. That is incorrect. There is not technical point in rewrapping debconf templates to 80 cols. The formatting of the original templates file is irrelevant to what will be displayed to users. Rewrapping to 80 cols is only relevant to improve the readability of the debconf templates when doing what we're doing right now. The formatting of PO files is of no importance for the result as well. Here also, using some reasonable wrapping is recommended but not mandatory. My usual recommendation with PO files is using msgcat on them. I also recommend maintainers to check the PO files: msgcat fr.po >fr2.po msgfmt -o /dev/null --statistics --check fr.po So, there is no need to give special warning to translators and I usually recommend maintainers to never ever touch translator's files...except when they really know what they're doing..:)
signature.asc
Description: Digital signature
