fdo-mirrors/xorg-libx11
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/xorg/lib/libx11.git synced 2026-05-05 04:08:15 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions

fix ``fake quotes'' in text

Browse source 
to remove the fake quotes replace them with propper
predefined macros \*(lq and \*(rq. this will allow
nroff to choose the propper characters when using ps etc.

Signed-off-by: Walter Harms <wharms@bfs.de>
This commit is contained in:
Walter Harms 2019-07-29 18:50:19 +02:00
parent 705027ea9b
commit ef31143c9d
16 changed files with 50 additions and 50 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
man/XButtonEvent.man
View file

@ -64,7 +64,7 @@ typedef struct {
unsigned long serial; /\&* # of last request processed by server */
Bool send_event; /\&* true if this came from a SendEvent request */
Display *display; /\&* Display the event was read from */
Window window; /\&* ``event'' window it is reported relative to */
Window window; /\&* \*(lqevent\*(rq window it is reported relative to */
Window root; /\&* root window that the event occurred on */
Window subwindow; /\&* child window */
Time time; /\&* milliseconds */
@ -84,7 +84,7 @@ typedef struct {
unsigned long serial; /\&* # of last request processed by server */
Bool send_event; /\&* true if this came from a SendEvent request */
Display *display; /\&* Display the event was read from */
Window window; /\&* ``event'' window it is reported relative to */
Window window; /\&* \*(lqevent\*(rq window it is reported relative to */
Window root; /\&* root window that the event occurred on */
Window subwindow; /\&* child window */
Time time; /\&* milliseconds */
@ -104,7 +104,7 @@ typedef struct {
unsigned long serial; /\&* # of last request processed by server */
Bool send_event; /\&* true if this came from a SendEvent request */
Display *display; /\&* Display the event was read from */
Window window; /\&* ``event'' window reported relative to */
Window window; /\&* \*(lqevent\*(rq window reported relative to */
Window root; /\&* root window that the event occurred on */
Window subwindow; /\&* child window */
Time time; /\&* milliseconds */

2
man/XCrossingEvent.man
View file

@ -61,7 +61,7 @@ typedef struct {
unsigned long serial; /\&* # of last request processed by server */
Bool send_event; /\&* true if this came from a SendEvent request */
Display *display; /\&* Display the event was read from */
Window window; /\&* ``event'' window reported relative to */
Window window; /\&* \*(lqevent\*(rq window reported relative to */
Window root; /\&* root window that the event occurred on */
Window subwindow; /\&* child window */
Time time; /\&* milliseconds */

2
man/XInternAtom.man
View file

@ -94,7 +94,7 @@ can return
If the atom name is not in the Host Portable Character Encoding,
the result is implementation-dependent.
Uppercase and lowercase matter;
the strings ``thing'', ``Thing'', and ``thinG''
the strings \*(lqthing\*(rq, ``Thing'', and ``thinG''
all designate different atoms.
The atom will remain defined even after the client's connection closes.
It will become undefined only when the last connection to

6
man/XLoadFont.man
View file

@ -100,11 +100,11 @@ function loads the specified font and returns its associated font ID.
If the font name is not in the Host Portable Character Encoding,
the result is implementation-dependent.
Use of uppercase or lowercase does not matter.
When the characters ``?'' and ``*'' are used in a font name, a
When the characters \*(lq?\*(rq and ``*'' are used in a font name, a
pattern match is performed and any matching font is used.
In the pattern,
the ``?'' character will match any single character,
and the ``*'' character will match any number of characters.
the \*(lq?\*(rq character will match any single character,
and the \*(lq*\*(rq character will match any number of characters.
A structured format for font names is specified in the X Consortium standard
\fIX Logical Font Description Conventions\fP.
If

4
man/XParseGeometry.man
View file

@ -117,7 +117,7 @@ Specifically, this function lets you parse strings of the form:
.LP
The fields map into the arguments associated with this function.
(Items enclosed in <\^> are integers, items in [\^] are optional, and
items enclosed in {\^} indicate ``choose one of.''
items enclosed in {\^} indicate \*(lqchoose one of.\*(rq
Note that the brackets should not appear in the actual string.)
If the string is not in the Host Portable Character Encoding,
the result is implementation-dependent.
@ -128,7 +128,7 @@ function returns a bitmask that indicates which of the four values (width,
height, xoffset, and yoffset) were actually found in the string
and whether the x and y values are negative.
By convention, \-0 is not equal to +0, because the user needs to
be able to say ``position the window relative to the right or bottom edge.''
be able to say \*(lqposition the window relative to the right or bottom edge.\*(rq
For each value found, the corresponding argument is updated.
For each value not found, the argument is left unchanged.
The bits are represented by

10
man/XQueryColor.man
View file

@ -161,7 +161,7 @@ can generate
error.
.SH "COLOR NAMES"
An RGB Device specification is identified by
the prefix ``rgb:'' and conforms to the following syntax:
the prefix \*(lqrgb:\*(rq and conforms to the following syntax:
.LP
.\" Start marker code here
.EX
@ -193,11 +193,11 @@ l l.
The R, G, and B represent single hexadecimal digits.
When fewer than 16 bits each are specified,
they represent the most significant bits of the value
(unlike the ``rgb:'' syntax, in which values are scaled).
For example, the string ``#3a7'' is the same as ``#3000a0007000''.
(unlike the \*(lqrgb:\*(rq syntax, in which values are scaled).
For example, the string \*(lq#3a7\*(rq is the same as ``#3000a0007000''.
.LP
An RGB intensity specification is identified
by the prefix ``rgbi:'' and conforms to the following syntax:
by the prefix \*(lqrgbi:\*(rq and conforms to the following syntax:
.LP
.\" Start marker code here
.EX
@ -230,7 +230,7 @@ All of the values (C, H, V, X, Y, Z, a, b, u, v, y, x) are
floating-point values.
The syntax for these values is an optional plus or minus sign,
a string of digits possibly containing a decimal point,
and an optional exponent field consisting of an ``E'' or ``e''
and an optional exponent field consisting of an \*(lqE\*(rq or ``e''
followed by an optional plus or minus followed by a string of digits.
.SH DIAGNOSTICS
.TP 1i

4
man/XQueryExtension.man
View file

@ -11,7 +11,7 @@
.\" for any purpose and without fee is hereby granted, provided that the above
.\" copyright notice and this permission notice appear in all copies.
.\" Chris Lee makes no representations about the suitability for any purpose
.\" of the information in this document. It is provided \`\`as-is'' without
.\" of the information in this document. It is provided \`\`as-is\*(rq without
.\" express or implied warranty.
.\"
.ds xL Programming with Xlib
@ -55,7 +55,7 @@ specific to the extension. If the extension involves additional error codes,
otherwise, it returns zero. The format of additional data in the errors is
specific to the extension. If the extension name is not in the Host Portable
Character Encoding the result is implementation-dependent. Uppercase and
lowercase matter; the strings ``thing'', ``Thing'', and ``thinG'' are all
lowercase matter; the strings \*(lqthing\*(rq, ``Thing'', and ``thinG'' are all
considered different names.
.LP
The \fIXListExtensions\fP function returns a list of all extensions supported

2
man/XSetErrorHandler.man
View file

@ -157,7 +157,7 @@ The name argument should generally be the name of your application.
The message argument should indicate which type of error message you want.
If the name and message are not in the Host Portable Character Encoding,
the result is implementation-dependent.
Xlib uses three predefined ``application names'' to report errors.
Xlib uses three predefined \*(lqapplication names\*(rq to report errors.
In these names,
uppercase and lowercase matter.
.IP XProtoError 1i

4
man/XSetWMProperties.man
View file

@ -164,9 +164,9 @@ in the encoding of the current locale, for
.B Xutf8SetWMProperties
in UTF-8 encoding.
If the arguments can be fully converted to the STRING encoding,
the properties are created with type ``STRING'';
the properties are created with type \*(lqSTRING\*(rq;
otherwise, the arguments are converted to Compound Text,
and the properties are created with type ``COMPOUND_TEXT''.
and the properties are created with type \*(lqCOMPOUND_TEXT\*(rq.
.LP
If the normal_hints argument is non-NULL,
.B XmbSetWMProperties

8
man/XSupportsLocale.man
View file

@ -69,14 +69,14 @@ Xlib locale-dependent functions for which the
.B XLocaleNotSupported
return status is defined will return
.BR XLocaleNotSupported .
Other Xlib locale-dependent routines will operate in the ``C'' locale.
Other Xlib locale-dependent routines will operate in the \*(lqC\*(rq locale.
.LP
The
.B XSetLocaleModifiers
function sets the X modifiers for the current locale setting.
The modifier_list argument is a null-terminated string of the form
``{@\^\fIcategory\fP\^=\^\fIvalue\fP\^}'', that is,
having zero or more concatenated ``@\^\fIcategory\fP\^=\^\fIvalue\fP\^''
\*(lq{@\^\fIcategory\fP\^=\^\fIvalue\fP\^}\*(rq, that is,
having zero or more concatenated \*(lq@\^\fIcategory\fP\^=\^\fIvalue\fP\^\*(rq
entries, where \fIcategory\fP is a category name
and \fIvalue\fP is the (possibly empty) setting for that category.
The values are encoded in the current locale.
@ -115,7 +115,7 @@ Clients should always call
with a non-NULL modifier_list after setting the locale
before they call any locale-dependent Xlib routine.
.LP
The only standard modifier category currently defined is ``im'',
The only standard modifier category currently defined is \*(lqim\*(rq,
which identifies the desired input method.
The values for input method are not standardized.
A single locale may use multiple input methods,

8
man/XmbTextListToTextProperty.man
View file

@ -129,11 +129,11 @@ If the style
or
.B XCompoundTextStyle
is specified,
this encoding is ``STRING'' or ``COMPOUND_TEXT'', respectively.
this encoding is \*(lqSTRING\*(rq or ``COMPOUND_TEXT'', respectively.
If the style
.B XUTF8StringStyle
is specified,
this encoding is ``UTF8_STRING''.
this encoding is \*(lqUTF8_STRING\*(rq.
(This is an extension introduced by The XFree86 Project, Inc. in their 4.0.2
release. Its presence is indicated by the macro
.BR X_HAVE_UTF8_STRING .)
@ -144,8 +144,8 @@ this encoding is the encoding of the current locale.
If the style
.B XStdICCTextStyle
is specified,
this encoding is ``STRING'' if the text is fully convertible to STRING,
else ``COMPOUND_TEXT''.
this encoding is \*(lqSTRING\*(rq if the text is fully convertible to STRING,
else \*(lqCOMPOUND_TEXT\*(rq.
A final terminating null byte is stored at the end of the value field
of text_prop_return but is not included in the nitems member.
.LP

24
man/XrmGetFileDatabase.man
View file

@ -115,7 +115,7 @@ Entries containing resource names that are not in the Host Portable Character
Encoding or containing values that are not in the encoding of the database
locale, are written in an implementation-dependent manner.
The order in which entries are written is implementation-dependent.
Entries with representation types other than ``String'' are ignored.
Entries with representation types other than \*(lqString\*(rq are ignored.
.LP
The
.B XrmGetStringDatabase
@ -187,15 +187,15 @@ Quotes ("\&.\&.\&.") are used around literal characters.
.LP
IncludeFile lines are interpreted by replacing the line with the
contents of the specified file.
The word ``include'' must be in lowercase.
The word \*(lqinclude\*(rq must be in lowercase.
The file name is interpreted relative to the directory of the file in
which the line occurs (for example, if the file name contains no
directory or contains a relative directory specification).
.LP
If a ResourceName contains a contiguous sequence of two or more Binding
characters, the sequence will be replaced with single ``\&.'' character
if the sequence contains only ``\&.'' characters;
otherwise, the sequence will be replaced with a single ``*'' character.
characters, the sequence will be replaced with single \*(lq\&.\*(rq character
if the sequence contains only \*(lq\&.\*(rq characters;
otherwise, the sequence will be replaced with a single \*(lq*\*(rq character.
.LP
A resource database never contains more than one entry for a given
ResourceName. If a resource file contains multiple lines with the
@ -204,24 +204,24 @@ same ResourceName, the last line in the file is used.
Any white space characters before or after the name or colon in a ResourceSpec
are ignored.
To allow a Value to begin with white space,
the two-character sequence ``\^\\\^\fIspace\fP'' (backslash followed by space)
the two-character sequence \*(lq\^\\\^\fIspace\fP\*(rq (backslash followed by space)
is recognized and replaced by a space character,
and the two-character sequence ``\^\\\^\fItab\fP''
and the two-character sequence \*(lq\^\\\^\fItab\fP\*(rq
(backslash followed by horizontal tab)
is recognized and replaced by a horizontal tab character.
To allow a Value to contain embedded newline characters,
the two-character sequence ``\^\\\^n'' is recognized and replaced by a
the two-character sequence \*(lq\^\\\^n\*(rq is recognized and replaced by a
newline character.
To allow a Value to be broken across multiple lines in a text file,
the two-character sequence ``\^\\\^\fInewline\fP''
the two-character sequence \*(lq\^\\\^\fInewline\fP\*(rq
(backslash followed by newline) is
recognized and removed from the value.
To allow a Value to contain arbitrary character codes,
the four-character sequence ``\^\\\^\fInnn\fP'',
where each \fIn\fP is a digit character in the range of ``0''\^\-``7'',
the four-character sequence \*(lq\^\\\^\fInnn\fP\*(rq,
where each \fIn\fP is a digit character in the range of \*(lq0\*(rq\^\-``7'',
is recognized and replaced with a single byte that contains
the octal value specified by the sequence.
Finally, the two-character sequence ``\^\\\\'' is recognized
Finally, the two-character sequence \*(lq\^\\\\\*(rq is recognized
and replaced with a single backslash.
.SH "SEE ALSO"
XrmGetResource(__libmansuffix__),

10
man/XrmGetResource.man
View file

@ -187,7 +187,7 @@ with the fully qualified name and class.
The algorithm for determining which resource database entry
matches a given query is the heart of the resource manager.
All queries must fully specify the name and class of the desired resource
(use of the characters ``*'' and ``?'' are not permitted).
(use of the characters \*(lq*\*(rq and ``?'' are not permitted).
The library supports up to 100 components in a full name or class.
Resources are stored in the database with only partially specified
names and classes, using pattern matching constructs.
@ -197,7 +197,7 @@ A period (.) is a tight binding and is used to separate immediately
adjacent components.
A question mark (?) is used to match any single component name or class.
A database entry cannot end in a loose binding;
the final component (which cannot be the character ``?'') must be specified.
the final component (which cannot be the character \*(lq?\*(rq) must be specified.
The lookup algorithm searches the database for the entry that most
closely matches (is most specific for) the full name and class being queried.
When more than one database entry matches the full name and class,
@ -213,14 +213,14 @@ until a rule selects a single entry over all others.
The rules, in order of precedence, are:
.IP 1. 5
An entry that contains a matching component (whether name, class,
or the character ``?'')
or the character \*(lq?\*(rq)
takes precedence over entries that elide the level (that is, entries
that match the level in a loose binding).
.IP 2. 5
An entry with a matching name takes precedence over both
entries with a matching class and entries that match using the character ``?''.
entries with a matching class and entries that match using the character \*(lq?\*(rq.
An entry with a matching class takes precedence over
entries that match using the character ``?''.
entries that match using the character \*(lq?\*(rq.
.IP 3. 5
An entry preceded by a tight binding takes precedence over entries
preceded by a loose binding.

4
man/XrmInitialize.man
View file

@ -80,7 +80,7 @@ It must be called before any other Xrm functions are used.
The
.B XrmParseCommand
function parses an (argc, argv) pair according to the specified option table,
loads recognized options into the specified database with type ``String,''
loads recognized options into the specified database with type \*(lqString,\*(rq
and modifies the (argc, argv) pair to remove all recognized options.
If database contains NULL,
.B XrmParseCommand
@ -101,7 +101,7 @@ independent of any locale.
The resource values given in the table are stored in the resource database
without modification.
All resource database entries are created
using a ``String'' representation type.
using a \*(lqString\*(rq representation type.
The argc argument specifies the number of arguments in argv
and is set on return to the remaining number of arguments that were not parsed.
The name argument should be the name of your application

4
man/XrmPutResource.man
View file

@ -117,7 +117,7 @@ is a convenience function that first calls
.B XrmStringToBindingQuarkList
on the specifier and then calls
.BR XrmQPutResource ,
using a ``String'' representation type.
using a \*(lqString\*(rq representation type.
If the specifier is not in the Host Portable Character Encoding,
the result is implementation-dependent.
The value is stored in the database without modification.
@ -133,7 +133,7 @@ for the value string (by calling
to compute the size) and
then calls
.BR XrmQPutResource ,
using a ``String'' representation type.
using a \*(lqString\*(rq representation type.
The value is stored in the database without modification.
.LP
If database contains NULL,

2
man/XrmUniqueQuark.man
View file

@ -194,7 +194,7 @@ Component names in the list are separated by a period or
an asterisk character.
If the string does not start with period or asterisk,
a period is assumed.
For example, ``*a.b*c'' becomes:
For example, \*(lq*a.b*c\*(rq becomes:
.LP
.TS
L l l l.