mirror of git://git.gnupg.org/gnupg.git
dc107b7850
* README, agent/command.c, agent/keyformat.txt, common/i18n.c,
common/iobuf.c, common/keyserver.h, dirmngr/cdblib.c,
dirmngr/ldap-wrapper.c, doc/DETAILS, doc/TRANSLATE,
doc/announce-2.1.txt, doc/gpg.texi, doc/gpgsm.texi,
doc/scdaemon.texi, doc/tools.texi, doc/whats-new-in-2.1.txt,
g10/export.c, g10/getkey.c, g10/import.c, g10/keyedit.c, m4/ksba.m4,
m4/libgcrypt.m4, m4/ntbtls.m4, po/ca.po, po/cs.po, po/da.po,
po/de.po, po/el.po, po/eo.po, po/es.po, po/et.po, po/fi.po,
po/fr.po, po/gl.po, po/hu.po, po/id.po, po/it.po, po/ja.po,
po/nb.po, po/pl.po, po/pt.po, po/ro.po, po/ru.po, po/sk.po,
po/sv.po, po/tr.po, po/uk.po, po/zh_CN.po, po/zh_TW.po,
scd/app-p15.c, scd/ccid-driver.c, scd/command.c, sm/gpgsm.c,
sm/sign.c, tools/gpgconf-comp.c, tools/gpgtar.h: replace "Allow to"
with clearer text.
In standard English, the normal construction is "${XXX} allows ${YYY}
to" -- that is, the subject (${XXX}) of the sentence is allowing the
object (${YYY}) to do something. When the object is missing, the
phrasing sounds awkward, even if the object is implied by context.
There's almost always a better construction that isn't as awkward.
These changes should make the language a bit clearer.
Signed-off-by: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
|
||
|---|---|---|
| .. | ||
| .gitattributes | ||
| ChangeLog-2011 | ||
| LINGUAS | ||
| Makefile.in.in | ||
| Makevars | ||
| Makevars.template | ||
| POTFILES.in | ||
| Rules-quot | ||
| boldquot.sed | ||
| ca.po | ||
| cs.po | ||
| da.po | ||
| de.po | ||
| el.po | ||
| en@boldquot.header | ||
| en@quot.header | ||
| eo.po | ||
| es.po | ||
| et.po | ||
| fi.po | ||
| fr.po | ||
| gl.po | ||
| hu.po | ||
| id.po | ||
| insert-header.sin | ||
| it.po | ||
| ja.po | ||
| nb.po | ||
| pl.po | ||
| pt.po | ||
| quot.sed | ||
| remove-potcdate.sin | ||
| ro.po | ||
| ru.po | ||
| sk.po | ||
| sv.po | ||
| tr.po | ||
| uk.po | ||
| zh_CN.po | ||
| zh_TW.po | ||