Provide some linguistic guidance for the documentation.
This will hopefully avoid questions over which spelling and grammar should be used. Translators are of course free to create localizations for specific English dialects. Signed-off-by: Marc Branchaud <marcnarc@xiplink.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:
committed by
Junio C Hamano
parent
8dc84fdc48
commit
42e0fae98e
@ -242,6 +242,14 @@ Writing Documentation:
|
||||
processed into HTML and manpages (e.g. git.html and git.1 in the
|
||||
same directory).
|
||||
|
||||
The documentation liberally mixes US and UK English (en_US/UK)
|
||||
norms for spelling and grammar, which is somewhat unfortunate.
|
||||
In an ideal world, it would have been better if it consistently
|
||||
used only one and not the other, and we would have picked en_US
|
||||
(if you wish to correct the English of some of the existing
|
||||
documentation, please see the documentation-related advice in the
|
||||
Documentation/SubmittingPatches file).
|
||||
|
||||
Every user-visible change should be reflected in the documentation.
|
||||
The same general rule as for code applies -- imitate the existing
|
||||
conventions. A few commented examples follow to provide reference
|
||||
|
||||
Reference in New Issue
Block a user