[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Review courier-base templates

On 28 Jan 2004 06:13:37 +0200
era+debian@iki.fi wrote:

> On Tue, 27 Jan 2004 23:50:19 +0100, Stefan Hornburg <deblists@linuxia.de>
> posted to debian-l10n-english:
>  > era+debian@iki.fi wrote:
>  >> To control and administer the Courier configuration through the
>  >> web-based administration frontend provided by the courier-webadmin
>  >> package, the directory and files need to be readable and writable by
>  >> the user ${courieruser}.
>  > That is better. I used "the directories" because there are subdirectories
>  > below /etc/courier.
> Oh, sure. I was going to ask about that but I forgot.
>  > _Description: Path to user's Maildir directory
>  >  This is a relative path name from each user's home directory to the
>  >  Maildir directory where the Courier servers store and access the
>  >  user's email. Please read the maildir(5) manual page if you are
>  >  unacquainted with Maildir's.
> I'd use "unfamiliar" instead of "unacquainted". 

I agree that unfamiliar is the better term :-)

> Also "Maildir's" is
> weird; the apostrophe is certainly wrong, and I would probably use
> lowercase too. But how about just rewriting it a bit:
>  Please refer to the maildir(5) manual page if you are unfamiliar with
>  the mail storage format used by Courier.

Applied, thanks again.

> Incidentally, packages.debian.org only returns one match when I search
> for maildir.5.gz -- in manpages-pl. I would have expected clashes.

There is a maildir(5) manual page in courier-base, but it is handled
by alternatives, so you didn't find it with your search. manpages-pl
uses a subdirectory, so it wouldn't clash.

> <http://packages.debian.org/cgi-bin/search_contents.pl?word=maildir.5.gz>
>  > Yes, indeed. Thank you very much for your help.
> You're most welcome.

:-) See you


LinuXia Systems => http://www.linuxia.de/
Expert Interchange Consulting and System Administration
ICDEVGROUP => http://www.icdevgroup.org/
Interchange Development Team

Reply to: