mirror of
https://github.com/python/cpython.git
synced 2025-07-24 19:54:21 +00:00
For \kbd, be more prescriptive regarding how keystrokes should be
written.
This commit is contained in:
parent
e38b2f1f00
commit
07178d237a
1 changed files with 7 additions and 2 deletions
|
@ -787,8 +787,13 @@ This \UNIX\ is also followed by a space.
|
||||||
\begin{macrodesc}{kbd}{\p{key sequence}}
|
\begin{macrodesc}{kbd}{\p{key sequence}}
|
||||||
Mark a sequence of keystrokes. What form \var{key sequence}
|
Mark a sequence of keystrokes. What form \var{key sequence}
|
||||||
takes may depend on platform- or application-specific
|
takes may depend on platform- or application-specific
|
||||||
conventions. For example, an \program{xemacs} key sequence
|
conventions. When there are no relevant conventions, the names
|
||||||
may be marked like \code{\e kbd\{C-x C-f\}}.
|
of modifier keys should be spelled out, to improve accessibility
|
||||||
|
for new users and non-native speakers. For example, an
|
||||||
|
\program{xemacs} key sequence may be marked like
|
||||||
|
\code{\e kbd\{C-x C-f\}}, but without reference to a specific
|
||||||
|
application or platform, the same sequence should be marked as
|
||||||
|
\code{\e kbd\{Control-x Control-f\}}.
|
||||||
\end{macrodesc}
|
\end{macrodesc}
|
||||||
|
|
||||||
\begin{macrodesc}{keyword}{\p{name}}
|
\begin{macrodesc}{keyword}{\p{name}}
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue