[PATCH] Remove U+FB0x ligatures from specs xml files
cloos at jhcloos.com
Fri May 20 13:00:51 PDT 2011
If there are no objections I'll commit this:
Author: James Cloos <cloos at jhcloos.com>
Date: Fri May 20 15:51:46 2011 -0400
Expand latin ligatures out to their NFKC equivalents.
Ligatures should be done by the typesetting system.
Manuscripts should not bother with them.
Signed-off-by: James Cloos <cloos at jhcloos.com>
diff --git a/specs/libX11/CH01.xml b/specs/libX11/CH01.xml
index 7d03389..7a2d115 100644
@@ -27,7 +27,7 @@ those provided by the toolkits for X) are built on top of the Xlib
library. For further information about these higher-level libraries,
see the appropriate toolkit documentation.
The <citetitle>X Window System Protocol</citetitle> provides the
-deﬁnitive word on the behavior of X.
+definitive word on the behavior of X.
Although additional information appears here, the protocol document is
the ruling document.
diff --git a/specs/libX11/CH03.xml b/specs/libX11/CH03.xml
index 700c7cb..36768e2 100644
@@ -2295,7 +2295,7 @@ structure are:
<!-- .LP -->
-/* Conﬁgure window value mask bits */
+/* Configure window value mask bits */
#define CWX (1<<0)
#define CWY (1<<1)
#define CWWidth (1<<2)
diff --git a/specs/libX11/CH06.xml b/specs/libX11/CH06.xml
index 832a410..a305671 100644
@@ -273,7 +273,7 @@ The following macros define standard formats.
-#define XcmsUndeﬁnedFormat 0x00000000
+#define XcmsUndefinedFormat 0x00000000
#define XcmsCIEXYZFormat 0x00000001 /* CIE XYZ */
#define XcmsCIEuvYFormat 0x00000002 /* CIE u'v'Y */
#define XcmsCIExyYFormat 0x00000003 /* CIE xyY */
diff --git a/specs/libX11/CH07.xml b/specs/libX11/CH07.xml
index 201680d..bfa9785 100644
@@ -14,7 +14,7 @@ Sharing of GCs is highly discouraged because the library may cache GC state.
Graphics operations can be performed to either windows or pixmaps, which collectively are
-called drawables. Each drawable exists on a single screen. A GC is created for a speciﬁc screen
+called drawables. Each drawable exists on a single screen. A GC is created for a specific screen
and drawable depth and can only be used with drawables of matching screen and depth.
diff --git a/specs/libX11/CH09.xml b/specs/libX11/CH09.xml
index 413762f..51f980f 100644
@@ -5,7 +5,7 @@
<title>Window and Session Manager Functions</title>
-Although it is difﬁcult to categorize functions as exclusively for an application,
+Although it is difficult to categorize functions as exclusively for an application,
a window manager, or a session manager, the functions in this chapter are most
often used by window managers and session managers. It is not expected that
these functions will be used by most application programs. Xlib provides
diff --git a/specs/libX11/CH13.xml b/specs/libX11/CH13.xml
index 9525750..1962798 100644
@@ -8,7 +8,7 @@
An internationalized application is one that is adaptable to the requirements of different native
languages, local customs, and character string encodings. The process of adapting the operation
to a particular native language, local custom, or string encoding is called localization. A goal of
-internationalization is to permit localization without program source modiﬁcations or recompilation.
+internationalization is to permit localization without program source modifications or recompilation.
As one of the localization mechanisms, Xlib provides an X Input Method (<acronym>XIM</acronym>)
@@ -16,13 +16,13 @@ functional interface for internationalized text input and an X Output Method
(<acronym>XOM</acronym>) functional interface for internationalized text output.
-Internationalization in X is based on the concept of a locale. A locale deﬁnes the localized
+Internationalization in X is based on the concept of a locale. A locale defines the localized
behavior of a program at run time. Locales affect Xlib in its:
<listitem><para>Encoding and processing of input method text</para></listitem>
- <listitem><para>Encoding of resource ﬁles and values</para></listitem>
+ <listitem><para>Encoding of resource files and values</para></listitem>
<listitem><para>Encoding and imaging of text strings</para></listitem>
<listitem><para>Encoding and decoding for inter-client text communication</para></listitem>
@@ -36,7 +36,7 @@ Different languages have different encodings, and there are even different
encodings for the same characters in the same language.
-This chapter deﬁnes support for localized text imaging and text input and describes the locale
+This chapter defines support for localized text imaging and text input and describes the locale
mechanism that controls all locale-dependent Xlib functions. Sets of functions are provided for
multibyte (char *) text as well as wide character (wchar_t) text in the form supported by the host
C language environment. The multibyte and wide character functions are equivalent except for
@@ -54,7 +54,7 @@ The remainder of this chapter discusses:
<listitem><para>X locale management</para></listitem>
- <listitem><para>Locale and modiﬁer dependencies</para></listitem>
+ <listitem><para>Locale and modifier dependencies</para></listitem>
<listitem><para>Variable argument lists</para></listitem>
@@ -9359,10 +9359,10 @@ typedef unsigned long XIMFeedback;
#define XIMVisibleToBackward (1L<<9)
#define XIMVisibleToCenter (1L<<10)
-*† The values for XIMPrimary, XIMSecondary, and XIMTertiary were incorrectly deﬁned in
-the R5 speciﬁcation. The X Consortium’s X11R5 implementation correctly
+*† The values for XIMPrimary, XIMSecondary, and XIMTertiary were incorrectly defined in
+the R5 specification. The X Consortium’s X11R5 implementation correctly
implemented the values for these highlights. The value of these highlights has
-been corrected in this speciﬁcation to agree with the values in the
+been corrected in this specification to agree with the values in the
Consortium’s X11R5 and X11R6 implementations.
diff --git a/specs/libX11/CH14.xml b/specs/libX11/CH14.xml
index 6283677..9c5ef07 100644
@@ -12,8 +12,8 @@ see the Inter-Client Communication Conventions Manual.
Xlib provides a number of standard properties and programming interfaces that are <acronym>ICCCM</acronym>
-compliant. The predeﬁned atoms for some of these properties are deﬁned in the <X11/Xatom.h>
-header ﬁle, where to avoid name conﬂicts with user symbols their #deﬁne name has an XA_ preﬁx.
+compliant. The predefined atoms for some of these properties are defined in the <X11/Xatom.h>
+header file, where to avoid name conflicts with user symbols their #define name has an XA_ prefix.
For further information about atoms and properties, see section 4.3.
More information about the xorg-devel