Re: [LCFC2] templates://typo3-dummy/{typo3-dummy.templates}
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Le 13/06/2010 11:09, David Prévot a écrit :
> Hi,
I forgot to include typo3-dummy maintainers in my previous mail, and
have another remark: I also thought that the "shorter" word in "shorter
URLs with TYPO3 as part of the domain name" isn't really true (one can
use, as it is proposed in the second example, to install TYPO3 in a
directory like "cms" (and "/cms" is only four symbols long while
"typo3." is two symbols longer), but I fail to find a suitable wording
("nicer" is really subjective), maybe something more neutral like "URLs
in a subdomain" would be more accurate?
> Le 13/06/2010 05:51, Christian PERRIER a écrit :
>> This is the last call for comments for the review of debconf
>> templates for typo3-dummy.
>
> Some propositions:
>
> - The typo3-dummy package has included the TYPO3 configuration into
> - the apache2 configuration and activated the rewrite module. In order
> + TYPO3 has been included into the apache2 configuration and
> + the rewrite module has been activated. In order
>
> Rationale: avoid the useless mention of "typo3-dummy package", and get
> rid of one of the two "configuration" word (actually, the first one is
> not really correct, since it really is Apache 2 that is configured at
> this stage, in order to make TYPO3 work, but TYPO3 configuration files
> must be elsewhere, as /etc/typo3/). On the other hand, the two phrases
> "has been [...]ed" doesn't sound really great, maybe it could be better
> to find other wordings.
>
> - contents into one of the new .conf files.
> + contents into one of the new configuration files
>
> Rationale: make it clear that we are talking about configuration files
> (even default configuration files created by Apache 2 in
> /etc/apache2/sites-available/ directory doesn't use .conf extension).
>
> Cheers
>
> David
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAkwU994ACgkQ18/WetbTC/p+eQCeOMWa3vSTvQKMdQ9rlVdmI89V
oV0AnizEOEvQhIFjI4zKYLDy3JBsEMYo
=ZlPU
-----END PGP SIGNATURE-----
Reply to: