Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 07 Nov 2006 19:51:36 +0100
From:      =?ISO-8859-1?Q?G=E1bor_K=F6vesd=E1n?= <gabor@FreeBSD.org>
To:        Marc Fonvieille <blackend@FreeBSD.org>
Cc:        Daniel Gerzo <danger@FreeBSD.org>, doc-committers@FreeBSD.org, cvs-doc@FreeBSD.org, cvs-all@FreeBSD.org
Subject:   Re: cvs commit: www/en about.sgml
Message-ID:  <4550D5B8.1020601@FreeBSD.org>
In-Reply-To: <20061107182634.GA90308@abigail.blackend.org>
References:  <200611071654.kA7GsWbj097708@repoman.freebsd.org> <20061107182634.GA90308@abigail.blackend.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Marc Fonvieille wrote:
> On Tue, Nov 07, 2006 at 04:54:31PM +0000, Daniel Gerzo wrote:
>   
>> danger      2006-11-07 16:54:31 UTC
>>
>>   FreeBSD doc repository
>>
>>   Modified files:
>>     en                   about.sgml 
>>   Log:
>>   - improve grammar
>>   - double space after full stop
>>     
>> [...]
> On another hand I don't see the benefit of
> adding a space after a full stop (to get a double space) in one sentence
> of a file containing many of this "issue"; till now we never (or
> hardly?) "corrected" a such thing.
>
> Marc
>
>   
Such changes are controversial, but personally I find them good. As for 
entity changes, like using &base; instead of ../.. or such, I can say 
the entities are better for translators. I can easily notice what is 
linked from my translated pages and what is from the English ones with 
&enbase;. As for the double spaces, they are also useful when updating 
translated webpages. I can easily count which sentence has been changed 
and can easily find the equivalent. And as for the indentation, I 
consider it good in general to have systematic files, that look the same 
and follow the same guidelines. It is just easier to work with such stuff.

-- 
Cheers,

Gabor




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4550D5B8.1020601>