From afbd3947071a33f59dda122f1ac396442a02c128 Mon Sep 17 00:00:00 2001 From: marha Date: Mon, 10 Oct 2011 07:52:38 +0200 Subject: fontconfig libX11 mesa pixman xkeyboard-config git updte 10 oct 2011 --- libX11/modules/im/ximcp/imRmAttr.c | 7 +- libX11/nls/locale.alias.pre | 2751 +++++++++++----------- libX11/nls/pt_BR.UTF-8/Compose.pre | 2 +- libX11/specs/XIM/xim.xml | 25 +- libX11/specs/XKB/ch01.xml | 22 +- libX11/specs/XKB/ch02.xml | 16 +- libX11/specs/XKB/ch03.xml | 12 +- libX11/specs/XKB/ch04.xml | 12 +- libX11/specs/XKB/ch05.xml | 14 +- libX11/specs/XKB/ch06.xml | 10 +- libX11/specs/XKB/ch07.xml | 16 +- libX11/specs/XKB/ch08.xml | 40 +- libX11/specs/XKB/ch09.xml | 16 +- libX11/specs/XKB/ch10.xml | 78 +- libX11/specs/XKB/ch11.xml | 30 +- libX11/specs/XKB/ch12.xml | 12 +- libX11/specs/XKB/ch13.xml | 26 +- libX11/specs/XKB/ch14.xml | 26 +- libX11/specs/XKB/ch15.xml | 44 +- libX11/specs/XKB/ch16.xml | 56 +- libX11/specs/XKB/ch17.xml | 22 +- libX11/specs/XKB/ch18.xml | 16 +- libX11/specs/XKB/ch19.xml | 2 +- libX11/specs/XKB/ch20.xml | 10 +- libX11/specs/XKB/ch21.xml | 17 +- libX11/specs/XKB/ch22.xml | 2 +- libX11/specs/i18n/framework/framework.xml | 164 +- libX11/specs/i18n/localedb/localedb.xml | 6 +- libX11/specs/i18n/trans/trans.xml | 32 +- libX11/specs/libX11/AppA.xml | 978 ++++---- libX11/specs/libX11/AppB.xml | 104 +- libX11/specs/libX11/AppC.xml | 266 +-- libX11/specs/libX11/AppD.xml | 204 +- libX11/specs/libX11/CH01.xml | 20 +- libX11/specs/libX11/CH02.xml | 270 +-- libX11/specs/libX11/CH03.xml | 308 +-- libX11/specs/libX11/CH04.xml | 204 +- libX11/specs/libX11/CH05.xml | 74 +- libX11/specs/libX11/CH06.xml | 570 ++--- libX11/specs/libX11/CH07.xml | 268 +-- libX11/specs/libX11/CH08.xml | 464 ++-- libX11/specs/libX11/CH09.xml | 232 +- libX11/specs/libX11/CH10.xml | 194 +- libX11/specs/libX11/CH11.xml | 264 +-- libX11/specs/libX11/CH12.xml | 344 +-- libX11/specs/libX11/CH13.xml | 852 +++---- libX11/specs/libX11/CH14.xml | 530 ++--- libX11/specs/libX11/CH15.xml | 246 +- libX11/specs/libX11/CH16.xml | 394 ++-- libX11/specs/libX11/credits.xml | 16 +- libX11/specs/libX11/glossary.xml | 3518 ++++++++++++++--------------- 51 files changed, 6883 insertions(+), 6923 deletions(-) (limited to 'libX11') diff --git a/libX11/modules/im/ximcp/imRmAttr.c b/libX11/modules/im/ximcp/imRmAttr.c index 2e732658a..c047715f6 100644 --- a/libX11/modules/im/ximcp/imRmAttr.c +++ b/libX11/modules/im/ximcp/imRmAttr.c @@ -177,6 +177,8 @@ _XimMakeICAttrIDList( else *len += new_len; return name; } + *len += new_len; + buf = (CARD16 *)((char *)buf + new_len); } else if (res->xrm_name == sts_quark) { if ((name = _XimMakeICAttrIDList(ic, res_list, res_num, (XIMArg *)p->value, buf, &new_len, @@ -185,9 +187,10 @@ _XimMakeICAttrIDList( else *len += new_len; return name; } + *len += new_len; + buf = (CARD16 *)((char *)buf + new_len); } - *len += new_len; - buf = (CARD16 *)((char *)buf + new_len); + if (!(res = _XimGetNestedListSeparator(res_list, res_num))) { p++; if (p) { diff --git a/libX11/nls/locale.alias.pre b/libX11/nls/locale.alias.pre index 25f06d430..7b3546099 100644 --- a/libX11/nls/locale.alias.pre +++ b/libX11/nls/locale.alias.pre @@ -1,1385 +1,1366 @@ -XCOMM -XCOMM This file contains alias name of locale. -XCOMM Each alias name is described within one line. -XCOMM The first word is the alias name (simplified locale name) -XCOMM the second word is full locale name. -XCOMM -XCOMM - -POSIX: C -POSIX-UTF2: C -C_C.C: C -C.en: C -C.ASCII: C -C.iso88591: en_US.ISO8859-1 -Cextend: en_US.ISO8859-1 -Cextend.en: en_US.ISO8859-1 -English_United-States.437: C -C.UTF-8: en_US.UTF-8 -XCOMM a3 is not an ISO 639 language code, but in Cyrillic, "Z" looks like "3". -a3: a3_AZ.KOI8-C -a3_AZ: a3_AZ.KOI8-C -a3_AZ.koi8c: a3_AZ.KOI8-C -af: af_ZA.ISO8859-1 -af_ZA: af_ZA.ISO8859-1 -af_ZA.iso88591: af_ZA.ISO8859-1 -af_ZA.ISO-8859-1: af_ZA.ISO8859-1 -af_ZA.utf8: af_ZA.UTF-8 -am: am_ET.UTF-8 -am_ET: am_ET.UTF-8 -ar: ar_AA.ISO8859-6 -ar_AA: ar_AA.ISO8859-6 -AR_AA: ar_AA.ISO8859-6 -Ar_AA: ar_AA.ISO8859-6 -AR_AA.UTF-8: ar_AA.UTF-8 -ar_AA.iso88596: ar_AA.ISO8859-6 -ar_AA.ISO-8859-6: ar_AA.ISO8859-6 -ar_AE: ar_AE.ISO8859-6 -ar_AE.iso88596: ar_AE.ISO8859-6 -ar_AE.ISO-8859-6: ar_AE.ISO8859-6 -ar_AE.utf8: ar_AE.UTF-8 -ar_BH: ar_BH.ISO8859-6 -ar_BH.iso88596: ar_BH.ISO8859-6 -ar_BH.ISO-8859-6: ar_BH.ISO8859-6 -ar_BH.utf8: ar_BH.UTF-8 -ar_DZ: ar_DZ.ISO8859-6 -ar_DZ.iso88596: ar_DZ.ISO8859-6 -ar_DZ.ISO-8859-6: ar_DZ.ISO8859-6 -ar_DZ.utf8: ar_DZ.UTF-8 -ar_EG: ar_EG.ISO8859-6 -ar_EG.iso88596: ar_EG.ISO8859-6 -ar_EG.ISO-8859-6: ar_EG.ISO8859-6 -ar_EG.utf8: ar_EG.UTF-8 -ar_IN.utf8: ar_IN.UTF-8 -ar_IN.UTF-8: ar_IN.UTF-8 -ar_IQ: ar_IQ.ISO8859-6 -ar_IQ.iso88596: ar_IQ.ISO8859-6 -ar_IQ.ISO-8859-6: ar_IQ.ISO8859-6 -ar_IQ.utf8: ar_IQ.UTF-8 -ar_JO: ar_JO.ISO8859-6 -ar_JO.iso88596: ar_JO.ISO8859-6 -ar_JO.ISO-8859-6: ar_JO.ISO8859-6 -ar_JO.utf8: ar_JO.UTF-8 -ar_KW: ar_KW.ISO8859-6 -ar_KW.iso88596: ar_KW.ISO8859-6 -ar_KW.ISO-8859-6: ar_KW.ISO8859-6 -ar_KW.utf8: ar_KW.UTF-8 -ar_LB: ar_LB.ISO8859-6 -ar_LB.iso88596: ar_LB.ISO8859-6 -ar_LB.ISO-8859-6: ar_LB.ISO8859-6 -ar_LB.utf8: ar_LB.UTF-8 -ar_LY: ar_LY.ISO8859-6 -ar_LY.iso88596: ar_LY.ISO8859-6 -ar_LY.ISO-8859-6: ar_LY.ISO8859-6 -ar_LY.utf8: ar_LY.UTF-8 -ar_MA: ar_MA.ISO8859-6 -ar_MA.iso88596: ar_MA.ISO8859-6 -ar_MA.ISO-8859-6: ar_MA.ISO8859-6 -ar_MA.utf8: ar_MA.UTF-8 -ar_OM: ar_OM.ISO8859-6 -ar_OM.iso88596: ar_OM.ISO8859-6 -ar_OM.ISO-8859-6: ar_OM.ISO8859-6 -ar_OM.utf8: ar_OM.UTF-8 -ar_QA: ar_QA.ISO8859-6 -ar_QA.iso88596: ar_QA.ISO8859-6 -ar_QA.ISO-8859-6: ar_QA.ISO8859-6 -ar_QA.utf8: ar_QA.UTF-8 -ar_SA: ar_SA.ISO8859-6 -ar_SA.iso88596: ar_SA.ISO8859-6 -ar_SA.ISO-8859-6: ar_SA.ISO8859-6 -ar_SA.utf8: ar_SA.UTF-8 -ar_SD: ar_SD.ISO8859-6 -ar_SD.iso88596: ar_SD.ISO8859-6 -ar_SD.ISO-8859-6: ar_SD.ISO8859-6 -ar_SD.utf8: ar_SD.UTF-8 -ar_SY: ar_SY.ISO8859-6 -ar_SY.iso88596: ar_SY.ISO8859-6 -ar_SY.ISO-8859-6: ar_SY.ISO8859-6 -ar_SY.utf8: ar_SY.UTF-8 -ar_TN: ar_TN.ISO8859-6 -ar_TN.iso88596: ar_TN.ISO8859-6 -ar_TN.ISO-8859-6: ar_TN.ISO8859-6 -ar_TN.utf8: ar_TN.UTF-8 -as: as_IN.UTF-8 -as_IN.utf8: as_IN.UTF-8 -as_IN.UTF-8: as_IN.UTF-8 -ar_YE: ar_YE.ISO8859-6 -ar_YE.iso88596: ar_YE.ISO8859-6 -ar_YE.ISO-8859-6: ar_YE.ISO8859-6 -ar_YE.utf8: ar_YE.UTF-8 -az: az_AZ.ISO8859-9E -az_AZ: az_AZ.ISO8859-9E -az_AZ.iso88599e: az_AZ.ISO8859-9E -be: be_BY.CP1251 -be@latin: be_BY.UTF-8@latin -be_BY: be_BY.CP1251 -be_BY@latin: be_BY.UTF-8@latin -be_BY.cp1251: be_BY.CP1251 -be_BY.microsoftcp1251: be_BY.CP1251 -be_BY.microsoft-cp1251: be_BY.CP1251 -be_BY.MICROSOFT-CP1251: be_BY.CP1251 -be_BY.utf8: be_BY.UTF-8 -be_BY.utf8@latin: be_BY.UTF-8@latin -bg: bg_BG.CP1251 -bg_BG: bg_BG.CP1251 -bg_BG.cp1251: bg_BG.CP1251 -bg_BG.microsoftcp1251: bg_BG.CP1251 -bg_BG.microsoft-cp1251: bg_BG.CP1251 -bg_BG.MICROSOFT-CP1251: bg_BG.CP1251 -bg_BG.iso88595: bg_BG.ISO8859-5 -bg_BG.ISO-8859-5: bg_BG.ISO8859-5 -bg_BG.koi8r: bg_BG.KOI8-R -be_BG.utf8: bg_BG.UTF-8 -bn_IN.utf8: bn_IN.UTF-8 -bn_IN.UTF-8: bn_IN.UTF-8 -bo_IN.utf8: bo_IN.UTF-8 -bo_IN.UTF-8: bo_IN.UTF-8 -br: br_FR.ISO8859-1 -br_FR: br_FR.ISO8859-1 -br_FR.iso88591: br_FR.ISO8859-1 -br_FR.ISO-8859-1: br_FR.ISO8859-1 -br_FR.iso885914: br_FR.ISO8859-14 -br_FR.ISO-8859-14: br_FR.ISO8859-14 -br_FR.iso885915: br_FR.ISO8859-15 -br_FR.ISO-8859-15: br_FR.ISO8859-15 -br_FR.ISO-8859-15@euro: br_FR.ISO8859-15 -br_FR@euro: br_FR.ISO8859-15 -br_FR.UTF-8@euro: br_FR.UTF-8 -bs: bs_BA.ISO8859-2 -bs_BA: bs_BA.ISO8859-2 -bs_BA.iso88592: bs_BA.ISO8859-2 -bs_BA.ISO-8859-2: bs_BA.ISO8859-2 -bs_BA.ISO_8859-2: bs_BA.ISO8859-2 -ca: ca_ES.ISO8859-1 -ca_AD: ca_AD.ISO8859-1 -ca_AD@euro: ca_AD.ISO8859-15 -ca_AD.iso88591: ca_AD.ISO8859-1 -ca_AD.ISO-8859-1: ca_AD.ISO8859-1 -ca_AD.iso885915: ca_AD.ISO8859-15 -ca_AD.utf8: ca_AD.UTF-8 -ca_AD.ISO-8859-15: ca_AD.ISO8859-15 -ca_AD.ISO-8859-15@euro: ca_AD.ISO8859-15 -ca_AD.UTF-8@euro: ca_AD.UTF-8 -ca_ES: ca_ES.ISO8859-1 -ca_ES@euro: ca_ES.ISO8859-15 -ca_ES.iso88591: ca_ES.ISO8859-1 -ca_ES.ISO-8859-1: ca_ES.ISO8859-1 -ca_ES.iso885915: ca_ES.ISO8859-15 -ca_ES.utf8: ca_ES.UTF-8 -ca_ES.ISO-8859-15: ca_ES.ISO8859-15 -ca_ES.ISO-8859-15@euro: ca_ES.ISO8859-15 -ca_ES.UTF-8@euro: ca_ES.UTF-8 -ca_FR: ca_FR.ISO8859-1 -ca_FR@euro: ca_FR.ISO8859-15 -ca_FR.iso88591: ca_FR.ISO8859-1 -ca_FR.ISO-8859-1: ca_FR.ISO8859-1 -ca_FR.iso885915: ca_FR.ISO8859-15 -ca_FR.utf8: ca_FR.UTF-8 -ca_FR.ISO-8859-15: ca_FR.ISO8859-15 -ca_FR.ISO-8859-15@euro: ca_FR.ISO8859-15 -ca_FR.UTF-8@euro: ca_FR.UTF-8 -ca_IT: ca_IT.ISO8859-1 -ca_IT@euro: ca_IT.ISO8859-15 -ca_IT.iso88591: ca_IT.ISO8859-1 -ca_IT.ISO-8859-1: ca_IT.ISO8859-1 -ca_IT.iso885915: ca_IT.ISO8859-15 -ca_IT.utf8: ca_IT.UTF-8 -ca_IT.ISO-8859-15: ca_IT.ISO8859-15 -ca_IT.ISO-8859-15@euro: ca_IT.ISO8859-15 -ca_IT.UTF-8@euro: ca_IT.UTF-8 -cs: cs_CZ.ISO8859-2 -cs_CS: cs_CZ.ISO8859-2 -cs_CS.ISO8859-2: cs_CZ.ISO8859-2 -cs_CZ: cs_CZ.ISO8859-2 -cs_CZ.iso88592: cs_CZ.ISO8859-2 -cs_CS.iso8859-2: cs_CS.ISO8859-2 -cs_CZ.ISO-8859-2: cs_CZ.ISO8859-2 -cs_CZ.ISO_8859-2: cs_CZ.ISO8859-2 -cs_CZ.utf8: cs_CZ.UTF-8 -XCOMM cz is an old name for Czech (now cs), and should be deleted in the future. -cz: cs_CZ.ISO8859-2 -cz_CZ: cs_CZ.ISO8859-2 -cz_CZ.utf8: cs_CZ.UTF-8 -cz_CZ.UTF-8: cs_CZ.UTF-8 -cy: cy_GB.ISO8859-1 -cy_GB: cy_GB.ISO8859-1 -cy_GB.iso88591: cy_GB.ISO8859-1 -cy_GB.ISO-8859-1: cy_GB.ISO8859-1 -cy_GB.iso885914: cy_GB.ISO8859-14 -cy_GB.ISO-8859-14: cy_GB.ISO8859-14 -cy_GB.iso885915: cy_GB.ISO8859-15 -cy_GB.ISO-8859-15: cy_GB.ISO8859-15 -da: da_DK.ISO8859-1 -da.ISO8859-15: da_DK.ISO8859-15 -da_DK: da_DK.ISO8859-1 -DA_DK: da_DK.ISO8859-1 -da_DK.88591: da_DK.ISO8859-1 -da_DK.88591.en: da_DK.ISO8859-1 -da_DK.iso88591: da_DK.ISO8859-1 -da_DK.ISO-8859-1: da_DK.ISO8859-1 -da_DK.ISO_8859-1: da_DK.ISO8859-1 -da_DK.iso885915: da_DK.ISO8859-15 -da_DK.ISO-8859-15: da_DK.ISO8859-15 -da_DK.8859-15: da_DK.ISO8859-15 -da_DK.utf8: da_DK.UTF-8 -DA_DK.UTF-8: da_DK.UTF-8 -de: de_DE.ISO8859-1 -de.ISO8859-15: de_DE.ISO8859-15 -de_AT: de_AT.ISO8859-1 -de_AT@euro: de_AT.ISO8859-15 -de_AT.iso88591: de_AT.ISO8859-1 -de_AT.ISO-8859-1: de_AT.ISO8859-1 -de_AT.ISO_8859-1: de_AT.ISO8859-1 -de_AT.iso885915: de_AT.ISO8859-15 -de_AT.ISO-8859-15: de_AT.ISO8859-15 -de_AT.ISO-8859-15@euro: de_AT.ISO8859-15 -de_AT.UTF-8@euro: de_AT.UTF-8 -de_AT.utf8: de_AT.UTF-8 -de_BE: de_BE.ISO8859-1 -de_BE@euro: de_BE.ISO8859-15 -de_BE.iso88591: de_BE.ISO8859-1 -de_BE.ISO_8859-1: de_BE.ISO8859-1 -de_BE.ISO-8859-1: de_BE.ISO8859-1 -de_BE.iso885915: de_BE.ISO8859-15 -de_BE.ISO_8859-15: de_BE.ISO8859-15 -de_BE.ISO-8859-15: de_BE.ISO8859-15 -de_BE.ISO-8859-15@euro: de_BE.ISO8859-15 -de_BE.UTF-8@euro: de_BE.UTF-8 -de_CH: de_CH.ISO8859-1 -de_CH.iso88591: de_CH.ISO8859-1 -de_CH.ISO_8859-1: de_CH.ISO8859-1 -de_CH.ISO-8859-1: de_CH.ISO8859-1 -de_CH.iso885915: de_CH.ISO8859-15 -de_CH.ISO_8859-15: de_CH.ISO8859-15 -de_CH.ISO-8859-15: de_CH.ISO8859-15 -de_CH.utf8: de_CH.UTF-8 -de_DE: de_DE.ISO8859-1 -de_DE@euro: de_DE.ISO8859-15 -de_DE.88591: de_DE.ISO8859-1 -de_DE.88591.en: de_DE.ISO8859-1 -de_DE.iso88591: de_DE.ISO8859-1 -de_DE.ISO-8859-1: de_DE.ISO8859-1 -de_DE.ISO_8859-1: de_DE.ISO8859-1 -de_DE.iso885915: de_DE.ISO8859-15 -de_DE.ISO-8859-15: de_DE.ISO8859-15 -de_DE.ISO_8859-15: de_DE.ISO8859-15 -de_DE.8859-15: de_DE.ISO8859-15 -de_DE.8859-15@euro: de_DE.ISO8859-15 -de_DE.ISO-8859-15@euro: de_DE.ISO8859-15 -de_DE.UTF-8@euro: de_DE.UTF-8 -de_DE.utf8: de_DE.UTF-8 -de_LU: de_LU.ISO8859-1 -de_LU@euro: de_LU.ISO8859-15 -de_LU.iso88591: de_LU.ISO8859-1 -de_LU.ISO_8859-1: de_LU.ISO8859-1 -de_LU.ISO-8859-1: de_LU.ISO8859-1 -de_LU.iso885915: de_LU.ISO8859-15 -de_LU.ISO_8859-15: de_LU.ISO8859-15 -de_LU.ISO-8859-15: de_LU.ISO8859-15 -de_LU.ISO-8859-15@euro: de_LU.ISO8859-15 -de_LU.UTF-8@euro: de_LU.UTF-8 -de_LU.utf8: de_LU.UTF-8 -GER_DE.8859: de_DE.ISO8859-1 -GER_DE.8859.in: de_DE.ISO8859-1 -ee: ee_EE.ISO8859-4 -ee_EE: ee_EE.ISO8859-4 -ee_EE.iso88594: ee_EE.ISO8859-4 -el: el_GR.ISO8859-7 -el_GR: el_GR.ISO8859-7 -el_GR.iso88597: el_GR.ISO8859-7 -el_GR.ISO-8859-7: el_GR.ISO8859-7 -el_GR@euro: el_GR.ISO8859-15 -el_GR.utf8: el_GR.UTF-8 -en: en_US.ISO8859-1 -en.ISO-8859-1: en_US.ISO8859-1 -en_AU: en_AU.ISO8859-1 -en_AU.iso88591: en_AU.ISO8859-1 -en_AU.ISO-8859-1: en_AU.ISO8859-1 -en_AU.ISO_8859-1: en_AU.ISO8859-1 -en_AU.utf8: en_AU.UTF-8 -en_BE: en_BE.ISO8859-1 -en_BE@euro: en_BE.ISO8859-15 -en_BE.utf8: en_BE.UTF-8 -en_BW: en_BW.ISO8859-1 -en_BW.iso88591: en_BW.ISO8859-1 -en_BW.ISO-8859-1: en_BW.ISO8859-1 -en_CA: en_CA.ISO8859-1 -en_CA.iso88591: en_CA.ISO8859-1 -en_CA.ISO-8859-1: en_CA.ISO8859-1 -en_CA.ISO_8859-1: en_CA.ISO8859-1 -en_CA.utf8: en_CA.UTF-8 -en_GB: en_GB.ISO8859-1 -en_GB.88591: en_GB.ISO8859-1 -en_GB.88591.en: en_GB.ISO8859-1 -en_GB.iso88591: en_GB.ISO8859-1 -en_GB.ISO-8859-1: en_GB.ISO8859-1 -en_GB.ISO_8859-1: en_GB.ISO8859-1 -en_GB.iso885915: en_GB.ISO8859-15 -en_GB.ISO-8859-15: en_GB.ISO8859-15 -en_GB.utf8: en_GB.UTF-8 -en_UK: en_GB.ISO8859-1 -ENG_GB.8859: en_GB.ISO8859-1 -ENG_GB.8859.in: en_GB.ISO8859-1 -en_HK: en_HK.ISO8859-1 -en_HK.iso88591: en_HK.ISO8859-1 -en_HK.ISO-8859-1: en_HK.ISO8859-1 -en_IE: en_IE.ISO8859-1 -en_IE.iso88591: en_IE.ISO8859-1 -en_IE.ISO-8859-1: en_IE.ISO8859-1 -en_IE.iso885915: en_IE.ISO8859-15 -en_IE.ISO-8859-15: en_IE.ISO8859-15 -en_IE.ISO-8859-15@euro: en_IE.ISO8859-15 -en_IE@euro: en_IE.ISO8859-15 -en_IE.UTF-8@euro: en_IE.UTF-8 -en_IE.utf8: en_IE.UTF-8 -en_IN: en_IN.ISO8859-1 -en_NZ: en_NZ.ISO8859-1 -en_NZ.iso88591: en_NZ.ISO8859-1 -en_NZ.ISO-8859-1: en_NZ.ISO8859-1 -en_NZ.utf8: en_NZ.UTF-8 -en_PH: en_PH.ISO8859-1 -en_PH.iso88591: en_PH.ISO8859-1 -en_PH.ISO-8859-1: en_PH.ISO8859-1 -en_SG: en_SG.ISO8859-1 -en_SG.iso88591: en_SG.ISO8859-1 -en_SG.ISO-8859-1: en_SG.ISO8859-1 -en_US: en_US.ISO8859-1 -EN_US: en_US.ISO8859-1 -en_US.88591: en_US.ISO8859-1 -en_US.88591.en: en_US.ISO8859-1 -en_US.iso88591: en_US.ISO8859-1 -en_US.ISO-8859-1: en_US.ISO8859-1 -en_US.ISO_8859-1: en_US.ISO8859-1 -en_US.iso885915: en_US.ISO8859-15 -en_US.ISO-8859-15: en_US.ISO8859-15 -en_US.8859-15: en_US.ISO8859-15 -en_US.ISO8859-15@euro: en_US.ISO8859-15 -en_US.utf8: en_US.UTF-8 -EN_US.UTF-8: en_US.UTF-8 -en_ZA: en_ZA.ISO8859-1 -en_ZA.88591: en_ZA.ISO8859-1 -en_ZA.88591.en: en_ZA.ISO8859-1 -en_ZA.iso88591: en_ZA.ISO8859-1 -en_ZA.ISO-8859-1: en_ZA.ISO8859-1 -en_ZA.ISO_8859-1: en_ZA.ISO8859-1 -en_ZA.iso885915: en_ZA.ISO8859-15 -en_ZA.ISO-8859-15: en_ZA.ISO8859-15 -en_ZA.utf8: en_ZA.UTF-8 -en_ZW: en_ZW.ISO8859-1 -en_ZW.iso88591: en_ZW.ISO8859-1 -en_ZW.ISO-8859-1: en_ZW.ISO8859-1 -eo: eo_XX.ISO8859-3 -eo_EO: eo_EO.ISO8859-3 -eo_EO.ISO8859-3: eo_EO.ISO8859-3 -eo_XX: eo_XX.ISO8859-3 -eo_XX.ISO8859-3: eo_XX.ISO8859-3 -es: es_ES.ISO8859-1 -es.UTF-8: es_ES.UTF-8 -es_AR: es_AR.ISO8859-1 -es_AR.iso88591: es_AR.ISO8859-1 -es_AR.ISO-8859-1: es_AR.ISO8859-1 -es_AR.utf8: es_AR.UTF-8 -es_BO: es_BO.ISO8859-1 -es_BO.iso88591: es_BO.ISO8859-1 -es_BO.ISO-8859-1: es_BO.ISO8859-1 -es_BO.utf8: es_BO.UTF-8 -es_CL: es_CL.ISO8859-1 -es_CL.iso88591: es_CL.ISO8859-1 -es_CL.ISO-8859-1: es_CL.ISO8859-1 -es_CL.utf8: es_CL.UTF-8 -es_CO: es_CO.ISO8859-1 -es_CO.iso88591: es_CO.ISO8859-1 -es_CO.ISO-8859-1: es_CO.ISO8859-1 -es_CO.utf8: es_CO.UTF-8 -es_CR: es_CR.ISO8859-1 -es_CR.iso88591: es_CR.ISO8859-1 -es_CR.ISO-8859-1: es_CR.ISO8859-1 -es_CR.utf8: es_CR.UTF-8 -es_DO: es_DO.ISO8859-1 -es_DO.iso88591: es_DO.ISO8859-1 -es_DO.ISO-8859-1: es_DO.ISO8859-1 -es_DO.utf8: es_DO.UTF-8 -es_EC: es_EC.ISO8859-1 -es_EC.iso88591: es_EC.ISO8859-1 -es_EC.ISO-8859-1: es_EC.ISO8859-1 -es_EC.utf8: es_EC.UTF-8 -es_ES: es_ES.ISO8859-1 -es_ES.88591: es_ES.ISO8859-1 -es_ES.88591.en: es_ES.ISO8859-1 -es_ES.iso88591: es_ES.ISO8859-1 -es_ES.ISO-8859-1: es_ES.ISO8859-1 -es_ES.ISO_8859-1: es_ES.ISO8859-1 -es_ES.iso885915: es_ES.ISO8859-15 -es_ES.ISO-8859-15: es_ES.ISO8859-15 -es_ES.ISO-8859-15@euro: es_ES.ISO8859-15 -es_ES@euro: es_ES.ISO8859-15 -es_ES.UTF-8@euro: es_ES.UTF-8 -es_ES.utf8: es_ES.UTF-8 -es_GT: es_GT.ISO8859-1 -es_GT.iso88591: es_GT.ISO8859-1 -es_GT.ISO-8859-1: es_GT.ISO8859-1 -es_GT.utf8: es_GT.UTF-8 -es_HN: es_HN.ISO8859-1 -es_HN.iso88591: es_HN.ISO8859-1 -es_HN.ISO-8859-1: es_HN.ISO8859-1 -es_HN.utf8: es_HN.UTF-8 -es_MX: es_MX.ISO8859-1 -es_MX.iso88591: es_MX.ISO8859-1 -es_MX.ISO-8859-1: es_MX.ISO8859-1 -es_MX.utf8: es_MX.UTF-8 -es_NI: es_NI.ISO8859-1 -es_NI.iso88591: es_NI.ISO8859-1 -es_NI.ISO-8859-1: es_NI.ISO8859-1 -es_NI.utf8: es_NI.UTF-8 -es_PA: es_PA.ISO8859-1 -es_PA.iso88591: es_PA.ISO8859-1 -es_PA.ISO-8859-1: es_PA.ISO8859-1 -es_PA.iso885915: es_PA.ISO8859-15 -es_PA.utf8: es_PA.UTF-8 -es_PE: es_PE.ISO8859-1 -es_PE.iso88591: es_PE.ISO8859-1 -es_PE.ISO-8859-1: es_PE.ISO8859-1 -es_PE.iso885915: es_PE.ISO8859-15 -es_PE.utf8: es_PE.UTF-8 -es_PR: es_PR.ISO8859-1 -es_PR.iso88591: es_PR.ISO8859-1 -es_PR.ISO-8859-1: es_PR.ISO8859-1 -es_PR.utf8: es_PR.UTF-8 -es_PY: es_PY.ISO8859-1 -es_PY.iso88591: es_PY.ISO8859-1 -es_PY.ISO-8859-1: es_PY.ISO8859-1 -es_PY.iso885915: es_PY.ISO8859-15 -es_PY.utf8: es_PY.UTF-8 -es_SV: es_SV.ISO8859-1 -es_SV.iso88591: es_SV.ISO8859-1 -es_SV.ISO-8859-1: es_SV.ISO8859-1 -es_SV.iso885915: es_SV.ISO8859-15 -es_SV.utf8: es_SV.UTF-8 -es_US: es_US.ISO8859-1 -es_US.iso88591: es_US.ISO8859-1 -es_US.ISO-8859-1: es_US.ISO8859-1 -es_UY: es_UY.ISO8859-1 -es_UY.iso88591: es_UY.ISO8859-1 -es_UY.ISO-8859-1: es_UY.ISO8859-1 -es_UY.iso885915: es_UY.ISO8859-15 -es_UY.utf8: es_UY.UTF-8 -es_VE: es_VE.ISO8859-1 -es_VE.iso88591: es_VE.ISO8859-1 -es_VE.ISO-8859-1: es_VE.ISO8859-1 -es_VE.iso885915: es_VE.ISO8859-15 -es_VE.utf8: es_VE.UTF-8 -#if defined(SVR4) && defined(sun) -XCOMM Sun Solaris 2.6 has erroneously specified Estonian as a Latin-1 -XCOMM language; however this is clearly incorrect according to ISO8859. -#endif -XCOMM According to Estonian local standards, ISO8859-4 is not a recommended -XCOMM charset. EVS8:2000 specifies ISO8859-15 as the base charset. -et: et_EE.ISO8859-15 -et_EE: et_EE.ISO8859-15 -et_EE.iso88591: et_EE.ISO8859-1 -et_EE.ISO-8859-1: et_EE.ISO8859-1 -et_EE.iso88594: et_EE.ISO8859-4 -et_EE.ISO-8859-4: et_EE.ISO8859-4 -et_EE.iso885913: et_EE.ISO8859-13 -et_EE.ISO-8859-13: et_EE.ISO8859-13 -et_EE.iso885915: et_EE.ISO8859-15 -et_EE.ISO-8859-15: et_EE.ISO8859-15 -et_EE.utf8: et_EE.UTF-8 -eu: eu_ES.ISO8859-1 -eu_ES: eu_ES.ISO8859-1 -eu_ES.iso88591: eu_ES.ISO8859-1 -eu_ES.ISO-8859-1: eu_ES.ISO8859-1 -eu_ES.iso885915: eu_ES.ISO8859-15 -eu_ES.ISO-8859-15: eu_ES.ISO8859-15 -eu_ES.ISO-8859-15@euro: eu_ES.ISO8859-15 -eu_ES@euro: eu_ES.ISO8859-15 -eu_ES.UTF-8@euro: eu_ES.UTF-8 -fa: fa_IR.UTF-8 -fa_IR: fa_IR.UTF-8 -fa_IR.isiri3342: fa_IR.ISIRI-3342 -fa_IR.utf8: fa_IR.UTF-8 -fi: fi_FI.ISO8859-15 -fi.ISO8859-15: fi_FI.ISO8859-15 -fi_FI: fi_FI.ISO8859-15 -fi_FI.88591: fi_FI.ISO8859-1 -fi_FI.88591.en: fi_FI.ISO8859-1 -fi_FI.iso88591: fi_FI.ISO8859-1 -fi_FI.ISO-8859-1: fi_FI.ISO8859-1 -fi_FI.ISO_8859-1: fi_FI.ISO8859-1 -fi_FI.iso885915: fi_FI.ISO8859-15 -fi_FI.ISO-8859-15: fi_FI.ISO8859-15 -fi_FI.ISO-8859-15@euro: fi_FI.ISO8859-15 -fi_FI@euro: fi_FI.ISO8859-15 -fi_FI.utf8: fi_FI.UTF-8 -fi_FI.UTF-8@euro: fi_FI.UTF-8 -fo: fo_FO.ISO8859-1 -fo_FO: fo_FO.ISO8859-1 -fo_FO.iso88591: fo_FO.ISO8859-1 -fo_FO.ISO-8859-1: fo_FO.ISO8859-1 -fo_FO.iso885915: fo_FO.ISO8859-15 -fo_FO.ISO-8859-15: fo_FO.ISO8859-15 -fo_FO.utf8: fo_FO.UTF-8 -fr: fr_FR.ISO8859-1 -fr.ISO8859-15: fr_FR.ISO8859-15 -fr.UTF-8: fr_FR.UTF-8 -fr_BE: fr_BE.ISO8859-1 -fr_BE.88591: fr_BE.ISO8859-1 -fr_BE.88591.en: fr_BE.ISO8859-1 -fr_BE.ISO-8859-1: fr_BE.ISO8859-1 -fr_BE.ISO_8859-1: fr_BE.ISO8859-1 -fr_BE.iso885915: fr_BE.ISO8859-15 -fr_BE.ISO-8859-15: fr_BE.ISO8859-15 -fr_BE.ISO-8859-15@euro: fr_BE.ISO8859-15 -fr_BE@euro: fr_BE.ISO8859-15 -fr_BE.utf8: fr_BE.UTF-8 -fr_BE.UTF-8@euro: fr_BE.UTF-8 -fr_CA: fr_CA.ISO8859-1 -fr_CA.88591: fr_CA.ISO8859-1 -fr_CA.88591.en: fr_CA.ISO8859-1 -fr_CA.iso88591: fr_CA.ISO8859-1 -fr_CA.ISO-8859-1: fr_CA.ISO8859-1 -fr_CA.ISO_8859-1: fr_CA.ISO8859-1 -fr_CA.iso885915: fr_CA.ISO8859-15 -fr_CA.ISO-8859-15: fr_CA.ISO8859-15 -fr_CA.utf8: fr_CA.UTF-8 -fr_CH: fr_CH.ISO8859-1 -fr_CH.88591: fr_CH.ISO8859-1 -fr_CH.88591.en: fr_CH.ISO8859-1 -fr_CH.ISO-8859-1: fr_CH.ISO8859-1 -fr_CH.ISO_8859-1: fr_CH.ISO8859-1 -fr_CH.iso885915: fr_CH.ISO8859-15 -fr_CH.ISO-8859-15: fr_CH.ISO8859-15 -fr_CH.utf8: fr_CH.UTF-8 -fr_FR: fr_FR.ISO8859-1 -fr_FR.88591: fr_FR.ISO8859-1 -fr_FR.88591.en: fr_FR.ISO8859-1 -fr_FR.iso88591: fr_FR.ISO8859-1 -fr_FR.ISO-8859-1: fr_FR.ISO8859-1 -fr_FR.ISO_8859-1: fr_FR.ISO8859-1 -fr_FR.iso885915: fr_FR.ISO8859-15 -fr_FR.ISO-8859-15: fr_FR.ISO8859-15 -fr_FR.ISO-8859-15@euro: fr_FR.ISO8859-15 -fr_FR@euro: fr_FR.ISO8859-15 -fr_FR.UTF-8@euro: fr_FR.UTF-8 -fr_FR.utf8: fr_FR.UTF-8 -fr_LU: fr_LU.ISO8859-1 -fr_LU.88591: fr_LU.ISO8859-1 -fr_LU.88591.en: fr_LU.ISO8859-1 -fr_LU.iso88591: fr_LU.ISO8859-1 -fr_LU.ISO-8859-1: fr_LU.ISO8859-1 -fr_LU.ISO_8859-1: fr_LU.ISO8859-1 -fr_LU.iso885915: fr_LU.ISO8859-15 -fr_LU.ISO-8859-15: fr_LU.ISO8859-15 -fr_LU.ISO-8859-15@euro: fr_LU.ISO8859-15 -fr_LU@euro: fr_LU.ISO8859-15 -fr_LU.UTF-8@euro: fr_LU.UTF-8 -fr_LU.utf8: fr_LU.UTF-8 -FRE_FR.8859: fr_FR.ISO8859-1 -FRE_FR.8859.in: fr_FR.ISO8859-1 -ga: ga_IE.ISO8859-1 -ga_IE: ga_IE.ISO8859-1 -ga_IE.iso88591: ga_IE.ISO8859-1 -ga_IE.ISO-8859-1: ga_IE.ISO8859-1 -ga_IE.iso885914: ga_IE.ISO8859-14 -ga_IE.ISO-8859-14: ga_IE.ISO8859-14 -ga_IE.iso885915: ga_IE.ISO8859-15 -ga_IE.ISO-8859-15: ga_IE.ISO8859-15 -ga_IE.ISO-8859-15@euro: ga_IE.ISO8859-15 -ga_IE@euro: ga_IE.ISO8859-15 -ga_IE.UTF-8@euro: ga_IE.UTF-8 -ga_IE.utf8: ga_IE.UTF-8 -gd: gd_GB.ISO8859-1 -gd_GB: gd_GB.ISO8859-1 -gd_GB.iso88591: gd_GB.ISO8859-1 -gd_GB.ISO-8859-1: gd_GB.ISO8859-1 -gd_GB.iso885914: gd_GB.ISO8859-14 -gd_GB.ISO-8859-14: gd_GB.ISO8859-14 -gd_GB.iso885915: gd_GB.ISO8859-15 -gd_GB.ISO-8859-15: gd_GB.ISO8859-15 -gl: gl_ES.ISO8859-1 -gl_ES: gl_ES.ISO8859-1 -gl_ES.iso88591: gl_ES.ISO8859-1 -gl_ES.ISO-8859-1: gl_ES.ISO8859-1 -gl_ES.iso885915: gl_ES.ISO8859-15 -gl_ES.ISO-8859-15: gl_ES.ISO8859-15 -gl_ES.ISO-8859-15@euro: gl_ES.ISO8859-15 -gl_ES@euro: gl_ES.ISO8859-15 -gl_ES.UTF-8@euro: gl_ES.UTF-8 -gl_ES.utf8: gl_ES.UTF-8 -gu_IN.utf8: gu_IN.UTF-8 -gu_IN.UTF-8: gu_IN.UTF-8 -gv: gv_GB.ISO8859-1 -gv_GB: gv_GB.ISO8859-1 -gv_GB.iso88591: gv_GB.ISO8859-1 -gv_GB.ISO-8859-1: gv_GB.ISO8859-1 -gv_GB.iso885914: gv_GB.ISO8859-14 -gv_GB.ISO-8859-14: gv_GB.ISO8859-14 -gv_GB.iso885915: gv_GB.ISO8859-15 -gv_GB.ISO-8859-15: gv_GB.ISO8859-15 -he: he_IL.ISO8859-8 -he_IL: he_IL.ISO8859-8 -HE_IL: he_IL.ISO8859-8 -he_IL.iso88598: he_IL.ISO8859-8 -he_IL.ISO-8859-8: he_IL.ISO8859-8 -he_IL.cp1255: he_IL.CP1255 -he_IL.microsoftcp1255: he_IL.CP1255 -he_IL.microsoft-cp1255: he_IL.CP1255 -he_IL.MICROSOFT-CP1255: he_IL.CP1255 -he_IL.utf8: he_IL.UTF-8 -HE_IL.UTF-8: he_IL.UTF-8 -hi: hi_IN.ISCII-DEV -hi_IN: hi_IN.ISCII-DEV -HI_IN: hi_IN.ISCII-DEV -hi_IN.isciidev: hi_IN.ISCII-DEV -hi_IN.utf8: hi_IN.UTF-8 -HI_IN.UTF-8: hi_IN.UTF-8 -hne: hne_IN.UTF-8 -hne_IN.utf8: hne_IN.UTF-8 -hne_IN.UTF-8: hne_IN.UTF-8 -hr: hr_HR.ISO8859-2 -hr_HR: hr_HR.ISO8859-2 -hr_HR.iso88592: hr_HR.ISO8859-2 -hr_HR.ISO-8859-2: hr_HR.ISO8859-2 -hr_HR.ISO_8859-2: hr_HR.ISO8859-2 -hr_HR.utf8: hr_HR.UTF-8 -hu: hu_HU.ISO8859-2 -hu_HU: hu_HU.ISO8859-2 -hu_HU.iso88592: hu_HU.ISO8859-2 -hu_HU.ISO-8859-2: hu_HU.ISO8859-2 -hu_HU.utf8: hu_HU.UTF-8 -XCOMM in was the old ISO code for Indonesian (now id). These lines should be -XCOMM deleted in the future. -in: id_ID.ISO8859-1 -in_ID: id_ID.ISO8859-1 -is: is_IS.ISO8859-1 -is_IS: is_IS.ISO8859-1 -is_IS.iso88591: is_IS.ISO8859-1 -is_IS.ISO-8859-1: is_IS.ISO8859-1 -is_IS.ISO_8859-1: is_IS.ISO8859-1 -is_IS.iso885915: is_IS.ISO8859-15 -is_IS.ISO-8859-15: is_IS.ISO8859-15 -is_IS.utf8: is_IS.UTF-8 -it: it_IT.ISO8859-1 -it.ISO8859-15: it_IT.ISO8859-15 -it.UTF-8: it_IT.UTF-8 -it_CH: it_CH.ISO8859-1 -it_CH.iso88591: it_CH.ISO8859-1 -it_CH.ISO_8859-1: it_CH.ISO8859-1 -it_CH.ISO-8859-1: it_CH.ISO8859-1 -it_CH.iso885915: it_CH.ISO8859-15 -it_CH.utf8: it_CH.UTF-8 -it_IT: it_IT.ISO8859-1 -it_IT.88591: it_IT.ISO8859-1 -it_IT.88591.en: it_IT.ISO8859-1 -it_IT.iso88591: it_IT.ISO8859-1 -it_IT.ISO-8859-1: it_IT.ISO8859-1 -it_IT.ISO_8859-1: it_IT.ISO8859-1 -it_IT.iso885915: it_IT.ISO8859-15 -it_IT.ISO-8859-15: it_IT.ISO8859-15 -it_IT.ISO-8859-15@euro: it_IT.ISO8859-15 -it_IT@euro: it_IT.ISO8859-15 -it_IT.utf8: it_IT.UTF-8 -it_IT.UTF-8@euro: it_IT.UTF-8 -iu: iu_CA.NUNACOM-8 -iu_CA: iu_CA.NUNACOM-8 -iu_CA.nunacom8: iu_CA.NUNACOM-8 -XCOMM iw was the old ISO code for Hebrew (now he). These lines should be -XCOMM deleted in the future. -iw: he_IL.ISO8859-8 -iw_IL: he_IL.ISO8859-8 -Iw_IL: he_IL.ISO8859-8 -iw_IL.iso88598: he_IL.ISO8859-8 -iw_IL.ISO-8859-8: he_IL.ISO8859-8 -#ifndef __uxp__ -ja_JP: ja_JP.eucJP -#else /* __uxp__ */ -ja_JP: ja_JP.U90 -ja_JP.U90: ja_JP.U90 -ja_JP.S90: ja_JP.S90 -#endif /* __uxp__ */ -ja: ja_JP.eucJP -ja.JIS: ja_JP.JIS7 -ja.SJIS: ja_JP.SJIS -ja_JP.ujis: ja_JP.eucJP -Jp_JP: ja_JP.eucJP -ja_JP.AJEC: ja_JP.eucJP -ja_JP.EUC: ja_JP.eucJP -ja_JP.EUC-JP: ja_JP.eucJP -ja_JP.EUC_JP: ja_JP.eucJP -ja_JP.eucjp: ja_JP.eucJP -ja_JP.ISO-2022-JP: ja_JP.JIS7 -ja_JP.JIS: ja_JP.JIS7 -ja_JP.jis7: ja_JP.JIS7 -ja_JP.mscode: ja_JP.SJIS -ja_JP.PCK: ja_JP.SJIS -ja_JP.SJIS: ja_JP.SJIS -ja_JP.sjis: ja_JP.SJIS -ja_JP.utf8: ja_JP.UTF-8 -JA_JP.utf8: ja_JP.UTF-8 -ka: ka_GE.GEORGIAN-ACADEMY -ka_GE: ka_GE.GEORGIAN-ACADEMY -ka_GE.georgianacademy: ka_GE.GEORGIAN-ACADEMY -ka_GE.georgianrs: ka_GE.GEORGIAN-ACADEMY -ka_GE.georgianps: ka_GE.GEORGIAN-PS -kl: kl_GL.ISO8859-1 -kl_GL: kl_GL.ISO8859-1 -kl_GL.iso88591: kl_GL.ISO8859-1 -kl_GL.ISO-8859-1: kl_GL.ISO8859-1 -kl_GL.iso885915: kl_GL.ISO8859-15 -kl_GL.utf8: kl_GL.UTF-8 -kn: kn_IN.UTF-8 -kn_IN.utf8: kn_IN.UTF-8 -kn_IN.UTF-8: kn_IN.UTF-8 -ko: ko_KR.eucKR -ko.UTF-8: ko_KR.UTF-8 -ko_KR: ko_KR.eucKR -KO_KR: ko_KR.eucKR -ko_KR.EUC: ko_KR.eucKR -ko_KR.EUC-KR: ko_KR.eucKR -ko_KR.euc: ko_KR.eucKR -ko_KR.euckr: ko_KR.eucKR -ko_KR.utf8: ko_KR.UTF-8 -KO_KR.UTF-8: ko_KR.UTF-8 -ks: ks_IN.UTF-8 -ks_IN.utf8: ks_IN.UTF-8 -ks_IN.UTF-8: ks_IN.UTF-8 -ks_IN@devanagari: ks_IN@devanagari.UTF-8 -ks_IN@devanagari.utf8: ks_IN@devanagari.UTF-8 -ks_IN@devanagari.UTF-8: ks_IN@devanagari.UTF-8 -kw: kw_GB.ISO8859-1 -kw_GB: kw_GB.ISO8859-1 -kw_GB.iso88591: kw_GB.ISO8859-1 -kw_GB.ISO-8859-1: kw_GB.ISO8859-1 -kw_GB.iso885914: kw_GB.ISO8859-14 -kw_GB.ISO-8859-14: kw_GB.ISO8859-14 -kw_GB.iso885915: kw_GB.ISO8859-15 -kw_GB.ISO-8859-15: kw_GB.ISO8859-15 -ky: ky_KG.UTF-8 -ky_KG: ky_KG.UTF-8 -ky_KG.utf8: ky_KG.UTF-8 -ky_KG.UTF-8: ky_KG.UTF-8 -lo: lo_LA.MULELAO-1 -lo_LA: lo_LA.MULELAO-1 -lo_LA.cp1133: lo_LA.IBM-CP1133 -lo_LA.ibmcp1133: lo_LA.IBM-CP1133 -lo_LA.mulelao1: lo_LA.MULELAO-1 -#if defined(VeryOldFreeBSD) -XCOMM most locales in FreeBSD 2.1.[56] do not work, allow use of FreeBSD's -XCOMM generic Latin-1 locale name. N.B. "lt" is a bad code to use for a -XCOMM generic Latin-1 locale anyway because it is the country code for -XCOMM Lithuania, which by default uses Latin-7 (ISO-8859-13). -lt_LN.ISO_8859-1: lt_LN.ISO8859-1 -#endif -lt: lt_LT.ISO8859-13 -lt_LT: lt_LT.ISO8859-13 -lt_LT.iso88594: lt_LT.ISO8859-4 -lt_LT.ISO-8859-4: lt_LT.ISO8859-4 -lt_LT.ISO_8859-4: lt_LT.ISO8859-4 -lt_LT.iso885913: lt_LT.ISO8859-13 -lt_LT.ISO-8859-13: lt_LT.ISO8859-13 -lt_LT.ISO_8859-13: lt_LT.ISO8859-13 -lt_LT.utf8: lt_LT.UTF-8 -lv: lv_LV.ISO8859-13 -lv_LV: lv_LV.ISO8859-13 -lv_LV.iso88594: lv_LV.ISO8859-4 -lv_LV.ISO-8859-4: lv_LV.ISO8859-4 -lv_LV.iso885913: lv_LV.ISO8859-13 -lv_LV.ISO-8859-13: lv_LV.ISO8859-13 -lv_LV.ISO_8859-13: lv_LV.ISO8859-13 -lv_LV.utf8: lv_LV.UTF-8 -mai: mai_IN.UTF-8 -mai_IN.utf8: mai_IN.UTF-8 -mai_IN.UTF-8: mai_IN.UTF-8 -mi: mi_NZ.ISO8859-1 -mi_NZ: mi_NZ.ISO8859-1 -mi_NZ.iso88591: mi_NZ.ISO8859-1 -mk: mk_MK.ISO8859-5 -mk_MK: mk_MK.ISO8859-5 -mk_MK.iso88595: mk_MK.ISO8859-5 -mk_MK.ISO-8859-5: mk_MK.ISO8859-5 -mk_MK.cp1251: mk_MK.CP1251 -mk_MK.microsoftcp1251: mk_MK.CP1251 -mk_MK.microsoft-cp1251: mk_MK.CP1251 -mk_MK.MICROSOFT-CP1251: mk_MK.CP1251 -mk_MK.utf8: mk_MK.UTF-8 -ml: ml_IN.UTF-8 -ml_IN.utf8: ml_IN.UTF-8 -ml_IN.UTF-8: ml_IN.UTF-8 -mr: mr_IN.UTF-8 -mr_IN: mr_IN.UTF-8 -mr_IN.utf8: mr_IN.UTF-8 -mr_IN.UTF-8: mr_IN.UTF-8 -ms: ms_MY.ISO8859-1 -ms_MY: ms_MY.ISO8859-1 -ms_MY.iso88591: ms_MY.ISO8859-1 -ms_MY.ISO-8859-1: ms_MY.ISO8859-1 -mt: mt_MT.ISO8859-3 -mt_MT: mt_MT.ISO8859-3 -mt_MT.ISO-8859-3: mt_MT.ISO8859-3 -nb: nb_NO.ISO8859-1 -nb_NO: nb_NO.ISO8859-1 -nb_NO.88591: nb_NO.ISO8859-1 -nb_NO.iso88591: nb_NO.ISO8859-1 -nb_NO.ISO-8859-1: nb_NO.ISO8859-1 -nb_NO.iso885915: nb_NO.ISO8859-15 -nb_NO.ISO-8859-15: nb_NO.ISO8859-15 -nb_NO.utf8: nb_NO.UTF-8 -ne_NP.utf8: ne_NP.UTF-8 -ne_NP.UTF-8: ne_NP.UTF-8 -nl: nl_NL.ISO8859-1 -nl.ISO8859-15: nl_NL.ISO8859-15 -nl_BE: nl_BE.ISO8859-1 -nl_BE.88591: nl_BE.ISO8859-1 -nl_BE.88591.en: nl_BE.ISO8859-1 -nl_BE.iso88591: nl_BE.ISO8859-1 -nl_BE.ISO-8859-1: nl_BE.ISO8859-1 -nl_BE.ISO_8859-1: nl_BE.ISO8859-1 -nl_BE.iso885915: nl_BE.ISO8859-15 -nl_BE.ISO-8859-15: nl_BE.ISO8859-15 -nl_BE.ISO-8859-15@euro: nl_BE.ISO8859-15 -nl_BE@euro: nl_BE.ISO8859-15 -nl_BE.utf8: nl_BE.UTF-8 -nl_BE.UTF-8@euro: nl_BE.UTF-8 -nl_NL: nl_NL.ISO8859-1 -nl_NL.88591: nl_NL.ISO8859-1 -nl_NL.88591.en: nl_NL.ISO8859-1 -nl_NL.iso88591: nl_NL.ISO8859-1 -nl_NL.ISO-8859-1: nl_NL.ISO8859-1 -nl_NL.ISO_8859-1: nl_NL.ISO8859-1 -nl_NL.iso885915: nl_NL.ISO8859-15 -nl_NL.ISO-8859-15: nl_NL.ISO8859-15 -nl_NL.ISO-8859-15@euro: nl_NL.ISO8859-15 -nl_NL@euro: nl_NL.ISO8859-15 -nl_NL.utf8: nl_NL.UTF-8 -nl_NL.UTF-8@euro: nl_NL.UTF-8 -nn: nn_NO.ISO8859-1 -nn_NO: nn_NO.ISO8859-1 -nn_NO.88591: nn_NO.ISO8859-1 -nn_NO.ISO-8859-1: nn_NO.ISO8859-1 -nn_NO.ISO_8859-1: nn_NO.ISO8859-1 -nn_NO.iso885915: nn_NO.ISO8859-15 -nn_NO.ISO-8859-15: nn_NO.ISO8859-15 -nn_NO.utf8: nn_NO.UTF-8 -no: no_NO.ISO8859-1 -no_NO: no_NO.ISO8859-1 -no_NO.88591: no_NO.ISO8859-1 -no_NO.88591.en: no_NO.ISO8859-1 -no_NO.iso88591: no_NO.ISO8859-1 -no_NO.ISO-8859-1: no_NO.ISO8859-1 -no_NO.ISO8859-1@bokmal: no_NO.ISO8859-1 -no_NO.ISO8859-1@nynorsk: no_NO.ISO8859-1 -no_NO.iso885915: no_NO.ISO8859-15 -no_NO.ISO-8859-15: no_NO.ISO8859-15 -no_NO.utf8: no_NO.UTF-8 -nr: nr_ZA.ISO8859-1 -nr_ZA: nr_ZA.ISO8859-1 -nr_ZA.iso88591: nr_ZA.ISO8859-1 -nr_ZA.utf8: nr_ZA.UTF-8 -nso: nso_ZA.ISO8859-15 -nso_ZA: nso_ZA.ISO8859-15 -nso_ZA.iso885915: nso_ZA.ISO8859-15 -nso_ZA.utf8: nso_ZA.UTF-8 -ny: ny_NO.ISO8859-1 -ny_NO: ny_NO.ISO8859-1 -ny_NO.88591: ny_NO.ISO8859-1 -ny_NO.ISO_8859-1: ny_NO.ISO8859-1 -ny_NO.iso885915: ny_NO.ISO8859-15 -no@nynorsk: ny_NO.ISO8859-1 -nynorsk: nn_NO.ISO8859-1 -oc: oc_FR.ISO8859-1 -oc_FR: oc_FR.ISO8859-1 -oc_FR.iso88591: oc_FR.ISO8859-1 -oc_FR.ISO-8859-1: oc_FR.ISO8859-1 -oc_FR.iso885915: oc_FR.ISO8859-15 -oc_FR.ISO-8859-15: oc_FR.ISO8859-15 -oc_FR@euro: oc_FR.ISO8859-15 -or: or_IN.UTF-8 -or_IN.utf8: or_IN.UTF-8 -or_IN.UTF-8: or_IN.UTF-8 -pa: pa_IN.UTF-8 -pa_IN.utf8: pa_IN.UTF-8 -pa_IN.UTF-8: pa_IN.UTF-8 -pa_PK.utf8: pa_PK.UTF-8 -pd: pd_US.ISO8859-1 -pd_DE: pd_DE.ISO8859-1 -pd_US: pd_US.ISO8859-1 -pd_DE.iso88591: pd_DE.ISO8859-1 -pd_US.iso88591: pd_US.ISO8859-1 -pd_DE.iso885915: pd_DE.ISO8859-15 -pd_US.iso885915: pd_US.ISO8859-15 -ph: ph_PH.ISO8859-1 -ph_PH: ph_PH.ISO8859-1 -ph_PH.iso88591: ph_PH.ISO8859-1 -pl: pl_PL.ISO8859-2 -pl.UTF-8: pl_PL.UTF-8 -pl_PL: pl_PL.ISO8859-2 -pl_PL.iso88592: pl_PL.ISO8859-2 -pl_PL.ISO-8859-2: pl_PL.ISO8859-2 -pl_PL.utf8: pl_PL.UTF-8 -pp: pp_AN.ISO8859-1 -pp_AN: pp_AN.ISO8859-1 -pp_AN.iso88591: pp_AN.ISO8859-1 -pt: pt_PT.ISO8859-1 -pt.ISO8859-15: pt_PT.ISO8859-15 -pt_BR: pt_BR.ISO8859-1 -pt_BR.88591: pt_BR.ISO8859-1 -pt_BR.88591.en: pt_BR.ISO8859-1 -pt_BR.iso88591: pt_BR.ISO8859-1 -pt_BR.ISO-8859-1: pt_BR.ISO8859-1 -pt_BR.ISO_8859-1: pt_BR.ISO8859-1 -pt_BR.iso885915: pt_BR.ISO8859-15 -pt_BR.utf8: pt_BR.UTF-8 -pt_PT: pt_PT.ISO8859-1 -pt_PT.88591: pt_PT.ISO8859-1 -pt_PT.88591.en: pt_PT.ISO8859-1 -pt_PT.iso88591: pt_PT.ISO8859-1 -pt_PT.ISO-8859-1: pt_PT.ISO8859-1 -pt_PT.ISO_8859-1: pt_PT.ISO8859-1 -pt_PT.iso885915: pt_PT.ISO8859-15 -pt_PT.ISO-8859-15: pt_PT.ISO8859-15 -pt_PT.ISO-8859-15@euro: pt_PT.ISO8859-15 -pt_PT@euro: pt_PT.ISO8859-15 -pt_PT.utf8: pt_PT.UTF-8 -pt_PT.UTF-8@euro: pt_PT.UTF-8 -ro: ro_RO.ISO8859-2 -ro_RO: ro_RO.ISO8859-2 -ro_RO.iso88592: ro_RO.ISO8859-2 -ro_RO.ISO-8859-2: ro_RO.ISO8859-2 -ro_RO.utf8: ro_RO.UTF-8 -ru: ru_RU.UTF-8 -ru.koi8-r: ru_RU.KOI8-R -ru.UTF-8: ru_RU.UTF-8 -ru_RU: ru_RU.UTF-8 -ru_RU.utf8: ru_RU.UTF-8 -ru_RU.iso88595: ru_RU.ISO8859-5 -ru_RU.ISO-8859-5: ru_RU.ISO8859-5 -ru_RU.koi8r: ru_RU.KOI8-R -ru_RU.cp1251: ru_RU.CP1251 -ru_RU.microsoftcp1251: ru_RU.CP1251 -ru_RU.microsoft-cp1251: ru_RU.CP1251 -ru_RU.MICROSOFT-CP1251: ru_RU.CP1251 -#if defined(INCLUDE_ru_SU) -XCOMM ru_SU is redundant now -ru_SU: ru_RU.KOI8-R -ru_SU.ISO8859-5: ru_RU.ISO8859-5 -ru_SU.KOI8-R: ru_RU.KOI8-R -#endif -ru_UA: ru_UA.KOI8-U -ru_UA.koi8u: ru_UA.KOI8-U -ru_UA.cp1251: ru_UA.CP1251 -ru_UA.microsoftcp1251: ru_UA.CP1251 -ru_UA.microsoft-cp1251: ru_UA.CP1251 -ru_UA.MICROSOFT-CP1251: ru_UA.CP1251 -rw: rw_RW.ISO8859-1 -rw_RW: rw_RW.ISO8859-1 -rw_RW.iso8859-1: rw_RW.ISO8859-1 -rw_RW.ISO-8859-1: rw_RW.ISO8859-1 -rw_RW.utf8: rw_RW.UTF-8 -sd: sd_IN.UTF-8 -sd_IN.utf8: sd_IN.UTF-8 -sd: sd_IN@devanagari.UTF-8 -sd_IN@devanagari.utf8: sd_IN@devanagari.UTF-8 -sd_IN@devanagari.UTF-8: sd_IN@devanagari.UTF-8 -se_NO: se_NO.UTF-8 -se_NO.utf8: se_NO.UTF-8 -XCOMM sh was the old ISO code for Serbo-Croatian (now individual sr and hr). -XCOMM YU was the old ISO code for Yugoslavia (later CS for Serbia&Montenegro). -XCOMM CS was the old ISO code for Serbia&Montenegro (now separate RS and ME). -XCOMM These lines should be deleted in the future. -sh: sr_RS.UTF-8@latin -sh_BA.ISO8859-2@bosnia: sr_CS.ISO8859-2 -sh_HR.iso88592: hr_HR.ISO8859-2 -sh_YU: sr_RS.UTF-8@latin -sh_YU.utf8: sr_RS.UTF-8@latin -si: si_LK.UTF-8 -si_LK: si_LK.UTF-8 -sk: sk_SK.ISO8859-2 -sk_SK: sk_SK.ISO8859-2 -sk_SK.iso88592: sk_SK.ISO8859-2 -sk_SK.ISO-8859-2: sk_SK.ISO8859-2 -sk_SK.utf8: sk_SK.UTF-8 -sl: sl_SI.ISO8859-2 -sl_SI: sl_SI.ISO8859-2 -sl_SI.iso88592: sl_SI.ISO8859-2 -sl_SI.ISO-8859-2: sl_SI.ISO8859-2 -sl_SI.utf8: sl_SI.UTF-8 -sq: sq_AL.ISO8859-2 -sq_AL: sq_AL.ISO8859-2 -sq_AL.iso88592: sq_AL.ISO8859-2 -sq_AL.ISO-8859-2: sq_AL.ISO8859-2 -sq_AL.utf8: sq_AL.UTF-8 -XCOMM YU was the old ISO code for Yugoslavia (later CS for Serbia&Montenegro). -XCOMM CS was the old ISO code for Serbia&Montenegro (now separate RS and ME). -XCOMM Some of these lines should be deleted in the future. -sr: sr_RS.UTF-8 -sr_YU: sr_RS.UTF-8@latin -sr@cyrillic: sr_RS.UTF-8 -sr_YU@cyrillic: sr_RS.UTF-8 -sr_YU.utf8: sr_RS.UTF-8 -sr_YU.UTF-8@cyrillic: sr_RS.UTF-8 -sr_CS: sr_RS.UTF-8 -sr@Latn: sr_RS.UTF-8@latin -sr_CS@Latn: sr_RS.UTF-8@latin -sr_CS.utf8: sr_RS.UTF-8 -sr_CS.UTF-8@Latn: sr_RS.UTF-8@latin -sr_RS: sr_RS.UTF-8 -sr@latin: sr_RS.UTF-8@latin -sr_RS@latin: sr_RS.UTF-8@latin -sr_RS@Latn: sr_RS.UTF-8@latin -sr_RS.UTF-8@Latn: sr_RS.UTF-8@latin -sr_RS.utf8: sr_RS.UTF-8 -sr_ME: sr_ME.UTF-8 -sr_ME.utf8: sr_ME.UTF-8 -ss: ss_ZA.ISO8859-1 -ss_ZA: ss_ZA.ISO8859-1 -ss_ZA.iso88591: ss_ZA.ISO8859-1 -ss_ZA.utf8: ss_ZA.UTF-8 -st: st_ZA.ISO8859-1 -st_ZA: st_ZA.ISO8859-1 -st_ZA.iso88591: st_ZA.ISO8859-1 -st_ZA.utf8: st_ZA.UTF-8 -sv: sv_SE.ISO8859-1 -sv.ISO8859-15: sv_SE.ISO8859-15 -sv.UTF-8: sv_SE.UTF-8 -sv_FI: sv_FI.ISO8859-1 -sv_FI.iso88591: sv_FI.ISO8859-1 -sv_FI.ISO-8859-1: sv_FI.ISO8859-1 -sv_FI.iso885915: sv_FI.ISO8859-15 -sv_FI.ISO-8859-15: sv_FI.ISO8859-15 -sv_FI.ISO-8859-15@euro: sv_FI.ISO8859-15 -sv_FI@euro: sv_FI.ISO8859-15 -sv_FI.UTF-8@euro: sv_FI.UTF-8 -sv_FI.utf8: sv_FI.UTF-8 -sv_SE: sv_SE.ISO8859-1 -sv_SE.88591: sv_SE.ISO8859-1 -sv_SE.88591.en: sv_SE.ISO8859-1 -sv_SE.iso88591: sv_SE.ISO8859-1 -sv_SE.ISO-8859-1: sv_SE.ISO8859-1 -sv_SE.ISO_8859-1: sv_SE.ISO8859-1 -sv_SE.iso885915: sv_SE.ISO8859-15 -sv_SE.ISO-8859-15: sv_SE.ISO8859-15 -sv_SE@euro: sv_SE.ISO8859-15 -sv_SE.utf8: sv_SE.UTF-8 -ta: ta_IN.TSCII-0 -ta_IN: ta_IN.TSCII-0 -ta_IN.tscii: ta_IN.TSCII-0 -ta_IN.tscii0: ta_IN.TSCII-0 -te: te_IN.UTF-8 -te_IN.utf8: te_IN.UTF-8 -te_IN.UTF-8: te_IN.UTF-8 -tg: tg_TJ.KOI8-C -tg_TJ: tg_TJ.KOI8-C -tg_TJ.koi8c: tg_TJ.KOI8-C -th: th_TH.ISO8859-11 -th_TH: th_TH.ISO8859-11 -th_TH.ISO-8859-11: th_TH.ISO8859-11 -th_TH.tis620: th_TH.TIS620 -th_TH.TIS-620: th_TH.TIS620 -th_TH.TACTIS: th_TH.TIS620 -th_TH.utf8: th_TH.UTF-8 -tl: tl_PH.ISO8859-1 -tl_PH: tl_PH.ISO8859-1 -tl_PH.iso88591: tl_PH.ISO8859-1 -tl_PH.ISO-8859-1: tl_PH.ISO8859-1 -tn: tn_ZA.ISO8859-15 -tn_ZA: tn_ZA.ISO8859-15 -tn_ZA.iso8859-15: tn_ZA.ISO8859-15 -tn_ZA.utf8: tn_ZA.UTF-8 -tr: tr_TR.ISO8859-9 -tr_TR: tr_TR.ISO8859-9 -TR_TR: tr_TR.ISO8859-9 -tr_TR.iso88599: tr_TR.ISO8859-9 -tr_TR.ISO-8859-9: tr_TR.ISO8859-9 -tr_TR.utf8: tr_TR.UTF-8 -TR_TR.utf8: tr_TR.UTF-8 -ts: ts_ZA.ISO8859-1 -ts_ZA: ts_ZA.ISO8859-1 -ts_ZA.iso88591: ts_ZA.ISO8859-1 -ts_ZA.utf8: ts_ZA.UTF-8 -tt: tt_RU.TATAR-CYR -tt_RU: tt_RU.TATAR-CYR -tt_RU.tatarcyr: tt_RU.TATAR-CYR -tt_RU.koi8c: tt_RU.KOI8-C -uk: uk_UA.KOI8-U -uk_UA: uk_UA.KOI8-U -uk_UA.iso88595: uk_UA.ISO8859-5 -uk_UA.koi8u: uk_UA.KOI8-U -uk_UA.cp1251: uk_UA.CP1251 -uk_UA.microsoftcp1251: uk_UA.CP1251 -uk_UA.microsoft-cp1251: uk_UA.CP1251 -uk_UA.MICROSOFT-CP1251: uk_UA.CP1251 -uk_UA.utf8: uk_UA.UTF-8 -ur: ur_IN.UTF-8 -ur_IN.utf8: ur_IN.UTF-8 -ur_IN.UTF-8: ur_IN.UTF-8 -ur: ur_PK.CP1256 -ur_PK: ur_PK.CP1256 -ur_PK.cp1256: ur_PK.CP1256 -ur_PK.microsoftcp1256: ur_PK.CP1256 -ur_PK.microsoft-cp1256: ur_PK.CP1256 -ur_PK.MICROSOFT-CP1256: ur_PK.CP1256 -uz: uz_UZ.UTF-8 -uz_UZ: uz_UZ.UTF-8 -uz_UZ.ISO-8859-1: uz_UZ.ISO8859-1 -uz_UZ@cyrillic: uz_UZ.UTF-8 -uz_UZ.UTF-8@cyrillic: uz_UZ.UTF-8 -ve: ve_ZA.UTF-8 -ve_ZA: ve_ZA.UTF-8 -ve_ZA.utf8: ve_ZA.UTF-8 -vi: vi_VN.TCVN -vi_VN: vi_VN.TCVN -Vi_VN: vi_VN.TCVN -VI_VN: vi_VN.TCVN -vi_VN.tcvn: vi_VN.TCVN -vi_VN.tcvn5712: vi_VN.TCVN -vi_VN.viscii: vi_VN.VISCII -vi_VN.viscii111: vi_VN.VISCII -vi_VN.utf8: vi_VN.UTF-8 -VI_VN.UTF-8: vi_VN.UTF-8 -wa: wa_BE.ISO8859-1 -wa_BE: wa_BE.ISO8859-1 -wa_BE.iso88591: wa_BE.ISO8859-1 -wa_BE.ISO-8859-1: wa_BE.ISO8859-1 -wa_BE.iso885915: wa_BE.ISO8859-15 -wa_BE.ISO-8859-15: wa_BE.ISO8859-15 -wa_BE.ISO-8859-15@euro: wa_BE.ISO8859-15 -wa_BE@euro: wa_BE.ISO8859-15 -xh: xh_ZA.ISO8859-1 -xh_ZA: xh_ZA.ISO8859-1 -xh_ZA.iso88591: xh_ZA.ISO8859-1 -xh_ZA.utf8: xh_ZA.UTF-8 -yi: yi_US.CP1255 -yi_US: yi_US.CP1255 -yi_US.cp1255: yi_US.CP1255 -yi_US.microsoftcp1255: yi_US.CP1255 -yi_US.microsoft-cp1255: yi_US.CP1255 -yi_US.MICROSOFT-CP1255: yi_US.CP1255 -zh_CN: zh_CN.gb2312 -zh_CN.Big5: zh_TW.big5 -zh_CN.EUC: zh_CN.eucCN -zh_CN.GB2312: zh_CN.gb2312 -zh_CN.GBK: zh_CN.gbk -zh_CN.GB18030: zh_CN.gb18030 -zh_CN.big5: zh_TW.big5 -zh_CN.euc: zh_CN.eucCN -zh_CN.utf8: zh_CN.UTF-8 -ZH_CN.UTF-8: zh_CN.UTF-8 -zh_HK: zh_HK.big5hkscs -zh_HK.BIG5HK: zh_HK.big5hkscs -zh_HK.Big5hkscs: zh_HK.big5hkscs -zh_HK.Big5-hkscs: zh_HK.big5hkscs -zh_HK.Big5_hkscs: zh_HK.big5hkscs -zh_HK.Big5HKSCS: zh_HK.big5hkscs -zh_HK.BIG5-HKSCS: zh_HK.big5hkscs -zh_HK.BIG5_HKSCS: zh_HK.big5hkscs -zh_HK.Big5: zh_HK.big5 -zh_HK.utf8: zh_HK.UTF-8 -ZH_HK.UTF-8: zh_HK.UTF-8 -ZH_SG.UTF-8: zh_SG.UTF-8 -zh_TW: zh_TW.big5 -zh_TW.Big5: zh_TW.big5 -zh_TW.BIG5: zh_TW.big5 -Zh_TW.big5: zh_TW.big5 -zh_TW.EUC: zh_TW.eucTW -zh_TW.EUC-TW: zh_TW.eucTW -zh_TW.utf8: zh_TW.UTF-8 -ZH_TW.UTF-8: zh_TW.UTF-8 -zu: zu_ZA.ISO8859-1 -zu_ZA: zu_ZA.ISO8859-1 -zu_ZA.iso88591: zu_ZA.ISO8859-1 -zu_ZA.utf8: zu_ZA.UTF-8 - -XCOMM The following locale names are used in SCO 3.0 -english_uk.8859: en_GB.ISO8859-1 -english_us.8859: en_US.ISO8859-1 -english_us.ascii: en_US.ISO8859-1 -french_france.8859: fr_FR.ISO8859-1 -german_germany.8859: de_DE.ISO8859-1 -portuguese_brazil.8859: pt_BR.ISO8859-1 -spanish_spain.8859: es_ES.ISO8859-1 -XCOMM The following locale names are used in HPUX 9.x -american.iso88591: en_US.ISO8859-1 -arabic.iso88596: ar_AA.ISO8859-6 -bokmal: nb_NO.ISO8859-1 -bokmål: nb_NO.ISO8859-1 -bulgarian: bg_BG.CP1251 -c-french.iso88591: fr_CA.ISO8859-1 -catalan: ca_ES.ISO8859-1 -chinese-s: zh_CN.eucCN -chinese-t: zh_TW.eucTW -croatian: hr_HR.ISO8859-2 -czech: cs_CZ.ISO8859-2 -danish: da_DK.ISO8859-1 -dansk: da_DK.ISO8859-1 -danish.iso88591: da_DK.ISO8859-1 -deutsch: de_DE.ISO8859-1 -dutch: nl_NL.ISO8859-1 -dutch.iso88591: nl_BE.ISO8859-1 -eesti: et_EE.ISO8859-1 -english.iso88591: en_EN.ISO8859-1 -estonian: et_EE.ISO8859-1 -finnish: fi_FI.ISO8859-1 -finnish.iso88591: fi_FI.ISO8859-1 -français: fr_FR.ISO8859-1 -french: fr_FR.ISO8859-1 -french.iso88591: fr_CH.ISO8859-1 -galego: gl_ES.ISO8859-1 -galician: gl_ES.ISO8859-1 -german: de_DE.ISO8859-1 -german.iso88591: de_CH.ISO8859-1 -greek: el_GR.ISO8859-7 -greek.iso88597: el_GR.ISO8859-7 -hebrew: iw_IL.ISO8859-8 -hebrew.iso88598: iw_IL.ISO8859-8 -hrvatski: hr_HR.ISO8859-2 -hungarian: hu_HU.ISO8859-2 -icelandic.iso88591: is_IS.ISO8859-1 -icelandic: is_IS.ISO8859-1 -italian: it_IT.ISO8859-1 -italian.iso88591: it_IT.ISO8859-1 -japanese: ja_JP.eucJP -japanese.euc: ja_JP.eucJP -japanese.sjis: ja_JP.SJIS -korean: ko_KR.eucKR -korean.euc: ko_KR.eucKR -lithuanian: lt_LT.ISO8859-13 -norwegian: no_NO.ISO8859-1 -norwegian.iso88591: no_NO.ISO8859-1 -polish: pl_PL.ISO8859-2 -portuguese: pt_PT.ISO8859-1 -portuguese.iso88591: pt_PT.ISO8859-1 -romanian: ro_RO.ISO8859-2 -rumanian: ro_RO.ISO8859-2 -russian: ru_RU.ISO8859-5 -serbocroatian: sr_RS.UTF-8@latin -sinhala: si_LK.UTF-8 -slovak: sk_SK.ISO8859-2 -slovene: sl_SI.ISO8859-2 -slovenian: sl_SI.ISO8859-2 -spanish: es_ES.ISO8859-1 -spanish.iso88591: es_ES.ISO8859-1 -swedish: sv_SE.ISO8859-1 -swedish.iso88591: sv_SE.ISO8859-1 -turkish: tr_TR.ISO8859-9 -turkish.iso88599: tr_TR.ISO8859-9 -thai: th_TH.ISO8859-11 -univ.utf8: en_US.UTF-8 -XCOMM Digital Unix utf -universal.utf8@ucs4: en_US.UTF-8 -XCOMM Solaris and SunOS have iso_8859_1 and iso_8859_15 LC_CTYPES -XCOMM to augment LANG=C -iso_8859_1: en_US.ISO8859-1 -iso_8859_15: en_US.ISO8859-15 -#ifdef WIN32 -XCOMM Microsoft Windows/NT 4.0 SP3 -XCOMM parser doesn't grok embedded spaces in locale name -Afrikaans_South Africa.1252: af_ZA.iso8859-1 -Arabic_Bahrain.1256: ar_BH.iso8859-6 -Arabic_Algeria.1256: ar_DZ.iso8859-6 -Arabic_Egypt.1256: ar_EG.iso8859-6 -Arabic_Iraq.1256: ar_IQ.iso8859-6 -Arabic_Jordan.1256: ar_JO.iso8859-6 -Arabic_Kuwait.1256: ar_KW.iso8859-6 -Arabic_Lebanon.1256: ar_LB.iso8859-6 -Arabic_Libya.1256: ar_LY.iso8859-6 -Arabic_Morocco.1256: ar_MA.iso8859-6 -Arabic_Oman.1256: ar_OM.iso8859-6 -Arabic_Qatar.1256: ar_QA.iso8859-6 -Arabic_Saudi Arabia.1256: ar_SA.iso8859-6 -Arabic_Tunisia.1256: ar_TN.iso8859-6 -Arabic_Yemen.1256: ar_YE.iso8859-6 -Belarusian_Belarus.1251: be_BY.iso8859-5 -Bulgarian_Bulgaria.1251: bg_BG.iso8859-5 -Catalan_Andorra.1252: ca_AD.iso8859-1 -Catalan_Spain.1252: ca_ES.iso8859-1 -Catalan_France.1252: ca_FR.iso8859-1 -Catalan_Italy.1252: ca_IT.iso8859-1 -Czech_Czech Republic.1250: cs_CZ.iso8859-2 -Danish_Denmark.1252: da_DK.iso8859-1 -German_Austria.1252: de_AT.iso8859-1 -German_Switzerland.1252: de_CH.iso8859-1 -German_Germany.1252: de_DE.iso8859-1 -German_Liechtenstein.1252: de_LI.iso8859-1 -German_Luxembourg.1252: de_LU.iso8859-1 -Greek_Greece.1253: el_GR.iso8859-7 -English_Australia.1252: en_AU.iso8859-1 -English_Belize.1252: en_BZ.iso8859-1 -English_Canada.1252: en_CA.iso8859-1 -English_Ireland.1252: en_IE.iso8859-1 -English_Jamaica.1252: en_JM.iso8859-1 -English_New Zealand.1252: en_NZ.iso8859-1 -English_Trinidad y Tobago.1252: en_TT.iso8859-1 -English_United Kingdom.1252: en_UK.iso8859-1 -English_United States.1252: en_US.iso8859-1 -English_South Africa.1252: en_ZA.iso8859-1 -Spanish_Argentina.1252: es_AR.iso8859-1 -Spanish_Bolivia.1252: es_BO.iso8859-1 -Spanish_Chile.1252: es_CL.iso8859-1 -Spanish_Colombia.1252: es_CO.iso8859-1 -Spanish_Costa Rica.1252: es_CR.iso8859-1 -Spanish_Dominican Republic.1252: es_DO.iso8859-1 -Spanish_Ecuador.1252: es_EC.iso8859-1 -Spanish - Modern Sort_Spain.1252: es_ES.iso8859-1 -Spanish - Traditional Sort_Spain.1252: es_ES.iso8859-1 -Spanish_Guatemala.1252: es_GT.iso8859-1 -Spanish_Honduras.1252: es_HN.iso8859-1 -Spanish_Mexican.1252: es_MX.iso8859-1 -Spanish_Nicaragua.1252: es_NI.iso8859-1 -Spanish_Panama.1252: es_PA.iso8859-1 -Spanish_Paraguay.1252: es_PY.iso8859-1 -Spanish_Peru.1252: es_PE.iso8859-1 -Spanish_Puerto Rico.1252: es_PR.iso8859-1 -Spanish_El Salvador.1252: es_SV.iso8859-1 -Spanish_Uruguay.1252: es_UY.iso8859-1 -Spanish_Venezuela.1252: es_VE.iso8859-1 -Estonian_Estonia.1257: et_EE.iso8859-13 -Basque_Spain.1252: eu_ES.iso8859-1 -Finnish_Finland.1252: fi_FI.iso8859-1 -French_Belgium.1252: fr_BE.iso8859-1 -French_Canada.1252: fr_CA.iso8859-1 -French_Switzerland.1252: fr_CH.iso8859-1 -French_France.1252: fr_FR.iso8859-1 -French_Luxembourg.1252: fr_LU.iso8859-1 -Faeroese_Faeroe Islands.1252: fo_FO.iso8859-1 -Hebrew_Israel.1255: he_IL.iso8859-8 -Croatian_Croatia.1250: hr_HR.iso8859-2 -Hungarian_Hungary.1250: hu_HU.iso8859-2 -Indonesian_Indonesia.1252: id_ID.iso8859-1 -Icelandic_Iceland.1252: is_IS.iso8859-1 -Italian_Switzerland.1252: it_CH.iso8859-1 -Italian_Italy.1252: it_IT.iso8859-1 -Japanese_Japan.932: ja_JP.SJIS -Korean_Korea.949: ko_KR.EUC -Lithuanian_Lithuania.1257: lt_LT.iso8859-13 -Latvian_Latvia.1257: lv_LV.iso8859-13 -Dutch_Belgium.1252: nl_BE.iso8859-1 -Dutch_Netherlands.1252: nl_NL.iso8859-1 -Norwegian (Nynorsk)_Norway.1252: no_NO.iso8859-1 -Norwegian (Bokmål)_Norway.1252: no_NO.iso8859-1 -Polish_Poland.1250: pl_PL.iso8859-2 -Portuguese_Brazil.1252: pt_BR.iso8859-1 -Portuguese_Portugal.1252: pt_PT.iso8859-1 -Romanian_Romania.1250: ro_RO.iso8859-2 -Russian_Russia.1251: ru_RU.iso8859-5 -Slovak_Slovakia.1250: sk_SK.iso8859-2 -Slovene_Slovenia.1250: sl_SI.iso8859-2 -Albanian_Albania.1250: sq_AL.iso8859-2 -Serbian (Latin)_Serbia.1250: sr_RS.UTF-8@latin -Swedish_Finland.1252: sv_FI.iso8859-1 -Swedish_Sweden.1252: sv_SE.iso8859-1 -Turkish_Turkey.1254: tr_TR.iso8859-9 -Ukrainian_Ukraine.1251: uk_UA.iso8859-5 -Chinese(PRC)_People's Republic of China.936: zh_CN.EUC -Chinese(PRC)_Hong Kong.950: zh_HK.EUC -Chinese(Singapore)_Signapore.936: zh_SG.EUC -Chinese(Taiwan)_Taiwan.950: zh_TW.EUC -#endif -XCOMM Other miscellaneous locale names -ISO8859-1: en_US.ISO8859-1 -ISO-8859-1: en_US.ISO8859-1 -#ifndef __uxp__ -japan: ja_JP.eucJP -#else -japan: ja_JP.U90 -#endif -Japanese-EUC: ja_JP.eucJP +XCOMM +XCOMM This file contains alias name of locale. +XCOMM Each alias name is described within one line. +XCOMM The first word is the alias name (simplified locale name) +XCOMM the second word is full locale name. +XCOMM +XCOMM + +POSIX: C +POSIX-UTF2: C +C_C.C: C +C.en: C +C.ASCII: C +C.iso88591: en_US.ISO8859-1 +Cextend: en_US.ISO8859-1 +Cextend.en: en_US.ISO8859-1 +English_United-States.437: C +C.UTF-8: en_US.UTF-8 +XCOMM a3 is not an ISO 639 language code, but in Cyrillic, "Z" looks like "3". +a3: a3_AZ.KOI8-C +a3_AZ: a3_AZ.KOI8-C +a3_AZ.koi8c: a3_AZ.KOI8-C +af: af_ZA.ISO8859-1 +af_ZA: af_ZA.ISO8859-1 +af_ZA.iso88591: af_ZA.ISO8859-1 +af_ZA.ISO-8859-1: af_ZA.ISO8859-1 +af_ZA.utf8: af_ZA.UTF-8 +am: am_ET.UTF-8 +am_ET: am_ET.UTF-8 +ar: ar_AA.ISO8859-6 +ar_AA: ar_AA.ISO8859-6 +AR_AA: ar_AA.ISO8859-6 +Ar_AA: ar_AA.ISO8859-6 +AR_AA.UTF-8: ar_AA.UTF-8 +ar_AA.iso88596: ar_AA.ISO8859-6 +ar_AA.ISO-8859-6: ar_AA.ISO8859-6 +ar_AE: ar_AE.ISO8859-6 +ar_AE.iso88596: ar_AE.ISO8859-6 +ar_AE.ISO-8859-6: ar_AE.ISO8859-6 +ar_AE.utf8: ar_AE.UTF-8 +ar_BH: ar_BH.ISO8859-6 +ar_BH.iso88596: ar_BH.ISO8859-6 +ar_BH.ISO-8859-6: ar_BH.ISO8859-6 +ar_BH.utf8: ar_BH.UTF-8 +ar_DZ: ar_DZ.ISO8859-6 +ar_DZ.iso88596: ar_DZ.ISO8859-6 +ar_DZ.ISO-8859-6: ar_DZ.ISO8859-6 +ar_DZ.utf8: ar_DZ.UTF-8 +ar_EG: ar_EG.ISO8859-6 +ar_EG.iso88596: ar_EG.ISO8859-6 +ar_EG.ISO-8859-6: ar_EG.ISO8859-6 +ar_EG.utf8: ar_EG.UTF-8 +ar_IN.utf8: ar_IN.UTF-8 +ar_IQ: ar_IQ.ISO8859-6 +ar_IQ.iso88596: ar_IQ.ISO8859-6 +ar_IQ.ISO-8859-6: ar_IQ.ISO8859-6 +ar_IQ.utf8: ar_IQ.UTF-8 +ar_JO: ar_JO.ISO8859-6 +ar_JO.iso88596: ar_JO.ISO8859-6 +ar_JO.ISO-8859-6: ar_JO.ISO8859-6 +ar_JO.utf8: ar_JO.UTF-8 +ar_KW: ar_KW.ISO8859-6 +ar_KW.iso88596: ar_KW.ISO8859-6 +ar_KW.ISO-8859-6: ar_KW.ISO8859-6 +ar_KW.utf8: ar_KW.UTF-8 +ar_LB: ar_LB.ISO8859-6 +ar_LB.iso88596: ar_LB.ISO8859-6 +ar_LB.ISO-8859-6: ar_LB.ISO8859-6 +ar_LB.utf8: ar_LB.UTF-8 +ar_LY: ar_LY.ISO8859-6 +ar_LY.iso88596: ar_LY.ISO8859-6 +ar_LY.ISO-8859-6: ar_LY.ISO8859-6 +ar_LY.utf8: ar_LY.UTF-8 +ar_MA: ar_MA.ISO8859-6 +ar_MA.iso88596: ar_MA.ISO8859-6 +ar_MA.ISO-8859-6: ar_MA.ISO8859-6 +ar_MA.utf8: ar_MA.UTF-8 +ar_OM: ar_OM.ISO8859-6 +ar_OM.iso88596: ar_OM.ISO8859-6 +ar_OM.ISO-8859-6: ar_OM.ISO8859-6 +ar_OM.utf8: ar_OM.UTF-8 +ar_QA: ar_QA.ISO8859-6 +ar_QA.iso88596: ar_QA.ISO8859-6 +ar_QA.ISO-8859-6: ar_QA.ISO8859-6 +ar_QA.utf8: ar_QA.UTF-8 +ar_SA: ar_SA.ISO8859-6 +ar_SA.iso88596: ar_SA.ISO8859-6 +ar_SA.ISO-8859-6: ar_SA.ISO8859-6 +ar_SA.utf8: ar_SA.UTF-8 +ar_SD: ar_SD.ISO8859-6 +ar_SD.iso88596: ar_SD.ISO8859-6 +ar_SD.ISO-8859-6: ar_SD.ISO8859-6 +ar_SD.utf8: ar_SD.UTF-8 +ar_SY: ar_SY.ISO8859-6 +ar_SY.iso88596: ar_SY.ISO8859-6 +ar_SY.ISO-8859-6: ar_SY.ISO8859-6 +ar_SY.utf8: ar_SY.UTF-8 +ar_TN: ar_TN.ISO8859-6 +ar_TN.iso88596: ar_TN.ISO8859-6 +ar_TN.ISO-8859-6: ar_TN.ISO8859-6 +ar_TN.utf8: ar_TN.UTF-8 +as: as_IN.UTF-8 +as_IN.utf8: as_IN.UTF-8 +ar_YE: ar_YE.ISO8859-6 +ar_YE.iso88596: ar_YE.ISO8859-6 +ar_YE.ISO-8859-6: ar_YE.ISO8859-6 +ar_YE.utf8: ar_YE.UTF-8 +az: az_AZ.ISO8859-9E +az_AZ: az_AZ.ISO8859-9E +az_AZ.iso88599e: az_AZ.ISO8859-9E +be: be_BY.CP1251 +be@latin: be_BY.UTF-8@latin +be_BY: be_BY.CP1251 +be_BY@latin: be_BY.UTF-8@latin +be_BY.cp1251: be_BY.CP1251 +be_BY.microsoftcp1251: be_BY.CP1251 +be_BY.microsoft-cp1251: be_BY.CP1251 +be_BY.MICROSOFT-CP1251: be_BY.CP1251 +be_BY.utf8: be_BY.UTF-8 +be_BY.utf8@latin: be_BY.UTF-8@latin +bg: bg_BG.CP1251 +bg_BG: bg_BG.CP1251 +bg_BG.cp1251: bg_BG.CP1251 +bg_BG.microsoftcp1251: bg_BG.CP1251 +bg_BG.microsoft-cp1251: bg_BG.CP1251 +bg_BG.MICROSOFT-CP1251: bg_BG.CP1251 +bg_BG.iso88595: bg_BG.ISO8859-5 +bg_BG.ISO-8859-5: bg_BG.ISO8859-5 +bg_BG.koi8r: bg_BG.KOI8-R +be_BG.utf8: bg_BG.UTF-8 +bn_IN.utf8: bn_IN.UTF-8 +bo_IN.utf8: bo_IN.UTF-8 +br: br_FR.ISO8859-1 +br_FR: br_FR.ISO8859-1 +br_FR.iso88591: br_FR.ISO8859-1 +br_FR.ISO-8859-1: br_FR.ISO8859-1 +br_FR.iso885914: br_FR.ISO8859-14 +br_FR.ISO-8859-14: br_FR.ISO8859-14 +br_FR.iso885915: br_FR.ISO8859-15 +br_FR.ISO-8859-15: br_FR.ISO8859-15 +br_FR.ISO-8859-15@euro: br_FR.ISO8859-15 +br_FR@euro: br_FR.ISO8859-15 +br_FR.UTF-8@euro: br_FR.UTF-8 +bs: bs_BA.ISO8859-2 +bs_BA: bs_BA.ISO8859-2 +bs_BA.iso88592: bs_BA.ISO8859-2 +bs_BA.ISO-8859-2: bs_BA.ISO8859-2 +bs_BA.ISO_8859-2: bs_BA.ISO8859-2 +ca: ca_ES.ISO8859-1 +ca_AD: ca_AD.ISO8859-1 +ca_AD@euro: ca_AD.ISO8859-15 +ca_AD.iso88591: ca_AD.ISO8859-1 +ca_AD.ISO-8859-1: ca_AD.ISO8859-1 +ca_AD.iso885915: ca_AD.ISO8859-15 +ca_AD.utf8: ca_AD.UTF-8 +ca_AD.ISO-8859-15: ca_AD.ISO8859-15 +ca_AD.ISO-8859-15@euro: ca_AD.ISO8859-15 +ca_AD.UTF-8@euro: ca_AD.UTF-8 +ca_ES: ca_ES.ISO8859-1 +ca_ES@euro: ca_ES.ISO8859-15 +ca_ES.iso88591: ca_ES.ISO8859-1 +ca_ES.ISO-8859-1: ca_ES.ISO8859-1 +ca_ES.iso885915: ca_ES.ISO8859-15 +ca_ES.utf8: ca_ES.UTF-8 +ca_ES.ISO-8859-15: ca_ES.ISO8859-15 +ca_ES.ISO-8859-15@euro: ca_ES.ISO8859-15 +ca_ES.UTF-8@euro: ca_ES.UTF-8 +ca_FR: ca_FR.ISO8859-1 +ca_FR@euro: ca_FR.ISO8859-15 +ca_FR.iso88591: ca_FR.ISO8859-1 +ca_FR.ISO-8859-1: ca_FR.ISO8859-1 +ca_FR.iso885915: ca_FR.ISO8859-15 +ca_FR.utf8: ca_FR.UTF-8 +ca_FR.ISO-8859-15: ca_FR.ISO8859-15 +ca_FR.ISO-8859-15@euro: ca_FR.ISO8859-15 +ca_FR.UTF-8@euro: ca_FR.UTF-8 +ca_IT: ca_IT.ISO8859-1 +ca_IT@euro: ca_IT.ISO8859-15 +ca_IT.iso88591: ca_IT.ISO8859-1 +ca_IT.ISO-8859-1: ca_IT.ISO8859-1 +ca_IT.iso885915: ca_IT.ISO8859-15 +ca_IT.utf8: ca_IT.UTF-8 +ca_IT.ISO-8859-15: ca_IT.ISO8859-15 +ca_IT.ISO-8859-15@euro: ca_IT.ISO8859-15 +ca_IT.UTF-8@euro: ca_IT.UTF-8 +cs: cs_CZ.ISO8859-2 +cs_CS: cs_CZ.ISO8859-2 +cs_CS.ISO8859-2: cs_CZ.ISO8859-2 +cs_CZ: cs_CZ.ISO8859-2 +cs_CZ.iso88592: cs_CZ.ISO8859-2 +cs_CS.iso8859-2: cs_CS.ISO8859-2 +cs_CZ.ISO-8859-2: cs_CZ.ISO8859-2 +cs_CZ.ISO_8859-2: cs_CZ.ISO8859-2 +cs_CZ.utf8: cs_CZ.UTF-8 +XCOMM cz is an old name for Czech (now cs), and should be deleted in the future. +cz: cs_CZ.ISO8859-2 +cz_CZ: cs_CZ.ISO8859-2 +cz_CZ.utf8: cs_CZ.UTF-8 +cz_CZ.UTF-8: cs_CZ.UTF-8 +cy: cy_GB.ISO8859-1 +cy_GB: cy_GB.ISO8859-1 +cy_GB.iso88591: cy_GB.ISO8859-1 +cy_GB.ISO-8859-1: cy_GB.ISO8859-1 +cy_GB.iso885914: cy_GB.ISO8859-14 +cy_GB.ISO-8859-14: cy_GB.ISO8859-14 +cy_GB.iso885915: cy_GB.ISO8859-15 +cy_GB.ISO-8859-15: cy_GB.ISO8859-15 +da: da_DK.ISO8859-1 +da.ISO8859-15: da_DK.ISO8859-15 +da_DK: da_DK.ISO8859-1 +DA_DK: da_DK.ISO8859-1 +da_DK.88591: da_DK.ISO8859-1 +da_DK.88591.en: da_DK.ISO8859-1 +da_DK.iso88591: da_DK.ISO8859-1 +da_DK.ISO-8859-1: da_DK.ISO8859-1 +da_DK.ISO_8859-1: da_DK.ISO8859-1 +da_DK.iso885915: da_DK.ISO8859-15 +da_DK.ISO-8859-15: da_DK.ISO8859-15 +da_DK.8859-15: da_DK.ISO8859-15 +da_DK.utf8: da_DK.UTF-8 +DA_DK.UTF-8: da_DK.UTF-8 +de: de_DE.ISO8859-1 +de.ISO8859-15: de_DE.ISO8859-15 +de_AT: de_AT.ISO8859-1 +de_AT@euro: de_AT.ISO8859-15 +de_AT.iso88591: de_AT.ISO8859-1 +de_AT.ISO-8859-1: de_AT.ISO8859-1 +de_AT.ISO_8859-1: de_AT.ISO8859-1 +de_AT.iso885915: de_AT.ISO8859-15 +de_AT.ISO-8859-15: de_AT.ISO8859-15 +de_AT.ISO-8859-15@euro: de_AT.ISO8859-15 +de_AT.UTF-8@euro: de_AT.UTF-8 +de_AT.utf8: de_AT.UTF-8 +de_BE: de_BE.ISO8859-1 +de_BE@euro: de_BE.ISO8859-15 +de_BE.iso88591: de_BE.ISO8859-1 +de_BE.ISO_8859-1: de_BE.ISO8859-1 +de_BE.ISO-8859-1: de_BE.ISO8859-1 +de_BE.iso885915: de_BE.ISO8859-15 +de_BE.ISO_8859-15: de_BE.ISO8859-15 +de_BE.ISO-8859-15: de_BE.ISO8859-15 +de_BE.ISO-8859-15@euro: de_BE.ISO8859-15 +de_BE.UTF-8@euro: de_BE.UTF-8 +de_CH: de_CH.ISO8859-1 +de_CH.iso88591: de_CH.ISO8859-1 +de_CH.ISO_8859-1: de_CH.ISO8859-1 +de_CH.ISO-8859-1: de_CH.ISO8859-1 +de_CH.iso885915: de_CH.ISO8859-15 +de_CH.ISO_8859-15: de_CH.ISO8859-15 +de_CH.ISO-8859-15: de_CH.ISO8859-15 +de_CH.utf8: de_CH.UTF-8 +de_DE: de_DE.ISO8859-1 +de_DE@euro: de_DE.ISO8859-15 +de_DE.88591: de_DE.ISO8859-1 +de_DE.88591.en: de_DE.ISO8859-1 +de_DE.iso88591: de_DE.ISO8859-1 +de_DE.ISO-8859-1: de_DE.ISO8859-1 +de_DE.ISO_8859-1: de_DE.ISO8859-1 +de_DE.iso885915: de_DE.ISO8859-15 +de_DE.ISO-8859-15: de_DE.ISO8859-15 +de_DE.ISO_8859-15: de_DE.ISO8859-15 +de_DE.8859-15: de_DE.ISO8859-15 +de_DE.8859-15@euro: de_DE.ISO8859-15 +de_DE.ISO-8859-15@euro: de_DE.ISO8859-15 +de_DE.UTF-8@euro: de_DE.UTF-8 +de_DE.utf8: de_DE.UTF-8 +de_LU: de_LU.ISO8859-1 +de_LU@euro: de_LU.ISO8859-15 +de_LU.iso88591: de_LU.ISO8859-1 +de_LU.ISO_8859-1: de_LU.ISO8859-1 +de_LU.ISO-8859-1: de_LU.ISO8859-1 +de_LU.iso885915: de_LU.ISO8859-15 +de_LU.ISO_8859-15: de_LU.ISO8859-15 +de_LU.ISO-8859-15: de_LU.ISO8859-15 +de_LU.ISO-8859-15@euro: de_LU.ISO8859-15 +de_LU.UTF-8@euro: de_LU.UTF-8 +de_LU.utf8: de_LU.UTF-8 +GER_DE.8859: de_DE.ISO8859-1 +GER_DE.8859.in: de_DE.ISO8859-1 +ee: ee_EE.ISO8859-4 +ee_EE: ee_EE.ISO8859-4 +ee_EE.iso88594: ee_EE.ISO8859-4 +el: el_GR.ISO8859-7 +el_GR: el_GR.ISO8859-7 +el_GR.iso88597: el_GR.ISO8859-7 +el_GR.ISO-8859-7: el_GR.ISO8859-7 +el_GR@euro: el_GR.ISO8859-15 +el_GR.utf8: el_GR.UTF-8 +en: en_US.ISO8859-1 +en.ISO-8859-1: en_US.ISO8859-1 +en_AU: en_AU.ISO8859-1 +en_AU.iso88591: en_AU.ISO8859-1 +en_AU.ISO-8859-1: en_AU.ISO8859-1 +en_AU.ISO_8859-1: en_AU.ISO8859-1 +en_AU.utf8: en_AU.UTF-8 +en_BE: en_BE.ISO8859-1 +en_BE@euro: en_BE.ISO8859-15 +en_BE.utf8: en_BE.UTF-8 +en_BW: en_BW.ISO8859-1 +en_BW.iso88591: en_BW.ISO8859-1 +en_BW.ISO-8859-1: en_BW.ISO8859-1 +en_CA: en_CA.ISO8859-1 +en_CA.iso88591: en_CA.ISO8859-1 +en_CA.ISO-8859-1: en_CA.ISO8859-1 +en_CA.ISO_8859-1: en_CA.ISO8859-1 +en_CA.utf8: en_CA.UTF-8 +en_GB: en_GB.ISO8859-1 +en_GB.88591: en_GB.ISO8859-1 +en_GB.88591.en: en_GB.ISO8859-1 +en_GB.iso88591: en_GB.ISO8859-1 +en_GB.ISO-8859-1: en_GB.ISO8859-1 +en_GB.ISO_8859-1: en_GB.ISO8859-1 +en_GB.iso885915: en_GB.ISO8859-15 +en_GB.ISO-8859-15: en_GB.ISO8859-15 +en_GB.utf8: en_GB.UTF-8 +en_UK: en_GB.ISO8859-1 +ENG_GB.8859: en_GB.ISO8859-1 +ENG_GB.8859.in: en_GB.ISO8859-1 +en_HK: en_HK.ISO8859-1 +en_HK.iso88591: en_HK.ISO8859-1 +en_HK.ISO-8859-1: en_HK.ISO8859-1 +en_IE: en_IE.ISO8859-1 +en_IE.iso88591: en_IE.ISO8859-1 +en_IE.ISO-8859-1: en_IE.ISO8859-1 +en_IE.iso885915: en_IE.ISO8859-15 +en_IE.ISO-8859-15: en_IE.ISO8859-15 +en_IE.ISO-8859-15@euro: en_IE.ISO8859-15 +en_IE@euro: en_IE.ISO8859-15 +en_IE.UTF-8@euro: en_IE.UTF-8 +en_IE.utf8: en_IE.UTF-8 +en_IN: en_IN.ISO8859-1 +en_NZ: en_NZ.ISO8859-1 +en_NZ.iso88591: en_NZ.ISO8859-1 +en_NZ.ISO-8859-1: en_NZ.ISO8859-1 +en_NZ.utf8: en_NZ.UTF-8 +en_PH: en_PH.ISO8859-1 +en_PH.iso88591: en_PH.ISO8859-1 +en_PH.ISO-8859-1: en_PH.ISO8859-1 +en_SG: en_SG.ISO8859-1 +en_SG.iso88591: en_SG.ISO8859-1 +en_SG.ISO-8859-1: en_SG.ISO8859-1 +en_US: en_US.ISO8859-1 +EN_US: en_US.ISO8859-1 +en_US.88591: en_US.ISO8859-1 +en_US.88591.en: en_US.ISO8859-1 +en_US.iso88591: en_US.ISO8859-1 +en_US.ISO-8859-1: en_US.ISO8859-1 +en_US.ISO_8859-1: en_US.ISO8859-1 +en_US.iso885915: en_US.ISO8859-15 +en_US.ISO-8859-15: en_US.ISO8859-15 +en_US.8859-15: en_US.ISO8859-15 +en_US.ISO8859-15@euro: en_US.ISO8859-15 +en_US.utf8: en_US.UTF-8 +EN_US.UTF-8: en_US.UTF-8 +en_ZA: en_ZA.ISO8859-1 +en_ZA.88591: en_ZA.ISO8859-1 +en_ZA.88591.en: en_ZA.ISO8859-1 +en_ZA.iso88591: en_ZA.ISO8859-1 +en_ZA.ISO-8859-1: en_ZA.ISO8859-1 +en_ZA.ISO_8859-1: en_ZA.ISO8859-1 +en_ZA.iso885915: en_ZA.ISO8859-15 +en_ZA.ISO-8859-15: en_ZA.ISO8859-15 +en_ZA.utf8: en_ZA.UTF-8 +en_ZW: en_ZW.ISO8859-1 +en_ZW.iso88591: en_ZW.ISO8859-1 +en_ZW.ISO-8859-1: en_ZW.ISO8859-1 +eo: eo_XX.ISO8859-3 +eo_EO: eo_EO.ISO8859-3 +eo_EO.ISO8859-3: eo_EO.ISO8859-3 +eo_XX: eo_XX.ISO8859-3 +eo_XX.ISO8859-3: eo_XX.ISO8859-3 +es: es_ES.ISO8859-1 +es.UTF-8: es_ES.UTF-8 +es_AR: es_AR.ISO8859-1 +es_AR.iso88591: es_AR.ISO8859-1 +es_AR.ISO-8859-1: es_AR.ISO8859-1 +es_AR.utf8: es_AR.UTF-8 +es_BO: es_BO.ISO8859-1 +es_BO.iso88591: es_BO.ISO8859-1 +es_BO.ISO-8859-1: es_BO.ISO8859-1 +es_BO.utf8: es_BO.UTF-8 +es_CL: es_CL.ISO8859-1 +es_CL.iso88591: es_CL.ISO8859-1 +es_CL.ISO-8859-1: es_CL.ISO8859-1 +es_CL.utf8: es_CL.UTF-8 +es_CO: es_CO.ISO8859-1 +es_CO.iso88591: es_CO.ISO8859-1 +es_CO.ISO-8859-1: es_CO.ISO8859-1 +es_CO.utf8: es_CO.UTF-8 +es_CR: es_CR.ISO8859-1 +es_CR.iso88591: es_CR.ISO8859-1 +es_CR.ISO-8859-1: es_CR.ISO8859-1 +es_CR.utf8: es_CR.UTF-8 +es_DO: es_DO.ISO8859-1 +es_DO.iso88591: es_DO.ISO8859-1 +es_DO.ISO-8859-1: es_DO.ISO8859-1 +es_DO.utf8: es_DO.UTF-8 +es_EC: es_EC.ISO8859-1 +es_EC.iso88591: es_EC.ISO8859-1 +es_EC.ISO-8859-1: es_EC.ISO8859-1 +es_EC.utf8: es_EC.UTF-8 +es_ES: es_ES.ISO8859-1 +es_ES.88591: es_ES.ISO8859-1 +es_ES.88591.en: es_ES.ISO8859-1 +es_ES.iso88591: es_ES.ISO8859-1 +es_ES.ISO-8859-1: es_ES.ISO8859-1 +es_ES.ISO_8859-1: es_ES.ISO8859-1 +es_ES.iso885915: es_ES.ISO8859-15 +es_ES.ISO-8859-15: es_ES.ISO8859-15 +es_ES.ISO-8859-15@euro: es_ES.ISO8859-15 +es_ES@euro: es_ES.ISO8859-15 +es_ES.UTF-8@euro: es_ES.UTF-8 +es_ES.utf8: es_ES.UTF-8 +es_GT: es_GT.ISO8859-1 +es_GT.iso88591: es_GT.ISO8859-1 +es_GT.ISO-8859-1: es_GT.ISO8859-1 +es_GT.utf8: es_GT.UTF-8 +es_HN: es_HN.ISO8859-1 +es_HN.iso88591: es_HN.ISO8859-1 +es_HN.ISO-8859-1: es_HN.ISO8859-1 +es_HN.utf8: es_HN.UTF-8 +es_MX: es_MX.ISO8859-1 +es_MX.iso88591: es_MX.ISO8859-1 +es_MX.ISO-8859-1: es_MX.ISO8859-1 +es_MX.utf8: es_MX.UTF-8 +es_NI: es_NI.ISO8859-1 +es_NI.iso88591: es_NI.ISO8859-1 +es_NI.ISO-8859-1: es_NI.ISO8859-1 +es_NI.utf8: es_NI.UTF-8 +es_PA: es_PA.ISO8859-1 +es_PA.iso88591: es_PA.ISO8859-1 +es_PA.ISO-8859-1: es_PA.ISO8859-1 +es_PA.iso885915: es_PA.ISO8859-15 +es_PA.utf8: es_PA.UTF-8 +es_PE: es_PE.ISO8859-1 +es_PE.iso88591: es_PE.ISO8859-1 +es_PE.ISO-8859-1: es_PE.ISO8859-1 +es_PE.iso885915: es_PE.ISO8859-15 +es_PE.utf8: es_PE.UTF-8 +es_PR: es_PR.ISO8859-1 +es_PR.iso88591: es_PR.ISO8859-1 +es_PR.ISO-8859-1: es_PR.ISO8859-1 +es_PR.utf8: es_PR.UTF-8 +es_PY: es_PY.ISO8859-1 +es_PY.iso88591: es_PY.ISO8859-1 +es_PY.ISO-8859-1: es_PY.ISO8859-1 +es_PY.iso885915: es_PY.ISO8859-15 +es_PY.utf8: es_PY.UTF-8 +es_SV: es_SV.ISO8859-1 +es_SV.iso88591: es_SV.ISO8859-1 +es_SV.ISO-8859-1: es_SV.ISO8859-1 +es_SV.iso885915: es_SV.ISO8859-15 +es_SV.utf8: es_SV.UTF-8 +es_US: es_US.ISO8859-1 +es_US.iso88591: es_US.ISO8859-1 +es_US.ISO-8859-1: es_US.ISO8859-1 +es_UY: es_UY.ISO8859-1 +es_UY.iso88591: es_UY.ISO8859-1 +es_UY.ISO-8859-1: es_UY.ISO8859-1 +es_UY.iso885915: es_UY.ISO8859-15 +es_UY.utf8: es_UY.UTF-8 +es_VE: es_VE.ISO8859-1 +es_VE.iso88591: es_VE.ISO8859-1 +es_VE.ISO-8859-1: es_VE.ISO8859-1 +es_VE.iso885915: es_VE.ISO8859-15 +es_VE.utf8: es_VE.UTF-8 +#if defined(SVR4) && defined(sun) +XCOMM Sun Solaris 2.6 has erroneously specified Estonian as a Latin-1 +XCOMM language; however this is clearly incorrect according to ISO8859. +#endif +XCOMM According to Estonian local standards, ISO8859-4 is not a recommended +XCOMM charset. EVS8:2000 specifies ISO8859-15 as the base charset. +et: et_EE.ISO8859-15 +et_EE: et_EE.ISO8859-15 +et_EE.iso88591: et_EE.ISO8859-1 +et_EE.ISO-8859-1: et_EE.ISO8859-1 +et_EE.iso88594: et_EE.ISO8859-4 +et_EE.ISO-8859-4: et_EE.ISO8859-4 +et_EE.iso885913: et_EE.ISO8859-13 +et_EE.ISO-8859-13: et_EE.ISO8859-13 +et_EE.iso885915: et_EE.ISO8859-15 +et_EE.ISO-8859-15: et_EE.ISO8859-15 +et_EE.utf8: et_EE.UTF-8 +eu: eu_ES.ISO8859-1 +eu_ES: eu_ES.ISO8859-1 +eu_ES.iso88591: eu_ES.ISO8859-1 +eu_ES.ISO-8859-1: eu_ES.ISO8859-1 +eu_ES.iso885915: eu_ES.ISO8859-15 +eu_ES.ISO-8859-15: eu_ES.ISO8859-15 +eu_ES.ISO-8859-15@euro: eu_ES.ISO8859-15 +eu_ES@euro: eu_ES.ISO8859-15 +eu_ES.UTF-8@euro: eu_ES.UTF-8 +fa: fa_IR.UTF-8 +fa_IR: fa_IR.UTF-8 +fa_IR.isiri3342: fa_IR.ISIRI-3342 +fa_IR.utf8: fa_IR.UTF-8 +fi: fi_FI.ISO8859-15 +fi.ISO8859-15: fi_FI.ISO8859-15 +fi_FI: fi_FI.ISO8859-15 +fi_FI.88591: fi_FI.ISO8859-1 +fi_FI.88591.en: fi_FI.ISO8859-1 +fi_FI.iso88591: fi_FI.ISO8859-1 +fi_FI.ISO-8859-1: fi_FI.ISO8859-1 +fi_FI.ISO_8859-1: fi_FI.ISO8859-1 +fi_FI.iso885915: fi_FI.ISO8859-15 +fi_FI.ISO-8859-15: fi_FI.ISO8859-15 +fi_FI.ISO-8859-15@euro: fi_FI.ISO8859-15 +fi_FI@euro: fi_FI.ISO8859-15 +fi_FI.utf8: fi_FI.UTF-8 +fi_FI.UTF-8@euro: fi_FI.UTF-8 +fo: fo_FO.ISO8859-1 +fo_FO: fo_FO.ISO8859-1 +fo_FO.iso88591: fo_FO.ISO8859-1 +fo_FO.ISO-8859-1: fo_FO.ISO8859-1 +fo_FO.iso885915: fo_FO.ISO8859-15 +fo_FO.ISO-8859-15: fo_FO.ISO8859-15 +fo_FO.utf8: fo_FO.UTF-8 +fr: fr_FR.ISO8859-1 +fr.ISO8859-15: fr_FR.ISO8859-15 +fr.UTF-8: fr_FR.UTF-8 +fr_BE: fr_BE.ISO8859-1 +fr_BE.88591: fr_BE.ISO8859-1 +fr_BE.88591.en: fr_BE.ISO8859-1 +fr_BE.ISO-8859-1: fr_BE.ISO8859-1 +fr_BE.ISO_8859-1: fr_BE.ISO8859-1 +fr_BE.iso885915: fr_BE.ISO8859-15 +fr_BE.ISO-8859-15: fr_BE.ISO8859-15 +fr_BE.ISO-8859-15@euro: fr_BE.ISO8859-15 +fr_BE@euro: fr_BE.ISO8859-15 +fr_BE.utf8: fr_BE.UTF-8 +fr_BE.UTF-8@euro: fr_BE.UTF-8 +fr_CA: fr_CA.ISO8859-1 +fr_CA.88591: fr_CA.ISO8859-1 +fr_CA.88591.en: fr_CA.ISO8859-1 +fr_CA.iso88591: fr_CA.ISO8859-1 +fr_CA.ISO-8859-1: fr_CA.ISO8859-1 +fr_CA.ISO_8859-1: fr_CA.ISO8859-1 +fr_CA.iso885915: fr_CA.ISO8859-15 +fr_CA.ISO-8859-15: fr_CA.ISO8859-15 +fr_CA.utf8: fr_CA.UTF-8 +fr_CH: fr_CH.ISO8859-1 +fr_CH.88591: fr_CH.ISO8859-1 +fr_CH.88591.en: fr_CH.ISO8859-1 +fr_CH.ISO-8859-1: fr_CH.ISO8859-1 +fr_CH.ISO_8859-1: fr_CH.ISO8859-1 +fr_CH.iso885915: fr_CH.ISO8859-15 +fr_CH.ISO-8859-15: fr_CH.ISO8859-15 +fr_CH.utf8: fr_CH.UTF-8 +fr_FR: fr_FR.ISO8859-1 +fr_FR.88591: fr_FR.ISO8859-1 +fr_FR.88591.en: fr_FR.ISO8859-1 +fr_FR.iso88591: fr_FR.ISO8859-1 +fr_FR.ISO-8859-1: fr_FR.ISO8859-1 +fr_FR.ISO_8859-1: fr_FR.ISO8859-1 +fr_FR.iso885915: fr_FR.ISO8859-15 +fr_FR.ISO-8859-15: fr_FR.ISO8859-15 +fr_FR.ISO-8859-15@euro: fr_FR.ISO8859-15 +fr_FR@euro: fr_FR.ISO8859-15 +fr_FR.UTF-8@euro: fr_FR.UTF-8 +fr_FR.utf8: fr_FR.UTF-8 +fr_LU: fr_LU.ISO8859-1 +fr_LU.88591: fr_LU.ISO8859-1 +fr_LU.88591.en: fr_LU.ISO8859-1 +fr_LU.iso88591: fr_LU.ISO8859-1 +fr_LU.ISO-8859-1: fr_LU.ISO8859-1 +fr_LU.ISO_8859-1: fr_LU.ISO8859-1 +fr_LU.iso885915: fr_LU.ISO8859-15 +fr_LU.ISO-8859-15: fr_LU.ISO8859-15 +fr_LU.ISO-8859-15@euro: fr_LU.ISO8859-15 +fr_LU@euro: fr_LU.ISO8859-15 +fr_LU.UTF-8@euro: fr_LU.UTF-8 +fr_LU.utf8: fr_LU.UTF-8 +FRE_FR.8859: fr_FR.ISO8859-1 +FRE_FR.8859.in: fr_FR.ISO8859-1 +ga: ga_IE.ISO8859-1 +ga_IE: ga_IE.ISO8859-1 +ga_IE.iso88591: ga_IE.ISO8859-1 +ga_IE.ISO-8859-1: ga_IE.ISO8859-1 +ga_IE.iso885914: ga_IE.ISO8859-14 +ga_IE.ISO-8859-14: ga_IE.ISO8859-14 +ga_IE.iso885915: ga_IE.ISO8859-15 +ga_IE.ISO-8859-15: ga_IE.ISO8859-15 +ga_IE.ISO-8859-15@euro: ga_IE.ISO8859-15 +ga_IE@euro: ga_IE.ISO8859-15 +ga_IE.UTF-8@euro: ga_IE.UTF-8 +ga_IE.utf8: ga_IE.UTF-8 +gd: gd_GB.ISO8859-1 +gd_GB: gd_GB.ISO8859-1 +gd_GB.iso88591: gd_GB.ISO8859-1 +gd_GB.ISO-8859-1: gd_GB.ISO8859-1 +gd_GB.iso885914: gd_GB.ISO8859-14 +gd_GB.ISO-8859-14: gd_GB.ISO8859-14 +gd_GB.iso885915: gd_GB.ISO8859-15 +gd_GB.ISO-8859-15: gd_GB.ISO8859-15 +gl: gl_ES.ISO8859-1 +gl_ES: gl_ES.ISO8859-1 +gl_ES.iso88591: gl_ES.ISO8859-1 +gl_ES.ISO-8859-1: gl_ES.ISO8859-1 +gl_ES.iso885915: gl_ES.ISO8859-15 +gl_ES.ISO-8859-15: gl_ES.ISO8859-15 +gl_ES.ISO-8859-15@euro: gl_ES.ISO8859-15 +gl_ES@euro: gl_ES.ISO8859-15 +gl_ES.UTF-8@euro: gl_ES.UTF-8 +gl_ES.utf8: gl_ES.UTF-8 +gu_IN.utf8: gu_IN.UTF-8 +gv: gv_GB.ISO8859-1 +gv_GB: gv_GB.ISO8859-1 +gv_GB.iso88591: gv_GB.ISO8859-1 +gv_GB.ISO-8859-1: gv_GB.ISO8859-1 +gv_GB.iso885914: gv_GB.ISO8859-14 +gv_GB.ISO-8859-14: gv_GB.ISO8859-14 +gv_GB.iso885915: gv_GB.ISO8859-15 +gv_GB.ISO-8859-15: gv_GB.ISO8859-15 +he: he_IL.ISO8859-8 +he_IL: he_IL.ISO8859-8 +HE_IL: he_IL.ISO8859-8 +he_IL.iso88598: he_IL.ISO8859-8 +he_IL.ISO-8859-8: he_IL.ISO8859-8 +he_IL.cp1255: he_IL.CP1255 +he_IL.microsoftcp1255: he_IL.CP1255 +he_IL.microsoft-cp1255: he_IL.CP1255 +he_IL.MICROSOFT-CP1255: he_IL.CP1255 +he_IL.utf8: he_IL.UTF-8 +HE_IL.UTF-8: he_IL.UTF-8 +hi: hi_IN.ISCII-DEV +hi_IN: hi_IN.ISCII-DEV +HI_IN: hi_IN.ISCII-DEV +hi_IN.isciidev: hi_IN.ISCII-DEV +hi_IN.utf8: hi_IN.UTF-8 +HI_IN.UTF-8: hi_IN.UTF-8 +hne: hne_IN.UTF-8 +hne_IN.utf8: hne_IN.UTF-8 +hr: hr_HR.ISO8859-2 +hr_HR: hr_HR.ISO8859-2 +hr_HR.iso88592: hr_HR.ISO8859-2 +hr_HR.ISO-8859-2: hr_HR.ISO8859-2 +hr_HR.ISO_8859-2: hr_HR.ISO8859-2 +hr_HR.utf8: hr_HR.UTF-8 +hu: hu_HU.ISO8859-2 +hu_HU: hu_HU.ISO8859-2 +hu_HU.iso88592: hu_HU.ISO8859-2 +hu_HU.ISO-8859-2: hu_HU.ISO8859-2 +hu_HU.utf8: hu_HU.UTF-8 +XCOMM in was the old ISO code for Indonesian (now id). These lines should be +XCOMM deleted in the future. +in: id_ID.ISO8859-1 +in_ID: id_ID.ISO8859-1 +is: is_IS.ISO8859-1 +is_IS: is_IS.ISO8859-1 +is_IS.iso88591: is_IS.ISO8859-1 +is_IS.ISO-8859-1: is_IS.ISO8859-1 +is_IS.ISO_8859-1: is_IS.ISO8859-1 +is_IS.iso885915: is_IS.ISO8859-15 +is_IS.ISO-8859-15: is_IS.ISO8859-15 +is_IS.utf8: is_IS.UTF-8 +it: it_IT.ISO8859-1 +it.ISO8859-15: it_IT.ISO8859-15 +it.UTF-8: it_IT.UTF-8 +it_CH: it_CH.ISO8859-1 +it_CH.iso88591: it_CH.ISO8859-1 +it_CH.ISO_8859-1: it_CH.ISO8859-1 +it_CH.ISO-8859-1: it_CH.ISO8859-1 +it_CH.iso885915: it_CH.ISO8859-15 +it_CH.utf8: it_CH.UTF-8 +it_IT: it_IT.ISO8859-1 +it_IT.88591: it_IT.ISO8859-1 +it_IT.88591.en: it_IT.ISO8859-1 +it_IT.iso88591: it_IT.ISO8859-1 +it_IT.ISO-8859-1: it_IT.ISO8859-1 +it_IT.ISO_8859-1: it_IT.ISO8859-1 +it_IT.iso885915: it_IT.ISO8859-15 +it_IT.ISO-8859-15: it_IT.ISO8859-15 +it_IT.ISO-8859-15@euro: it_IT.ISO8859-15 +it_IT@euro: it_IT.ISO8859-15 +it_IT.utf8: it_IT.UTF-8 +it_IT.UTF-8@euro: it_IT.UTF-8 +iu: iu_CA.NUNACOM-8 +iu_CA: iu_CA.NUNACOM-8 +iu_CA.nunacom8: iu_CA.NUNACOM-8 +XCOMM iw was the old ISO code for Hebrew (now he). These lines should be +XCOMM deleted in the future. +iw: he_IL.ISO8859-8 +iw_IL: he_IL.ISO8859-8 +Iw_IL: he_IL.ISO8859-8 +iw_IL.iso88598: he_IL.ISO8859-8 +iw_IL.ISO-8859-8: he_IL.ISO8859-8 +#ifndef __uxp__ +ja_JP: ja_JP.eucJP +#else /* __uxp__ */ +ja_JP: ja_JP.U90 +ja_JP.U90: ja_JP.U90 +ja_JP.S90: ja_JP.S90 +#endif /* __uxp__ */ +ja: ja_JP.eucJP +ja.JIS: ja_JP.JIS7 +ja.SJIS: ja_JP.SJIS +ja_JP.ujis: ja_JP.eucJP +Jp_JP: ja_JP.eucJP +ja_JP.AJEC: ja_JP.eucJP +ja_JP.EUC: ja_JP.eucJP +ja_JP.EUC-JP: ja_JP.eucJP +ja_JP.EUC_JP: ja_JP.eucJP +ja_JP.eucjp: ja_JP.eucJP +ja_JP.ISO-2022-JP: ja_JP.JIS7 +ja_JP.JIS: ja_JP.JIS7 +ja_JP.jis7: ja_JP.JIS7 +ja_JP.mscode: ja_JP.SJIS +ja_JP.PCK: ja_JP.SJIS +ja_JP.SJIS: ja_JP.SJIS +ja_JP.sjis: ja_JP.SJIS +ja_JP.utf8: ja_JP.UTF-8 +JA_JP.utf8: ja_JP.UTF-8 +ka: ka_GE.GEORGIAN-ACADEMY +ka_GE: ka_GE.GEORGIAN-ACADEMY +ka_GE.georgianacademy: ka_GE.GEORGIAN-ACADEMY +ka_GE.georgianrs: ka_GE.GEORGIAN-ACADEMY +ka_GE.georgianps: ka_GE.GEORGIAN-PS +kl: kl_GL.ISO8859-1 +kl_GL: kl_GL.ISO8859-1 +kl_GL.iso88591: kl_GL.ISO8859-1 +kl_GL.ISO-8859-1: kl_GL.ISO8859-1 +kl_GL.iso885915: kl_GL.ISO8859-15 +kl_GL.utf8: kl_GL.UTF-8 +kn: kn_IN.UTF-8 +kn_IN.utf8: kn_IN.UTF-8 +ko: ko_KR.eucKR +ko.UTF-8: ko_KR.UTF-8 +ko_KR: ko_KR.eucKR +KO_KR: ko_KR.eucKR +ko_KR.EUC: ko_KR.eucKR +ko_KR.EUC-KR: ko_KR.eucKR +ko_KR.euc: ko_KR.eucKR +ko_KR.euckr: ko_KR.eucKR +ko_KR.utf8: ko_KR.UTF-8 +KO_KR.UTF-8: ko_KR.UTF-8 +ks: ks_IN.UTF-8 +ks_IN.utf8: ks_IN.UTF-8 +ks_IN@devanagari: ks_IN@devanagari.UTF-8 +ks_IN@devanagari.utf8: ks_IN@devanagari.UTF-8 +kw: kw_GB.ISO8859-1 +kw_GB: kw_GB.ISO8859-1 +kw_GB.iso88591: kw_GB.ISO8859-1 +kw_GB.ISO-8859-1: kw_GB.ISO8859-1 +kw_GB.iso885914: kw_GB.ISO8859-14 +kw_GB.ISO-8859-14: kw_GB.ISO8859-14 +kw_GB.iso885915: kw_GB.ISO8859-15 +kw_GB.ISO-8859-15: kw_GB.ISO8859-15 +ky: ky_KG.UTF-8 +ky_KG: ky_KG.UTF-8 +ky_KG.UTF-8: ky_KG.UTF-8 +lo: lo_LA.MULELAO-1 +lo_LA: lo_LA.MULELAO-1 +lo_LA.cp1133: lo_LA.IBM-CP1133 +lo_LA.ibmcp1133: lo_LA.IBM-CP1133 +lo_LA.mulelao1: lo_LA.MULELAO-1 +#if defined(VeryOldFreeBSD) +XCOMM most locales in FreeBSD 2.1.[56] do not work, allow use of FreeBSD's +XCOMM generic Latin-1 locale name. N.B. "lt" is a bad code to use for a +XCOMM generic Latin-1 locale anyway because it is the country code for +XCOMM Lithuania, which by default uses Latin-7 (ISO-8859-13). +lt_LN.ISO_8859-1: lt_LN.ISO8859-1 +#endif +lt: lt_LT.ISO8859-13 +lt_LT: lt_LT.ISO8859-13 +lt_LT.iso88594: lt_LT.ISO8859-4 +lt_LT.ISO-8859-4: lt_LT.ISO8859-4 +lt_LT.ISO_8859-4: lt_LT.ISO8859-4 +lt_LT.iso885913: lt_LT.ISO8859-13 +lt_LT.ISO-8859-13: lt_LT.ISO8859-13 +lt_LT.ISO_8859-13: lt_LT.ISO8859-13 +lt_LT.utf8: lt_LT.UTF-8 +lv: lv_LV.ISO8859-13 +lv_LV: lv_LV.ISO8859-13 +lv_LV.iso88594: lv_LV.ISO8859-4 +lv_LV.ISO-8859-4: lv_LV.ISO8859-4 +lv_LV.iso885913: lv_LV.ISO8859-13 +lv_LV.ISO-8859-13: lv_LV.ISO8859-13 +lv_LV.ISO_8859-13: lv_LV.ISO8859-13 +lv_LV.utf8: lv_LV.UTF-8 +mai: mai_IN.UTF-8 +mai_IN.utf8: mai_IN.UTF-8 +mi: mi_NZ.ISO8859-1 +mi_NZ: mi_NZ.ISO8859-1 +mi_NZ.iso88591: mi_NZ.ISO8859-1 +mk: mk_MK.ISO8859-5 +mk_MK: mk_MK.ISO8859-5 +mk_MK.iso88595: mk_MK.ISO8859-5 +mk_MK.ISO-8859-5: mk_MK.ISO8859-5 +mk_MK.cp1251: mk_MK.CP1251 +mk_MK.microsoftcp1251: mk_MK.CP1251 +mk_MK.microsoft-cp1251: mk_MK.CP1251 +mk_MK.MICROSOFT-CP1251: mk_MK.CP1251 +mk_MK.utf8: mk_MK.UTF-8 +ml: ml_IN.UTF-8 +ml_IN.utf8: ml_IN.UTF-8 +mr: mr_IN.UTF-8 +mr_IN: mr_IN.UTF-8 +mr_IN.utf8: mr_IN.UTF-8 +ms: ms_MY.ISO8859-1 +ms_MY: ms_MY.ISO8859-1 +ms_MY.iso88591: ms_MY.ISO8859-1 +ms_MY.ISO-8859-1: ms_MY.ISO8859-1 +mt: mt_MT.ISO8859-3 +mt_MT: mt_MT.ISO8859-3 +mt_MT.ISO-8859-3: mt_MT.ISO8859-3 +nb: nb_NO.ISO8859-1 +nb_NO: nb_NO.ISO8859-1 +nb_NO.88591: nb_NO.ISO8859-1 +nb_NO.iso88591: nb_NO.ISO8859-1 +nb_NO.ISO-8859-1: nb_NO.ISO8859-1 +nb_NO.iso885915: nb_NO.ISO8859-15 +nb_NO.ISO-8859-15: nb_NO.ISO8859-15 +nb_NO.utf8: nb_NO.UTF-8 +ne_NP.utf8: ne_NP.UTF-8 +nl: nl_NL.ISO8859-1 +nl.ISO8859-15: nl_NL.ISO8859-15 +nl_BE: nl_BE.ISO8859-1 +nl_BE.88591: nl_BE.ISO8859-1 +nl_BE.88591.en: nl_BE.ISO8859-1 +nl_BE.iso88591: nl_BE.ISO8859-1 +nl_BE.ISO-8859-1: nl_BE.ISO8859-1 +nl_BE.ISO_8859-1: nl_BE.ISO8859-1 +nl_BE.iso885915: nl_BE.ISO8859-15 +nl_BE.ISO-8859-15: nl_BE.ISO8859-15 +nl_BE.ISO-8859-15@euro: nl_BE.ISO8859-15 +nl_BE@euro: nl_BE.ISO8859-15 +nl_BE.utf8: nl_BE.UTF-8 +nl_BE.UTF-8@euro: nl_BE.UTF-8 +nl_NL: nl_NL.ISO8859-1 +nl_NL.88591: nl_NL.ISO8859-1 +nl_NL.88591.en: nl_NL.ISO8859-1 +nl_NL.iso88591: nl_NL.ISO8859-1 +nl_NL.ISO-8859-1: nl_NL.ISO8859-1 +nl_NL.ISO_8859-1: nl_NL.ISO8859-1 +nl_NL.iso885915: nl_NL.ISO8859-15 +nl_NL.ISO-8859-15: nl_NL.ISO8859-15 +nl_NL.ISO-8859-15@euro: nl_NL.ISO8859-15 +nl_NL@euro: nl_NL.ISO8859-15 +nl_NL.utf8: nl_NL.UTF-8 +nl_NL.UTF-8@euro: nl_NL.UTF-8 +nn: nn_NO.ISO8859-1 +nn_NO: nn_NO.ISO8859-1 +nn_NO.88591: nn_NO.ISO8859-1 +nn_NO.ISO-8859-1: nn_NO.ISO8859-1 +nn_NO.ISO_8859-1: nn_NO.ISO8859-1 +nn_NO.iso885915: nn_NO.ISO8859-15 +nn_NO.ISO-8859-15: nn_NO.ISO8859-15 +nn_NO.utf8: nn_NO.UTF-8 +no: no_NO.ISO8859-1 +no_NO: no_NO.ISO8859-1 +no_NO.88591: no_NO.ISO8859-1 +no_NO.88591.en: no_NO.ISO8859-1 +no_NO.iso88591: no_NO.ISO8859-1 +no_NO.ISO-8859-1: no_NO.ISO8859-1 +no_NO.ISO8859-1@bokmal: no_NO.ISO8859-1 +no_NO.ISO8859-1@nynorsk: no_NO.ISO8859-1 +no_NO.iso885915: no_NO.ISO8859-15 +no_NO.ISO-8859-15: no_NO.ISO8859-15 +no_NO.utf8: no_NO.UTF-8 +nr: nr_ZA.ISO8859-1 +nr_ZA: nr_ZA.ISO8859-1 +nr_ZA.iso88591: nr_ZA.ISO8859-1 +nr_ZA.utf8: nr_ZA.UTF-8 +nso: nso_ZA.ISO8859-15 +nso_ZA: nso_ZA.ISO8859-15 +nso_ZA.iso885915: nso_ZA.ISO8859-15 +nso_ZA.utf8: nso_ZA.UTF-8 +ny: ny_NO.ISO8859-1 +ny_NO: ny_NO.ISO8859-1 +ny_NO.88591: ny_NO.ISO8859-1 +ny_NO.ISO_8859-1: ny_NO.ISO8859-1 +ny_NO.iso885915: ny_NO.ISO8859-15 +no@nynorsk: ny_NO.ISO8859-1 +nynorsk: nn_NO.ISO8859-1 +oc: oc_FR.ISO8859-1 +oc_FR: oc_FR.ISO8859-1 +oc_FR.iso88591: oc_FR.ISO8859-1 +oc_FR.ISO-8859-1: oc_FR.ISO8859-1 +oc_FR.iso885915: oc_FR.ISO8859-15 +oc_FR.ISO-8859-15: oc_FR.ISO8859-15 +oc_FR@euro: oc_FR.ISO8859-15 +or: or_IN.UTF-8 +or_IN.utf8: or_IN.UTF-8 +pa: pa_IN.UTF-8 +pa_IN.utf8: pa_IN.UTF-8 +pa_PK.utf8: pa_PK.UTF-8 +pd: pd_US.ISO8859-1 +pd_DE: pd_DE.ISO8859-1 +pd_US: pd_US.ISO8859-1 +pd_DE.iso88591: pd_DE.ISO8859-1 +pd_US.iso88591: pd_US.ISO8859-1 +pd_DE.iso885915: pd_DE.ISO8859-15 +pd_US.iso885915: pd_US.ISO8859-15 +ph: ph_PH.ISO8859-1 +ph_PH: ph_PH.ISO8859-1 +ph_PH.iso88591: ph_PH.ISO8859-1 +pl: pl_PL.ISO8859-2 +pl.UTF-8: pl_PL.UTF-8 +pl_PL: pl_PL.ISO8859-2 +pl_PL.iso88592: pl_PL.ISO8859-2 +pl_PL.ISO-8859-2: pl_PL.ISO8859-2 +pl_PL.utf8: pl_PL.UTF-8 +pp: pp_AN.ISO8859-1 +pp_AN: pp_AN.ISO8859-1 +pp_AN.iso88591: pp_AN.ISO8859-1 +pt: pt_PT.ISO8859-1 +pt.ISO8859-15: pt_PT.ISO8859-15 +pt_BR: pt_BR.ISO8859-1 +pt_BR.88591: pt_BR.ISO8859-1 +pt_BR.88591.en: pt_BR.ISO8859-1 +pt_BR.iso88591: pt_BR.ISO8859-1 +pt_BR.ISO-8859-1: pt_BR.ISO8859-1 +pt_BR.ISO_8859-1: pt_BR.ISO8859-1 +pt_BR.iso885915: pt_BR.ISO8859-15 +pt_BR.utf8: pt_BR.UTF-8 +pt_PT: pt_PT.ISO8859-1 +pt_PT.88591: pt_PT.ISO8859-1 +pt_PT.88591.en: pt_PT.ISO8859-1 +pt_PT.iso88591: pt_PT.ISO8859-1 +pt_PT.ISO-8859-1: pt_PT.ISO8859-1 +pt_PT.ISO_8859-1: pt_PT.ISO8859-1 +pt_PT.iso885915: pt_PT.ISO8859-15 +pt_PT.ISO-8859-15: pt_PT.ISO8859-15 +pt_PT.ISO-8859-15@euro: pt_PT.ISO8859-15 +pt_PT@euro: pt_PT.ISO8859-15 +pt_PT.utf8: pt_PT.UTF-8 +pt_PT.UTF-8@euro: pt_PT.UTF-8 +ro: ro_RO.ISO8859-2 +ro_RO: ro_RO.ISO8859-2 +ro_RO.iso88592: ro_RO.ISO8859-2 +ro_RO.ISO-8859-2: ro_RO.ISO8859-2 +ro_RO.utf8: ro_RO.UTF-8 +ru: ru_RU.UTF-8 +ru.koi8-r: ru_RU.KOI8-R +ru.UTF-8: ru_RU.UTF-8 +ru_RU: ru_RU.UTF-8 +ru_RU.utf8: ru_RU.UTF-8 +ru_RU.iso88595: ru_RU.ISO8859-5 +ru_RU.ISO-8859-5: ru_RU.ISO8859-5 +ru_RU.koi8r: ru_RU.KOI8-R +ru_RU.cp1251: ru_RU.CP1251 +ru_RU.microsoftcp1251: ru_RU.CP1251 +ru_RU.microsoft-cp1251: ru_RU.CP1251 +ru_RU.MICROSOFT-CP1251: ru_RU.CP1251 +#if defined(INCLUDE_ru_SU) +XCOMM ru_SU is redundant now +ru_SU: ru_RU.KOI8-R +ru_SU.ISO8859-5: ru_RU.ISO8859-5 +ru_SU.KOI8-R: ru_RU.KOI8-R +#endif +ru_UA: ru_UA.KOI8-U +ru_UA.koi8u: ru_UA.KOI8-U +ru_UA.cp1251: ru_UA.CP1251 +ru_UA.microsoftcp1251: ru_UA.CP1251 +ru_UA.microsoft-cp1251: ru_UA.CP1251 +ru_UA.MICROSOFT-CP1251: ru_UA.CP1251 +rw: rw_RW.ISO8859-1 +rw_RW: rw_RW.ISO8859-1 +rw_RW.iso8859-1: rw_RW.ISO8859-1 +rw_RW.ISO-8859-1: rw_RW.ISO8859-1 +rw_RW.utf8: rw_RW.UTF-8 +sd: sd_IN.UTF-8 +sd_IN.utf8: sd_IN.UTF-8 +sd: sd_IN@devanagari.UTF-8 +sd_IN@devanagari.utf8: sd_IN@devanagari.UTF-8 +se_NO: se_NO.UTF-8 +se_NO.utf8: se_NO.UTF-8 +XCOMM sh was the old ISO code for Serbo-Croatian (now individual sr and hr). +XCOMM YU was the old ISO code for Yugoslavia (later CS for Serbia&Montenegro). +XCOMM CS was the old ISO code for Serbia&Montenegro (now separate RS and ME). +XCOMM These lines should be deleted in the future. +sh: sr_RS.UTF-8@latin +sh_BA.ISO8859-2@bosnia: sr_CS.ISO8859-2 +sh_HR.iso88592: hr_HR.ISO8859-2 +sh_YU: sr_RS.UTF-8@latin +sh_YU.utf8: sr_RS.UTF-8@latin +si: si_LK.UTF-8 +si_LK: si_LK.UTF-8 +sk: sk_SK.ISO8859-2 +sk_SK: sk_SK.ISO8859-2 +sk_SK.iso88592: sk_SK.ISO8859-2 +sk_SK.ISO-8859-2: sk_SK.ISO8859-2 +sk_SK.utf8: sk_SK.UTF-8 +sl: sl_SI.ISO8859-2 +sl_SI: sl_SI.ISO8859-2 +sl_SI.iso88592: sl_SI.ISO8859-2 +sl_SI.ISO-8859-2: sl_SI.ISO8859-2 +sl_SI.utf8: sl_SI.UTF-8 +sq: sq_AL.ISO8859-2 +sq_AL: sq_AL.ISO8859-2 +sq_AL.iso88592: sq_AL.ISO8859-2 +sq_AL.ISO-8859-2: sq_AL.ISO8859-2 +sq_AL.utf8: sq_AL.UTF-8 +XCOMM YU was the old ISO code for Yugoslavia (later CS for Serbia&Montenegro). +XCOMM CS was the old ISO code for Serbia&Montenegro (now separate RS and ME). +XCOMM Some of these lines should be deleted in the future. +sr: sr_RS.UTF-8 +sr_YU: sr_RS.UTF-8@latin +sr@cyrillic: sr_RS.UTF-8 +sr_YU@cyrillic: sr_RS.UTF-8 +sr_YU.utf8: sr_RS.UTF-8 +sr_YU.UTF-8@cyrillic: sr_RS.UTF-8 +sr_CS: sr_RS.UTF-8 +sr@Latn: sr_RS.UTF-8@latin +sr_CS@Latn: sr_RS.UTF-8@latin +sr_CS.utf8: sr_RS.UTF-8 +sr_CS.UTF-8@Latn: sr_RS.UTF-8@latin +sr_RS: sr_RS.UTF-8 +sr@latin: sr_RS.UTF-8@latin +sr_RS@latin: sr_RS.UTF-8@latin +sr_RS@Latn: sr_RS.UTF-8@latin +sr_RS.UTF-8@Latn: sr_RS.UTF-8@latin +sr_RS.utf8: sr_RS.UTF-8 +sr_ME: sr_ME.UTF-8 +sr_ME.utf8: sr_ME.UTF-8 +ss: ss_ZA.ISO8859-1 +ss_ZA: ss_ZA.ISO8859-1 +ss_ZA.iso88591: ss_ZA.ISO8859-1 +ss_ZA.utf8: ss_ZA.UTF-8 +st: st_ZA.ISO8859-1 +st_ZA: st_ZA.ISO8859-1 +st_ZA.iso88591: st_ZA.ISO8859-1 +st_ZA.utf8: st_ZA.UTF-8 +sv: sv_SE.ISO8859-1 +sv.ISO8859-15: sv_SE.ISO8859-15 +sv.UTF-8: sv_SE.UTF-8 +sv_FI: sv_FI.ISO8859-1 +sv_FI.iso88591: sv_FI.ISO8859-1 +sv_FI.ISO-8859-1: sv_FI.ISO8859-1 +sv_FI.iso885915: sv_FI.ISO8859-15 +sv_FI.ISO-8859-15: sv_FI.ISO8859-15 +sv_FI.ISO-8859-15@euro: sv_FI.ISO8859-15 +sv_FI@euro: sv_FI.ISO8859-15 +sv_FI.UTF-8@euro: sv_FI.UTF-8 +sv_FI.utf8: sv_FI.UTF-8 +sv_SE: sv_SE.ISO8859-1 +sv_SE.88591: sv_SE.ISO8859-1 +sv_SE.88591.en: sv_SE.ISO8859-1 +sv_SE.iso88591: sv_SE.ISO8859-1 +sv_SE.ISO-8859-1: sv_SE.ISO8859-1 +sv_SE.ISO_8859-1: sv_SE.ISO8859-1 +sv_SE.iso885915: sv_SE.ISO8859-15 +sv_SE.ISO-8859-15: sv_SE.ISO8859-15 +sv_SE@euro: sv_SE.ISO8859-15 +sv_SE.utf8: sv_SE.UTF-8 +ta: ta_IN.TSCII-0 +ta_IN: ta_IN.TSCII-0 +ta_IN.tscii: ta_IN.TSCII-0 +ta_IN.tscii0: ta_IN.TSCII-0 +te: te_IN.UTF-8 +te_IN.utf8: te_IN.UTF-8 +tg: tg_TJ.KOI8-C +tg_TJ: tg_TJ.KOI8-C +tg_TJ.koi8c: tg_TJ.KOI8-C +th: th_TH.ISO8859-11 +th_TH: th_TH.ISO8859-11 +th_TH.ISO-8859-11: th_TH.ISO8859-11 +th_TH.tis620: th_TH.TIS620 +th_TH.TIS-620: th_TH.TIS620 +th_TH.TACTIS: th_TH.TIS620 +th_TH.utf8: th_TH.UTF-8 +tl: tl_PH.ISO8859-1 +tl_PH: tl_PH.ISO8859-1 +tl_PH.iso88591: tl_PH.ISO8859-1 +tl_PH.ISO-8859-1: tl_PH.ISO8859-1 +tn: tn_ZA.ISO8859-15 +tn_ZA: tn_ZA.ISO8859-15 +tn_ZA.iso8859-15: tn_ZA.ISO8859-15 +tn_ZA.utf8: tn_ZA.UTF-8 +tr: tr_TR.ISO8859-9 +tr_TR: tr_TR.ISO8859-9 +TR_TR: tr_TR.ISO8859-9 +tr_TR.iso88599: tr_TR.ISO8859-9 +tr_TR.ISO-8859-9: tr_TR.ISO8859-9 +tr_TR.utf8: tr_TR.UTF-8 +TR_TR.utf8: tr_TR.UTF-8 +ts: ts_ZA.ISO8859-1 +ts_ZA: ts_ZA.ISO8859-1 +ts_ZA.iso88591: ts_ZA.ISO8859-1 +ts_ZA.utf8: ts_ZA.UTF-8 +tt: tt_RU.TATAR-CYR +tt_RU: tt_RU.TATAR-CYR +tt_RU.tatarcyr: tt_RU.TATAR-CYR +tt_RU.koi8c: tt_RU.KOI8-C +uk: uk_UA.KOI8-U +uk_UA: uk_UA.KOI8-U +uk_UA.iso88595: uk_UA.ISO8859-5 +uk_UA.koi8u: uk_UA.KOI8-U +uk_UA.cp1251: uk_UA.CP1251 +uk_UA.microsoftcp1251: uk_UA.CP1251 +uk_UA.microsoft-cp1251: uk_UA.CP1251 +uk_UA.MICROSOFT-CP1251: uk_UA.CP1251 +uk_UA.utf8: uk_UA.UTF-8 +ur: ur_IN.UTF-8 +ur_IN.utf8: ur_IN.UTF-8 +ur: ur_PK.CP1256 +ur_PK: ur_PK.CP1256 +ur_PK.cp1256: ur_PK.CP1256 +ur_PK.microsoftcp1256: ur_PK.CP1256 +ur_PK.microsoft-cp1256: ur_PK.CP1256 +ur_PK.MICROSOFT-CP1256: ur_PK.CP1256 +uz: uz_UZ.UTF-8 +uz_UZ: uz_UZ.UTF-8 +uz_UZ.ISO-8859-1: uz_UZ.ISO8859-1 +uz_UZ@cyrillic: uz_UZ.UTF-8 +uz_UZ.UTF-8@cyrillic: uz_UZ.UTF-8 +ve: ve_ZA.UTF-8 +ve_ZA: ve_ZA.UTF-8 +ve_ZA.utf8: ve_ZA.UTF-8 +vi: vi_VN.TCVN +vi_VN: vi_VN.TCVN +Vi_VN: vi_VN.TCVN +VI_VN: vi_VN.TCVN +vi_VN.tcvn: vi_VN.TCVN +vi_VN.tcvn5712: vi_VN.TCVN +vi_VN.viscii: vi_VN.VISCII +vi_VN.viscii111: vi_VN.VISCII +vi_VN.utf8: vi_VN.UTF-8 +VI_VN.UTF-8: vi_VN.UTF-8 +wa: wa_BE.ISO8859-1 +wa_BE: wa_BE.ISO8859-1 +wa_BE.iso88591: wa_BE.ISO8859-1 +wa_BE.ISO-8859-1: wa_BE.ISO8859-1 +wa_BE.iso885915: wa_BE.ISO8859-15 +wa_BE.ISO-8859-15: wa_BE.ISO8859-15 +wa_BE.ISO-8859-15@euro: wa_BE.ISO8859-15 +wa_BE@euro: wa_BE.ISO8859-15 +xh: xh_ZA.ISO8859-1 +xh_ZA: xh_ZA.ISO8859-1 +xh_ZA.iso88591: xh_ZA.ISO8859-1 +xh_ZA.utf8: xh_ZA.UTF-8 +yi: yi_US.CP1255 +yi_US: yi_US.CP1255 +yi_US.cp1255: yi_US.CP1255 +yi_US.microsoftcp1255: yi_US.CP1255 +yi_US.microsoft-cp1255: yi_US.CP1255 +yi_US.MICROSOFT-CP1255: yi_US.CP1255 +zh_CN: zh_CN.gb2312 +zh_CN.Big5: zh_TW.big5 +zh_CN.EUC: zh_CN.eucCN +zh_CN.GB2312: zh_CN.gb2312 +zh_CN.GBK: zh_CN.gbk +zh_CN.GB18030: zh_CN.gb18030 +zh_CN.big5: zh_TW.big5 +zh_CN.euc: zh_CN.eucCN +zh_CN.utf8: zh_CN.UTF-8 +ZH_CN.UTF-8: zh_CN.UTF-8 +zh_HK: zh_HK.big5hkscs +zh_HK.BIG5HK: zh_HK.big5hkscs +zh_HK.Big5hkscs: zh_HK.big5hkscs +zh_HK.Big5-hkscs: zh_HK.big5hkscs +zh_HK.Big5_hkscs: zh_HK.big5hkscs +zh_HK.Big5HKSCS: zh_HK.big5hkscs +zh_HK.BIG5-HKSCS: zh_HK.big5hkscs +zh_HK.BIG5_HKSCS: zh_HK.big5hkscs +zh_HK.Big5: zh_HK.big5 +zh_HK.utf8: zh_HK.UTF-8 +ZH_HK.UTF-8: zh_HK.UTF-8 +ZH_SG.UTF-8: zh_SG.UTF-8 +zh_TW: zh_TW.big5 +zh_TW.Big5: zh_TW.big5 +zh_TW.BIG5: zh_TW.big5 +Zh_TW.big5: zh_TW.big5 +zh_TW.EUC: zh_TW.eucTW +zh_TW.EUC-TW: zh_TW.eucTW +zh_TW.utf8: zh_TW.UTF-8 +ZH_TW.UTF-8: zh_TW.UTF-8 +zu: zu_ZA.ISO8859-1 +zu_ZA: zu_ZA.ISO8859-1 +zu_ZA.iso88591: zu_ZA.ISO8859-1 +zu_ZA.utf8: zu_ZA.UTF-8 + +XCOMM The following locale names are used in SCO 3.0 +english_uk.8859: en_GB.ISO8859-1 +english_us.8859: en_US.ISO8859-1 +english_us.ascii: en_US.ISO8859-1 +french_france.8859: fr_FR.ISO8859-1 +german_germany.8859: de_DE.ISO8859-1 +portuguese_brazil.8859: pt_BR.ISO8859-1 +spanish_spain.8859: es_ES.ISO8859-1 +XCOMM The following locale names are used in HPUX 9.x +american.iso88591: en_US.ISO8859-1 +arabic.iso88596: ar_AA.ISO8859-6 +bokmal: nb_NO.ISO8859-1 +bokmål: nb_NO.ISO8859-1 +bulgarian: bg_BG.CP1251 +c-french.iso88591: fr_CA.ISO8859-1 +catalan: ca_ES.ISO8859-1 +chinese-s: zh_CN.eucCN +chinese-t: zh_TW.eucTW +croatian: hr_HR.ISO8859-2 +czech: cs_CZ.ISO8859-2 +danish: da_DK.ISO8859-1 +dansk: da_DK.ISO8859-1 +danish.iso88591: da_DK.ISO8859-1 +deutsch: de_DE.ISO8859-1 +dutch: nl_NL.ISO8859-1 +dutch.iso88591: nl_BE.ISO8859-1 +eesti: et_EE.ISO8859-1 +english.iso88591: en_EN.ISO8859-1 +estonian: et_EE.ISO8859-1 +finnish: fi_FI.ISO8859-1 +finnish.iso88591: fi_FI.ISO8859-1 +français: fr_FR.ISO8859-1 +french: fr_FR.ISO8859-1 +french.iso88591: fr_CH.ISO8859-1 +galego: gl_ES.ISO8859-1 +galician: gl_ES.ISO8859-1 +german: de_DE.ISO8859-1 +german.iso88591: de_CH.ISO8859-1 +greek: el_GR.ISO8859-7 +greek.iso88597: el_GR.ISO8859-7 +hebrew: iw_IL.ISO8859-8 +hebrew.iso88598: iw_IL.ISO8859-8 +hrvatski: hr_HR.ISO8859-2 +hungarian: hu_HU.ISO8859-2 +icelandic.iso88591: is_IS.ISO8859-1 +icelandic: is_IS.ISO8859-1 +italian: it_IT.ISO8859-1 +italian.iso88591: it_IT.ISO8859-1 +japanese: ja_JP.eucJP +japanese.euc: ja_JP.eucJP +japanese.sjis: ja_JP.SJIS +korean: ko_KR.eucKR +korean.euc: ko_KR.eucKR +lithuanian: lt_LT.ISO8859-13 +norwegian: no_NO.ISO8859-1 +norwegian.iso88591: no_NO.ISO8859-1 +polish: pl_PL.ISO8859-2 +portuguese: pt_PT.ISO8859-1 +portuguese.iso88591: pt_PT.ISO8859-1 +romanian: ro_RO.ISO8859-2 +rumanian: ro_RO.ISO8859-2 +russian: ru_RU.ISO8859-5 +serbocroatian: sr_RS.UTF-8@latin +sinhala: si_LK.UTF-8 +slovak: sk_SK.ISO8859-2 +slovene: sl_SI.ISO8859-2 +slovenian: sl_SI.ISO8859-2 +spanish: es_ES.ISO8859-1 +spanish.iso88591: es_ES.ISO8859-1 +swedish: sv_SE.ISO8859-1 +swedish.iso88591: sv_SE.ISO8859-1 +turkish: tr_TR.ISO8859-9 +turkish.iso88599: tr_TR.ISO8859-9 +thai: th_TH.ISO8859-11 +univ.utf8: en_US.UTF-8 +XCOMM Digital Unix utf +universal.utf8@ucs4: en_US.UTF-8 +XCOMM Solaris and SunOS have iso_8859_1 and iso_8859_15 LC_CTYPES +XCOMM to augment LANG=C +iso_8859_1: en_US.ISO8859-1 +iso_8859_15: en_US.ISO8859-15 +#ifdef WIN32 +XCOMM Microsoft Windows/NT 4.0 SP3 +XCOMM parser doesn't grok embedded spaces in locale name +Afrikaans_South Africa.1252: af_ZA.iso8859-1 +Arabic_Bahrain.1256: ar_BH.iso8859-6 +Arabic_Algeria.1256: ar_DZ.iso8859-6 +Arabic_Egypt.1256: ar_EG.iso8859-6 +Arabic_Iraq.1256: ar_IQ.iso8859-6 +Arabic_Jordan.1256: ar_JO.iso8859-6 +Arabic_Kuwait.1256: ar_KW.iso8859-6 +Arabic_Lebanon.1256: ar_LB.iso8859-6 +Arabic_Libya.1256: ar_LY.iso8859-6 +Arabic_Morocco.1256: ar_MA.iso8859-6 +Arabic_Oman.1256: ar_OM.iso8859-6 +Arabic_Qatar.1256: ar_QA.iso8859-6 +Arabic_Saudi Arabia.1256: ar_SA.iso8859-6 +Arabic_Tunisia.1256: ar_TN.iso8859-6 +Arabic_Yemen.1256: ar_YE.iso8859-6 +Belarusian_Belarus.1251: be_BY.iso8859-5 +Bulgarian_Bulgaria.1251: bg_BG.iso8859-5 +Catalan_Andorra.1252: ca_AD.iso8859-1 +Catalan_Spain.1252: ca_ES.iso8859-1 +Catalan_France.1252: ca_FR.iso8859-1 +Catalan_Italy.1252: ca_IT.iso8859-1 +Czech_Czech Republic.1250: cs_CZ.iso8859-2 +Danish_Denmark.1252: da_DK.iso8859-1 +German_Austria.1252: de_AT.iso8859-1 +German_Switzerland.1252: de_CH.iso8859-1 +German_Germany.1252: de_DE.iso8859-1 +German_Liechtenstein.1252: de_LI.iso8859-1 +German_Luxembourg.1252: de_LU.iso8859-1 +Greek_Greece.1253: el_GR.iso8859-7 +English_Australia.1252: en_AU.iso8859-1 +English_Belize.1252: en_BZ.iso8859-1 +English_Canada.1252: en_CA.iso8859-1 +English_Ireland.1252: en_IE.iso8859-1 +English_Jamaica.1252: en_JM.iso8859-1 +English_New Zealand.1252: en_NZ.iso8859-1 +English_Trinidad y Tobago.1252: en_TT.iso8859-1 +English_United Kingdom.1252: en_UK.iso8859-1 +English_United States.1252: en_US.iso8859-1 +English_South Africa.1252: en_ZA.iso8859-1 +Spanish_Argentina.1252: es_AR.iso8859-1 +Spanish_Bolivia.1252: es_BO.iso8859-1 +Spanish_Chile.1252: es_CL.iso8859-1 +Spanish_Colombia.1252: es_CO.iso8859-1 +Spanish_Costa Rica.1252: es_CR.iso8859-1 +Spanish_Dominican Republic.1252: es_DO.iso8859-1 +Spanish_Ecuador.1252: es_EC.iso8859-1 +Spanish - Modern Sort_Spain.1252: es_ES.iso8859-1 +Spanish - Traditional Sort_Spain.1252: es_ES.iso8859-1 +Spanish_Guatemala.1252: es_GT.iso8859-1 +Spanish_Honduras.1252: es_HN.iso8859-1 +Spanish_Mexican.1252: es_MX.iso8859-1 +Spanish_Nicaragua.1252: es_NI.iso8859-1 +Spanish_Panama.1252: es_PA.iso8859-1 +Spanish_Paraguay.1252: es_PY.iso8859-1 +Spanish_Peru.1252: es_PE.iso8859-1 +Spanish_Puerto Rico.1252: es_PR.iso8859-1 +Spanish_El Salvador.1252: es_SV.iso8859-1 +Spanish_Uruguay.1252: es_UY.iso8859-1 +Spanish_Venezuela.1252: es_VE.iso8859-1 +Estonian_Estonia.1257: et_EE.iso8859-13 +Basque_Spain.1252: eu_ES.iso8859-1 +Finnish_Finland.1252: fi_FI.iso8859-1 +French_Belgium.1252: fr_BE.iso8859-1 +French_Canada.1252: fr_CA.iso8859-1 +French_Switzerland.1252: fr_CH.iso8859-1 +French_France.1252: fr_FR.iso8859-1 +French_Luxembourg.1252: fr_LU.iso8859-1 +Faeroese_Faeroe Islands.1252: fo_FO.iso8859-1 +Hebrew_Israel.1255: he_IL.iso8859-8 +Croatian_Croatia.1250: hr_HR.iso8859-2 +Hungarian_Hungary.1250: hu_HU.iso8859-2 +Indonesian_Indonesia.1252: id_ID.iso8859-1 +Icelandic_Iceland.1252: is_IS.iso8859-1 +Italian_Switzerland.1252: it_CH.iso8859-1 +Italian_Italy.1252: it_IT.iso8859-1 +Japanese_Japan.932: ja_JP.SJIS +Korean_Korea.949: ko_KR.EUC +Lithuanian_Lithuania.1257: lt_LT.iso8859-13 +Latvian_Latvia.1257: lv_LV.iso8859-13 +Dutch_Belgium.1252: nl_BE.iso8859-1 +Dutch_Netherlands.1252: nl_NL.iso8859-1 +Norwegian (Nynorsk)_Norway.1252: no_NO.iso8859-1 +Norwegian (Bokmål)_Norway.1252: no_NO.iso8859-1 +Polish_Poland.1250: pl_PL.iso8859-2 +Portuguese_Brazil.1252: pt_BR.iso8859-1 +Portuguese_Portugal.1252: pt_PT.iso8859-1 +Romanian_Romania.1250: ro_RO.iso8859-2 +Russian_Russia.1251: ru_RU.iso8859-5 +Slovak_Slovakia.1250: sk_SK.iso8859-2 +Slovene_Slovenia.1250: sl_SI.iso8859-2 +Albanian_Albania.1250: sq_AL.iso8859-2 +Serbian (Latin)_Serbia.1250: sr_RS.UTF-8@latin +Swedish_Finland.1252: sv_FI.iso8859-1 +Swedish_Sweden.1252: sv_SE.iso8859-1 +Turkish_Turkey.1254: tr_TR.iso8859-9 +Ukrainian_Ukraine.1251: uk_UA.iso8859-5 +Chinese(PRC)_People's Republic of China.936: zh_CN.EUC +Chinese(PRC)_Hong Kong.950: zh_HK.EUC +Chinese(Singapore)_Signapore.936: zh_SG.EUC +Chinese(Taiwan)_Taiwan.950: zh_TW.EUC +#endif +XCOMM Other miscellaneous locale names +ISO8859-1: en_US.ISO8859-1 +ISO-8859-1: en_US.ISO8859-1 +#ifndef __uxp__ +japan: ja_JP.eucJP +#else +japan: ja_JP.U90 +#endif +Japanese-EUC: ja_JP.eucJP diff --git a/libX11/nls/pt_BR.UTF-8/Compose.pre b/libX11/nls/pt_BR.UTF-8/Compose.pre index bd938aa1b..641c96999 100644 --- a/libX11/nls/pt_BR.UTF-8/Compose.pre +++ b/libX11/nls/pt_BR.UTF-8/Compose.pre @@ -74,7 +74,7 @@ XCOMM on some keyboards. : "~" asciitilde XCOMM Spaces - : " " nobreakspace # NO-BREAK SPACE + : "\240" nobreakspace # NO-BREAK SPACE : " " U2008 # PUNCTUATION SPACE : "©" copyright diff --git a/libX11/specs/XIM/xim.xml b/libX11/specs/XIM/xim.xml index 23558ea39..fa4941153 100644 --- a/libX11/specs/XIM/xim.xml +++ b/libX11/specs/XIM/xim.xml @@ -374,11 +374,9 @@ synchronization problem between the IM library and the IM Server. Using this method, the IM library forwards all KeyPress and KeyRelease events to the IM Server (as required by the Event Flow Control model described in - -) +) and synchronizes with the IM Server (as described in - -). +). @@ -405,8 +403,7 @@ client, and these problems could possibly cause the loss or duplication of key events. For this reason, the BackEnd method is the core method supported, and the FrontEnd method is made available as an extension for performance purposes. (Refer to - - + for more information.) @@ -426,7 +423,7 @@ Fig.1 The Flow of Events - + Event Flow Control @@ -466,8 +463,7 @@ message in order to switch the event flow in the Dynamic Event Flow. The protocol for this process is described in - -. +. @@ -511,8 +507,7 @@ The address information retrievable from the TRANSPORT target is a transport-specific name. The preregistered formats for transport-specific names are listed in - -. +. Additional transport-specific names may be registered with X Consortium. @@ -1431,7 +1426,7 @@ XIM_CLOSE_REPLY (IM Server -> IM library) - + Event Flow Control @@ -1933,7 +1928,7 @@ is an asynchronous request. - + Filtering Events Event filtering is mainly provided for BackEnd method to allow input method @@ -3534,7 +3529,7 @@ The arguments of the XChangeProperty are as follows: The read/write property ATOM allocates the following strings by -XInternAtom. +XInternAtom. @@ -3844,7 +3839,7 @@ The arguments of the XChangeProperty are as follows: (*1) The read/write property ATOM allocates some strings, which are not -allocated by the client, by XInternAtom. +allocated by the client, by XInternAtom. diff --git a/libX11/specs/XKB/ch01.xml b/libX11/specs/XKB/ch01.xml index 5079a411a..e756d1a96 100644 --- a/libX11/specs/XKB/ch01.xml +++ b/libX11/specs/XKB/ch01.xml @@ -1,4 +1,4 @@ - + Overview @@ -6,7 +6,7 @@ The X Keyboard Extension provides capabilities that are lacking or are cumbersome in the core X protocol. - + Core X Protocol Support for Keyboards @@ -74,7 +74,7 @@ heuristics. - + Xkb Keyboard Extension Support for Keyboards @@ -93,7 +93,7 @@ designed to make keyboards more accessible to people with movement impairments. - + Xkb Extension Components @@ -214,7 +214,7 @@ configuration from its database of named components. Partial reconfiguration and incremental reconfiguration are both supported. - + Groups and Shift Levels @@ -225,7 +225,7 @@ description of groups and levels. - + Radio Groups @@ -242,7 +242,7 @@ XkbKB_RadioGroup - + Client Types @@ -285,7 +285,7 @@ operate properly. - + Compatibility With the Core Protocol @@ -301,7 +301,7 @@ configuration. - + Additional Protocol Errors @@ -315,7 +315,7 @@ BadKeyboard - + Extension Library Functions @@ -345,7 +345,7 @@ directly manipulate the new capabilities. - + Error Indications diff --git a/libX11/specs/XKB/ch02.xml b/libX11/specs/XKB/ch02.xml index 55f15a322..57286a475 100644 --- a/libX11/specs/XKB/ch02.xml +++ b/libX11/specs/XKB/ch02.xml @@ -1,6 +1,6 @@ - + Initialization and General Programming Information - + Extension Header Files The following include files are part of the Xkb standard: @@ -48,7 +48,7 @@ keyboard geometry descriptions. - + Extension Name The name of the Xkb extension is given in @@ -70,7 +70,7 @@ XInitExtension directly. - + Determining Library Compatibility If an application is dynamically linked, both the X server and the client-side @@ -160,7 +160,7 @@ XkbQueryExtension - + Initializing the Keyboard Extension Call @@ -469,7 +469,7 @@ XkbOD_Success - + Disabling the Keyboard Extension If a server supports the Xkb extension, the X library normally implements @@ -538,7 +538,7 @@ False - + Protocol Errors Many of the Xkb extension library functions described in this document can @@ -712,7 +712,7 @@ indicated ID - + Display and Device Specifications in Function Calls Where a connection to the server is passed as an argument (Display*) and an diff --git a/libX11/specs/XKB/ch03.xml b/libX11/specs/XKB/ch03.xml index 5ea411c4e..06d6d93f0 100644 --- a/libX11/specs/XKB/ch03.xml +++ b/libX11/specs/XKB/ch03.xml @@ -1,4 +1,4 @@ - + Data Structures @@ -27,7 +27,7 @@ structures. You should use them instead of allocating and freeing the structures yourself. - + Allocating Xkb Data Structures @@ -62,7 +62,7 @@ might be invalidated by calls to allocator functions. - + Adding Data and Editing Data Structures @@ -141,7 +141,7 @@ num_ - + Making Changes to the Server’s Keyboard Description @@ -178,7 +178,7 @@ changes data structure causes indeterminate behavior. - + Tracking Keyboard Changes in the Server @@ -224,7 +224,7 @@ keyboard description. - + Freeing Data Structures diff --git a/libX11/specs/XKB/ch04.xml b/libX11/specs/XKB/ch04.xml index dc9065d79..f267ee512 100644 --- a/libX11/specs/XKB/ch04.xml +++ b/libX11/specs/XKB/ch04.xml @@ -1,4 +1,4 @@ - + Xkb Events @@ -39,7 +39,7 @@ XkbSelectEventDetails specify have been met. - + Xkb Event Types @@ -264,7 +264,7 @@ event. - + Xkb Event Data Structures @@ -334,7 +334,7 @@ chapters where the events are described. - + Selecting Xkb Events @@ -635,7 +635,7 @@ XkbSelectEventDetails - + Event Masks @@ -767,7 +767,7 @@ XkbSelectEvents - + Unified Xkb Event Type diff --git a/libX11/specs/XKB/ch05.xml b/libX11/specs/XKB/ch05.xml index 3785c44d7..626a0c040 100644 --- a/libX11/specs/XKB/ch05.xml +++ b/libX11/specs/XKB/ch05.xml @@ -1,4 +1,4 @@ - + Keyboard State @@ -13,7 +13,7 @@ Keyboard state encompasses all of the transitory information necessary to map a - + Keyboard State Description The Xkb keyboard state is comprised of the state of all keyboard modifiers, the keyboard group, and the state of the pointer buttons. These are grouped into the following components: @@ -294,10 +294,10 @@ The X11 protocol interpretation of modifiers does not include direct support for - + Changing the Keyboard State - + Changing Modifiers @@ -492,7 +492,7 @@ False - + Changing Groups @@ -645,7 +645,7 @@ False - + Determining Keyboard State @@ -739,7 +739,7 @@ All group values are expressed as group indices in the range [0..3]. Modifiers a - + Tracking Keyboard State diff --git a/libX11/specs/XKB/ch06.xml b/libX11/specs/XKB/ch06.xml index 3bd77fab2..f74137131 100644 --- a/libX11/specs/XKB/ch06.xml +++ b/libX11/specs/XKB/ch06.xml @@ -1,4 +1,4 @@ - + Complete Keyboard Description @@ -8,7 +8,7 @@ this single structure and provides references to other sections of this document that discuss the major Xkb components in detail. - + The XkbDescRec Structure @@ -189,7 +189,7 @@ XkbDescRec - + Obtaining a Keyboard Description from the Server @@ -277,7 +277,7 @@ XkbFreeKeyboard - + Tracking Changes to the Keyboard Description in the Server @@ -288,7 +288,7 @@ tracking changes to the keyboard description. - + Allocating and Freeing a Keyboard Description diff --git a/libX11/specs/XKB/ch07.xml b/libX11/specs/XKB/ch07.xml index cd1b7dbd0..93d61d8cc 100644 --- a/libX11/specs/XKB/ch07.xml +++ b/libX11/specs/XKB/ch07.xml @@ -1,4 +1,4 @@ - + Virtual Modifiers @@ -62,7 +62,7 @@ specify the desired behavior, without regard for the actual physical bindings in effect. - + Virtual Modifier Names and Masks @@ -101,7 +101,7 @@ XkbGetNames - + Modifier Definitions @@ -158,7 +158,7 @@ for the keyboard mapping of interest. - + Binding Virtual Modifiers to Real Modifiers @@ -174,7 +174,7 @@ Figure 16.2. - + Virtual Modifier Key Mapping @@ -326,7 +326,7 @@ client has not requested it) while the server’s corresponding definition may contain virtual modifier information. - + Inactive Modifier Sets @@ -364,7 +364,7 @@ virtual modifiers are bound. - + Conventions @@ -384,7 +384,7 @@ following names are suggested: - + Example diff --git a/libX11/specs/XKB/ch08.xml b/libX11/specs/XKB/ch08.xml index 0d19a3d7a..87c0c08f8 100644 --- a/libX11/specs/XKB/ch08.xml +++ b/libX11/specs/XKB/ch08.xml @@ -1,4 +1,4 @@ - + Indicators @@ -42,7 +42,7 @@ keyboard indicators, which makes it straightforward to provide an on-screen used for manipulating them. - + Indicator Names @@ -62,7 +62,7 @@ XkbGetNames - + Indicator Data Structures @@ -74,7 +74,7 @@ XkbIndicatorMapRec - + XkbIndicatorRec @@ -129,7 +129,7 @@ phys_indicators - + XkbIndicatorMapRec @@ -191,7 +191,7 @@ For more information on the effects of explicit changes to indicators and the relationship to the indicator map, see section 8.4.1. - + XkbIndicatorMapRec flags field @@ -306,7 +306,7 @@ indicator on. If the conditions do not match, Xkb turns the indicator off. - + XkbIndicatorMapRec which_groups and groups fields @@ -520,7 +520,7 @@ groups - + XkbIndicatorMapRec which_mods and mods fields @@ -787,7 +787,7 @@ mods - + XkbIndicatorMapRec ctrls field @@ -824,7 +824,7 @@ ctrls - + Getting Information About Indicators @@ -842,7 +842,7 @@ XkbIndicatorRec - + Getting Indicator State @@ -923,7 +923,7 @@ XkbGetIndicatorState - + Getting Indicator Information by Index @@ -1018,7 +1018,7 @@ XkbFreeIndicatorMaps - + Getting Indicator Information by Name @@ -1189,7 +1189,7 @@ BadImplementation - + Changing Indicator Maps and State @@ -1216,7 +1216,7 @@ XkbChangeIndicators. - + Effects of Explicit Changes on Indicators @@ -1314,7 +1314,7 @@ ctrls - + Changing Indicator Maps by Index @@ -1380,7 +1380,7 @@ desc - + Changing Indicator Maps by Name @@ -1567,7 +1567,7 @@ XkbNamesNotify - + The XkbIndicatorChangesRec Structure @@ -1704,7 +1704,7 @@ XkbIndicatorMapNotify - + Tracking Changes to Indicator State or Map @@ -1983,7 +1983,7 @@ BadMatch - + Allocating and Freeing Indicator Maps diff --git a/libX11/specs/XKB/ch09.xml b/libX11/specs/XKB/ch09.xml index d04669a12..9a6bc9b73 100644 --- a/libX11/specs/XKB/ch09.xml +++ b/libX11/specs/XKB/ch09.xml @@ -1,4 +1,4 @@ - + Bells @@ -95,7 +95,7 @@ This chapter describes bell names, the functions used to generate named bells, and the events the server generates for bells. - + Bell Names @@ -192,7 +192,7 @@ XkbBellNotify - + Audible Bells @@ -232,7 +232,7 @@ information on auto-reset controls, see section 10.1.2. - + Bell Functions @@ -334,7 +334,7 @@ XkbBellNotifyEvent - + Generating Named Bells @@ -564,7 +564,7 @@ XkbBell - + Generating Named Bell Events @@ -787,7 +787,7 @@ without first initializing the keyboard extension. - + Forcing a Server-Generated Bell @@ -980,7 +980,7 @@ XkbBell - + Detecting Bells diff --git a/libX11/specs/XKB/ch10.xml b/libX11/specs/XKB/ch10.xml index 76acd032f..97ce484e1 100644 --- a/libX11/specs/XKB/ch10.xml +++ b/libX11/specs/XKB/ch10.xml @@ -1,4 +1,4 @@ - + Keyboard Controls @@ -197,7 +197,7 @@ XkbControlsRec once follow at the end of the chapter. - + Controls that Enable and Disable Other Controls @@ -211,7 +211,7 @@ AutoReset - + The EnabledControls Control @@ -337,7 +337,7 @@ its behavior in detail. - + The AutoReset Control @@ -597,7 +597,7 @@ changes - + Control for Bell Behavior @@ -607,7 +607,7 @@ AudibleBell - + The AudibleBell Control @@ -627,7 +627,7 @@ sound is forced. See section 9.2. - + Controls for Repeat Key Behavior @@ -650,7 +650,7 @@ down. - + The PerKeyRepeat Control @@ -672,7 +672,7 @@ XkbControlsRec - + The RepeatKeys Control @@ -865,7 +865,7 @@ False - + The DetectableAutorepeat Control @@ -1110,7 +1110,7 @@ False - + Controls for Keyboard Overlays (Overlay1 and Overlay2 Controls) @@ -1159,7 +1159,7 @@ XkbKB_Overlay2 - + Controls for Using the Mouse from the Keyboard @@ -1183,7 +1183,7 @@ discussed in Chapter 16. - + The MouseKeys Control @@ -1226,7 +1226,7 @@ Shift+Alt+NumLock , but this may vary depending on the keymap. - + The MouseKeysAccel Control @@ -1302,7 +1302,7 @@ XkbSA_MovePtr action (see section 16.1) specifies relative or absolute pointer motion. - + Absolute Pointer Motion @@ -1319,7 +1319,7 @@ stays at the same X position. - + Relative Pointer Motion @@ -1474,7 +1474,7 @@ MouseKeys Acceleration - + Controls for Better Keyboard Access by Physically Impaired Persons @@ -1493,7 +1493,7 @@ Wisconsin-Madison WI 53705-2280. Phone: 608-262-6966. e-mail: info@trace.wisc.ed . - + The AccessXKeys Control @@ -1561,7 +1561,7 @@ in state, as described in section 10.6.3, or - + The AccessXTimeout Control @@ -1849,7 +1849,7 @@ False - + The AccessXFeedback Control @@ -1989,7 +1989,7 @@ XkbBellNotify - + AccessXNotify Events @@ -2089,7 +2089,7 @@ BounceKeys debounce delay. - + Selecting for AccessX Events @@ -2183,7 +2183,7 @@ values_for_bits - + StickyKeys, RepeatKeys, and MouseKeys Events @@ -2211,7 +2211,7 @@ MouseKeys - + The SlowKeys Control @@ -2399,7 +2399,7 @@ False - + The BounceKeys Control @@ -2581,7 +2581,7 @@ False - + The StickyKeys Control @@ -2698,7 +2698,7 @@ configured: one to automatically disable it, and one to control the latching behavior of modifier keys. - + StickyKeys Options @@ -2904,7 +2904,7 @@ False - + Controls for General Keyboard Mapping @@ -2944,7 +2944,7 @@ IgnoreGroupLock specifying a grab for every possible modifier combination. - + The GroupsWrap Control @@ -3019,7 +3019,7 @@ group_info , which also normalizes a group under certain circumstances. - + The IgnoreLockMods Control @@ -3202,7 +3202,7 @@ False - + The IgnoreGroupLock Control @@ -3222,7 +3222,7 @@ functions (see section 10.1) to change its state. - + The InternalMods Control @@ -3397,7 +3397,7 @@ False - + The XkbControlsRec Structure @@ -4303,7 +4303,7 @@ indicates that the key is a repeating key. - + Querying Controls @@ -4443,7 +4443,7 @@ which - + Changing Controls @@ -4585,7 +4585,7 @@ XkbChangeEnabledControls - + The XkbControlsChangesRec Structure @@ -4707,7 +4707,7 @@ dpy - + Tracking Changes to Keyboard Controls @@ -5019,7 +5019,7 @@ BadMatch - + Allocating and Freeing an XkbControlsRec @@ -5208,7 +5208,7 @@ NULL. - + The Miscellaneous Per-client Controls diff --git a/libX11/specs/XKB/ch11.xml b/libX11/specs/XKB/ch11.xml index fe05e9cb2..1d8d1dc2a 100644 --- a/libX11/specs/XKB/ch11.xml +++ b/libX11/specs/XKB/ch11.xml @@ -1,4 +1,4 @@ - + X Library Controls @@ -53,7 +53,7 @@ normally; however, the feedback that would normally occur with the controls enabled may be missing. - + Controls Affecting Keycode-to-String Translation @@ -71,7 +71,7 @@ affecting simple string lookups are: LevelOneUsesShiftAndLock - + ForceLatin1Lookup @@ -89,7 +89,7 @@ is disabled, allowing characters outside of the Latin1 set to be returned. - + ConsumeLookupMods @@ -166,7 +166,7 @@ refer to Chapter 12. - + AlwaysConsumeShiftAndLock @@ -187,7 +187,7 @@ AlwaysConsumeShiftAndLock - + Controls Affecting Compose Processing @@ -216,7 +216,7 @@ the compose processing controls is optional in an Xkb implementation. - + ConsumeKeysOnComposeFail @@ -255,7 +255,7 @@ ConsumeKeysOnComposeFail - + ComposeLED @@ -288,7 +288,7 @@ this purpose. - + BeepOnComposeFail @@ -325,10 +325,10 @@ ComposeFail - + Controls Effecting Event Delivery - + IgnoreNewKeyboards @@ -361,7 +361,7 @@ MappingNotify - + Manipulating the Library Controls @@ -418,7 +418,7 @@ defined in Table 11.1. - + Determining Which Library Controls are Implemented @@ -459,7 +459,7 @@ library and is composed of an inclusive OR of bits from Table 11.1. - + Determining the State of the Library Controls @@ -502,7 +502,7 @@ is enabled does not imply that it is actually implemented. - + Changing the State of the Library Controls diff --git a/libX11/specs/XKB/ch12.xml b/libX11/specs/XKB/ch12.xml index 1f10261c7..928d83828 100644 --- a/libX11/specs/XKB/ch12.xml +++ b/libX11/specs/XKB/ch12.xml @@ -1,4 +1,4 @@ - + Interpreting Key Events @@ -7,7 +7,7 @@ to directly interpret Xkb data structures. Xkb also modifies the behavior of several core X library functions. - + Effects of Xkb on the Core X Library @@ -24,7 +24,7 @@ includes ways to control or disable it. - + Effects of Xkb on Event State @@ -38,7 +38,7 @@ by the core protocol. - + Effects of Xkb on MappingNotify Events @@ -112,7 +112,7 @@ requesting notification of changes to the legal range of keycodes. - + X Library Functions Affected by Xkb @@ -228,7 +228,7 @@ the keysym are consumed and are not used to look up the string. - + Xkb Event and Keymap Functions diff --git a/libX11/specs/XKB/ch13.xml b/libX11/specs/XKB/ch13.xml index 6f8fce033..101003817 100644 --- a/libX11/specs/XKB/ch13.xml +++ b/libX11/specs/XKB/ch13.xml @@ -1,4 +1,4 @@ - + Keyboard Geometry @@ -244,7 +244,7 @@ section. Keyboard with Four Sections --> - + Shapes and Outlines @@ -348,7 +348,7 @@ degraded image of the keyboard. - + Sections @@ -436,7 +436,7 @@ containing the entire section. - + Rows and Keys @@ -464,7 +464,7 @@ between a key and its predecessor. - + Doodads @@ -629,7 +629,7 @@ XkbLogoDoodad - + Overlay Rows and Overlay Keys @@ -660,7 +660,7 @@ while the key specified in over must not be. - + Drawing a Keyboard Representation @@ -678,7 +678,7 @@ To draw a representation of the keyboard, draw in the following order: - + Geometry Data Structures @@ -956,7 +956,7 @@ angle degrees. - + DoodadRec Structures @@ -1071,7 +1071,7 @@ typedef struct _XkbLogoDoodad { - + Getting Keyboard Geometry From the Server @@ -1202,7 +1202,7 @@ name - + Using Keyboard Geometry @@ -1544,7 +1544,7 @@ under - + Adding Elements to a Keyboard Geometry @@ -2402,7 +2402,7 @@ NULL - + Allocating and Freeing Geometry Components diff --git a/libX11/specs/XKB/ch14.xml b/libX11/specs/XKB/ch14.xml index cc376dba4..518e1aca4 100644 --- a/libX11/specs/XKB/ch14.xml +++ b/libX11/specs/XKB/ch14.xml @@ -1,4 +1,4 @@ - + Xkb Keyboard Mapping @@ -30,7 +30,7 @@ Chapter 15, "Xkb Client Keyboard Mapping" and Chapter 16, "Xkb Server Keyboard Mapping." - + Notation and Terminology @@ -118,7 +118,7 @@ A . - + Core Implementation @@ -161,7 +161,7 @@ Num_Lock - + Xkb Implementation @@ -209,7 +209,7 @@ detail in section 16.2. - + Getting Map Components from the Server @@ -571,7 +571,7 @@ the reply from the server was invalid). - + Changing Map Components in the Server @@ -679,7 +679,7 @@ helper functions and provides a pointer to where they are defined. - + The XkbMapChangesRec Structure @@ -944,7 +944,7 @@ BadValue - + Tracking Changes to Map Components @@ -1042,7 +1042,7 @@ resized - + Allocating and Freeing Client and Server Maps @@ -1082,7 +1082,7 @@ Xfree - + Allocating an Empty Client Map @@ -1271,7 +1271,7 @@ BadValue - + Freeing a Client Map @@ -1363,7 +1363,7 @@ NULL. - + Allocating an Empty Server Map @@ -1548,7 +1548,7 @@ BadAlloc - + Freeing a Server Map diff --git a/libX11/specs/XKB/ch15.xml b/libX11/specs/XKB/ch15.xml index 25ee61f5f..5ab96ae13 100644 --- a/libX11/specs/XKB/ch15.xml +++ b/libX11/specs/XKB/ch15.xml @@ -1,4 +1,4 @@ - + Xkb Client Keyboard Mapping @@ -25,7 +25,7 @@ Figure 15.1 shows the relationships between elements in the client map: Xkb Client Map --> - + The XkbClientMapRec Structure @@ -58,7 +58,7 @@ XkbClientMapRec - + Key Types @@ -398,7 +398,7 @@ level-one symbols. - + The Canonical Key Types @@ -423,7 +423,7 @@ types XkbKeypadIndex - + ONE_LEVEL @@ -451,7 +451,7 @@ XkbOneLevelIndex - + TWO_LEVEL @@ -484,7 +484,7 @@ XkbTwoLevelIndex - + ALPHABETIC @@ -561,7 +561,7 @@ XkbAlphabeticIndex - + KEYPAD @@ -635,7 +635,7 @@ XkbKeypadIndex - + Initializing the Canonical Key Types in a New Client Map @@ -740,7 +740,7 @@ xkb - + Getting Key Types from the Server @@ -834,7 +834,7 @@ num - + Changing the Number of Levels in a Key Type @@ -1004,7 +1004,7 @@ Success - + Copying Key Types @@ -1182,7 +1182,7 @@ Success - + Key Symbol Map @@ -1264,7 +1264,7 @@ These fields are described in detail in the following sections. - + Per-Key Key Type Indices @@ -1392,7 +1392,7 @@ group - + Per-Key Group Information @@ -1646,7 +1646,7 @@ XkbSymMapRec - + Key Width @@ -1664,7 +1664,7 @@ symbols or set of types bound to a key are changed. - + Offset in to the Symbol Map @@ -1974,7 +1974,7 @@ keycode - + Getting the Symbol Map for Keys from the Server @@ -2090,7 +2090,7 @@ BadAlloc - + Changing the Number of Groups and Types Bound to a Key @@ -2332,7 +2332,7 @@ BadAlloc - + Changing the Number of Symbols Bound to a Key @@ -2458,7 +2458,7 @@ a key. - + The Per-Key Modifier Map @@ -2496,7 +2496,7 @@ Chapter 16). - + Getting the Per-Key Modifier Map from the Server diff --git a/libX11/specs/XKB/ch16.xml b/libX11/specs/XKB/ch16.xml index 515323f7b..2cfdd8e2d 100644 --- a/libX11/specs/XKB/ch16.xml +++ b/libX11/specs/XKB/ch16.xml @@ -1,4 +1,4 @@ - + Xkb Server Keyboard Mapping @@ -72,7 +72,7 @@ vmodmap and are defined in section 16.4. - + Key Actions @@ -410,7 +410,7 @@ keycode - + The XkbAction Structure @@ -448,7 +448,7 @@ structures for each action in detail. - + The XkbAnyAction Structure @@ -598,7 +598,7 @@ have an associated data structure. - + Actions for Changing Modifiers’ State @@ -973,7 +973,7 @@ XkbISOAction - + Actions for Changing Group State @@ -1272,7 +1272,7 @@ XkbISOAction - + Actions for Moving the Pointer @@ -1563,7 +1563,7 @@ y - + Actions for Simulating Pointer Button Press and Release @@ -1782,7 +1782,7 @@ XkbSA_LockPtrBtn - + Actions for Changing the Pointer Button Simulated @@ -1982,7 +1982,7 @@ val - + Actions for Locking Modifiers and Group @@ -2424,7 +2424,7 @@ SA_LockControls - + Actions for Changing the Active Screen @@ -2596,7 +2596,7 @@ s - + Actions for Changing Boolean Controls State @@ -2858,7 +2858,7 @@ ctrls - + Actions for Generating Messages @@ -2954,7 +2954,7 @@ XkbActionMessageLength unsigned characters and may be set to anything the keymap designer wishes. - + Detecting Key Action Messages @@ -3090,7 +3090,7 @@ XkbActionMessageLength - + Actions for Generating a Different Keycode @@ -3351,7 +3351,7 @@ v - + Actions for Generating DeviceButtonPress and DeviceButtonRelease @@ -3531,7 +3531,7 @@ XkbSA_LockDeviceBtn - + Actions for Simulating Events from Device Valuators @@ -3683,7 +3683,7 @@ For a dial box with eight dials, any value in the range 0..7 would be correct. - + Obtaining Key Actions for Keys from the Server @@ -3802,7 +3802,7 @@ BadAlloc - + Changing the Number of Actions Bound to a Key @@ -3932,7 +3932,7 @@ a key. - + Key Behavior @@ -3944,7 +3944,7 @@ pressed again. - + Radio Groups @@ -3989,7 +3989,7 @@ currently defined is: - + The XkbBehavior Structure @@ -4123,7 +4123,7 @@ keyboard to implement the behavior. - + Obtaining Key Behaviors for Keys from the Server @@ -4242,7 +4242,7 @@ BadAlloc - + Explicit Components—Avoiding Automatic Remapping by the Server @@ -4354,7 +4354,7 @@ match the key. - + Obtaining Explicit Components for Keys from the Server @@ -4473,7 +4473,7 @@ BadAlloc - + Virtual Modifier Mapping @@ -4565,7 +4565,7 @@ keyboard description are shown in Figure 16.2. Virtual Modifier Relationships --> - + Obtaining Virtual Modifier Bindings from the Server @@ -4670,7 +4670,7 @@ BadAlloc. - + Obtaining Per-Key Virtual Modifier Mappings from the Server diff --git a/libX11/specs/XKB/ch17.xml b/libX11/specs/XKB/ch17.xml index 3c44da5c1..2bf30275b 100644 --- a/libX11/specs/XKB/ch17.xml +++ b/libX11/specs/XKB/ch17.xml @@ -1,4 +1,4 @@ - + The Xkb Compatibility Map @@ -122,7 +122,7 @@ subsequent transformations have a particular result. - + The XkbCompatMap Structure @@ -171,7 +171,7 @@ override controls are used in each of the three cases where compatibility transformations are made. - + Xkb State to Core Protocol State Transformation @@ -247,7 +247,7 @@ event as zero. - + Core Keyboard Mapping to Xkb Keyboard Mapping Transformation @@ -399,7 +399,7 @@ XkbCompatMapRec (see Figure 17.3). - + Symbol Interpretations — the XkbSymInterpretRec Structure @@ -671,7 +671,7 @@ KB_Lock - + Xkb Keyboard Mapping to Core Keyboard Mapping Transformations @@ -733,7 +733,7 @@ modifier mapping. - + Getting Compatibility Map Components From the Server @@ -883,7 +883,7 @@ BadLength - + Using the Compatibility Map @@ -1241,7 +1241,7 @@ bindings of the key. - + Changing the Server’s Compatibility Map @@ -1456,7 +1456,7 @@ NULL - + Tracking Changes to the Compatibility Map @@ -1585,7 +1585,7 @@ compat.sym_interpret - + Allocating and Freeing the Compatibility Map diff --git a/libX11/specs/XKB/ch18.xml b/libX11/specs/XKB/ch18.xml index 025d777f9..98239bf2f 100644 --- a/libX11/specs/XKB/ch18.xml +++ b/libX11/specs/XKB/ch18.xml @@ -1,4 +1,4 @@ - + Symbolic Names @@ -26,7 +26,7 @@ names component of the keyboard description. - + The XkbNamesRec Structure @@ -227,7 +227,7 @@ radio_groups - + Symbolic Names Masks @@ -361,7 +361,7 @@ description are shown in Table 18.1. - + Getting Symbolic Names From the Server @@ -495,7 +495,7 @@ XkbFreeNames - + Changing Symbolic Names on the Server @@ -621,7 +621,7 @@ num_types -<sect3 id='the_xkbnamechangesrec_structure'> +<sect3 id='The_XkbNameChangesRec_Structure'> <title>The XkbNameChangesRec Structure @@ -814,7 +814,7 @@ changes - + Tracking Name Changes @@ -1044,7 +1044,7 @@ BadMatch - + Allocating and Freeing Symbolic Names diff --git a/libX11/specs/XKB/ch19.xml b/libX11/specs/XKB/ch19.xml index 9e675b358..b00afc34b 100644 --- a/libX11/specs/XKB/ch19.xml +++ b/libX11/specs/XKB/ch19.xml @@ -1,4 +1,4 @@ - + Replacing a Keyboard "On the Fly" diff --git a/libX11/specs/XKB/ch20.xml b/libX11/specs/XKB/ch20.xml index e58686f35..20d5b27d4 100644 --- a/libX11/specs/XKB/ch20.xml +++ b/libX11/specs/XKB/ch20.xml @@ -1,4 +1,4 @@ - + Server Database of Keyboard Components @@ -117,7 +117,7 @@ When a keyboard description is built, the components are processed in the order in which they appear in Table 20.1; later definitions override earlier ones. - + Component Names @@ -151,7 +151,7 @@ use of other characters is implementation-dependent. - + Listing the Known Keyboard Components @@ -389,7 +389,7 @@ XkbComponentListRec - + Component Hints @@ -523,7 +523,7 @@ XkbLC_AlternateGroup - + Building a Keyboard Description Using the Server Database diff --git a/libX11/specs/XKB/ch21.xml b/libX11/specs/XKB/ch21.xml index aef8378fe..bd5738991 100644 --- a/libX11/specs/XKB/ch21.xml +++ b/libX11/specs/XKB/ch21.xml @@ -1,4 +1,4 @@ - + Attaching Xkb Actions to X Input Extension Devices @@ -154,7 +154,7 @@ KeyClass silently if Xkb access to those devices is not supported by the X server. - + XkbDeviceInfoRec @@ -364,7 +364,7 @@ them. - + Querying Xkb Features for Non-KeyClass Input Extension Devices @@ -923,8 +923,7 @@ Match - + Allocating, Initializing, and Freeing the XkbDeviceInfoRec Structure @@ -1319,8 +1318,8 @@ themselves are preserved. - -Setting Xkb Features for Non-KeyClass Input Extension Devices + +Setting Xkb Features for Non-KeyClass Input Extension Devices The Xkb extension allows clients to assign any key action to either core @@ -1681,7 +1680,7 @@ BadMatch - + XkbExtensionDeviceNotify Event @@ -1783,7 +1782,7 @@ state or configuration. - + Tracking Changes to Extension Devices diff --git a/libX11/specs/XKB/ch22.xml b/libX11/specs/XKB/ch22.xml index ba16bffbc..8a509b7d4 100644 --- a/libX11/specs/XKB/ch22.xml +++ b/libX11/specs/XKB/ch22.xml @@ -1,4 +1,4 @@ - + Debugging Aids diff --git a/libX11/specs/i18n/framework/framework.xml b/libX11/specs/i18n/framework/framework.xml index a6ec1d9c4..79688e712 100644 --- a/libX11/specs/i18n/framework/framework.xml +++ b/libX11/specs/i18n/framework/framework.xml @@ -71,9 +71,9 @@ in this Software without prior written authorization from X Consortium. - + Framework - + Preface This document proposes to define the structures, methods and their @@ -163,7 +163,7 @@ dependent. The loader is called in _XOpenLC, but caller of -_XOpenLC + does not need to care about its inside. For example, if the loader is implemented with dynamic load functions, and the dynamic module is expected to be unloaded when the corresponding XLCd is freed, @@ -201,7 +201,7 @@ typedef int XlcPosition; #define XlcTail - + Bool _XlcAddLoader XLCdLoadProc proc @@ -211,7 +211,7 @@ typedef int XlcPosition; The -_XlcAddLoader + function registers the specified locale loader "proc" to the internal loader list. The position specifies that the loader "proc" should be placed in the top of the loader list(XlcHead) @@ -227,7 +227,7 @@ when calling time. Remove a loader - + void _XlcRemoveLoader XLCdLoadProc proc @@ -236,7 +236,7 @@ when calling time. The -_XlcRemoveLoader + function removes the locale loader specified by "proc" from the loader list. @@ -280,7 +280,7 @@ independently each other. Open a Locale Method - + XLCd _XOpenLC char *name @@ -289,18 +289,18 @@ independently each other. The -_XOpenLC + function opens a locale method which corresponds to the specified locale name. -_XOpenLC + calls a locale object loader, which is registered via _XlcAddLoader into the internal loader list. If the called loader is valid and successfully opens a locale, -_XOpenLC + returns the XLCd. If the loader is invalid or failed to open a locale, -_XOpenLC + calls the next loader. If all registered loaders cannot open a locale, -_XOpenLC + returns NULL. @@ -316,7 +316,7 @@ function returns an XLCd that are bound to current locale. Close a Locale Method - + void _XCloseLC XLCd lcd @@ -326,7 +326,7 @@ function returns an XLCd that are bound to current locale. The -_XCloseLC + function close a locale method the specified lcd. @@ -334,7 +334,7 @@ function close a locale method the specified lcd. Obtain Locale Method values - + char *_XGetLCValues XLCd lcd @@ -343,7 +343,7 @@ function close a locale method the specified lcd. The -_XGetLCValues + function returns NULL if no error occurred; otherwise, it returns the name of the first argument that could not be obtained. The following values are defined as standard arguments. Other values @@ -445,7 +445,7 @@ typedef struct _XlcCharSetRec { Get an XlcCharSet - + XlcCharSet _XlcGetCharSet char *name @@ -454,10 +454,10 @@ typedef struct _XlcCharSetRec { The -_XlcGetCharSet + function gets an XlcCharSet which corresponds to the charset name specified by "name". -_XlcGetCharSet + returns NULL, if no XlcCharSet bound to specified "name". @@ -600,7 +600,7 @@ The following character sets are pre-registered. Add an XlcCharSet - + Bool _XlcAddCharSet XlcCharSet charset @@ -609,7 +609,7 @@ The following character sets are pre-registered. The -_XlcAddCharSet + function registers XlcCharSet specified by "charset". @@ -619,7 +619,7 @@ function registers XlcCharSet specified by "charsetObtain Character Set values - + char * _XlcGetCSValues XlcCharSet charset @@ -629,7 +629,7 @@ function registers XlcCharSet specified by "charset The -_XlcGetCSValues + function returns NULL if no error occurred; otherwise, it returns the name of the first argument that could not be obtained. The following values are defined as standard arguments. @@ -726,7 +726,7 @@ typedef struct _XlcConvRec { Open a converter - + XlcConv _XlcOpenConverter XLCd from_lcd @@ -737,7 +737,7 @@ typedef struct _XlcConvRec { -_XlcOpenConverter + function opens the converter which converts a text from specified "from_type" to specified "to_type" encoding. If the function cannot find proper converter or cannot open a corresponding @@ -809,7 +809,7 @@ dependent. Close a converter - + void _XlcCloseConverter XlcConv conv @@ -818,7 +818,7 @@ dependent. The -_XlcCloseConverter + function closes the specified converter "conv". @@ -826,7 +826,7 @@ function closes the specified converter "conv". Code conversion - + int _XlcConvert XlcConv conv @@ -841,7 +841,7 @@ function closes the specified converter "conv". The -_XlcConvert + function converts a sequence of characters from one type, in the array specified by "from", into a sequence of corresponding characters in another type, in the array specified by "to". The types are @@ -900,7 +900,7 @@ More than one segment cannot be converted in a call. Reset a converter - + void _XlcResetConverter XlcConv conv @@ -909,7 +909,7 @@ More than one segment cannot be converted in a call. The -_XlcResetConverter + function reset the specified converter "conv". @@ -925,7 +925,7 @@ typedef XlcConv (*XlcOpenConverterProc)(from_lcd, char *to_type; - + Bool _XlcSetConverter XLCd from_lcd @@ -960,7 +960,7 @@ X Locale Database Definition document. Get a resource from database - + void _XlcGetResource XLCd lcd @@ -973,7 +973,7 @@ X Locale Database Definition document. The -_XlcGetResource + function obtains a locale dependent data which is associated with the locale of specified "lcd". The locale data is provided by system locale or by X Locale Database @@ -999,7 +999,7 @@ or freed by caller. Get a locale relative file name - + char *_XlcFileName XLCd lcd @@ -1009,18 +1009,18 @@ or freed by caller. The -_XlcFileName + functions returns a file name which is bound to the specified "lcd" and "category", as a null-terminated string. If no file name can be found, or there is no readable file for the found file name, -_XlcFileName + returns NULL. The returned file name should be freed by caller. The rule for searching a file name is implementation dependent. In current implementation, -_XlcFileName + uses "{category}.dir" file as mapping table, which has pairs of strings, a full locale name and a corresponding file name. @@ -1034,14 +1034,14 @@ strings, a full locale name and a corresponding file name. Compare Latin-1 strings - + int _XlcCompareISOLatin1 char*str1, *str2 - + int _XlcNCompareISOLatin1 char*str1, *str2 @@ -1071,7 +1071,7 @@ except that at most "len" bytes are compared. Resource Utility - + int XlcNumber ArrayType array @@ -1082,7 +1082,7 @@ except that at most "len" bytes are compared. Similar to XtNumber. - + void _XlcCopyFromArg char *src @@ -1091,7 +1091,7 @@ Similar to XtNumber. - + void _XlcCopyToArg char *src @@ -1107,7 +1107,7 @@ and _XtCopyToArg. - + void _XlcCountVaList va_list var @@ -1120,7 +1120,7 @@ Similar to _XtCountVaList. - + void _XlcVaToArgList va_list var @@ -1152,7 +1152,7 @@ typedef struct _XlcResource { #define XlcIgnoreMask (1L<<4) - + void _XlcCompileResourceList XlcResourceList resources @@ -1165,7 +1165,7 @@ Similar to _XtCompileResourceList. - + char * _XlcGetValues XPointer base @@ -1181,7 +1181,7 @@ Similar to Similar to XtGetSubvalues. - + char * _XlcSetValues XPointer base @@ -1205,7 +1205,7 @@ Similar to XtSetSubvalues. The following are ANSI C/MSE Compatible Functions for non-ANSI C environment. - + int _Xmblen char *str @@ -1215,7 +1215,7 @@ The following are ANSI C/MSE Compatible Functions for non-ANSI C environment. The -_Xmblen + function returns the number of characters pointed to by "str". Only "len" bytes in "str" are used in determining the character count returned. "Str" may point at characters from @@ -1224,12 +1224,12 @@ any valid codeset in the current locale. The call -_Xmblen + is equivalent to _Xmbtowc(_Xmbtowc((wchar_t*)NULL, str, len)) - + int _Xmbtowc wchar_t *wstr @@ -1240,7 +1240,7 @@ _Xmbtowc(_Xmbtowc((wchar_t*)NULL, The -_Xmbtowc + function converts the character(s) pointed to by "str" to their wide character representation(s) pointed to by "wstr". "Len" is the number of bytes in "str" to be converted. @@ -1249,12 +1249,12 @@ The return value is the number of characters converted. The call -_Xmbtowc + is equivalent to _Xlcmbtowc((XLCd)NULL, wstr, str, len) - + int _Xlcmbtowc XLCd lcd @@ -1266,7 +1266,7 @@ _Xlcmbtowc((XLCd)NULL, wstr, The -_Xlcmbtowc + function is identical to _Xmbtowc, except that it requires the "lcd" argument. If "lcd" @@ -1277,7 +1277,7 @@ calls to determine the current locale. - + int _Xwctomb char *str @@ -1287,7 +1287,7 @@ to determine the current locale. The -_Xwctomb + function converts a single wide character pointed to by "wc" to its multibyte representation pointed to by "str". On success, the return value is 1. @@ -1295,12 +1295,12 @@ On success, the return value is 1. The call -_Xwctomb + is equivalent to _Xlcwctomb((XLCd)NULL, str, wstr) - + int _Xlcwctomb XLCd lcd @@ -1311,7 +1311,7 @@ _Xlcwctomb((XLCd)NULL, str, w The -_Xlcwctomb + function is identical to _Xwctomb, except that it requires the "lcd" argument. If "lcd" is (XLCd) NULL, _Xlcwctomb, @@ -1320,7 +1320,7 @@ calls to determine the current locale. - + int _Xmbstowcs wchar_t *wstr @@ -1331,7 +1331,7 @@ to determine the current locale. The -_Xmbstowcs + function converts the NULL-terminated string pointed to by "str" to its wide character string representation pointed to by "wstr". "Len" is the number of characters in "str" to be converted. @@ -1339,12 +1339,12 @@ to its wide character string representation pointed to by "w The call -_Xmbstowcs + is equivalent to _Xlcmbstowcs((XLCd)NULL, wstr, str, len) - + int _Xlcmbstowcs XLCd lcd @@ -1356,7 +1356,7 @@ _Xlcmbstowcs((XLCd)NULL, wstr, function is identical to _Xmbstowcs, except that it requires the "lcd" argument. If "lcd" is (XLCd) NULL, _Xlcmbstowcs, @@ -1365,7 +1365,7 @@ calls to determine the current locale. - + int _Xwcstombs char *str @@ -1376,7 +1376,7 @@ to determine the current locale. The -_Xwcstombs + function converts the (wchar_t) NULL terminated wide character string pointed to by "wstr" to the NULL terminated multibyte string pointed to by "str". @@ -1384,12 +1384,12 @@ pointed to by "str". The call -_Xwcstombs + is equivalent to _Xlcwcstombs((XLCd)NULL, str, wstr, len) - + int _Xlcwcstombs XLCd lcd @@ -1401,7 +1401,7 @@ _Xlcwcstombs((XLCd)NULL, str, The -_Xlcwcstombs + function is identical to _Xwcstombs, except that it requires the "lcd" argument. If "lcd" is (XLCd) NULL, _Xlcwcstombs, @@ -1410,7 +1410,7 @@ calls to determine the current locale. - + int _Xwcslen wchar_t *wstr @@ -1419,12 +1419,12 @@ to determine the current locale. The -_Xwcslen + function returns the count of wide characters in the (wchar_t) NULL terminated wide character string pointed to by "wstr". - + wchar_t * _Xwcscpy wchar_t *wstr1 @@ -1432,7 +1432,7 @@ terminated wide character string pointed to by "wstr - + wchar_t * _Xwcsncpy wchar_t *wstr1 @@ -1443,7 +1443,7 @@ terminated wide character string pointed to by "wstr The -_Xwcscpy + function copies the (wchar_t) NULL terminated wide character string pointed to by "wstr2" to the object pointed at by "wstr1". "Wstr1" is (wchar_t) NULL terminated. The return value is a @@ -1452,21 +1452,21 @@ pointer to "wstr1". The -_Xwcsncpy + function is identical to _Xwcscpy, except that it copies "len" wide characters from the object pointed to by "wstr2" to the object pointed to "wstr1". - + int _Xwcscmp wchar_t*wstr1, *wstr2 - + int _Xwcsncmp wchar_t*wstr1, *wstr2 @@ -1476,7 +1476,7 @@ pointed to by "wstr2" to the object pointed to "< The -_Xwcscmp + function compares two (wchar_t) NULL terminated wide character strings. The value returned is an integer less than, equal to, or greater than zero, depending on whether "wstr1" is lexicographicly less then, equal to, @@ -1485,7 +1485,7 @@ or greater than "str2". The -_Xwcsncmp + function is identical to _XlcCompareISOLatin1, except that at most "len" wide characters are compared. diff --git a/libX11/specs/i18n/localedb/localedb.xml b/libX11/specs/i18n/localedb/localedb.xml index c2feccff8..c08516125 100644 --- a/libX11/specs/i18n/localedb/localedb.xml +++ b/libX11/specs/i18n/localedb/localedb.xml @@ -75,7 +75,7 @@ this Software without prior written authorization from the X Consortium. - + LocaleDB @@ -302,8 +302,8 @@ unescaped, is ignored. - -Contents of Database + +Contents of Database The available categories and classes depend on implementation, because different platform will require different information set. diff --git a/libX11/specs/i18n/trans/trans.xml b/libX11/specs/i18n/trans/trans.xml index fe16c1d98..afbc69403 100644 --- a/libX11/specs/i18n/trans/trans.xml +++ b/libX11/specs/i18n/trans/trans.xml @@ -75,7 +75,7 @@ this Software without prior written authorization from the X Consortium. - + X Transport Specification @@ -269,7 +269,7 @@ described below. - + The interface/transport layer functions Following functions are used for the transport interface. @@ -339,7 +339,7 @@ provided so as to make easier to implement the Protocol Layer. Opening connection -When XOpenIM is called, the following function is called to connect +When XOpenIM is called, the following function is called to connect with the IM Server. @@ -369,7 +369,7 @@ connection is established successfully, this function returns True. The Alternative Entry for this function is: - + Bool _XimConnect XIM im @@ -397,7 +397,7 @@ Specifies XIM structure address. -When XCloseIM is called, the following function is called to +When XCloseIM is called, the following function is called to disconnect the connection with the IM Server. The Alternative Entry for this function is: @@ -429,7 +429,7 @@ connection is closed successfully, this function returns True. The Alternative Entry for this function is: - + Bool _XimShutdown XIM im @@ -458,7 +458,7 @@ The following function is called, when Xlib needs to write data to the IM Server. - + Bool _XimWrite XIM im @@ -559,7 +559,7 @@ The following function is called when Xlib waits for response from IM server synchronously. - + Bool _XimRead XIM im @@ -798,7 +798,7 @@ transport layer. If data transfer is completed, the function returns True. The Alternative Entry for this function is: - + void _XimFlush XIM im @@ -833,7 +833,7 @@ will call asynchronous data handler in the protocol layer. Then it calls dispatchers in the transport layer. The dispatchers are implemented by the protocol layer. This function must store the information and prepare for later call of the dispatchers using -_XimCallDispatcher. +. @@ -953,7 +953,7 @@ that the data has been processed by the upper layer. The Alternative Entry for this function is: - + Bool _XimRegisterDispatcher XIM im @@ -1062,7 +1062,7 @@ Protocol packet unit or not. The Alternative Entry for this function is: - + Bool _XimCallDispatcher XIM im @@ -1363,8 +1363,8 @@ lager than this size, is sent via Property. - -read/write + +read/write The data is transferred via either ClientMessage or Window Property in the X Window System. @@ -1589,7 +1589,7 @@ The arguments of the XChangeProperty are as follows: (*1) The read/write property ATOM allocates the following strings by -XInternAtom. +XInternAtom. "_clientXXX" @@ -1888,7 +1888,7 @@ The arguments of the XChangeProperty are as follows: (*1) The read/write property ATOM allocates some strings, which are not -allocated by the client, by XInternAtom. +allocated by the client, by XInternAtom. diff --git a/libX11/specs/libX11/AppA.xml b/libX11/specs/libX11/AppA.xml index 0bd585cdd..6e168ac88 100644 --- a/libX11/specs/libX11/AppA.xml +++ b/libX11/specs/libX11/AppA.xml @@ -20,130 +20,130 @@ and the corresponding protocol request that it generates. - XActivateScreenSaver + ForceScreenSaver - XAddHost + ChangeHosts - XAddHosts + ChangeHosts - XAddToSaveSet + ChangeSaveSet - XAllocColor + AllocColor - XAllocColorCells + AllocColorCells - XAllocColorPlanes + AllocColorPlanes - XAllocNamedColor + AllocNamedColor - XAllowEvents + AllowEvents - XAutoRepeatOff + ChangeKeyboardControl - XAutoRepeatOn + ChangeKeyboardControl - XBell + Bell - XChangeActivePointerGrab + ChangeActivePointerGrab - XChangeGC + ChangeGC - XChangeKeyboardControl + ChangeKeyboardControl - XChangeKeyboardMapping + ChangeKeyboardMapping - XChangePointerControl + ChangePointerControl - XChangeProperty + ChangeProperty - XChangeSaveSet + ChangeSaveSet - XChangeWindowAttributes + ChangeWindowAttributes - XCirculateSubwindows + CirculateWindow - XCirculateSubwindowsDown + CirculateWindow - XCirculateSubwindowsUp + CirculateWindow - XClearArea + ClearArea - XClearWindow + ClearArea - XConfigureWindow + ConfigureWindow - XConvertSelection + ConvertSelection - XCopyArea + CopyArea - XCopyColormapAndFree + CopyColormapAndFree - XCopyGC + CopyGC - XCopyPlane + CopyPlane - XCreateBitmapFromData + CreateGC @@ -159,27 +159,27 @@ and the corresponding protocol request that it generates. PutImage - XCreateColormap + CreateColormap - XCreateFontCursor + CreateGlyphCursor - XCreateGC + CreateGC - XCreateGlyphCursor + CreateGlyphCursor - XCreatePixmap + CreatePixmap - XCreatePixmapCursor + CreateCursor @@ -199,243 +199,243 @@ and the corresponding protocol request that it generates. PutImage - XCreateSimpleWindow + CreateWindow - XCreateWindow + CreateWindow - XDefineCursor + ChangeWindowAttributes - XDeleteProperty + DeleteProperty - XDestroySubwindows + DestroySubwindows - XDestroyWindow + DestroyWindow - XDisableAccessControl + SetAccessControl - XDrawArc + PolyArc - XDrawArcs + PolyArc - XDrawImageString + ImageText8 - XDrawImageString16 + ImageText16 - XDrawLine + PolySegment - XDrawLines + PolyLine - XDrawPoint + PolyPoint - XDrawPoints + PolyPoint - XDrawRectangle + PolyRectangle - XDrawRectangles + PolyRectangle - XDrawSegments + PolySegment - XDrawString + PolyText8 - XDrawString16 + PolyText16 - XDrawText + PolyText8 - XDrawText16 + PolyText16 - XEnableAccessControl + SetAccessControl - XFetchBytes + GetProperty - XFetchName + GetProperty - XFillArc + PolyFillArc - XFillArcs + PolyFillArc - XFillPolygon + FillPoly - XFillRectangle + PolyFillRectangle - XFillRectangles + PolyFillRectangle - XForceScreenSaver + ForceScreenSaver - XFreeColormap + FreeColormap - XFreeColors + FreeColors - XFreeCursor + FreeCursor - XFreeFont + CloseFont - XFreeGC + FreeGC - XFreePixmap + FreePixmap - XGetAtomName + GetAtomName - XGetClassHint + GetProperty - XGetFontPath + GetFontPath - XGetGeometry + GetGeometry - XGetIconName + GetProperty - XGetIconSizes + GetProperty - XGetImage + GetImage - XGetInputFocus + GetInputFocus - XGetKeyboardControl + GetKeyboardControl - XGetKeyboardMapping + GetKeyboardMapping - XGetModifierMapping + GetModifierMapping - XGetMotionEvents + GetMotionEvents - XGetNormalHints + GetProperty - XGetPointerControl + GetPointerControl - XGetPointerMapping + GetPointerMapping - XGetRGBColormaps + GetProperty - XGetScreenSaver + GetScreenSaver - XGetSelectionOwner + GetSelectionOwner - XGetSizeHints + GetProperty - XGetTextProperty + GetProperty - XGetTransientForHint + GetProperty - XGetWMClientMachine + GetProperty - XGetWMColormapWindows + GetProperty @@ -443,23 +443,23 @@ and the corresponding protocol request that it generates. InternAtom - XGetWMHints + GetProperty - XGetWMIconName + GetProperty - XGetWMName + GetProperty - XGetWMNormalHints + GetProperty - XGetWMProtocols + GetProperty @@ -467,11 +467,11 @@ and the corresponding protocol request that it generates. InternAtom - XGetWMSizeHints + GetProperty - XGetWindowAttributes + GetWindowAttributes @@ -479,35 +479,35 @@ and the corresponding protocol request that it generates. GetGeometry - XGetWindowProperty + GetProperty - XGetZoomHints + GetProperty - XGrabButton + GrabButton - XGrabKey + GrabKey - XGrabKeyboard + GrabKeyboard - XGrabPointer + GrabPointer - XGrabServer + GrabServer - XIconifyWindow + InternAtom @@ -515,51 +515,51 @@ and the corresponding protocol request that it generates. SendEvent - XInitExtension + QueryExtension - XInstallColormap + InstallColormap - XInternAtom + InternAtom - XKillClient + KillClient - XListExtensions + ListExtensions - XListFonts + ListFonts - XListFontsWithInfo + ListFontsWithInfo - XListHosts + ListHosts - XListInstalledColormaps + ListInstalledColormaps - XListProperties + ListProperties - XLoadFont + OpenFont - XLoadQueryFont + OpenFont @@ -567,15 +567,15 @@ and the corresponding protocol request that it generates. QueryFont - XLookupColor + LookupColor - XLowerWindow + ConfigureWindow - XMapRaised + ConfigureWindow @@ -583,95 +583,95 @@ and the corresponding protocol request that it generates. MapWindow - XMapSubwindows + MapSubwindows - XMapWindow + MapWindow - XMoveResizeWindow + ConfigureWindow - XMoveWindow + ConfigureWindow - XNoOp + NoOperation - XOpenDisplay + CreateGC - XParseColor + LookupColor - XPutImage + PutImage - XQueryBestCursor + QueryBestSize - XQueryBestSize + QueryBestSize - XQueryBestStipple + QueryBestSize - XQueryBestTile + QueryBestSize - XQueryColor + QueryColors - XQueryColors + QueryColors - XQueryExtension + QueryExtension - XQueryFont + QueryFont - XQueryKeymap + QueryKeymap - XQueryPointer + QueryPointer - XQueryTextExtents + QueryTextExtents - XQueryTextExtents16 + QueryTextExtents - XQueryTree + QueryTree - XRaiseWindow + ConfigureWindow - XReadBitmapFile + CreateGC @@ -687,11 +687,11 @@ and the corresponding protocol request that it generates. PutImage - XRecolorCursor + RecolorCursor - XReconfigureWMWindow + ConfigureWindow @@ -699,203 +699,203 @@ and the corresponding protocol request that it generates. SendEvent - XRemoveFromSaveSet + ChangeSaveSet - XRemoveHost + ChangeHosts - XRemoveHosts + ChangeHosts - XReparentWindow + ReparentWindow - XResetScreenSaver + ForceScreenSaver - XResizeWindow + ConfigureWindow - XRestackWindows + ConfigureWindow - XRotateBuffers + RotateProperties - XRotateWindowProperties + RotateProperties - XSelectInput + ChangeWindowAttributes - XSendEvent + SendEvent - XSetAccessControl + SetAccessControl - XSetArcMode + ChangeGC - XSetBackground + ChangeGC - XSetClassHint + ChangeProperty - XSetClipMask + ChangeGC - XSetClipOrigin + ChangeGC - XSetClipRectangles + SetClipRectangles - XSetCloseDownMode + SetCloseDownMode - XSetCommand + ChangeProperty - XSetDashes + SetDashes - XSetFillRule + ChangeGC - XSetFillStyle + ChangeGC - XSetFont + ChangeGC - XSetFontPath + SetFontPath - XSetForeground + ChangeGC - XSetFunction + ChangeGC - XSetGraphicsExposures + ChangeGC - XSetIconName + ChangeProperty - XSetIconSizes + ChangeProperty - XSetInputFocus + SetInputFocus - XSetLineAttributes + ChangeGC - XSetModifierMapping + SetModifierMapping - XSetNormalHints + ChangeProperty - XSetPlaneMask + ChangeGC - XSetPointerMapping + SetPointerMapping - XSetRGBColormaps + ChangeProperty - XSetScreenSaver + SetScreenSaver - XSetSelectionOwner + SetSelectionOwner - XSetSizeHints + ChangeProperty - XSetStandardProperties + ChangeProperty - XSetState + ChangeGC - XSetStipple + ChangeGC - XSetSubwindowMode + ChangeGC - XSetTextProperty + ChangeProperty - XSetTile + ChangeGC - XSetTransientForHint + ChangeProperty - XSetTSOrigin + ChangeGC - XSetWMClientMachine + ChangeProperty - XSetWMColormapWindows + ChangeProperty @@ -903,27 +903,27 @@ and the corresponding protocol request that it generates. InternAtom - XSetWMHints + ChangeProperty - XSetWMIconName + ChangeProperty - XSetWMName + ChangeProperty - XSetWMNormalHints + ChangeProperty - XSetWMProperties + ChangeProperty - XSetWMProtocols + ChangeProperty @@ -931,63 +931,63 @@ and the corresponding protocol request that it generates. InternAtom - XSetWMSizeHints + ChangeProperty - XSetWindowBackground + ChangeWindowAttributes - XSetWindowBackgroundPixmap + ChangeWindowAttributes - XSetWindowBorder + ChangeWindowAttributes - XSetWindowBorderPixmap + ChangeWindowAttributes - XSetWindowBorderWidth + ConfigureWindow - XSetWindowColormap + ChangeWindowAttributes - XSetZoomHints + ChangeProperty - XStoreBuffer + ChangeProperty - XStoreBytes + ChangeProperty - XStoreColor + StoreColors - XStoreColors + StoreColors - XStoreName + ChangeProperty - XStoreNamedColor + StoreNamedColor - XSync + GetInputFocus @@ -995,55 +995,55 @@ and the corresponding protocol request that it generates. GetInputFocus - XTranslateCoordinates + TranslateCoordinates - XUndefineCursor + ChangeWindowAttributes - XUngrabButton + UngrabButton - XUngrabKey + UngrabKey - XUngrabKeyboard + UngrabKeyboard - XUngrabPointer + UngrabPointer - XUngrabServer + UngrabServer - XUninstallColormap + UninstallColormap - XUnloadFont + CloseFont - XUnmapSubwindows + UnmapSubwindows - XUnmapWindow + UnmapWindow - XWarpPointer + WarpPointer - XWithdrawWindow + SendEvent @@ -1069,387 +1069,387 @@ order) and the Xlib functions that reference it. AllocColor - XAllocColor + AllocColorCells - XAllocColorCells + AllocColorPlanes - XAllocColorPlanes + AllocNamedColor - XAllocNamedColor + AllowEvents - XAllowEvents + Bell - XBell + ChangeActivePointerGrab - XChangeActivePointerGrab + ChangeGC - XChangeGC + - XSetArcMode + - XSetBackground + - XSetClipMask + - XSetClipOrigin + - XSetFillRule + - XSetFillStyle + - XSetFont + - XSetForeground + - XSetFunction + - XSetGraphicsExposures + - XSetLineAttributes + - XSetPlaneMask + - XSetState + - XSetStipple + - XSetSubwindowMode + - XSetTile + - XSetTSOrigin + ChangeHosts - XAddHost + - XAddHosts + - XRemoveHost + - XRemoveHosts + ChangeKeyboardControl - XAutoRepeatOff + - XAutoRepeatOn + - XChangeKeyboardControl + ChangeKeyboardMapping - XChangeKeyboardMapping + ChangePointerControl - XChangePointerControl + ChangeProperty - XChangeProperty + - XSetClassHint + - XSetCommand + - XSetIconName + - XSetIconSizes + - XSetNormalHints + - XSetRGBColormaps + - XSetSizeHints + - XSetStandardProperties + - XSetTextProperty + - XSetTransientForHint + - XSetWMClientMachine + - XSetWMColormapWindows + - XSetWMHints + - XSetWMIconName + - XSetWMName + - XSetWMNormalHints + - XSetWMProperties + - XSetWMProtocols + - XSetWMSizeHints + - XSetZoomHints + - XStoreBuffer + - XStoreBytes + - XStoreName + ChangeSaveSet - XAddToSaveSet + - XChangeSaveSet + - XRemoveFromSaveSet + ChangeWindowAttributes - XChangeWindowAttributes + - XDefineCursor + - XSelectInput + - XSetWindowBackground + - XSetWindowBackgroundPixmap + - XSetWindowBorder + - XSetWindowBorderPixmap + - XSetWindowColormap + - XUndefineCursor + CirculateWindow - XCirculateSubwindowsDown + - XCirculateSubwindowsUp + - XCirculateSubwindows + ClearArea - XClearArea + - XClearWindow + CloseFont - XFreeFont + - XUnloadFont + ConfigureWindow - XConfigureWindow + - XLowerWindow + - XMapRaised + - XMoveResizeWindow + - XMoveWindow + - XRaiseWindow + - XReconfigureWMWindow + - XResizeWindow + - XRestackWindows + - XSetWindowBorderWidth + ConvertSelection - XConvertSelection + CopyArea - XCopyArea + CopyColormapAndFree - XCopyColormapAndFree + CopyGC - XCopyGC + CopyPlane - XCopyPlane + CreateColormap - XCreateColormap + CreateCursor - XCreatePixmapCursor + CreateGC - XCreateGC + - XCreateBitmapFromData + @@ -1457,27 +1457,27 @@ order) and the Xlib functions that reference it. - XOpenDisplay + - XReadBitmapFile + CreateGlyphCursor - XCreateFontCursor + - XCreateGlyphCursor + CreatePixmap - XCreatePixmap + - XCreateBitmapFromData + @@ -1485,63 +1485,63 @@ order) and the Xlib functions that reference it. - XReadBitmapFile + CreateWindow - XCreateSimpleWindow + - XCreateWindow + DeleteProperty - XDeleteProperty + DestroySubwindows - XDestroySubwindows + DestroyWindow - XDestroyWindow + FillPoly - XFillPolygon + ForceScreenSaver - XActivateScreenSaver + - XForceScreenSaver + - XResetScreenSaver + FreeColormap - XFreeColormap + FreeColors - XFreeColors + FreeCursor - XFreeCursor + FreeGC - XFreeGC + - XCreateBitmapFromData + @@ -1549,39 +1549,39 @@ order) and the Xlib functions that reference it. - XReadBitmapFile + FreePixmap - XFreePixmap + GetAtomName - XGetAtomName + GetFontPath - XGetFontPath + GetGeometry - XGetGeometry + - XGetWindowAttributes + GetImage - XGetImage + GetInputFocus - XGetInputFocus + - XSync + @@ -1589,307 +1589,307 @@ order) and the Xlib functions that reference it. GetKeyboardControl - XGetKeyboardControl + GetKeyboardMapping - XGetKeyboardMapping + GetModifierMapping - XGetModifierMapping + GetMotionEvents - XGetMotionEvents + GetPointerControl - XGetPointerControl + GetPointerMapping - XGetPointerMapping + GetProperty - XFetchBytes + - XFetchName + - XGetClassHint + - XGetIconName + - XGetIconSizes + - XGetNormalHints + - XGetRGBColormaps + - XGetSizeHints + - XGetTextProperty + - XGetTransientForHint + - XGetWMClientMachine + - XGetWMColormapWindows + - XGetWMHints + - XGetWMIconName + - XGetWMName + - XGetWMNormalHints + - XGetWMProtocols + - XGetWMSizeHints + - XGetWindowProperty + - XGetZoomHints + GetSelectionOwner - XGetSelectionOwner + GetWindowAttributes - XGetWindowAttributes + GrabButton - XGrabButton + GrabKey - XGrabKey + GrabKeyboard - XGrabKeyboard + GrabPointer - XGrabPointer + GrabServer - XGrabServer + ImageText8 - XDrawImageString + ImageText16 - XDrawImageString16 + InstallColormap - XInstallColormap + InternAtom - XGetWMColormapWindows + - XGetWMProtocols + - XIconifyWindow + - XInternAtom + - XSetWMColormapWindows + - XSetWMProtocols + KillClient - XKillClient + ListExtensions - XListExtensions + ListFonts - XListFonts + ListFontsWithInfo - XListFontsWithInfo + ListHosts - XListHosts + ListInstalledColormaps - XListInstalledColormaps + ListProperties - XListProperties + LookupColor - XLookupColor + - XParseColor + MapSubwindows - XMapSubwindows + MapWindow - XMapRaised + - XMapWindow + NoOperation - XNoOp + OpenFont - XLoadFont + - XLoadQueryFont + PolyArc - XDrawArc + - XDrawArcs + PolyFillArc - XFillArc + - XFillArcs + PolyFillRectangle - XFillRectangle + - XFillRectangles + PolyLine - XDrawLines + PolyPoint - XDrawPoint + - XDrawPoints + PolyRectangle - XDrawRectangle + - XDrawRectangles + PolySegment - XDrawLine + - XDrawSegments + PolyText8 - XDrawString + - XDrawText + PolyText16 - XDrawString16 + - XDrawText16 + PutImage - XPutImage + - XCreateBitmapFromData + @@ -1897,191 +1897,191 @@ order) and the Xlib functions that reference it. - XReadBitmapFile + QueryBestSize - XQueryBestCursor + - XQueryBestSize + - XQueryBestStipple + - XQueryBestTile + QueryColors - XQueryColor + - XQueryColors + QueryExtension - XInitExtension + - XQueryExtension + QueryFont - XLoadQueryFont + - XQueryFont + QueryKeymap - XQueryKeymap + QueryPointer - XQueryPointer + QueryTextExtents - XQueryTextExtents + - XQueryTextExtents16 + QueryTree - XQueryTree + RecolorCursor - XRecolorCursor + ReparentWindow - XReparentWindow + RotateProperties - XRotateBuffers + - XRotateWindowProperties + SendEvent - XIconifyWindow + - XReconfigureWMWindow + - XSendEvent + - XWithdrawWindow + SetAccessControl - XDisableAccessControl + - XEnableAccessControl + - XSetAccessControl + SetClipRectangles - XSetClipRectangles + SetCloseDownMode - XSetCloseDownMode + SetDashes - XSetDashes + SetFontPath - XSetFontPath + SetInputFocus - XSetInputFocus + SetModifierMapping - XSetModifierMapping + SetPointerMapping - XSetPointerMapping + SetScreenSaver - XGetScreenSaver + - XSetScreenSaver + SetSelectionOwner - XSetSelectionOwner + StoreColors - XStoreColor + - XStoreColors + StoreNamedColor - XStoreNamedColor + TranslateCoordinates - XTranslateCoordinates + UngrabButton - XUngrabButton + UngrabKey - XUngrabKey + UngrabKeyboard - XUngrabKeyboard + UngrabPointer - XUngrabPointer + UngrabServer - XUngrabServer + UninstallColormap - XUninstallColormap + UnmapSubwindows @@ -2089,15 +2089,15 @@ order) and the Xlib functions that reference it. UnmapWindow - XUnmapWindow + - XWithdrawWindow + WarpPointer - XWarpPointer + diff --git a/libX11/specs/libX11/AppB.xml b/libX11/specs/libX11/AppB.xml index ca435fb01..8c424bda1 100644 --- a/libX11/specs/libX11/AppB.xml +++ b/libX11/specs/libX11/AppB.xml @@ -1,52 +1,52 @@ - - - -X Font Cursors - -The following are the available cursors that can be used with -XCreateFontCursor. - - -#define XC_X_cursor 0 #define XC_ll_angle 76 -#define XC_arrow 2 #define XC_lr_angle 78 -#define XC_based_arrow_down 4 #define XC_man 80 -#define XC_based_arrow_up 6 #define XC_middlebutton 82 -#define XC_boat 8 #define XC_mouse 84 -#define XC_bogosity 10 #define XC_pencil 86 -#define XC_bottom_left_corner 12 #define XC_pirate 88 -#define XC_bottom_right_corner 14 #define XC_plus 90 -#define XC_bottom_side 16 #define XC_question_arrow 92 -#define XC_bottom_tee 18 #define XC_right_ptr 94 -#define XC_box_spiral 20 #define XC_right_side 96 -#define XC_center_ptr 22 #define XC_right_tee 98 -#define XC_circle 24 #define XC_rightbutton 100 -#define XC_clock 26 #define XC_rtl_logo 102 -#define XC_coffee_mug 28 #define XC_sailboat 104 -#define XC_cross 30 #define XC_sb_down_arrow 106 -#define XC_cross_reverse 32 #define XC_sb_h_double_arrow 108 -#define XC_crosshair 34 #define XC_sb_left_arrow 110 -#define XC_diamond_cross 36 #define XC_sb_right_arrow 112 -#define XC_dot 38 #define XC_sb_up_arrow 114 -#define XC_dot_box_mask 40 #define XC_sb_v_double_arrow 116 -#define XC_double_arrow 42 #define XC_shuttle 118 -#define XC_draft_large 44 #define XC_sizing 120 -#define XC_draft_small 46 #define XC_spider 122 -#define XC_draped_box 48 #define XC_spraycan 124 -#define XC_exchange 50 #define XC_star 126 -#define XC_fleur 52 #define XC_target 128 -#define XC_gobbler 54 #define XC_tcross 130 -#define XC_gumby 56 #define XC_top_left_arrow 132 -#define XC_hand1 58 #define XC_top_left_corner 134 -#define XC_hand2 60 #define XC_top_right_corner 136 -#define XC_heart 62 #define XC_top_side 138 -#define XC_icon 64 #define XC_top_tee 140 -#define XC_iron_cross 66 #define XC_trek 142 -#define XC_left_ptr 68 #define XC_ul_angle 144 -#define XC_left_side 70 #define XC_umbrella 146 -#define XC_left_tee 72 #define XC_ur_angle 148 -#define XC_leftbutton 74 #define XC_watch 150 - #define XC_xterm 152 - - - + + + +X Font Cursors + +The following are the available cursors that can be used with +. + + +#define XC_X_cursor 0 #define XC_ll_angle 76 +#define XC_arrow 2 #define XC_lr_angle 78 +#define XC_based_arrow_down 4 #define XC_man 80 +#define XC_based_arrow_up 6 #define XC_middlebutton 82 +#define XC_boat 8 #define XC_mouse 84 +#define XC_bogosity 10 #define XC_pencil 86 +#define XC_bottom_left_corner 12 #define XC_pirate 88 +#define XC_bottom_right_corner 14 #define XC_plus 90 +#define XC_bottom_side 16 #define XC_question_arrow 92 +#define XC_bottom_tee 18 #define XC_right_ptr 94 +#define XC_box_spiral 20 #define XC_right_side 96 +#define XC_center_ptr 22 #define XC_right_tee 98 +#define XC_circle 24 #define XC_rightbutton 100 +#define XC_clock 26 #define XC_rtl_logo 102 +#define XC_coffee_mug 28 #define XC_sailboat 104 +#define XC_cross 30 #define XC_sb_down_arrow 106 +#define XC_cross_reverse 32 #define XC_sb_h_double_arrow 108 +#define XC_crosshair 34 #define XC_sb_left_arrow 110 +#define XC_diamond_cross 36 #define XC_sb_right_arrow 112 +#define XC_dot 38 #define XC_sb_up_arrow 114 +#define XC_dot_box_mask 40 #define XC_sb_v_double_arrow 116 +#define XC_double_arrow 42 #define XC_shuttle 118 +#define XC_draft_large 44 #define XC_sizing 120 +#define XC_draft_small 46 #define XC_spider 122 +#define XC_draped_box 48 #define XC_spraycan 124 +#define XC_exchange 50 #define XC_star 126 +#define XC_fleur 52 #define XC_target 128 +#define XC_gobbler 54 #define XC_tcross 130 +#define XC_gumby 56 #define XC_top_left_arrow 132 +#define XC_hand1 58 #define XC_top_left_corner 134 +#define XC_hand2 60 #define XC_top_right_corner 136 +#define XC_heart 62 #define XC_top_side 138 +#define XC_icon 64 #define XC_top_tee 140 +#define XC_iron_cross 66 #define XC_trek 142 +#define XC_left_ptr 68 #define XC_ul_angle 144 +#define XC_left_side 70 #define XC_umbrella 146 +#define XC_left_tee 72 #define XC_ur_angle 148 +#define XC_leftbutton 74 #define XC_watch 150 + #define XC_xterm 152 + + + diff --git a/libX11/specs/libX11/AppC.xml b/libX11/specs/libX11/AppC.xml index 72103095b..c2e7f54fb 100644 --- a/libX11/specs/libX11/AppC.xml +++ b/libX11/specs/libX11/AppC.xml @@ -42,13 +42,13 @@ Basic Protocol Support Routines The basic protocol requests for extensions are -XQueryExtension + and -XListExtensions. +. XQueryExtension - + Bool XQueryExtension Display *display @@ -96,29 +96,29 @@ and The -XQueryExtension + function determines if the named extension is present. If the extension is not present, -XQueryExtension + returns False; otherwise, it returns True. If the extension is present, -XQueryExtension + returns the major opcode for the extension to major_opcode_return; otherwise, it returns zero. Any minor opcode and the request formats are specific to the extension. If the extension involves additional event types, -XQueryExtension + returns the base event type code to first_event_return; otherwise, it returns zero. The format of the events is specific to the extension. If the extension involves additional error codes, -XQueryExtension + returns the base error code to first_error_return; otherwise, it returns zero. @@ -134,7 +134,7 @@ are all considered different names. XListExtensions - + char **XListExtensions Display *display @@ -168,7 +168,7 @@ Returns the number of extensions listed. The -XListExtensions + function returns a list of all extensions supported by the server. If the data returned by the server is in the Latin Portable Character Encoding, then the returned strings are in the Host Portable Character Encoding. @@ -176,7 +176,7 @@ Otherwise, the result is implementation-dependent. XFreeExtensionList - + XFreeExtensionList char **list @@ -199,9 +199,9 @@ Specifies the list of extension names. The -XFreeExtensionList + function frees the memory allocated by -XListExtensions. +. Hooking into Xlib @@ -219,7 +219,7 @@ called stubs. In extensions, stubs first should check to see if they have initialized themselves on a connection. If they have not, they then should call -XInitExtension + to attempt to initialize themselves on the connection. @@ -234,7 +234,7 @@ called when these events occur. The XExtCodes structure returns the information from -XInitExtension + and is defined in <X11/Xlib.h>: @@ -257,7 +257,7 @@ typedef struct _XExtCodes { /* public to extension, cannot be changed */ XInitExtension - + XExtCodes *XInitExtension Display *display @@ -291,7 +291,7 @@ Specifies the extension name. The -XInitExtension + function determines if the named extension exists. Then, it allocates storage for maintaining the information about the extension on the connection, @@ -299,7 +299,7 @@ chains this onto the extension list for the connection, and returns the information the stub implementor will need to access the extension. If the extension does not exist, -XInitExtension + returns NULL. @@ -321,7 +321,7 @@ This extension number is unique only to a single connection. XAddExtension - + XExtCodes *XAddExtension Display *display @@ -344,7 +344,7 @@ Specifies the connection to the X server. For local Xlib extensions, the -XAddExtension + function allocates the XExtCodes structure, bumps the extension number count, @@ -369,7 +369,7 @@ extension. XESetCloseDisplay - + int XESetCloseDisplay Display *display @@ -414,7 +414,7 @@ Specifies the procedure to call when the display is closed. The -XESetCloseDisplay + function defines a procedure to be called whenever XCloseDisplay is called. @@ -437,7 +437,7 @@ with these arguments: XESetCreateGC - + int *XESetCreateGC Display *display @@ -482,7 +482,7 @@ Specifies the procedure to call when a GC is closed. The -XESetCreateGC + function defines a procedure to be called whenever a new GC is created. It returns any previously defined procedure, usually NULL. @@ -504,7 +504,7 @@ your procedure is called with these arguments: XESetCopyGC - + int *XESetCopyGC Display *display @@ -549,7 +549,7 @@ Specifies the procedure to call when GC components are copied. The -XESetCopyGC + function defines a procedure to be called whenever a GC is copied. It returns any previously defined procedure, usually NULL. @@ -567,7 +567,7 @@ your procedure is called with these arguments: - + int *XESetFreeGC Display *display @@ -611,7 +611,7 @@ Specifies the procedure to call when a GC is freed. The -XESetFreeGC + function defines a procedure to be called whenever a GC is freed. It returns any previously defined procedure, usually NULL. @@ -638,7 +638,7 @@ your procedure is called with these arguments: XESetCreateFont - + int *XESetCreateFont Display *display @@ -683,20 +683,20 @@ Specifies the procedure to call when a font is created. The -XESetCreateFont + function defines a procedure to be called whenever -XLoadQueryFont + and -XQueryFont + are called. It returns any previously defined procedure, usually NULL. When -XLoadQueryFont + or -XQueryFont + is called, your procedure is called with these arguments: @@ -717,7 +717,7 @@ your procedure is called with these arguments: XESetFreeFont - + int *XESetFreeFont Display *display @@ -762,16 +762,16 @@ Specifies the procedure to call when a font is freed. The -XESetFreeFont + function defines a procedure to be called whenever -XFreeFont + is called. It returns any previously defined procedure, usually NULL. When -XFreeFont + is called, your procedure is called with these arguments: @@ -791,9 +791,9 @@ is called, your procedure is called with these arguments: The -XESetWireToEvent + and -XESetEventToWire + functions allow you to define new events to the library. An XEvent @@ -829,7 +829,7 @@ in the structure will be fully portable between machines. XESetWireToEvent - + int *XESetWireToEvent Display *display @@ -874,7 +874,7 @@ Specifies the procedure to call when converting an event. The -XESetWireToEvent + function defines a procedure to be called when an event needs to be converted from wire format (xEvent) @@ -882,7 +882,7 @@ to host format (XEvent). The event number defines which protocol event number to install a conversion procedure for. -XESetWireToEvent + returns any previously defined procedure. You can replace a core event conversion function with one @@ -931,13 +931,13 @@ if it should not be placed in the queue. To initialize the serial number component of the event, call -_XSetLastRequestRead + with the event and use the return value. _XSetLastRequestRead - + unsigned long_XSetLastRequestRead Display *display @@ -971,7 +971,7 @@ Specifies the wire event structure. The -_XSetLastRequestRead + function computes and returns a complete serial number from the partial serial number in the event. @@ -979,7 +979,7 @@ serial number in the event. XESetEventToWire - + Status *XESetEventToWire Display *display @@ -1024,7 +1024,7 @@ Specifies the procedure to call when converting an event. The -XESetEventToWire + function defines a procedure to be called when an event needs to be converted from host format (XEvent) @@ -1033,7 +1033,7 @@ to wire format form. The event number defines which protocol event number to install a conversion procedure for. -XESetEventToWire + returns any previously defined procedure. It returns zero if the conversion fails or nonzero otherwise. @@ -1071,7 +1071,7 @@ structure. XESetWireToError - + Bool *XESetWireToError Display *display @@ -1116,12 +1116,12 @@ Specifies the procedure to call when an error is received. The -XESetWireToError + function defines a procedure to be called when an extension error needs to be converted from wire format to host format. The error number defines which protocol error code to install the conversion procedure for. -XESetWireToError + returns any previously defined procedure. @@ -1166,7 +1166,7 @@ otherwise, it should return XESetError - + int *XESetError Display *display @@ -1219,7 +1219,7 @@ case, and are typically programmed to be synchronous). When Xlib detects a protocol error in -_XReply, +, it calls your procedure with these arguments: @@ -1240,7 +1240,7 @@ it calls your procedure with these arguments: The err argument is a pointer to the 32-byte wire format error. The codes argument is a pointer to the extension codes structure. The ret_code argument is the return code you may want -_XReply + returned to. @@ -1252,12 +1252,12 @@ the client's error handler is called. see section 11.8.2.) If your procedure returns nonzero, the error is suppressed, and -_XReply + returns the value of ret_code. XESetErrorString - + char *XESetErrorString Display *display @@ -1302,9 +1302,9 @@ Specifies the procedure to call to obtain an error string. The -XGetErrorText + function returns a string to the user for an error. -XESetErrorString + allows you to define a procedure to be called that should return a pointer to the error message. The following is an example. @@ -1333,7 +1333,7 @@ error message into buffer. XESetPrintErrorValues - + void *XESetPrintErrorValues Display *display @@ -1378,7 +1378,7 @@ Specifies the procedure to call when an error is printed. The -XESetPrintErrorValues + function defines a procedure to be called when an extension error is printed, to print the error values. Use this function for extension errors that contain additional error values @@ -1409,13 +1409,13 @@ The structure pointed at by ev is guaranteed to be as large as an structure and so can be cast to a type larger than an XErrorEvent to obtain additional values set by using -XESetWireToError. +. The underlying type of the fp argument is system dependent; on a POSIX-compliant system, fp should be cast to type FILE*. XESetFlushGC - + int *XESetFlushGC Display *display @@ -1460,9 +1460,9 @@ Specifies the procedure to call when a GC is flushed. The procedure set by the -XESetFlushGC + function has the same interface as the procedure set by the -XESetCopyGC + function, but is called when a GC cache needs to be updated in the server. XESetBeforeFlush @@ -1603,7 +1603,7 @@ union { Display *display; XEHeadOfExtensionList - + XExtData **XEHeadOfExtensionList XEDataObject object @@ -1626,12 +1626,12 @@ Specifies the object. The -XEHeadOfExtensionList + function returns a pointer to the list of extension structures attached to the specified object. In concert with -XAddToExtensionList, -XEHeadOfExtensionList +, + allows an extension to attach arbitrary data to any of the structures of types contained in XEDataObject. @@ -1639,7 +1639,7 @@ of types contained in XAddToExtensionList - + XAddToExtensionList XExtData **structure @@ -1679,7 +1679,7 @@ before calling this function. XFindOnExtensionList - + XExtData *XFindOnExtensionList struct_XExtData **structure @@ -1705,7 +1705,7 @@ Specifies the extension list. Specifies the extension number from -XInitExtension. +. @@ -1714,7 +1714,7 @@ Specifies the extension number from The -XFindOnExtensionList + function returns the first extension data structure for the extension numbered number. It is expected that an extension will add at most one extension @@ -1724,13 +1724,13 @@ There is no way to find additional structures. The -XAllocID + macro, which allocates and returns a resource ID, is defined in <X11/Xlib.h>. XAllocID - + XAllocID Display *display @@ -1760,12 +1760,12 @@ It returns a resource ID that you can use when creating new resources. The -XAllocIDs + macro allocates and returns an array of resource ID. XAllocIDs - + XAllocIDs Display *display @@ -1814,7 +1814,7 @@ This macro is a call through the structure to an internal resource ID allocator. It returns resource IDs to the array supplied by the caller. To correctly handle automatic reuse of resource IDs, you must call -XAllocIDs + when requesting multiple resource IDs. This call might generate protocol requests. @@ -1832,17 +1832,17 @@ in its GC. The -FlushGC + macro checks the dirty bits in the library's GC structure and calls -_XFlushGCCache + if any elements have changed. The -FlushGC + macro is defined as follows: FlushGC - + FlushGC Display *display @@ -1882,17 +1882,17 @@ using it, so if you only stored the value in the cache without forcing a protocol request, the resource might be destroyed before being set into the GC. You can use the -_XFlushGCCache + procedure to force the cache to be flushed. The -_XFlushGCCache + procedure is defined as follows: _XFlushGCCache - + _XFlushGCCache Display *display @@ -1945,7 +1945,7 @@ to just extend the previous graphics request by extending the length field of the request and appending the data to the buffer. This can improve performance by five times or more in naive programs. For example, here is the source for the -XDrawPoint + stub. (Writing extension stubs is discussed in the next section.) @@ -2007,7 +2007,7 @@ there is a symbol defined in of EPERBATCH on the number of requests batched. Most of the performance benefit occurs in the first few merged requests. Note that -FlushGC + is called before picking up the value of last_req, because it may modify this field. @@ -2314,7 +2314,7 @@ architecture. Two calls, which are generally implemented as macros, have been provided. LockDisplay - + LockDisplay Display *display @@ -2324,7 +2324,7 @@ Two calls, which are generally implemented as macros, have been provided. UnlockDisplay - + UnlockDisplay Display *display @@ -2427,13 +2427,13 @@ req->arg2 = arg2; ... A few stub procedures (such as -XCreateGC + and -XCreatePixmap) +) return a resource ID to the caller but pass a resource ID as an argument to the protocol request. Such procedures use the macro -XAllocID + to allocate a resource ID from the range of IDs that were assigned to this client when it opened the connection. @@ -2448,13 +2448,13 @@ return (rid); Finally, some stub procedures transmit a fixed amount of variable-length data after the request. Typically, these procedures (such as -XMoveWindow + and -XSetBackground) +) are special cases of more general functions like -XMoveResizeWindow + and -XChangeGC. +. These procedures use GetReqExtra, which is the same as @@ -2491,23 +2491,23 @@ then you must round the length up and shift it before adding: req->length += (nbytes+3)>>2; To transmit variable-length data, use the -Data + macros. If the data fits into the output buffer, then this macro copies it to the buffer. If it does not fit, however, the -Data + macro calls _XSend, which transmits first the contents of the buffer and then your data. The -Data + macros take three arguments: the display, a pointer to the beginning of the data, and the number of bytes to be sent. - + Data display @@ -2519,7 +2519,7 @@ and the number of bytes to be sent. -Data, +, Data16, and Data32 @@ -2536,13 +2536,13 @@ If the protocol request requires a reply, then call the procedure _XSend instead of the -Data + macro. _XSend takes the same arguments, but because it sends your data immediately instead of copying it into the output buffer (which would later be flushed anyway by the following call on -_XReply), +), it is faster. Replies @@ -2551,20 +2551,20 @@ Replies If the protocol request has a reply, then call -_XReply + after you have finished dealing with all the fixed-length and variable-length arguments. -_XReply + flushes the output buffer and waits for an xReply packet to arrive. If any events arrive in the meantime, -_XReply + places them in the queue for later use. _XReply - + Status _XReply Display *display @@ -2621,12 +2621,12 @@ should be discarded. The -_XReply + function waits for a reply packet and copies its contents into the specified rep. -_XReply + handles error and event packets that occur before the reply is received. -_XReply + takes four arguments: @@ -2655,7 +2655,7 @@ in the reply structure A Boolean that indicates whether -_XReply + is to discard any additional bytes beyond those it was told to read @@ -2693,7 +2693,7 @@ larger, but compatible, xGetWindowAttributesReply that contains additional attribute data at the end. -_XReply + returns True if it received a reply successfully or @@ -2725,12 +2725,12 @@ change the to False, and use the appropriate -_XRead + function to read the variable-length data. - + _XRead Display *display @@ -2775,12 +2775,12 @@ Specifies the number of bytes required. The -_XRead + function reads the specified number of bytes into data_return. - + _XRead16 Display *display @@ -2825,14 +2825,14 @@ Specifies the number of bytes required. The -_XRead16 + function reads the specified number of bytes, unpacking them as 16-bit quantities, into the specified array as shorts. - + _XRead32 Display *display @@ -2877,14 +2877,14 @@ Specifies the number of bytes required. The -_XRead32 + function reads the specified number of bytes, unpacking them as 32-bit quantities, into the specified array as longs. - + _XRead16Pad Display *display @@ -2929,17 +2929,17 @@ Specifies the number of bytes required. The -_XRead16Pad + function reads the specified number of bytes, unpacking them as 16-bit quantities, into the specified array as shorts. If the number of bytes is not a multiple of four, -_XRead16Pad + reads and discards up to two additional pad bytes. - + _XReadPad Display *display @@ -2984,10 +2984,10 @@ Specifies the number of bytes required. The -_XReadPad + function reads the specified number of bytes into data_return. If the number of bytes is not a multiple of four, -_XReadPad + reads and discards up to three additional pad bytes. @@ -3039,7 +3039,7 @@ critical section: _XAllocScratch - + char *_XAllocScratch Display *display @@ -3078,14 +3078,14 @@ that might permit another thread to execute inside Xlib. For example, the pointer cannot be assumed valid after any use of the GetReq or -Data + families of macros, after any use of -_XReply, +, or after any use of the _XSend or -_XRead + families of functions. @@ -3096,7 +3096,7 @@ critical sections: _XAllocTemp - + char *_XAllocTemp Display *display @@ -3135,7 +3135,7 @@ The following function returns the storage: _XFreeTemp - + void _XFreeTemp Display *display @@ -3180,7 +3180,7 @@ Specifies the size of the buffer. You must pass back the same pointer and size that were returned by -_XAllocTemp. +. Portability Considerations @@ -3288,7 +3288,7 @@ Call your initialization procedure and pass to it the display pointer. Once in your initialization procedure, call -XInitExtension; +; if it succeeds, store the pointer returned into this array. Make sure to establish a close display handler to allow you to zero the entry. Do whatever other initialization your extension requires. diff --git a/libX11/specs/libX11/AppD.xml b/libX11/specs/libX11/AppD.xml index a8cd375c3..f3c0e2f6a 100644 --- a/libX11/specs/libX11/AppD.xml +++ b/libX11/specs/libX11/AppD.xml @@ -47,16 +47,16 @@ Get X environment defaults To specify a minimum set of properties describing the simplest application, use -XSetStandardProperties. +. This function has been superseded by -XSetWMProperties + and sets all or portions of the WM_NAME, WM_ICON_NAME, WM_HINTS, WM_COMMAND, and WM_NORMAL_HINTS properties. XSetStandardProperties - + XSetStandardProperties Display *display @@ -159,22 +159,22 @@ Specifies a pointer to the size hints for the window in its normal state. The -XSetStandardProperties + function provides a means by which simple applications set the most essential properties with a single call. -XSetStandardProperties + should be used to give a window manager some information about your program's preferences. It should not be used by applications that need to communicate more information than is possible with -XSetStandardProperties. +. (Typically, argv is the argv array of your main program.) If the strings are not in the Host Portable Character Encoding, the result is implementation-dependent. -XSetStandardProperties + can generate BadAlloc and @@ -199,13 +199,13 @@ header file and use the WM_NORMAL_HINTS property. To set the size hints for a given window in its normal state, use -XSetNormalHints. +. This function has been superseded by -XSetWMNormalHints. +. XSetNormalHints - + XSetNormalHints Display *display @@ -250,15 +250,15 @@ Specifies a pointer to the size hints for the window in its normal state. The -XSetNormalHints + function sets the size hints structure for the specified window. Applications use -XSetNormalHints + to inform the window manager of the size or position desirable for that window. In addition, an application that wants to move or resize itself should call -XSetNormalHints + and specify its new desired location and size as well as making direct Xlib calls to move or resize. This is because window managers may ignore redirected @@ -271,13 +271,13 @@ an application not only must assign values to the appropriate members in the hints structure but also must set the flags member of the structure to indicate which information is present and where it came from. A call to -XSetNormalHints + is meaningless, unless the flags member is set to indicate which members of the structure have been assigned values. -XSetNormalHints + can generate BadAlloc and @@ -288,13 +288,13 @@ errors. To return the size hints for a window in its normal state, use -XGetNormalHints. +. This function has been superseded by -XGetWMNormalHints. +. XGetNormalHints - + Status XGetNormalHints Display *display @@ -339,14 +339,14 @@ Returns the size hints for the window in its normal state. The -XGetNormalHints + function returns the size hints for a window in its normal state. It returns a nonzero status if it succeeds or zero if the application specified no normal size hints for this window. -XGetNormalHints + can generate a BadWindow error. @@ -359,13 +359,13 @@ The next two functions set and read the WM_ZOOM_HINTS prope To set the zoom hints for a window, use -XSetZoomHints. +. This function is no longer supported by the Inter-Client Communication Conventions Manual. XSetZoomHints - + XSetZoomHints Display *display @@ -412,13 +412,13 @@ Specifies a pointer to the zoom hints. Many window managers think of windows in one of three states: iconic, normal, or zoomed. The -XSetZoomHints + function provides the window manager with information for the window in the zoomed state. -XSetZoomHints + can generate BadAlloc and @@ -429,13 +429,13 @@ errors. To read the zoom hints for a window, use -XGetZoomHints. +. This function is no longer supported by the Inter-Client Communication Conventions Manual. XGetZoomHints - + Status XGetZoomHints Display *display @@ -480,14 +480,14 @@ Returns the zoom hints. The -XGetZoomHints + function returns the size hints for a window in its zoomed state. It returns a nonzero status if it succeeds or zero if the application specified no zoom size hints for this window. -XGetZoomHints + can generate a BadWindow error. @@ -496,13 +496,13 @@ error. To set the value of any property of type WM_SIZE_HINTS, use -XSetSizeHints. +. This function has been superseded by -XSetWMSizeHints. +. XSetSizeHints - + XSetSizeHints Display *display @@ -558,20 +558,20 @@ Specifies the property name. The -XSetSizeHints + function sets the XSizeHints structure for the named property and the specified window. This is used by -XSetNormalHints + and -XSetZoomHints + and can be used to set the value of any property of type WM_SIZE_HINTS. Thus, it may be useful if other properties of that type get defined. -XSetSizeHints + can generate BadAlloc, BadAtom, @@ -583,13 +583,13 @@ errors. To read the value of any property of type WM_SIZE_HINTS, use -XGetSizeHints. +. This function has been superseded by -XGetWMSizeHints. +. XGetSizeHints - + Status XGetSizeHints Display *display @@ -645,24 +645,24 @@ Specifies the property name. The -XGetSizeHints + function returns the XSizeHints structure for the named property and the specified window. This is used by -XGetNormalHints + and -XGetZoomHints. +. It also can be used to retrieve the value of any property of type WM_SIZE_HINTS. Thus, it may be useful if other properties of that type get defined. -XGetSizeHints + returns a nonzero status if a size hint was defined or zero otherwise. -XGetSizeHints + can generate BadAtom and @@ -676,13 +676,13 @@ errors. To get the XStandardColormap structure associated with one of the described atoms, use -XGetStandardColormap. +. This function has been superseded by -XGetRGBColormaps. +. XGetStandardColormap - + Status XGetStandardColormap Display *display @@ -738,17 +738,17 @@ Specifies the property name. The -XGetStandardColormap + function returns the colormap definition associated with the atom supplied as the property argument. -XGetStandardColormap + returns a nonzero status if successful and zero otherwise. For example, to fetch the standard GrayScale colormap for a display, you use -XGetStandardColormap + with the following syntax: XGetStandardColormap(dpy, DefaultRootWindow(dpy), &cmap, XA_RGB_GRAY_MAP); @@ -758,7 +758,7 @@ semantics of standard colormaps. -XGetStandardColormap + can generate BadAtom and @@ -769,13 +769,13 @@ errors. To set a standard colormap, use -XSetStandardColormap. +. This function has been superseded by -XSetRGBColormaps. +. XSetStandardColormap - + XSetStandardColormap Display *display @@ -831,12 +831,12 @@ Specifies the property name. The -XSetStandardColormap + function usually is only used by window or session managers. -XSetStandardColormap + can generate BadAlloc, BadAtom, @@ -851,14 +851,14 @@ errors. To parse window geometry given a user-specified position and a default position, use -XGeometry. +. This function has been superseded by -XWMGeometry. +. Windowdetermining location XGeometry - + int XGeometry Display *display @@ -1018,19 +1018,19 @@ size of the increments fwidth and fheight and any additional interior space (xadder and yadder) to make it easy to compute the resulting size. The -XGeometry + function returns the position the window should be placed given a position and a default position. -XGeometry + determines the placement of a window using a geometry specification as specified by -XParseGeometry + and the additional information about the window. Given a fully qualified default geometry specification and an incomplete geometry specification, -XParseGeometry + returns a bitmask value as defined above in the -XParseGeometry + call, by using the position argument. @@ -1049,16 +1049,16 @@ geometry specifications. Getting the X Environment Defaults The -XGetDefault + function provides a primitive interface to the resource manager facilities -discussed in chapter 15. +discussed in chapter 15. It is only useful in very simple applications. XGetDefault - + char *XGetDefault Display *display @@ -1104,31 +1104,31 @@ Specifies the option name. The -XGetDefault + function returns the value of the resource prog.option, where prog is the program argument with the directory prefix removed and option must be a single component. Note that multilevel resources cannot be used with -XGetDefault. +. The class "Program.Name" is always used for the resource lookup. If the specified option name does not exist for this program, -XGetDefault + returns NULL. The strings returned by -XGetDefault + are owned by Xlib and should not be modified or freed by the client. If a database has been set with -XrmSetDatabase, +, that database is used for the lookup. Otherwise, a database is created and is set in the display (as if by calling -XrmSetDatabase). +). The database is created in the current locale. To create a database, -XGetDefault + uses resources from the RESOURCE_MANAGER property on the root window of screen zero. If no such property exists, @@ -1138,13 +1138,13 @@ this file is "$HOME/.Xdefaults". Files$HOME/.Xdefaults After loading these defaults, -XGetDefault + merges additional defaults specified by the XENVIRONMENT environment variable. If XENVIRONMENT is defined, it contains a full path name for the additional resource file. If XENVIRONMENT is not defined, -XGetDefault + looks for "$HOME/.Xdefaults-name" , where name specifies the name of the machine on which the application @@ -1179,10 +1179,10 @@ These functions are provided mainly for compatibility with X Version 10 and have no server support. That is, they call other Xlib functions, not the server directly. Thus, if you just have straight lines to draw, using -XDrawLines + XDrawLines or -XDrawSegments + XDrawSegments is much faster. @@ -1190,9 +1190,9 @@ is much faster. The functions discussed here provide all the functionality of the X Version 10 functions -XDraw, +, X10 compatibilityXDraw -XDrawFilled, +, X10 compatibilityXDrawFilled XDrawPatterned, X10 compatibilityXDrawPatterned @@ -1219,7 +1219,7 @@ Just how the graphics context you use is set up actually determines whether you get dashes or not, and so on. Lines are properly joined if they connect and include the closing of a closed figure (see -XDrawLines). +). The functions discussed here fail (return zero) only if they run out of memory or are passed a Vertex @@ -1237,7 +1237,7 @@ set. To achieve the effects of the X Version 10 -XDraw, +, X10 compatibilityXDraw XDrawDashed, X10 compatibilityXDrawDashed @@ -1245,14 +1245,14 @@ and XDrawPatterned, X10 compatibilityXDrawPatterned use -XDraw. +. #include <X11/X10.h> - + Status XDraw Display *display @@ -1319,7 +1319,7 @@ Specifies how many vertices are in vlist. The -XDraw + function draws an arbitrary polygon or curve. The figure drawn is defined by the specified list of vertices (vlist). The points are connected by lines as specified in the flags in the @@ -1451,15 +1451,15 @@ To achieve the effects of the X Version 10 XDrawTiled X10 compatibilityXDrawTiled and -XDrawFilled, +, X10 compatibilityXDrawFilled use -XDrawFilled. +. #include <X11/X10.h> - + Status XDrawFilled Display *display @@ -1527,7 +1527,7 @@ Specifies how many vertices are in vlist. The -XDrawFilled + function draws arbitrary polygons or curves and then fills them. @@ -1611,11 +1611,11 @@ bucket. To return a pointer to a new XAssocTable, use -XCreateAssocTable. +. XCreateAssocTable - + XAssocTable *XCreateAssocTable int size @@ -1657,11 +1657,11 @@ a NULL pointer is returned. To create an entry in a given XAssocTable, use -XMakeAssoc. +. XMakeAssoc - + XMakeAssoc Display *display @@ -1717,7 +1717,7 @@ Specifies the data to be associated with the X resource ID. The -XMakeAssoc + function inserts data into an XAssocTable keyed on an XID. @@ -1732,11 +1732,11 @@ the highest XID. To obtain data from a given XAssocTable, use -XLookUpAssoc. +. XLookUpAssoc - + char *XLookUpAssoc Display *display @@ -1781,12 +1781,12 @@ Specifies the X resource ID. The -XLookUpAssoc + function retrieves the data stored in an XAssocTable by its XID. If an appropriately matching XID can be found in the table, -XLookUpAssoc + returns the data associated with it. If the x_id cannot be found in the table, it returns NULL. @@ -1797,11 +1797,11 @@ it returns NULL. To delete an entry from a given XAssocTable, use -XDeleteAssoc. +. XDeleteAssoc - + XDeleteAssoc Display *display @@ -1846,7 +1846,7 @@ Specifies the X resource ID. The -XDeleteAssoc + function deletes an association in an XAssocTable keyed on its XID. @@ -1860,11 +1860,11 @@ Deleting associations in no way impairs the performance of an To free the memory associated with a given XAssocTable, use -XDestroyAssocTable. +. XDestroyAssocTable - + XDestroyAssocTable XAssocTable *table diff --git a/libX11/specs/libX11/CH01.xml b/libX11/specs/libX11/CH01.xml index 21750aba1..8d2092420 100644 --- a/libX11/specs/libX11/CH01.xml +++ b/libX11/specs/libX11/CH01.xml @@ -151,7 +151,7 @@ which will be called when the error is reported. XSync If a client does not want a request to execute asynchronously, it can follow the request with a call to -XSync, +, which blocks until all previously buffered asynchronous events have been sent and acted on. As an important side effect, @@ -206,12 +206,12 @@ programs must be prepared to handle (or ignore) events of all types. Input events (for example, a key pressed or the pointer moved) arrive asynchronously from the server and are queued until they are requested by an explicit call (for example, -XNextEvent + or -XWindowEvent). +). In addition, some library functions (for example, -XRaiseWindow) +) generate Expose and @@ -220,7 +220,7 @@ events. These events also arrive asynchronously, but the client may XSync wish to explicitly wait for them by calling -XSync + after calling a function that can cause the server to generate events. @@ -316,7 +316,7 @@ reference this file directly. Headers<X11/Xcms.h> This file contains symbols for much of the color management facilities -described in chapter 6. +described in chapter 6. All functions, types, and symbols with the prefix "Xcms", plus the Color Conversion Contexts macros, are declared in this file. <X11/Xlib.h> @@ -334,8 +334,8 @@ must be included before including this file. This file declares various functions, types, and symbols used for inter-client communication and application utility functions, which are described in chapters -14 and -16. +14 and +16. <X11/Xlib.h> must be included before including this file. @@ -349,7 +349,7 @@ which are described in chapters This file declares all functions, types, and symbols for the resource manager facilities, which are described in -chapter 15. +chapter 15. <X11/Xlib.h> must be included before including this file. @@ -683,7 +683,7 @@ rather than presume control of the entire screen. What you do inside of your top-level window, however, is up to your application. For further information, -see chapter 14 +see chapter 14 and the Inter-Client Communication Conventions Manual. diff --git a/libX11/specs/libX11/CH02.xml b/libX11/specs/libX11/CH02.xml index 4a57266bd..12df68ee4 100644 --- a/libX11/specs/libX11/CH02.xml +++ b/libX11/specs/libX11/CH02.xml @@ -1,7 +1,7 @@ - + Display Functions Before your program can use a display, you must establish a connection @@ -63,10 +63,10 @@ Use internal connections To open a connection to the X server that controls a display, use -XOpenDisplay. +. XOpenDisplay - + Display *XOpenDisplay char *display_name @@ -157,9 +157,9 @@ The screen_number sets an internal variable that can be accessed by using the DefaultScreen macro or the -XDefaultScreen + function if you are using languages other than C -(see section 2.2.1). +(see section 2.2.1). @@ -179,13 +179,13 @@ dual-headed:0.1 The -XOpenDisplay + function returns a Display structure that serves as the connection to the X server and that contains all the information about that X server. -XOpenDisplay + connects your application to the X server through TCP or DECnet communications protocols, or through some local inter-process communication protocol. @@ -194,7 +194,7 @@ or through some local inter-process communication protocol. If the protocol is specified as "tcp", "inet", or "inet6", or if no protocol is specified and the hostname is a host machine name and a single colon (:) separates the hostname and display number, -XOpenDisplay + connects using TCP streams. (If the protocol is specified as "inet", TCP over IPv4 is used. If the protocol is specified as "inet6", TCP over IPv6 is used. Otherwise, the implementation determines which IP version is used.) @@ -202,7 +202,7 @@ If the hostname and protocol are both not specified, Xlib uses whatever it believes is the fastest transport. If the hostname is a host machine name and a double colon (::) separates the hostname and display number, -XOpenDisplay + connects using DECnet. A single X server can support any or all of these transport mechanisms simultaneously. @@ -213,7 +213,7 @@ mechanisms. Display If successful, -XOpenDisplay + returns a pointer to a Display structure, @@ -223,16 +223,16 @@ which is defined in Files<X11/Xlib.h> Headers<X11/Xlib.h> If -XOpenDisplay + does not succeed, it returns NULL. After a successful call to -XOpenDisplay, +, all of the screens in the display can be used by the client. The screen number specified in the display_name argument is returned by the DefaultScreen macro (or the -XDefaultScreen + function). You can access elements of the Display @@ -243,7 +243,7 @@ For information about using macros and functions to obtain information from the Display structure, -see section 2.2.1. +see section 2.2.1. @@ -295,21 +295,21 @@ Applications must never directly modify or inspect these private members of the structure. The -XDisplayWidth, -XDisplayHeight, -XDisplayCells, -XDisplayPlanes, -XDisplayWidthMM, +, +, +, +, +, and -XDisplayHeightMM + functions in the next sections are misnamed. These functions really should be named Screenwhatever and XScreenwhatever, not Displaywhatever or XDisplaywhatever. Our apologies for the resulting confusion. - -Display Macros + +Display Macros @@ -357,7 +357,7 @@ The names are intended to convey the expected relative intensity of the colors. BlackPixel(display, screen_number) - + unsigned long XBlackPixel Display *display @@ -402,7 +402,7 @@ Both return the black pixel value for the specified screen. WhitePixel(display, screen_number) - + unsigned long XWhitePixel Display *display @@ -447,7 +447,7 @@ Both return the white pixel value for the specified screen. ConnectionNumber(display) - + int XConnectionNumber Display *display @@ -484,7 +484,7 @@ this is the file descriptor of the connection. DefaultColormap(display, screen_number) - + Colormap XDefaultColormap Display *display @@ -530,7 +530,7 @@ Most routine allocations of color should be made out of this colormap. DefaultDepth(display, screen_number) - + int XDefaultDepth Display *display @@ -568,7 +568,7 @@ Specifies the appropriate screen number on the host server. Both return the depth (number of planes) of the default root window for the specified screen. Other depths may also be supported on this screen (see -XMatchVisualInfo). +). @@ -581,7 +581,7 @@ To determine the number of depths that are available on a given screen, use DefaultGC(display, screen_number) - + GC XDefaultGC Display *display @@ -636,7 +636,7 @@ can be allocated, sets count_return to the number of available depths. Otherwise, it does not set count_return and returns NULL. To release the memory allocated for the array of depths, use -XFree. +. @@ -699,7 +699,7 @@ This GC should never be freed. DefaultRootWindow(display) - + Window XDefaultRootWindow Display *display @@ -733,7 +733,7 @@ Both return the root window for the default screen. DefaultScreenOfDisplay(display) - + Screen *XDefaultScreenOfDisplay Display *display @@ -767,7 +767,7 @@ Both return a pointer to the default screen. ScreenOfDisplay(display, screen_number) - + Screen *XScreenOfDisplay Display *display @@ -812,7 +812,7 @@ Both return a pointer to the indicated screen. DefaultScreen(display) - + int XDefaultScreen Display *display @@ -837,7 +837,7 @@ Specifies the connection to the X server. DefaultScreen XDefaultScreen Both return the default screen number referenced by the -XOpenDisplay + function. This macro or function should be used to retrieve the screen number in applications that will use only a single screen. @@ -850,7 +850,7 @@ in applications that will use only a single screen. DefaultVisual(display, screen_number) - + Visual *XDefaultVisual Display *display @@ -897,7 +897,7 @@ see section 3.1. DisplayCells(display, screen_number) - + int XDisplayCells Display *display @@ -942,7 +942,7 @@ Both return the number of entries in the default colormap. DisplayPlanes(display, screen_number) - + int XDisplayPlanes Display *display @@ -989,7 +989,7 @@ see the glossary. DisplayString(display) - + char *XDisplayString Display *display @@ -1014,7 +1014,7 @@ Specifies the connection to the X server. DisplayString XDisplayString Both return the string that was passed to -XOpenDisplay + when the current display was opened. On POSIX-conformant systems, if the passed string was NULL, these return the value of @@ -1033,7 +1033,7 @@ child process as well as for printing error messages. LastKnownRequestProcessed(display) - + unsigned long XLastKnownRequestProcessed Display *display @@ -1057,28 +1057,28 @@ Specifies the connection to the X server. XExtendedMaxRequestSize The -XExtendedMaxRequestSize +XExtendedMaxRequestSize function returns zero if the specified display does not support an extended-length protocol encoding; otherwise, it returns the maximum request size (in 4-byte units) supported by the server using the extended-length encoding. The Xlib functions -XDrawLines, -XDrawArcs, -XFillPolygon, -XChangeProperty, -XSetClipRectangles, +, +, +, +, +, and -XSetRegion + will use the extended-length encoding as necessary, if supported by the server. Use of the extended-length encoding in other Xlib functions (for example, -XDrawPoints, -XDrawRectangles, -XDrawSegments, -XFillArcs, -XFillRectangles, -XPutImage) +, +, +, +, +, +) is permitted but not required; an Xlib implementation may choose to split the data across multiple smaller requests instead. @@ -1123,13 +1123,13 @@ The protocol guarantees the size to be no smaller than 4096 units (16384 bytes). Xlib automatically breaks data up into multiple protocol requests as necessary for the following functions: -XDrawPoints, -XDrawRectangles, -XDrawSegments, -XFillArcs, -XFillRectangles, +, +, +, +, +, and -XPutImage. +. @@ -1176,7 +1176,7 @@ are received. NextRequest(display) - + unsigned long XNextRequest Display *display @@ -1212,7 +1212,7 @@ Serial numbers are maintained separately for each display connection. ProtocolVersion(display) - + int XProtocolVersion Display *display @@ -1247,7 +1247,7 @@ the connected display. ProtocolRevision(display) - + int XProtocolRevision Display *display @@ -1281,7 +1281,7 @@ Both return the minor protocol revision number of the X server. QLength(display) - + int XQLength Display *display @@ -1308,7 +1308,7 @@ Specifies the connection to the X server. Both return the length of the event queue for the connected display. Note that there may be more events that have not been read into the queue yet (see -XEventsQueued). +). @@ -1318,7 +1318,7 @@ the queue yet (see RootWindow(display, screen_number) - + Window XRootWindow Display *display @@ -1367,7 +1367,7 @@ and for creating top-level windows. ScreenCount(display) - + int XScreenCount Display *display @@ -1401,7 +1401,7 @@ Both return the number of available screens. ServerVendor(display) - + char *XServerVendor Display *display @@ -1439,7 +1439,7 @@ Otherwise, the contents of the string are implementation-dependent. VendorRelease(display) - + int XVendorRelease Display *display @@ -1514,7 +1514,7 @@ To obtain the pixmap format information for a given display, use ImageByteOrder(display) - + int XImageByteOrder Display *display @@ -1560,7 +1560,7 @@ returns NULL. To free the allocated storage for the XPixmapFormatValues structures, use -XFree. +. @@ -1617,7 +1617,7 @@ or BitmapUnit(display) - + int XBitmapUnit Display *display @@ -1652,7 +1652,7 @@ The scanline is calculated in multiples of this value. BitmapBitOrder(display) - + int XBitmapBitOrder Display *display @@ -1692,7 +1692,7 @@ or BitmapPad(display) - + int XBitmapPad Display *display @@ -1727,7 +1727,7 @@ by this macro or function. DisplayHeight(display, screen_number) - + int XDisplayHeight Display *display @@ -1773,7 +1773,7 @@ in pixels. DisplayHeightMM(display, screen_number) - + int XDisplayHeightMM Display *display @@ -1818,7 +1818,7 @@ Both return the height of the specified screen in millimeters. DisplayWidth(display, screen_number) - + int XDisplayWidth Display *display @@ -1863,7 +1863,7 @@ Both return the width of the screen in pixels. DisplayWidthMM(display, screen_number) - + int XDisplayWidthMM Display *display @@ -1922,7 +1922,7 @@ structure. BlackPixelOfScreen(screen) - + unsigned long XBlackPixelOfScreen Screen *screen @@ -1958,7 +1958,7 @@ Both return the black pixel value of the specified screen. WhitePixelOfScreen(screen) - + unsigned long XWhitePixelOfScreen Screen *screen @@ -1994,7 +1994,7 @@ Both return the white pixel value of the specified screen. CellsOfScreen(screen) - + int XCellsOfScreen Screen *screen @@ -2031,7 +2031,7 @@ of the specified screen. DefaultColormapOfScreen(screen) - + Colormap XDefaultColormapOfScreen Screen *screen @@ -2067,7 +2067,7 @@ Both return the default colormap of the specified screen. DefaultDepthOfScreen(screen) - + int XDefaultDepthOfScreen Screen *screen @@ -2103,7 +2103,7 @@ Both return the depth of the root window. DefaultGCOfScreen(screen) - + GC XDefaultGCOfScreen Screen *screen @@ -2141,7 +2141,7 @@ The GC must never be freed. DefaultVisualOfScreen(screen) - + Visual *XDefaultVisualOfScreen Screen *screen @@ -2179,7 +2179,7 @@ see section 3.1. DoesBackingStore(screen) - + int XDoesBackingStore Screen *screen @@ -2222,7 +2222,7 @@ or DoesSaveUnders(screen) - + Bool XDoesSaveUnders Screen *screen @@ -2266,7 +2266,7 @@ the screen does not support save unders DisplayOfScreen(screen) - + Display *XDisplayOfScreen Screen *screen @@ -2303,7 +2303,7 @@ Both return the display of the specified screen. EventMaskOfScreen(screen) - + long XEventMaskOfScreen Screen *screen @@ -2376,7 +2376,7 @@ at connection setup time. WidthOfScreen(screen) - + int XWidthOfScreen Screen *screen @@ -2412,7 +2412,7 @@ Both return the width of the specified screen in pixels. HeightOfScreen(screen) - + int XHeightOfScreen Screen *screen @@ -2448,7 +2448,7 @@ Both return the height of the specified screen in pixels. WidthMMOfScreen(screen) - + int XWidthMMOfScreen Screen *screen @@ -2484,7 +2484,7 @@ Both return the width of the specified screen in millimeters. HeightMMOfScreen(screen) - + int XHeightMMOfScreen Screen *screen @@ -2520,7 +2520,7 @@ Both return the height of the specified screen in millimeters. MaxCmapsOfScreen(screen) - + int XMaxCmapsOfScreen Screen *screen @@ -2558,7 +2558,7 @@ by the specified screen MinCmapsOfScreen(screen) - + int XMinCmapsOfScreen Screen *screen @@ -2596,7 +2596,7 @@ by the specified screen PlanesOfScreen(screen) - + int XPlanesOfScreen Screen *screen @@ -2632,7 +2632,7 @@ Both return the depth of the root window. RootWindowOfScreen(screen) - + Window XRootWindowOfScreen Screen *screen @@ -2672,11 +2672,11 @@ Both return the root window of the specified screen. To execute a NoOperation protocol request, use -XNoOp. +. XNoOp - + XNoOp Display *display @@ -2695,7 +2695,7 @@ protocol request, use The -XNoOp + function sends a NoOperation protocol request to the X server, @@ -2710,11 +2710,11 @@ thereby exercising the connection. To free in-memory data that was created by an Xlib function, use -XFree. +. XFree - + XFree void *data @@ -2738,7 +2738,7 @@ Specifies the data that is to be freed. The -XFree + function is a general-purpose Xlib routine that frees the specified data. You must use it to free any objects that were allocated by Xlib, unless an alternate function is explicitly specified for the object. @@ -2798,7 +2798,7 @@ and or other resources that the client has created on this display, unless the close-down mode of the resource has been changed (see -XSetCloseDownMode). +). Therefore, these windows, resource IDs, and other resources should never be referenced again or an error will be generated. Before exiting, you should call @@ -2806,7 +2806,7 @@ Before exiting, you should call explicitly so that any pending errors are reported as XCloseDisplay performs a final -XSync + operation. Resource IDs XCloseDisplay @@ -2824,11 +2824,11 @@ error. Xlib provides a function to permit the resources owned by a client to survive after the client's connection is closed. To change a client's close-down mode, use -XSetCloseDownMode. +. XSetCloseDownMode - + XSetCloseDownMode Display *display @@ -2867,7 +2867,7 @@ or The -XSetCloseDownMode + defines what will happen to the client's resources at connection close. A connection starts in DestroyAll @@ -2877,18 +2877,18 @@ close_mode argument is RetainPermanent or RetainTemporary, -see section 2.6. +see section 2.6. -XSetCloseDownMode + can generate a BadValue error. - -Using X Server Connection Close Operations + +Using X Server Connection Close Operations @@ -2905,15 +2905,15 @@ automatic operations: It disowns all selections owned by the client (see -XSetSelectionOwner). +). It performs an -XUngrabPointer + and -XUngrabKeyboard + if the client has actively grabbed the pointer or the keyboard. @@ -2921,7 +2921,7 @@ or the keyboard. It performs an -XUngrabServer + if the client has grabbed the server. @@ -2940,7 +2940,7 @@ or RetainTemporary. However, this does not prevent other client applications from explicitly destroying the resources (see -XSetCloseDownMode). +). @@ -3144,7 +3144,7 @@ the display is unlocked by this thread. Nested calls to XLockDisplay work correctly; the display will not actually be unlocked until -XUnlockDisplay + has been called the same number of times as XLockDisplay. This function has no effect unless Xlib was successfully initialized @@ -3155,11 +3155,11 @@ for threads using To unlock a display, use -XUnlockDisplay. +. XUnlockDisplay - + XUnlockDisplay Display *display @@ -3182,13 +3182,13 @@ Specifies the connection to the X server. The -XUnlockDisplay + function allows other threads to use the specified display again. Any threads that have blocked on the display are allowed to continue. Nested locking works correctly; if XLockDisplay has been called multiple times by a thread, then -XUnlockDisplay + must be called an equal number of times before the display is actually unlocked. This function has no effect unless Xlib was successfully initialized @@ -3206,7 +3206,7 @@ for threads using In addition to the connection to the X server, an Xlib implementation may require connections to other kinds of servers (for example, to input method servers as described in -chapter 13). +chapter 13). Toolkits and clients that use multiple displays, or that use displays in combination with other inputs, need to obtain these additional connections to correctly @@ -3218,7 +3218,7 @@ facilities. To track internal connections for a display, use -XAddConnectionWatch. +. @@ -3231,7 +3231,7 @@ To track internal connections for a display, use - + Status XAddConnectionWatch Display *display @@ -3276,7 +3276,7 @@ Specifies the additional client data. The -XAddConnectionWatch + function registers a procedure to be called each time Xlib opens or closes an internal connection for the specified display. The procedure is passed the display, the specified client_data, the file descriptor for the connection, @@ -3294,9 +3294,9 @@ the location pointed to by watch_data will hold this same private data pointer. This function can be called at any time after a display is opened. If internal connections already exist, the registered procedure will immediately be called for each of them, before -XAddConnectionWatch + returns. -XAddConnectionWatch + returns a nonzero status if the procedure is successfully registered; otherwise, it returns zero. @@ -3377,14 +3377,14 @@ was initially registered. To process input on an internal connection, use -XProcessInternalConnection. +. XProcessInternalConnection () - + void XProcessInternalConnection Display *display @@ -3418,7 +3418,7 @@ Specifies the file descriptor. The -XProcessInternalConnection + function processes input available on an internal connection. This function should be called for an internal connection only after an operating system facility (for example, @@ -3432,14 +3432,14 @@ the effect is not defined. To obtain all of the current internal connections for a display, use -XInternalConnectionNumbers. +. XInternalConnectionNumbers () - + Status XInternalConnectionNumbers Display *display @@ -3485,12 +3485,12 @@ Returns the number of (Cn. The -XInternalConnectionNumbers + function returns a list of the file descriptors for all internal connections currently open for the specified display. When the allocated list is no longer needed, free it by using -XFree. +. This functions returns a nonzero status if the list is successfully allocated; otherwise, it returns zero. diff --git a/libX11/specs/libX11/CH03.xml b/libX11/specs/libX11/CH03.xml index c2c70cbdd..a16a3bb77 100644 --- a/libX11/specs/libX11/CH03.xml +++ b/libX11/specs/libX11/CH03.xml @@ -1,7 +1,7 @@ -Window Functions +Window Functions Visual Types @@ -23,7 +23,7 @@ Because default windows and visual types are defined for each screen, most simple applications need not deal with this complexity. Xlib provides macros and functions that return the default root window, the default depth of the default root window, and the default visual type -(see sections 2.2.1 +(see sections 2.2.1 and 16.7). @@ -176,11 +176,11 @@ this is the size of an individual pixel subfield. To obtain the visual ID from a Visual, use -XVisualIDFromVisual. +. XVisualIDFromVisual - + VisualID XVisualIDFromVisual Visual *visual @@ -203,7 +203,7 @@ Specifies the visual type. The -XVisualIDFromVisual + function returns the visual ID for the specified visual type. @@ -330,7 +330,7 @@ An application may wish to create a window long before it is mapped to the screen. When a window is eventually mapped to the screen (using -XMapWindow), +), XMapWindow the X server generates an Expose @@ -356,9 +356,9 @@ To set an attribute of a window, set the appropriate member of the XSetWindowAttributes structure and OR in the corresponding value bitmask in your subsequent calls to -XCreateWindow + and -XChangeWindowAttributes, +, or use one of the other convenience functions that set the appropriate attribute. The symbols for the value mask bits and the @@ -1072,7 +1072,7 @@ or False (default). Window managers use this information to avoid tampering with pop-up windows -(see also chapter 14). +(see also chapter 14). @@ -1093,7 +1093,7 @@ error results. X servers capable of supporting multiple hardware colormaps can use this information, and window managers can use it for calls to -XInstallColormap. +. You can set the colormap attribute to a colormap or to CopyFromParent (default). @@ -1147,7 +1147,7 @@ or window, and any change in the parent's cursor will cause an immediate change in the displayed cursor. By calling -XFreeCursor, +, the cursor can be freed immediately as long as no further explicit reference to it is made. @@ -1167,7 +1167,7 @@ which are discussed in the appropriate toolkit documentation. If you do not use a toolkit, however, you must provide some standard information or hints for the window manager by using the Xlib inter-client communication functions -(see chapter 14). +(see chapter 14). @@ -1211,15 +1211,15 @@ you should set these properties for top-level windows before mapping them. For further information, -see chapter 14 and +see chapter 14 and the Inter-Client Communication Conventions Manual. -XCreateWindow + is the more general function that allows you to set specific window attributes when you create a window. -XCreateSimpleWindow + creates a window that inherits its attributes from its parent window. @@ -1245,11 +1245,11 @@ Extension packages can define other classes of windows. To create an unmapped window and set its window attributes, use -XCreateWindow. +. XCreateWindow - + Window XCreateWindow Display *display @@ -1424,7 +1424,7 @@ set to indicate which attributes have been set in the structure. The -XCreateWindow + function creates an unmapped subwindow for a specified parent window, returns the window ID of the created window, and causes the X server to generate a @@ -1480,11 +1480,11 @@ error results. The created window is not yet displayed (mapped) on the user's display. To display the window, call -XMapWindow. +. The new window initially uses the same cursor as its parent. A new cursor can be defined for the new window by calling -XDefineCursor. +. CursorInitial State XDefineCursor The window will not be visible on the screen unless it and all of its @@ -1492,7 +1492,7 @@ ancestors are mapped and it is not obscured by any of its ancestors. -XCreateWindow + can generate BadAlloc, BadColor, @@ -1510,11 +1510,11 @@ errors. To create an unmapped InputOutput subwindow of a given parent window, use -XCreateSimpleWindow. +. XCreateSimpleWindow - + Window XCreateSimpleWindow Display *display @@ -1634,7 +1634,7 @@ Specifies the background pixel value of the window. The -XCreateSimpleWindow + function creates an unmapped InputOutput subwindow for a specified parent window, returns the @@ -1649,14 +1649,14 @@ The border_width for an window must be zero, or a BadMatch error results. -XCreateSimpleWindow + inherits its depth, class, and visual from its parent. All other window attributes, except background and border, have their default values. -XCreateSimpleWindow + can generate BadAlloc, BadMatch, @@ -1680,11 +1680,11 @@ subwindows of a window. To destroy a window and all of its subwindows, use -XDestroyWindow. +. XDestroyWindow - + XDestroyWindow Display *display @@ -1718,7 +1718,7 @@ Specifies the window. The -XDestroyWindow + function destroys the specified window as well as all of its subwindows and causes the X server to generate a DestroyNotify @@ -1741,7 +1741,7 @@ events on other windows that were obscured by the window being destroyed. -XDestroyWindow + can generate a BadWindow error. @@ -1750,11 +1750,11 @@ error. To destroy all subwindows of a specified window, use -XDestroySubwindows. +. XDestroySubwindows - + XDestroySubwindows Display *display @@ -1788,7 +1788,7 @@ Specifies the window. The -XDestroySubwindows + function destroys all inferior windows of the specified window, in bottom-to-top stacking order. It causes the X server to generate a @@ -1796,7 +1796,7 @@ It causes the X server to generate a event for each window. If any mapped subwindows were actually destroyed, -XDestroySubwindows + causes the X server to generate Expose events on the specified window. @@ -1807,21 +1807,21 @@ The subwindows should never be referenced again. -XDestroySubwindows + can generate a BadWindow error. - -Mapping Windows + +Mapping Windows A window is considered mapped if an -XMapWindow + call has been made on it. It may not be visible on the screen for one of the following reasons: @@ -1876,7 +1876,7 @@ A window manager that wants to provide decoration might reparent the child into a frame first. For further information, see sections 3.2.8 -and 10.10. +and 10.10. Only a single client at a time can select for SubstructureRedirectMask. @@ -1894,11 +1894,11 @@ event. To map a given window, use -XMapWindow. +. XMapWindow - + XMapWindow Display *display @@ -1932,7 +1932,7 @@ Specifies the window. The -XMapWindow + function maps the window and all of its subwindows that have had map requests. @@ -1954,7 +1954,7 @@ and if some other client has selected on the parent window, then the X server generates a MapRequest event, and the -XMapWindow + function does not map the window. Otherwise, the window is mapped, and the X server generates a MapNotify @@ -1984,7 +1984,7 @@ Similar tiling and exposure take place for any newly viewable inferiors. If the window is an InputOutput window, -XMapWindow + generates Expose events on each @@ -2011,7 +2011,7 @@ with window managers. -XMapWindow + can generate a BadWindow error. @@ -2020,11 +2020,11 @@ error. To map and raise a window, use -XMapRaised. +. XMapRaised - + XMapRaised Display *display @@ -2058,20 +2058,20 @@ Specifies the window. The -XMapRaised + function essentially is similar to -XMapWindow + in that it maps the window and all of its subwindows that have had map requests. However, it also raises the specified window to the top of the stack. For additional information, see -XMapWindow. +. -XMapRaised + can generate multiple BadWindow errors. @@ -2080,11 +2080,11 @@ errors. To map all subwindows for a specified window, use -XMapSubwindows. +. XMapSubwindows - + XMapSubwindows Display *display @@ -2118,7 +2118,7 @@ Specifies the window. The -XMapSubwindows + XMapSubwindows function maps all subwindows for a specified window in top-to-bottom stacking order. @@ -2131,7 +2131,7 @@ only once, for all of the windows, rather than for each window. -XMapSubwindows + can generate a BadWindow error. @@ -2150,11 +2150,11 @@ Xlib provides functions that you can use to unmap a window or all subwindows. To unmap a window, use -XUnmapWindow. +. XUnmapWindow - + XUnmapWindow Display *display @@ -2188,14 +2188,14 @@ Specifies the window. The -XUnmapWindow + function unmaps the specified window and causes the X server to generate an UnmapNotify UnmapNotify Event XUnmapWindow event. If the specified window is already unmapped, -XUnmapWindow + has no effect. Normal exposure processing on formerly obscured windows is performed. Any child window will no longer be visible until another map call is @@ -2208,7 +2208,7 @@ events on windows that were formerly obscured by it. -XUnmapWindow + can generate a BadWindow error. @@ -2217,11 +2217,11 @@ error. To unmap all subwindows for a specified window, use -XUnmapSubwindows. +. XUnmapSubwindows - + XUnmapSubwindows Display *display @@ -2255,7 +2255,7 @@ Specifies the window. The -XUnmapSubwindows + function unmaps all subwindows for the specified window in bottom-to-top stacking order. It causes the X server to generate an @@ -2270,7 +2270,7 @@ only once, for all of the windows, rather than for each window. -XUnmapSubwindows + can generate a BadWindow error. @@ -2293,7 +2293,7 @@ To change one of these parameters, set the appropriate member of the XWindowChanges structure and OR in the corresponding value mask in subsequent calls to -XConfigureWindow. +. The symbols for the value mask bits and the XWindowChanges structure are: @@ -2524,11 +2524,11 @@ Attempts to configure a root window have no effect. To configure a window's size, location, stacking, or border, use -XConfigureWindow. +. XConfigureWindow - + XConfigureWindow Display *display @@ -2589,7 +2589,7 @@ structure. The -XConfigureWindow + function uses the values specified in the XWindowChanges structure to reconfigure a window's size, position, border, and stacking order. @@ -2609,7 +2609,7 @@ and Opposite are performed with respect to the window's final geometry (as controlled by the other arguments passed to -XConfigureWindow), +), not its initial geometry. Any backing store contents of the window, its inferiors, and other newly visible windows are either discarded or @@ -2618,7 +2618,7 @@ changed to reflect the current screen contents -XConfigureWindow + can generate BadMatch, BadValue, @@ -2630,11 +2630,11 @@ errors. To move a window without changing its size, use -XMoveWindow. +. XMoveWindow - + XMoveWindow Display *display @@ -2693,7 +2693,7 @@ Specify the x and y coordinates(Xy. The -XMoveWindow + function moves the specified window to the specified x and y coordinates, but it does not change the window's size, raise the window, or change the mapping state of the window. @@ -2723,7 +2723,7 @@ Otherwise, the window is moved. -XMoveWindow + can generate a BadWindow error. @@ -2732,11 +2732,11 @@ error. To change a window's size without changing the upper-left coordinate, use -XResizeWindow. +. XResizeWindow - + XResizeWindow Display *display @@ -2794,7 +2794,7 @@ Specify the width and height(Wh. The -XResizeWindow + function changes the inside dimensions of the specified window, not including its borders. This function does not change the window's upper-left coordinate or @@ -2824,7 +2824,7 @@ error results. -XResizeWindow + can generate BadValue and @@ -2835,11 +2835,11 @@ errors. To change the size and location of a window, use -XMoveResizeWindow. +. XMoveResizeWindow - + XMoveResizeWindow Display *display @@ -2920,7 +2920,7 @@ Specify the width and height(Wh. The -XMoveResizeWindow + function changes the size and location of the specified window without raising it. Moving and resizing a mapped window may generate an @@ -2945,7 +2945,7 @@ Otherwise, the window size and location are changed. -XMoveResizeWindow + can generate BadValue and @@ -2956,11 +2956,11 @@ errors. To change the border width of a given window, use -XSetWindowBorderWidth. +. XSetWindowBorderWidth - + XSetWindowBorderWidth Display *display @@ -3005,12 +3005,12 @@ Specifies the width of the window border. The -XSetWindowBorderWidth + function sets the specified window's border width to the specified width. -XSetWindowBorderWidth + can generate a BadWindow error. @@ -3033,11 +3033,11 @@ or restack windows. To raise a window so that no sibling window obscures it, use -XRaiseWindow. +. XRaiseWindow - + XRaiseWindow Display *display @@ -3071,7 +3071,7 @@ Specifies the window. The -XRaiseWindow + function raises the specified window to the top of the stack so that no sibling window obscures it. @@ -3097,7 +3097,7 @@ Otherwise, the window is raised. -XRaiseWindow + can generate a BadWindow error. @@ -3106,11 +3106,11 @@ error. To lower a window so that it does not obscure any sibling windows, use -XLowerWindow. +. XLowerWindow - + XLowerWindow Display *display @@ -3144,7 +3144,7 @@ Specifies the window. The -XLowerWindow + function lowers the specified window to the bottom of the stack so that it does not obscure any sibling windows. @@ -3171,7 +3171,7 @@ stack. -XLowerWindow + can generate a BadWindow error. @@ -3180,11 +3180,11 @@ error. To circulate a subwindow up or down, use -XCirculateSubwindows. +. XCirculateSubwindows - + XCirculateSubwindows Display *display @@ -3234,17 +3234,17 @@ or The -XCirculateSubwindows + function circulates children of the specified window in the specified direction. If you specify RaiseLowest, -XCirculateSubwindows + raises the lowest mapped child (if any) that is occluded by another child to the top of the stack. If you specify LowerHighest, -XCirculateSubwindows + lowers the highest mapped child (if any) that occludes another child to the bottom of the stack. Exposure processing is then performed on formerly obscured windows. @@ -3260,7 +3260,7 @@ event. -XCirculateSubwindows + can generate BadValue and @@ -3272,11 +3272,11 @@ errors. To raise the lowest mapped child of a window that is partially or completely occluded by another child, use -XCirculateSubwindowsUp. +. XCirculateSubwindowsUp - + XCirculateSubwindowsUp Display *display @@ -3310,21 +3310,21 @@ Specifies the window. The -XCirculateSubwindowsUp + function raises the lowest mapped child of the specified window that is partially or completely occluded by another child. Completely unobscured children are not affected. This is a convenience function equivalent to -XCirculateSubwindows + with RaiseLowest specified. -XCirculateSubwindowsUp + can generate a BadWindow error. @@ -3334,11 +3334,11 @@ error. To lower the highest mapped child of a window that partially or completely occludes another child, use -XCirculateSubwindowsDown. +. XCirculateSubwindowsDown - + XCirculateSubwindowsDown Display *display @@ -3372,19 +3372,19 @@ Specifies the window. The -XCirculateSubwindowsDown + function lowers the highest mapped child of the specified window that partially or completely occludes another child. Completely unobscured children are not affected. This is a convenience function equivalent to -XCirculateSubwindows + with LowerHighest specified. -XCirculateSubwindowsDown + can generate a BadWindow error. @@ -3393,11 +3393,11 @@ error. To restack a set of windows from top to bottom, use -XRestackWindows. +. XRestackWindows - + XRestackWindows Display *display @@ -3442,7 +3442,7 @@ Specifies the number of windows to be restacked. The -XRestackWindows + function restacks the windows in the order specified, from top to bottom. The stacking order of the first window in the windows array is unaffected, @@ -3469,7 +3469,7 @@ Otherwise, the windows will be restacked in top-to-bottom order. -XRestackWindows + can generate a BadWindow error. @@ -3486,7 +3486,7 @@ error. Xlib provides functions that you can use to set window attributes. -XChangeWindowAttributes + is the more general function that allows you to set one or more window attributes provided by the XSetWindowAttributes @@ -3498,11 +3498,11 @@ window attribute, such as a window's background. To change one or more attributes for a given window, use -XChangeWindowAttributes. +. XChangeWindowAttributes - + XChangeWindowAttributes Display *display @@ -3546,7 +3546,7 @@ If valuemask is zero, the attributes are ignored and are not referenced. The values and restrictions are the same as for -XCreateWindow. +. @@ -3579,14 +3579,14 @@ set to indicate which attributes have been set in the structure Depending on the valuemask, the -XChangeWindowAttributes + function uses the window attributes in the XSetWindowAttributes structure to change the specified window attributes. Changing the background does not cause the window contents to be changed. To repaint the window and its background, use -XClearWindow. +. Setting the border or changing the background such that the border tile origin changes causes the border to be repainted. Changing the background of a root window to @@ -3612,7 +3612,7 @@ event. Changing the colormap of a visible window may have no immediate effect on the screen because the map may not be installed (see -XInstallColormap). +). Changing the cursor of a root window to None restores the default @@ -3640,7 +3640,7 @@ not one per client. -XChangeWindowAttributes + can generate BadAccess, BadColor, @@ -3656,11 +3656,11 @@ errors. To set the background of a window to a given pixel, use -XSetWindowBackground. +. XSetWindowBackground - + XSetWindowBackground Display *display @@ -3705,10 +3705,10 @@ Specifies the pixel that is to be used for the background. The -XSetWindowBackground + function sets the background of the window to the specified pixel value. Changing the background does not cause the window contents to be changed. -XSetWindowBackground + uses a pixmap of undefined size filled with the pixel value you passed. If you try to change the background of an InputOnly @@ -3718,7 +3718,7 @@ error results. -XSetWindowBackground + can generate BadMatch and @@ -3732,12 +3732,12 @@ errors. To set the background of a window to a given pixmap, use -XSetWindowBackgroundPixmap. +. Windowbackground XSetWindowBackgroundPixmap - + XSetWindowBackgroundPixmap Display *display @@ -3787,7 +3787,7 @@ or Resource IDsfreeing Freeingresources The -XSetWindowBackgroundPixmap + function sets the background pixmap of the window to the specified pixmap. The background pixmap can immediately be freed if no further explicit references to it are to be made. @@ -3807,7 +3807,7 @@ the window has no defined background. -XSetWindowBackgroundPixmap + can generate BadMatch, BadPixmap, @@ -3815,9 +3815,9 @@ and BadWindow errors. -XSetWindowBackground + and -XSetWindowBackgroundPixmap + do not change the current contents of the window. @@ -3825,11 +3825,11 @@ do not change the current contents of the window. To change and repaint a window's border to a given pixel, use -XSetWindowBorder. +. XSetWindowBorder - + XSetWindowBorder Display *display @@ -3874,7 +3874,7 @@ Specifies the entry in the colormap. The -XSetWindowBorder + function sets the border of the window to the pixel value you specify. If you attempt to perform this on an InputOnly @@ -3884,7 +3884,7 @@ error results. -XSetWindowBorder + can generate BadMatch and @@ -3895,11 +3895,11 @@ errors. To change and repaint the border tile of a given window, use -XSetWindowBorderPixmap. +. XSetWindowBorderPixmap - + XSetWindowBorderPixmap Display *display @@ -3945,7 +3945,7 @@ Specifies the border pixmap or The -XSetWindowBorderPixmap + function sets the border pixmap of the window to the pixmap you specify. The border pixmap can be freed immediately if no further explicit references to it are to be made. @@ -3962,7 +3962,7 @@ error results. -XSetWindowBorderPixmap + can generate BadMatch, BadPixmap, @@ -3974,11 +3974,11 @@ errors. To set the colormap of a given window, use -XSetWindowColormap. +. XSetWindowColormap - + XSetWindowColormap Display *display @@ -4023,7 +4023,7 @@ Specifies the colormap. The -XSetWindowColormap + function sets the specified colormap of the specified window. The colormap must have the same visual type as the window, or a @@ -4032,7 +4032,7 @@ error results. -XSetWindowColormap + can generate BadColor, BadMatch, @@ -4044,12 +4044,12 @@ errors. To define which cursor will be used in a window, use -XDefineCursor. +. Windowdefining the cursor XDefineCursor - + XDefineCursor Display *display @@ -4098,11 +4098,11 @@ If a cursor is set, it will be used when the pointer is in the window. If the cursor is None, it is equivalent to -XUndefineCursor. +. -XDefineCursor + can generate BadCursor and @@ -4113,12 +4113,12 @@ errors. To undefine the cursor in a given window, use -XUndefineCursor. +. Windowundefining the cursor XUndefineCursor - + XUndefineCursor Display *display @@ -4152,9 +4152,9 @@ Specifies the window. The -XUndefineCursor + function undoes the effect of a previous -XDefineCursor + for this window. When the pointer is in the window, the parent's cursor will now be used. @@ -4163,7 +4163,7 @@ the default cursor is restored. -XUndefineCursor + can generate a BadWindow error. diff --git a/libX11/specs/libX11/CH04.xml b/libX11/specs/libX11/CH04.xml index 5ace5e1a3..973e7907e 100644 --- a/libX11/specs/libX11/CH04.xml +++ b/libX11/specs/libX11/CH04.xml @@ -1,7 +1,7 @@ - + Window Information Functions @@ -35,13 +35,13 @@ exists. To obtain the parent, a list of children, and number of children for a given window, use -XQueryTree. +. Child Window Parent Window XQueryTree - + Status XQueryTree Display *display @@ -121,21 +121,21 @@ Returns the number of children. The -XQueryTree + function returns the root ID, the parent window ID, a pointer to the list of children windows (NULL when there are no children), and the number of children in the list for the specified window. The children are listed in current stacking order, from bottom-most (first) to top-most (last). -XQueryTree + returns zero if it fails and nonzero if it succeeds. To free a non-NULL children list when it is no longer needed, use -XFree. +. -XQueryTree + can generate a BadWindow error. @@ -144,11 +144,11 @@ error. To obtain the current attributes of a given window, use -XGetWindowAttributes. +. XGetWindowAttributes - + Status XGetWindowAttributes Display *display @@ -196,7 +196,7 @@ structure. The -XGetWindowAttributes + function returns the current attributes for the specified window to an XWindowAttributes structure. @@ -358,7 +358,7 @@ having to loop over the root window fields to see which field matches. -XGetWindowAttributes + can generate BadDrawable and @@ -369,11 +369,11 @@ errors. To obtain the current geometry of a given drawable, use -XGetGeometry. +. XGetGeometry - + Status XGetGeometry Display *display @@ -492,7 +492,7 @@ Returns the depth of the drawable (bits per pixel for the object). The -XGetGeometry + function returns the root window and the current geometry of the drawable. The geometry of the drawable includes the x and y coordinates, width and height, border width, and depth. @@ -502,7 +502,7 @@ It is legal to pass to this function a window whose class is -XGetGeometry + can generate a BadDrawable error. @@ -519,9 +519,9 @@ Applications sometimes need to perform a coordinate transformation from the coordinate space of one window to another window or need to determine which window the pointing device is in. -XTranslateCoordinates + and -XQueryPointer + fulfill these needs (and avoid any race conditions) by asking the X server to perform these operations. @@ -530,11 +530,11 @@ asking the X server to perform these operations. To translate a coordinate in one window to the coordinate space of another window, use -XTranslateCoordinates. +. XTranslateCoordinates - + Bool XTranslateCoordinates Display *display @@ -634,7 +634,7 @@ destination window. If -XTranslateCoordinates + returns True, it takes the src_x and src_y coordinates relative @@ -642,7 +642,7 @@ to the source window's origin and returns these coordinates to dest_x_return and dest_y_return relative to the destination window's origin. If -XTranslateCoordinates + returns False, src_w and dest_w are on different screens, @@ -654,7 +654,7 @@ Otherwise, child_return is set to -XTranslateCoordinates + can generate a BadWindow error. @@ -664,11 +664,11 @@ error. To obtain the screen coordinates of the pointer or to determine the pointer coordinates relative to a specified window, use -XQueryPointer. +. XQueryPointer - + Bool XQueryPointer Display *display @@ -779,26 +779,26 @@ Returns the current state of the modifier keys and pointer buttons. The -XQueryPointer + function returns the root window the pointer is logically on and the pointer coordinates relative to the root window's origin. If -XQueryPointer + returns False, the pointer is not on the same screen as the specified window, and -XQueryPointer + returns None to child_return and zero to win_x_return and win_y_return. If -XQueryPointer + returns True, the pointer coordinates returned to win_x_return and win_y_return are relative to the origin of the specified window. In this case, -XQueryPointer + returns the child that contains the pointer, if any, or else None @@ -806,7 +806,7 @@ to child_return. -XQueryPointer + returns the current logical state of the keyboard buttons and the modifier keys in mask_return. It sets mask_return to the bitwise inclusive OR of one or more @@ -817,11 +817,11 @@ the current state of the mouse buttons and the modifier keys. Note that the logical state of a device (as seen through Xlib) may lag the physical state if device event processing is frozen -(see section 12.1). +(see section 12.1). -XQueryPointer + can generate a BadWindow error. @@ -851,7 +851,7 @@ property name. Clients can store and retrieve properties associated with windows. For efficiency reasons, an atom is used rather than a character string. -XInternAtom + can be used to obtain the atom for property names. Atom @@ -887,7 +887,7 @@ To avoid name clashes with user symbols, the name for each atom has the XA_ prefix. For an explanation of the functions that let you get and set much of the information stored in these predefined properties, -see chapter 14. +see chapter 14. @@ -1046,12 +1046,12 @@ see section 8.5. To return an atom for a given name, use -XInternAtom. +. Atominterning XInternAtom - + Atom XInternAtom Display *display @@ -1096,14 +1096,14 @@ Specifies a Boolean value that indicates whether the atom must be created. The -XInternAtom + function returns the atom identifier associated with the specified atom_name string. If only_if_exists is False, the atom is created if it does not exist. Therefore, -XInternAtom + can return None. If the atom name is not in the Host Portable Character Encoding, @@ -1117,7 +1117,7 @@ the X server closes. -XInternAtom + can generate BadAlloc and @@ -1128,12 +1128,12 @@ errors. To return atoms for an array of names, use -XInternAtoms. +. Atominterning XInternAtoms - + Status XInternAtoms Display *display @@ -1201,11 +1201,11 @@ Returns the atoms. The -XInternAtoms + function returns the atom identifiers associated with the specified names. The atoms are stored in the atoms_return array supplied by the caller. Calling this function is equivalent to calling -XInternAtom + for each of the names in turn with the specified value of only_if_exists, but this function minimizes the number of round-trip protocol exchanges between the client and the X server. @@ -1218,7 +1218,7 @@ otherwise, it returns zero. -XInternAtoms + can generate BadAlloc and @@ -1229,12 +1229,12 @@ errors. To return a name for a given atom identifier, use -XGetAtomName. +. Atomgetting name XGetAtomName - + char *XGetAtomName Display *display @@ -1268,18 +1268,18 @@ Specifies the atom for the property name you want returned. The -XGetAtomName + function returns the name associated with the specified atom. If the data returned by the server is in the Latin Portable Character Encoding, then the returned string is in the Host Portable Character Encoding. Otherwise, the result is implementation-dependent. To free the resulting string, call -XFree. +. -XGetAtomName + can generate a BadAtom error. @@ -1288,12 +1288,12 @@ error. To return the names for an array of atom identifiers, use -XGetAtomNames. +. Atomgetting name XGetAtomNames - + Status XGetAtomNames Display *display @@ -1350,11 +1350,11 @@ Returns the atom names. The -XGetAtomNames + function returns the names associated with the specified atoms. The names are stored in the names_return array supplied by the caller. Calling this function is equivalent to calling -XGetAtomName + for each of the atoms in turn, but this function minimizes the number of round-trip protocol exchanges between the client and the X server. @@ -1367,7 +1367,7 @@ otherwise, it returns zero. -XGetAtomNames + can generate a BadAtom error. @@ -1398,19 +1398,19 @@ Xlib provides functions that you can use to obtain, change, update, or interchange window properties. In addition, Xlib provides other utility functions for inter-client communication -(see chapter 14). +(see chapter 14). To obtain the type, format, and value of a property of a given window, use -XGetWindowProperty. +. Propertygetting XGetWindowProperty - + int XGetWindowProperty display @@ -1559,18 +1559,18 @@ Returns the data in the specified format. The -XGetWindowProperty + function returns the actual type of the property; the actual format of the property; the number of 8-bit, 16-bit, or 32-bit items transferred; the number of bytes remaining to be read in the property; and a pointer to the data actually returned. -XGetWindowProperty + sets the return arguments as follows: If the specified property does not exist for the specified window, -XGetWindowProperty + returns None to actual_type_return and the value zero to @@ -1583,7 +1583,7 @@ In this case, the delete argument is ignored. If the specified property exists but its type does not match the specified type, -XGetWindowProperty + returns the actual property type to actual_type_return, the actual property format (never zero) to actual_format_return, and the property length in bytes @@ -1598,7 +1598,7 @@ The nitems_return argument is empty. If the specified property exists and either you assign AnyPropertyType to the req_type argument or the specified type matches the actual property type, -XGetWindowProperty + returns the actual property type to actual_type_return and the actual property format (never zero) to actual_format_return. It also returns a value to bytes_after_return and nitems_return, by @@ -1645,7 +1645,7 @@ array and should be cast to that type to obtain the elements. -XGetWindowProperty + always allocates one extra byte in prop_return (even if the property is zero length) and sets it to zero so that simple properties consisting of characters @@ -1656,7 +1656,7 @@ do not have to be copied into yet another string before use. If delete is True and bytes_after_return is zero, -XGetWindowProperty + deletes the property from the window and generates a PropertyNotify @@ -1669,11 +1669,11 @@ The function returns if it executes successfully. To free the resulting data, use -XFree. +. -XGetWindowProperty + can generate BadAtom, BadValue, @@ -1685,12 +1685,12 @@ errors. To obtain a given window's property list, use -XListProperties. +. Propertylisting XListProperties - + Atom *XListProperties Display *display @@ -1736,15 +1736,15 @@ Returns the length of the properties array. The -XListProperties + function returns a pointer to an array of atom properties that are defined for the specified window or returns NULL if no properties were found. To free the memory allocated by this function, use -XFree. +. -XListProperties + can generate a BadWindow error. @@ -1753,7 +1753,7 @@ error. To change a property of a given window, use -XChangeProperty. +. Propertychanging Propertyappending @@ -1763,7 +1763,7 @@ To change a property of a given window, use Propertytype XChangeProperty - + XChangeProperty Display *display @@ -1817,7 +1817,7 @@ Specifies the property name. Specifies the type of the property. The X server does not interpret the type but simply passes it back to an application that later calls -XGetWindowProperty. +. @@ -1835,7 +1835,7 @@ byte-swap operations as necessary. If the format is 16-bit or 32-bit, you must explicitly cast your data pointer to an (unsigned char *) in the call to -XChangeProperty. +. @@ -1880,12 +1880,12 @@ Specifies the number of elements of the specified data format. The -XChangeProperty + function alters the property for the specified window and causes the X server to generate a PropertyNotify event on that window. -XChangeProperty + performs the following: @@ -1893,7 +1893,7 @@ performs the following: If mode is PropModeReplace, -XChangeProperty + discards the previous property value and stores the new data. @@ -1903,7 +1903,7 @@ If mode is PropModePrepend or PropModeAppend, -XChangeProperty + inserts the specified data before the beginning of the existing data or onto the end of the existing data, respectively. The type and format must match the existing property value, @@ -1934,7 +1934,7 @@ The lifetime of a property is not tied to the storing client. Properties remain until explicitly deleted, until the window is destroyed, or until the server resets. For a discussion of what happens when the connection to the X server is closed, -see section 2.6. +see section 2.6. The maximum size of a property is server dependent and can vary dynamically depending on the amount of memory the server has available. (If there is insufficient space, a @@ -1943,7 +1943,7 @@ error results.) -XChangeProperty + can generate BadAlloc, BadAtom, @@ -1957,12 +1957,12 @@ errors. To rotate a window's property list, use -XRotateWindowProperties. +. XRotateWindowProperties - + XRotateWindowProperties Display *display @@ -2029,7 +2029,7 @@ Specifies the rotation amount. The -XRotateWindowProperties + function allows you to rotate properties on a window and causes the X server to generate PropertyNotify @@ -2059,7 +2059,7 @@ no properties are changed. -XRotateWindowProperties + can generate BadAtom, BadMatch, @@ -2071,12 +2071,12 @@ errors. To delete a property on a given window, use -XDeleteProperty. +. Propertydeleting XDeleteProperty - + XDeleteProperty Display *display @@ -2122,7 +2122,7 @@ Specifies the property name. The -XDeleteProperty + function deletes the specified property only if the property was defined on the specified window and causes the X server to generate a @@ -2131,7 +2131,7 @@ event on the window unless the property does not exist. -XDeleteProperty + can generate BadAtom and @@ -2194,12 +2194,12 @@ The protocol does not constrain the semantics. To set the selection owner, use -XSetSelectionOwner. +. Selectionsetting the owner XSetSelectionOwner - + XSetSelectionOwner Display *display @@ -2259,7 +2259,7 @@ You can pass either a timestamp or The -XSetSelectionOwner + function changes the owner and last-change time for the specified selection and has no effect if the specified time is earlier than the current last-change time of the specified selection @@ -2296,7 +2296,7 @@ reverts to None, but the last-change time is not affected. The selection atom is uninterpreted by the X server. -XGetSelectionOwner + returns the owner window, which is reported in SelectionRequest and @@ -2306,7 +2306,7 @@ Selections are global to the X server. -XSetSelectionOwner + can generate BadAtom and @@ -2317,12 +2317,12 @@ errors. To return the selection owner, use -XGetSelectionOwner. +. Selectiongetting the owner XGetSelectionOwner - + Window XGetSelectionOwner Display *display @@ -2357,7 +2357,7 @@ Specifies the selection atom (Se. The -XGetSelectionOwner + function returns the window ID associated with the window that currently owns the specified selection. @@ -2370,7 +2370,7 @@ there is no owner for the selection. -XGetSelectionOwner + can generate a BadAtom error. @@ -2379,12 +2379,12 @@ error. To request conversion of a selection, use -XConvertSelection. +. Selectionconverting XConvertSelection - + XConvertSelection Display *display @@ -2464,7 +2464,7 @@ You can pass either a timestamp or -XConvertSelection + requests that the specified selection be converted to the specified target type: @@ -2494,7 +2494,7 @@ There are two predefined selection atoms: PRIMARY and SECONDARY. -XConvertSelection + can generate BadAtom and diff --git a/libX11/specs/libX11/CH05.xml b/libX11/specs/libX11/CH05.xml index 134831e60..501ead0d9 100644 --- a/libX11/specs/libX11/CH05.xml +++ b/libX11/specs/libX11/CH05.xml @@ -1,7 +1,7 @@ - + Pixmap and Cursor Functions Creating and Freeing Pixmaps @@ -21,11 +21,11 @@ A bitmap is a single bit-plane pixmap. To create a pixmap of a given size, use -XCreatePixmap. +. XCreatePixmap - + Pixmap XCreatePixmap Display *display @@ -93,7 +93,7 @@ Specifies the depth of the pixmap. The -XCreatePixmap + function creates a pixmap of the width, height, and depth you specified and returns a pixmap ID that identifies it. It is valid to pass an @@ -115,13 +115,13 @@ The server uses the specified drawable to determine on which screen to create the pixmap. The pixmap can be used only on this screen and only with other drawables of the same depth (see -XCopyPlane + for an exception to this rule). The initial contents of the pixmap are undefined. -XCreatePixmap + can generate BadAlloc, BadDrawable, @@ -133,11 +133,11 @@ errors. To free all storage associated with a specified pixmap, use -XFreePixmap. +. XFreePixmap - + XFreePixmap Display *display @@ -171,14 +171,14 @@ Specifies the pixmap. The -XFreePixmap + function first deletes the association between the pixmap ID and the pixmap. Then, the X server frees the pixmap storage when there are no references to it. The pixmap should never be referenced again. -XFreePixmap + can generate a BadPixmap error. @@ -210,7 +210,7 @@ when a pointer event occurs. There may be limitations imposed by the hardware on cursors as to size and whether a mask is implemented. XQueryBestCursor -XQueryBestCursor + can be used to find out what sizes are possible. There is a standard font for creating cursors, but Xlib provides functions that you can use to create cursors @@ -220,7 +220,7 @@ from an arbitrary font or from bitmaps. To create a cursor from the standard cursor font, use -XCreateFontCursor. +. #include <X11/cursorfont.h> @@ -228,7 +228,7 @@ To create a cursor from the standard cursor font, use XCreateFontCursor - + Cursor XCreateFontCursor Display *display @@ -275,13 +275,13 @@ to use. The hotspot comes from the information stored in the cursor font. The initial colors of a cursor are a black foreground and a white background (see -XRecolorCursor). +). For further information about cursor shapes, see appendix B. -XCreateFontCursor + can generate BadAlloc and @@ -292,11 +292,11 @@ errors. To create a cursor from font glyphs, use -XCreateGlyphCursor. +. XCreateGlyphCursor - + Cursor XCreateGlyphCursor Display *display @@ -384,9 +384,9 @@ Specifies the RGB values for the background of the source. The -XCreateGlyphCursor + function is similar to -XCreatePixmapCursor + except that the source and mask bitmaps are obtained from the specified font glyphs. The source_char must be a defined glyph in source_font, @@ -406,7 +406,7 @@ and there is no restriction on the placement of the hotspot relative to the boun boxes. If no mask_char is given, all pixels of the source are displayed. You can free the fonts immediately by calling -XFreeFont + if no further explicit references to them are to be made. @@ -418,7 +418,7 @@ least significant byte. -XCreateGlyphCursor + can generate BadAlloc, BadFont, @@ -431,11 +431,11 @@ errors. To create a cursor from two bitmaps, use -XCreatePixmapCursor. +. XCreatePixmapCursor - + Cursor XCreatePixmapCursor Display *display @@ -527,7 +527,7 @@ Specify the x and y coordinates(Xy. The -XCreatePixmapCursor + function creates a cursor and returns the cursor ID associated with it. The foreground and background RGB values must be specified using foreground_color and background_color, @@ -567,7 +567,7 @@ The X server might or might not make a copy of the pixmap. -XCreatePixmapCursor + can generate BadAlloc and @@ -578,11 +578,11 @@ errors. To determine useful cursor sizes, use -XQueryBestCursor. +. XQueryBestCursor - + Status XQueryBestCursor Display *display @@ -664,7 +664,7 @@ and height. Some displays allow larger cursors than other displays. The -XQueryBestCursor + function provides a way to find out what size cursors are actually possible on the display. Cursorlimitations @@ -674,7 +674,7 @@ cannot support large ones. -XQueryBestCursor + can generate a BadDrawable error. @@ -683,11 +683,11 @@ error. To change the color of a given cursor, use -XRecolorCursor. +. XRecolorCursor - + XRecolorCursor Display *display @@ -742,7 +742,7 @@ Specifies the RGB values for the background of the source. The -XRecolorCursor + function changes the color of the specified cursor, and if the cursor is being displayed on a screen, the change is visible immediately. @@ -752,7 +752,7 @@ structures are ignored; only the RGB values are used. -XRecolorCursor + can generate a BadCursor error. @@ -761,11 +761,11 @@ error. To free (destroy) a given cursor, use -XFreeCursor. +. XFreeCursor - + XFreeCursor Display *display @@ -799,7 +799,7 @@ Specifies the cursor. The -XFreeCursor + function deletes the association between the cursor resource ID and the specified cursor. The cursor storage is freed when no other resource references it. @@ -807,7 +807,7 @@ The specified cursor ID should not be referred to again. -XFreeCursor + can generate a BadCursor error. diff --git a/libX11/specs/libX11/CH06.xml b/libX11/specs/libX11/CH06.xml index e4c54fd74..da19f7a09 100644 --- a/libX11/specs/libX11/CH06.xml +++ b/libX11/specs/libX11/CH06.xml @@ -1,7 +1,7 @@ - + Color Management Functions @@ -138,9 +138,9 @@ At any time, there is a set of installed colormaps for a screen. Windows using one of the installed colormaps display with true colors, and windows using other colormaps generally display with incorrect colors. You can control the set of installed colormaps by using -XInstallColormap + and -XUninstallColormap. +. @@ -301,9 +301,9 @@ If references to such a color space must be made outside the client (for example, storing a color specification in a file), then reference should be made by color space string prefix (see -XcmsFormatOfPrefix + and -XcmsPrefixOfFormat). +). @@ -499,32 +499,32 @@ Color strings are used in the following functions: -XAllocNamedColor + -XcmsAllocNamedColor + -XLookupColor + -XcmsLookupColor + -XParseColor + -XStoreNamedColor + @@ -811,10 +811,10 @@ or in the CCC indirectly specified by means of the colormap argument. To create a colormap for a screen, use -XCreateColormap. +. XCreateColormap - + Colormap XCreateColormap Display *display @@ -880,7 +880,7 @@ or The -XCreateColormap + function creates a colormap of the specified visual type for the screen on which the specified window resides and returns the colormap ID associated with it. @@ -930,23 +930,23 @@ For and PseudoColor, the effect is as if an -XAllocColorCells + call returned all pixel values from zero to N - 1, where N is the colormap entries value in the specified visual. For DirectColor, the effect is as if an -XAllocColorPlanes + call returned a pixel value of zero and red_mask, green_mask, and blue_mask values containing the same bits as the corresponding masks in the specified visual. However, in all cases, none of these entries can be freed by using -XFreeColors. +. -XCreateColormap + can generate BadAlloc, BadMatch, @@ -960,11 +960,11 @@ errors. To create a new colormap when the allocation out of a previously shared colormap has failed because of resource exhaustion, use -XCopyColormapAndFree. +. XCopyColormapAndFree - + Colormap XCopyColormapAndFree Display *display @@ -998,7 +998,7 @@ Specifies the colormap. The -XCopyColormapAndFree + function creates a colormap of the same visual type and for the same screen as the specified colormap and returns the new colormap ID. It also moves all of the client's existing allocation from the specified @@ -1016,16 +1016,16 @@ If the specified colormap was not created by the client with AllocAll, the allocations to be moved are all those pixels and planes that have been allocated by the client using -XAllocColor, -XAllocNamedColor, -XAllocColorCells, +, +, +, or -XAllocColorPlanes + and that have not been freed since they were allocated. -XCopyColormapAndFree + can generate BadAlloc and @@ -1036,11 +1036,11 @@ errors. To destroy a colormap, use -XFreeColormap. +. XFreeColormap - + XFreeColormap Display *display @@ -1076,19 +1076,19 @@ Specifies the colormap (Cm. The -XFreeColormap + function deletes the association between the colormap resource ID and the colormap and frees the colormap storage. However, this function has no effect on the default colormap for a screen. If the specified colormap is an installed map for a screen, it is uninstalled (see -XUninstallColormap). +). If the specified colormap is defined as the colormap for a window (by -XCreateWindow, -XSetWindowColormap, +, +, or -XChangeWindowAttributes), -XFreeColormap +), + changes the colormap associated with the window to None and generates a @@ -1099,7 +1099,7 @@ X does not define the colors displayed for a window with a colormap of -XFreeColormap + can generate a BadColor error. @@ -1114,12 +1114,12 @@ error. To map a color name to an RGB value, use -XLookupColor. +. Colornaming XLookupColor - + Status XLookupColor Display *display @@ -1187,7 +1187,7 @@ Returns the closest RGB values provided by the hardware. The -XLookupColor + function looks up the string name of a color with respect to the screen associated with the specified colormap. It returns both the exact color values and @@ -1196,13 +1196,13 @@ with respect to the visual type of the specified colormap. If the color name is not in the Host Portable Character Encoding, the result is implementation-dependent. Use of uppercase or lowercase does not matter. -XLookupColor + returns nonzero if the name is resolved; otherwise, it returns zero. -XLookupColor + can generate a BadColor error. @@ -1211,12 +1211,12 @@ error. To map a color name to the exact RGB value, use -XParseColor. +. Colornaming XParseColor - + Status XParseColor Display *display @@ -1279,20 +1279,20 @@ flags. The -XParseColor + function looks up the string name of a color with respect to the screen associated with the specified colormap. It returns the exact color value. If the color name is not in the Host Portable Character Encoding, the result is implementation-dependent. Use of uppercase or lowercase does not matter. -XParseColor + returns nonzero if the name is resolved; otherwise, it returns zero. -XParseColor + can generate a BadColor error. @@ -1301,12 +1301,12 @@ error. To map a color name to a value in an arbitrary color space, use -XcmsLookupColor. +. Colornaming XcmsLookupColor - + Status XcmsLookupColor Display *display @@ -1398,7 +1398,7 @@ to store the color in the database. The -XcmsLookupColor + function looks up the string name of a color with respect to the screen associated with the specified colormap. It returns both the exact color values and @@ -1408,7 +1408,7 @@ The values are returned in the format specified by result_format. If the color name is not in the Host Portable Character Encoding, the result is implementation-dependent. Use of uppercase or lowercase does not matter. -XcmsLookupColor + returns XcmsSuccess or @@ -1455,14 +1455,14 @@ times, the server counts each such allocation, not just the first one. To allocate a read-only color cell with an RGB value, use -XAllocColor. +. Allocationread-only colormap cells Read-only colormap cellsallocating Colorallocation XAllocColor - + Status XAllocColor Display *display @@ -1508,16 +1508,16 @@ Specifies and returns the values actually used in the colormap. The -XAllocColor + function allocates a read-only colormap entry corresponding to the closest RGB value supported by the hardware. -XAllocColor + returns the pixel value of the color closest to the specified RGB elements supported by the hardware and returns the RGB value actually used. The corresponding colormap cell is read-only. In addition, -XAllocColor + returns nonzero if it succeeded or zero if it failed. Color map Colorallocation @@ -1526,14 +1526,14 @@ returns nonzero if it succeeded or zero if it failed. Multiple clients that request the same effective RGB value can be assigned the same read-only entry, thus allowing entries to be shared. When the last client deallocates a shared cell, it is deallocated. -XAllocColor + does not use or affect the flags in the XColor structure. -XAllocColor + can generate a BadColor error. @@ -1545,14 +1545,14 @@ delim %% To allocate a read-only color cell with a color in arbitrary format, use -XcmsAllocColor. +. Allocationread-only colormap cells Read-only colormap cellsallocating Colorallocation XcmsAllocColor - + Status XcmsAllocColor Display *display @@ -1609,25 +1609,25 @@ Specifies the color format for the returned color specification. The -XcmsAllocColor + function is similar to -XAllocColor + except the color can be specified in any format. The -XcmsAllocColor + function ultimately calls -XAllocColor + to allocate a read-only color cell (colormap entry) with the specified color. -XcmsAllocColor + first converts the color specified to an RGB value and then passes this to -XAllocColor. -XcmsAllocColor +. + returns the pixel value of the color cell and the color specification actually allocated. This returned color specification is the result of converting the RGB value returned by -XAllocColor + into the format specified with the result_format argument. If there is no interest in a returned color specification, unnecessary computation can be bypassed if result_format is set to @@ -1639,7 +1639,7 @@ the color_in_out color specification is left unchanged. -XcmsAllocColor + can generate a BadColor error. @@ -1649,7 +1649,7 @@ error. To allocate a read-only color cell using a color name and return the closest color supported by the hardware in RGB format, use -XAllocNamedColor. +. Allocationread-only colormap cells Read-only colormap cellsallocating @@ -1657,7 +1657,7 @@ color supported by the hardware in RGB format, use Colorallocation XAllocNamedColor - + Status XAllocNamedColor Display *display @@ -1725,7 +1725,7 @@ Returns the exact RGB values. The -XAllocNamedColor + function looks up the named color with respect to the screen that is associated with the specified colormap. It returns both the exact database definition and @@ -1738,13 +1738,13 @@ Use of uppercase or lowercase does not matter. If screen_def_return and exact_def_return point to the same structure, the pixel field will be set correctly, but the color values are undefined. -XAllocNamedColor + returns nonzero if a cell is allocated; otherwise, it returns zero. -XAllocNamedColor + can generate a BadColor error. @@ -1754,7 +1754,7 @@ error. To allocate a read-only color cell using a color name and return the closest color supported by the hardware in an arbitrary format, use -XcmsAllocNamedColor. +. Allocationread-only colormap cells Read-only colormap cellsallocating @@ -1762,7 +1762,7 @@ color supported by the hardware in an arbitrary format, use Colorallocation XcmsAllocNamedColor - + Status XcmsAllocNamedColor Display *display @@ -1855,22 +1855,22 @@ to store the color in the database. The -XcmsAllocNamedColor + function is similar to -XAllocNamedColor + except that the color returned can be in any format specified. This function ultimately calls -XAllocColor + to allocate a read-only color cell with the color specified by a color string. The color string is parsed into an XcmsColor structure (see -XcmsLookupColor), +), converted to an RGB value, and finally passed to -XAllocColor. +. If the color name is not in the Host Portable Character Encoding, the result is implementation-dependent. Use of uppercase or lowercase does not matter. @@ -1882,7 +1882,7 @@ of parsing (exact specification) and the actual color specification stored (screen specification). This screen specification is the result of converting the RGB value returned by -XAllocColor + into the format specified in result_format. If there is no interest in a returned color specification, unnecessary computation can be bypassed if result_format is set to @@ -1893,7 +1893,7 @@ but the color values are undefined. -XcmsAllocNamedColor + can generate a BadColor error. @@ -1904,14 +1904,14 @@ error. To allocate read/write color cell and color plane combinations for a PseudoColor model, use -XAllocColorCells. +. Read/write colormap cellsallocating Allocationread/write colormap cells Colorallocation XAllocColorCells - + Status XAllocColorCells Display *display @@ -2004,7 +2004,7 @@ pixels_return array. The -XAllocColorCells + function allocates read/write color cells. The number of colors must be positive and the number of planes nonnegative, or a @@ -2040,12 +2040,12 @@ pixel subfield) for DirectColor. The RGB values of the allocated entries are undefined. -XAllocColorCells + returns nonzero if it succeeded or zero if it failed. -XAllocColorCells + can generate BadColor and @@ -2058,14 +2058,14 @@ errors. To allocate read/write color resources for a DirectColor model, use -XAllocColorPlanes. +. Read/write colormap planesallocating Allocationread/write colormap planes Colorallocation XAllocColorPlanes - + Status XAllocColorPlanes Display *display @@ -2116,7 +2116,7 @@ Specifies a Boolean value that indicates whether the planes must be contiguous. Returns an array of pixel values. -XAllocColorPlanes + returns the pixel values in this array. @@ -2239,18 +2239,18 @@ This is true even for PseudoColor. When the colormap entry of a pixel value is changed (using -XStoreColors, -XStoreColor, +, +, or -XStoreNamedColor), +), the pixel is decomposed according to the masks, and the corresponding independent entries are updated. -XAllocColorPlanes + returns nonzero if it succeeded or zero if it failed. -XAllocColorPlanes + can generate BadColor and @@ -2262,12 +2262,12 @@ errors. Freeingcolors To free colormap cells, use -XFreeColors. +. XFreeColors Colordeallocation - + XFreeColors Display *display @@ -2336,7 +2336,7 @@ Specifies the planes you want to free. The -XFreeColors + function frees the cells represented by pixels whose values are in the pixels array. The planes argument should not have any bits set to 1 in common with any of the @@ -2349,14 +2349,14 @@ were allocated by the client (using XAllocNamedColor XAllocColorCells XAllocColorPlanes -XAllocColor, -XAllocNamedColor, -XAllocColorCells, +, +, +, and -XAllocColorPlanes). +). Note that freeing an individual pixel obtained from -XAllocColorPlanes + may not actually allow it to be reused until all of its related pixels are also freed. Similarly, @@ -2376,7 +2376,7 @@ client (that is, is unallocated or is only allocated by another client) or if the colormap was created with all entries writable (by passing AllocAll to -XCreateColormap), +), a BadAccess error results. @@ -2385,7 +2385,7 @@ the one that gets reported is arbitrary. -XFreeColors + can generate BadAccess, BadColor, @@ -2403,12 +2403,12 @@ errors. To store an RGB value in a single colormap cell, use -XStoreColor. +. Colorstoring XStoreColor - + XStoreColor Display *display @@ -2454,7 +2454,7 @@ Specifies the pixel and RGB values. The -XStoreColor + function changes the colormap entry of the pixel value specified in the pixel member of the XColor @@ -2468,7 +2468,7 @@ If a specified pixel is not a valid index into the colormap, a BadValue error results. -XStoreColor + also changes the red, green, and/or blue color components. You specify which color components are to be changed by setting DoRed, @@ -2483,7 +2483,7 @@ the changes are visible immediately. -XStoreColor + can generate BadAccess, BadColor, @@ -2495,12 +2495,12 @@ errors. To store multiple RGB values in multiple colormap cells, use -XStoreColors. +. Colorstoring XStoreColors - + XStoreColors Display *display @@ -2560,7 +2560,7 @@ structures in the color definition array. The -XStoreColors + function changes the colormap entries of the pixel values specified in the pixel members of the XColor @@ -2575,7 +2575,7 @@ in the flags member of the structures. If the colormap is an installed map for its screen, the changes are visible immediately. -XStoreColors + changes the specified pixels if they are allocated writable in the colormap by any client, even if one or more pixels generates an error. If a specified pixel is not a valid index into the colormap, a @@ -2589,7 +2589,7 @@ the one that gets reported is arbitrary. -XStoreColors + can generate BadAccess, BadColor, @@ -2601,12 +2601,12 @@ errors. To store a color of arbitrary format in a single colormap cell, use -XcmsStoreColor. +. Colorstoring XcmsStoreColor - + Status XcmsStoreColor Display *display @@ -2655,7 +2655,7 @@ structure remain unchanged on return. The -XcmsStoreColor + function converts the color specified in the XcmsColor structure into RGB values. @@ -2667,7 +2667,7 @@ structure, whose three flags and DoBlue) are set, in a call to -XStoreColor + to change the color cell specified by the pixel member of the XcmsColor structure. @@ -2685,22 +2685,22 @@ the changes are visible immediately. Note that -XStoreColor + has no return value; therefore, an XcmsSuccess return value from this function indicates that the conversion to RGB succeeded and the call to -XStoreColor + was made. To obtain the actual color stored, use -XcmsQueryColor. +. Because of the screen's hardware limitations or gamut compression, the color stored in the colormap may not be identical to the color specified. -XcmsStoreColor + can generate BadAccess, BadColor, @@ -2712,12 +2712,12 @@ errors. To store multiple colors of arbitrary format in multiple colormap cells, use -XcmsStoreColors. +. Colorstoring XcmsStoreColors - + Status XcmsStoreColors Display *display @@ -2798,7 +2798,7 @@ Pass NULL if the compression status is not useful. The -XcmsStoreColors + function converts the colors specified in the array of XcmsColor structures into RGB values and then uses these RGB specifications in @@ -2809,7 +2809,7 @@ structures, whose three flags and DoBlue) are set, in a call to -XStoreColors + to change the color cells specified by the pixel member of the corresponding XcmsColor structure. @@ -2829,22 +2829,22 @@ the changes are visible immediately. Note that -XStoreColors + has no return value; therefore, an XcmsSuccess return value from this function indicates that conversions to RGB succeeded and the call to -XStoreColors + was made. To obtain the actual colors stored, use -XcmsQueryColors. +. Because of the screen's hardware limitations or gamut compression, the colors stored in the colormap may not be identical to the colors specified. -XcmsStoreColors + can generate BadAccess, BadColor, @@ -2856,13 +2856,13 @@ errors. To store a color specified by name in a single colormap cell, use -XStoreNamedColor. +. Colorstoring Colornaming XStoreNamedColor - + XStoreNamedColor Display *display @@ -2930,7 +2930,7 @@ Specifies which red, green, and blue components are set. The -XStoreNamedColor + function looks up the named color with respect to the screen associated with the colormap and stores the result in the specified colormap. The pixel argument determines the entry in the colormap. @@ -2954,7 +2954,7 @@ error results. -XStoreNamedColor + can generate BadAccess, BadColor, @@ -2966,9 +2966,9 @@ errors. The -XQueryColor + and -XQueryColors + functions take pixel values in the pixel member of XColor structures and store in the structures the RGB values for those @@ -2987,12 +2987,12 @@ the one that gets reported is arbitrary. To query the RGB value of a single colormap cell, use -XQueryColor. +. Colorquerying XQueryColor - + XQueryColor Display *display @@ -3038,7 +3038,7 @@ Specifies and returns the RGB values for the pixel specified The -XQueryColor + function returns the current RGB value for the pixel in the XColor structure and sets the @@ -3050,7 +3050,7 @@ flags. -XQueryColor + can generate BadColor and @@ -3061,12 +3061,12 @@ errors. To query the RGB values of multiple colormap cells, use -XQueryColors. +. Colorquerying XQueryColors - + XQueryColors Display *display @@ -3127,7 +3127,7 @@ structures in the color definition array. The -XQueryColors + function returns the RGB value for each pixel in each XColor structure and sets the @@ -3140,7 +3140,7 @@ flags in each structure. -XQueryColors + can generate BadColor and @@ -3151,12 +3151,12 @@ errors. To query the color of a single colormap cell in an arbitrary format, use -XcmsQueryColor. +. Colorquerying XcmsQueryColor - + Status XcmsQueryColor Display *display @@ -3216,7 +3216,7 @@ Specifies the color format for the returned color specification. The -XcmsQueryColor + function obtains the RGB value for the pixel value in the pixel member of the specified XcmsColor @@ -3229,7 +3229,7 @@ error results. -XcmsQueryColor + can generate BadColor and @@ -3240,12 +3240,12 @@ errors. To query the color of multiple colormap cells in an arbitrary format, use -XcmsQueryColors. +. Colorquerying XcmsQueryColors - + Status XcmsQueryColors Display *display @@ -3318,7 +3318,7 @@ Specifies the color format for the returned color specification. The -XcmsQueryColors + function obtains the RGB values for pixel values in the pixel members of XcmsColor @@ -3333,7 +3333,7 @@ the one that gets reported is arbitrary. -XcmsQueryColors + can generate BadColor and @@ -3397,14 +3397,14 @@ There is a default CCC associated with each screen. To obtain the CCC associated with a colormap, use -XcmsCCCOfColormap. +. XcmsCCCOfColormap ColormapCCC of CCCof colormap Color Conversion Contextof colormap - + XcmsCCC XcmsCCCOfColormap Display *display @@ -3439,12 +3439,12 @@ Specifies the colormap. The -XcmsCCCOfColormap + function returns the CCC associated with the specified colormap. Once obtained, the CCC attributes can be queried or modified. Unless the CCC associated with the specified colormap is changed with -XcmsSetCCCOfColormap, +, this CCC is used when the specified colormap is used as an argument to color functions. @@ -3452,14 +3452,14 @@ to color functions. To change the CCC associated with a colormap, use -XcmsSetCCCOfColormap. +. XcmsSetCCCOfColormap ColormapCCC of CCCof colormap Color Conversion Contextof colormap - + XcmsCCC XcmsSetCCCOfColormap Display *display @@ -3505,12 +3505,12 @@ Specifies the CCC. The -XcmsSetCCCOfColormap + function changes the CCC associated with the specified colormap. It returns the CCC previously associated with the colormap. If they are not used again in the application, CCCs should be freed by calling -XcmsFreeCCC. +. Several colormaps may share the same CCC without restriction; this includes the CCCs generated by Xlib with each colormap. Xlib, however, creates a new CCC with each new colormap. @@ -3533,13 +3533,13 @@ A default CCC is associated with each screen. To obtain the default CCC for a screen, use -XcmsDefaultCCC. +. XcmsDefaultCCC Color Conversion Contextdefault CCCdefault - + XcmsCCC XcmsDefaultCCC Display *display @@ -3574,7 +3574,7 @@ Specifies the appropriate screen number on the host server. The -XcmsDefaultCCC + function returns the default CCC for the specified screen. Its visual is the default visual of the screen. Its initial gamut compression and white point @@ -3601,14 +3601,14 @@ can return. XcmsDisplayOfCCC - + DisplayOfCCC XcmsCCC ccc - + Display *XcmsDisplayOfCCC XcmsCCC ccc @@ -3638,14 +3638,14 @@ Both return the display associated with the specified CCC. VisualOfCCC XcmsVisualOfCCC - + VisualOfCCC XcmsCCC ccc - + Visual *XcmsVisualOfCCC XcmsCCC ccc @@ -3675,14 +3675,14 @@ Both return the visual associated with the specified CCC. ScreenNumberOfCCC XcmsScreenNumberOfCCC - + ScreenNumberOfCCC XcmsCCC ccc - + int XcmsScreenNumberOfCCC XcmsCCC ccc @@ -3712,13 +3712,13 @@ Both return the number of the screen associated with the specified CCC. ScreenWhitePointOfCCC XcmsScreenWhitePointOfCCC - + ScreenWhitePointOfCCC XcmsCCC ccc - + XcmsColor XcmsScreenWhitePointOfCCC XcmsCCC ccc @@ -3748,14 +3748,14 @@ Both return the white point of the screen associated with the specified CCC. ClientWhitePointOfCCC XcmsClientWhitePointOfCCC - + ClientWhitePointOfCCC XcmsCCC ccc - + XcmsColor *XcmsClientWhitePointOfCCC XcmsCCC ccc @@ -3790,12 +3790,12 @@ Both return the Client White Point of the specified CCC. To set the Client White Point in the CCC, use -XcmsSetWhitePoint. +. XcmsSetWhitePoint Client White Pointof Color Conversion Context - + Status XcmsSetWhitePoint XcmsCCC ccc @@ -3831,7 +3831,7 @@ Specifies the new Client White Point. The -XcmsSetWhitePoint + function changes the Client White Point in the specified CCC. Note that the pixel member is ignored and that the color specification is left unchanged upon return. @@ -3859,14 +3859,14 @@ otherwise, it returns zero. To set the gamut compression procedure and corresponding client data in a specified CCC, use -XcmsSetCompressionProc. +. XcmsSetCompressionProc Gamut compressionsetting in Color Conversion Context Gamut compressionprocedure Gamut compressionclient data - + XcmsCompressionProc XcmsSetCompressionProc XcmsCCC ccc @@ -3919,7 +3919,7 @@ Specifies client data for gamut compression procedure or NULL. The -XcmsSetCompressionProc + function first sets the gamut compression procedure and client data in the specified CCC with the newly specified procedure and client data and then returns the old procedure. @@ -3929,13 +3929,13 @@ and then returns the old procedure. To set the white point adjustment procedure and corresponding client data in a specified CCC, use -XcmsSetWhiteAdjustProc. +. XcmsSetWhiteAdjustProc White point adjustmentsetting in Color Conversion Context White point adjustmentprocedure White point adjustmentclient data - + XcmsWhiteAdjustProc XcmsSetWhiteAdjustProc XcmsCCC ccc @@ -3982,7 +3982,7 @@ Specifies client data for white point adjustment procedure or NULL. The -XcmsSetWhiteAdjustProc + function first sets the white point adjustment procedure and client data in the specified CCC with the newly specified procedure and client data and then returns the old procedure. @@ -3996,23 +3996,23 @@ and then returns the old procedure. You can explicitly create a CCC within your application by calling -XcmsCreateCCC. +. These created CCCs can then be used by those functions that explicitly call for a CCC argument. Old CCCs that will not be used by the application should be freed using -XcmsFreeCCC. +. To create a CCC, use -XcmsCreateCCC. +. XcmsCreateCCC Color Conversion Contextcreation CCCcreation - + XcmsCCC XcmsCreateCCC Display *display @@ -4126,20 +4126,20 @@ Specifies client data for use with the white point adjustment procedure or NULL. The -XcmsCreateCCC + function creates a CCC for the specified display, screen, and visual. To free a CCC, use -XcmsFreeCCC. +. XcmsFreeCCC Color Conversion Contextfreeing CCCfreeing - + void XcmsFreeCCC XcmsCCC ccc @@ -4163,7 +4163,7 @@ Specifies the CCC. The -XcmsFreeCCC + function frees the memory used for the specified CCC. Note that default CCCs and those currently associated with colormaps are ignored. @@ -4180,13 +4180,13 @@ are ignored. To convert an array of color specifications in arbitrary color formats to a single destination format, use -XcmsConvertColors. +. Color conversion Colorconversion XcmsConvertColors - + Status XcmsConvertColors XcmsCCC ccc @@ -4267,7 +4267,7 @@ Pass NULL if the compression status is not useful. The -XcmsConvertColors + function converts the color specifications in the specified array of XcmsColor structures from their current format to a single target format, @@ -4330,7 +4330,7 @@ following: XcmsCompressionProc - + typedef Status(*XcmsCompressionProc) XcmsCCC ccc @@ -4466,7 +4466,7 @@ is the Screen White Point. If the gamut compression procedure uses a device-independent color space not initially accessible for use in the color management system, use -XcmsAddColorSpace + to ensure that it is added. @@ -4518,7 +4518,7 @@ then while maintaining the same Psychometric Hue Angle, the color will be clipped to the CIE L*a*b* coordinates of maximum Psychometric Chroma. See -XcmsCIELabQueryMaxC. +. No client data is necessary. @@ -4567,7 +4567,7 @@ then, while maintaining the same Psychometric Hue Angle, the color will be clipped to the CIE L*u*v* coordinates of maximum Psychometric Chroma. See -XcmsCIELuvQueryMaxC. +. No client data is necessary. @@ -4657,7 +4657,7 @@ The white point adjustment procedure interface must adhere to the following: XcmsWhiteAdjustProc - + typedef Status (*XcmsWhiteAdjustProc) XcmsCCC ccc @@ -4838,7 +4838,7 @@ are CIE u'v'Y, CIE XYZ, and CIEXcmsAddColorSpace + to ensure that it is added. @@ -4846,7 +4846,7 @@ to ensure that it is added. As an example, if the CCC specifies a white point adjustment procedure and if the Client White Point and Screen White Point differ, the -XcmsAllocColor + function will use the white point adjustment procedure twice: @@ -4873,7 +4873,7 @@ and the adjustment procedure is During conversion to XcmsRGB, the call to -XcmsAllocColor + results in the following series of color specification conversions: @@ -4925,10 +4925,10 @@ to The resulting RGB specification is passed to -XAllocColor, +, and the RGB specification returned by -XAllocColor + is converted back to XcmsCIEuvY by reversing the color conversion sequence. @@ -5004,7 +5004,7 @@ The <dimensions> consists of a letter or letters that identify the dimensions of the color space that are not fixed. For example, -XcmsTekHVCQueryMaxC + is given a fixed Hue and Value for which maximum Chroma is found. @@ -5016,11 +5016,11 @@ is given a fixed Hue and Value for which maximum Chroma is found. To obtain the color specification for black (zero-intensity red, green, and blue), use -XcmsQueryBlack. +. XcmsQueryBlack - + Status XcmsQueryBlack XcmsCCC ccc @@ -5073,7 +5073,7 @@ The value returned in the pixel member is undefined. The -XcmsQueryBlack + function returns the color specification in the specified target format for zero-intensity red, green, and blue. @@ -5082,11 +5082,11 @@ for zero-intensity red, green, and blue. To obtain the color specification for blue (full-intensity blue while red and green are zero), use -XcmsQueryBlue. +. XcmsQueryBlue - + Status XcmsQueryBlue XcmsCCC ccc @@ -5139,7 +5139,7 @@ The value returned in the pixel member is undefined. The -XcmsQueryBlue + function returns the color specification in the specified target format for full-intensity blue while red and green are zero. @@ -5148,11 +5148,11 @@ for full-intensity blue while red and green are zero. To obtain the color specification for green (full-intensity green while red and blue are zero), use -XcmsQueryGreen. +. XcmsQueryGreen - + Status XcmsQueryGreen XcmsCCC ccc @@ -5205,7 +5205,7 @@ The value returned in the pixel member is undefined. The -XcmsQueryGreen + function returns the color specification in the specified target format for full-intensity green while red and blue are zero. @@ -5214,11 +5214,11 @@ for full-intensity green while red and blue are zero. To obtain the color specification for red (full-intensity red while green and blue are zero), use -XcmsQueryRed. +. XcmsQueryRed - + Status XcmsQueryRed XcmsCCC ccc @@ -5271,7 +5271,7 @@ The value returned in the pixel member is undefined. The -XcmsQueryRed + function returns the color specification in the specified target format for full-intensity red while green and blue are zero. @@ -5280,11 +5280,11 @@ for full-intensity red while green and blue are zero. To obtain the color specification for white (full-intensity red, green, and blue), use -XcmsQueryWhite. +. XcmsQueryWhite - + Status XcmsQueryWhite XcmsCCC ccc @@ -5337,7 +5337,7 @@ The value returned in the pixel member is undefined. The -XcmsQueryWhite + function returns the color specification in the specified target format for full-intensity red, green, and blue. @@ -5368,11 +5368,11 @@ delim %% To obtain the CIE L*a*b* coordinates of maximum Psychometric Chroma for a given Psychometric Hue Angle and CIE metric lightness (L*), use -XcmsCIELabQueryMaxC. +. XcmsCIELabQueryMaxC - + Status XcmsCIELabQueryMaxC XcmsCCC ccc @@ -5439,7 +5439,7 @@ The value returned in the pixel member is undefined. The -XcmsCIELabQueryMaxC + function, given a hue angle and lightness, finds the point of maximum chroma displayable by the screen. It returns this point in CIE L*a*b* coordinates. @@ -5449,14 +5449,14 @@ It returns this point in CIE L*a*b* coordinates. To obtain the CIE L*a*b* coordinates of maximum CIE metric lightness (L*) for a given Psychometric Hue Angle and Psychometric Chroma, use -XcmsCIELabQueryMaxL. +. Psychometric Hue Angle CIE metric lightness CIE metric lightnessmaximum XcmsCIELabQueryMaxL - + Status XcmsCIELabQueryMaxL XcmsCCC ccc @@ -5523,7 +5523,7 @@ The value returned in the pixel member is undefined. The -XcmsCIELabQueryMaxL + function, given a hue angle and chroma, finds the point in CIE L*a*b* color space of maximum lightness (L*) displayable by the screen. @@ -5538,7 +5538,7 @@ is beyond maximum for the given hue angle. To obtain the CIE L*a*b* coordinates of maximum Psychometric Chroma for a given Psychometric Hue Angle, use -XcmsCIELabQueryMaxLC. +. Psychometric Hue Angle Psychometric Chroma @@ -5547,7 +5547,7 @@ for a given Psychometric Hue Angle, use CIE metric lightnessmaximum XcmsCIELabQueryMaxLC - + Status XcmsCIELabQueryMaxLC XcmsCCC ccc @@ -5602,7 +5602,7 @@ The value returned in the pixel member is undefined. The -XcmsCIELabQueryMaxLC + function, given a hue angle, finds the point of maximum chroma displayable by the screen. It returns this point in CIE L*a*b* coordinates. @@ -5612,14 +5612,14 @@ It returns this point in CIE L*a*b* coordinates. To obtain the CIE L*a*b* coordinates of minimum CIE metric lightness (L*) for a given Psychometric Hue Angle and Psychometric Chroma, use -XcmsCIELabQueryMinL. +. Psychometric Hue Angle CIE metric lightness CIE metric lightnessminimum XcmsCIELabQueryMinL - + Status XcmsCIELabQueryMinL XcmsCCC ccc @@ -5686,7 +5686,7 @@ The value returned in the pixel member is undefined. The -XcmsCIELabQueryMinL + function, given a hue angle and chroma, finds the point of minimum lightness (L*) displayable by the screen. It returns this point in CIE L*a*b* coordinates. @@ -5725,11 +5725,11 @@ delim %% To obtain the CIE L*u*v* coordinates of maximum Psychometric Chroma for a given Psychometric Hue Angle and CIE metric lightness (L*), use -XcmsCIELuvQueryMaxC. +. XcmsCIELuvQueryMaxC - + Status XcmsCIELuvQueryMaxC XcmsCCC ccc @@ -5796,7 +5796,7 @@ The value returned in the pixel member is undefined. The -XcmsCIELuvQueryMaxC + function, given a hue angle and lightness, finds the point of maximum chroma displayable by the screen. It returns this point in CIE L*u*v* coordinates. @@ -5806,14 +5806,14 @@ It returns this point in CIE L*u*v* coordinates. To obtain the CIE L*u*v* coordinates of maximum CIE metric lightness (L*) for a given Psychometric Hue Angle and Psychometric Chroma, use -XcmsCIELuvQueryMaxL. +. Psychometric Hue Angle CIE metric lightness CIE metric lightnessmaximum XcmsCIELuvQueryMaxL - + Status XcmsCIELuvQueryMaxL XcmsCCC ccc @@ -5880,7 +5880,7 @@ The value returned in the pixel member is undefined. The -XcmsCIELuvQueryMaxL + function, given a hue angle and chroma, finds the point in CIE L*u*v* color space of maximum lightness (L*) displayable by the screen. @@ -5895,7 +5895,7 @@ is beyond maximum for the given hue angle. To obtain the CIE L*u*v* coordinates of maximum Psychometric Chroma for a given Psychometric Hue Angle, use -XcmsCIELuvQueryMaxLC. +. Psychometric Hue Angle Psychometric Chroma @@ -5904,7 +5904,7 @@ for a given Psychometric Hue Angle, use CIE metric lightnessmaximum XcmsCIELuvQueryMaxLC - + Status XcmsCIELuvQueryMaxLC XcmsCCC ccc @@ -5959,7 +5959,7 @@ The value returned in the pixel member is undefined. The -XcmsCIELuvQueryMaxLC + function, given a hue angle, finds the point of maximum chroma displayable by the screen. It returns this point in CIE L*u*v* coordinates. @@ -5969,14 +5969,14 @@ It returns this point in CIE L*u*v* coordinates. To obtain the CIE L*u*v* coordinates of minimum CIE metric lightness (L*) for a given Psychometric Hue Angle and Psychometric Chroma, use -XcmsCIELuvQueryMinL. +. Psychometric Hue Angle CIE metric lightness CIE metric lightnessminimum XcmsCIELuvQueryMinL - + Status XcmsCIELuvQueryMinL XcmsCCC ccc @@ -6043,7 +6043,7 @@ The value returned in the pixel member is undefined. The -XcmsCIELuvQueryMinL + function, given a hue angle and chroma, finds the point of minimum lightness (L*) displayable by the screen. It returns this point in CIE L*u*v* coordinates. @@ -6061,13 +6061,13 @@ is beyond maximum for the given hue angle. To obtain the maximum Chroma for a given Hue and Value, use -XcmsTekHVCQueryMaxC. +. Chroma Chromamaximum XcmsTekHVCQueryMaxC - + Status XcmsTekHVCQueryMaxC XcmsCCC ccc @@ -6133,7 +6133,7 @@ The value returned in the pixel member is undefined. The -XcmsTekHVCQueryMaxC + function, given a Hue and Value, determines the maximum Chroma in TekHVC color space displayable by the screen. @@ -6144,13 +6144,13 @@ and Value at which the maximum Chroma was found. To obtain the maximum Value for a given Hue and Chroma, use -XcmsTekHVCQueryMaxV. +. Value Valuemaximum XcmsTekHVCQueryMaxV - + Status XcmsTekHVCQueryMaxV XcmsCCC ccc @@ -6216,7 +6216,7 @@ The value returned in the pixel member is undefined. The -XcmsTekHVCQueryMaxV + function, given a Hue and Chroma, determines the maximum Value in TekHVC color space displayable by the screen. @@ -6229,7 +6229,7 @@ at which the maximum Value was found. To obtain the maximum Chroma and Value at which it is reached for a specified Hue, use -XcmsTekHVCQueryMaxVC. +. Chroma Value @@ -6237,7 +6237,7 @@ for a specified Hue, use Valuemaximum XcmsTekHVCQueryMaxVC - + Status XcmsTekHVCQueryMaxVC XcmsCCC ccc @@ -6293,7 +6293,7 @@ The value returned in the pixel member is undefined. The -XcmsTekHVCQueryMaxVC + function, given a Hue, determines the maximum Chroma in TekHVC color space displayable by the screen and the Value at which that maximum Chroma is reached. @@ -6307,7 +6307,7 @@ and the actual Hue for which the maximum Chroma was found. To obtain a specified number of TekHVC specifications such that they contain maximum Values for a specified Hue and the Chroma at which the maximum Values are reached, use -XcmsTekHVCQueryMaxVSamples. +. Chroma Value @@ -6315,7 +6315,7 @@ Chroma at which the maximum Values are reached, use Valuemaximum XcmsTekHVCQueryMaxVSamples - + Status XcmsTekHVCQueryMaxVSamples XcmsCCC ccc @@ -6379,7 +6379,7 @@ The value returned in the pixel member is undefined. The -XcmsTekHVCQueryMaxVSamples + returns nsamples of maximum Value, the Chroma at which that maximum Value is reached, and the actual Hue for which the maximum Chroma was found. These sample points may then be used to plot the maximum Value/Chroma @@ -6390,13 +6390,13 @@ space. To obtain the minimum Value for a given Hue and Chroma, use -XcmsTekHVCQueryMinV. +. Value Valueminimum XcmsTekHVCQueryMinV - + Status XcmsTekHVCQueryMinV XcmsCCC ccc @@ -6462,7 +6462,7 @@ The value returned in the pixel member is undefined. The -XcmsTekHVCQueryMinV + function, given a Hue and Chroma, determines the minimum Value in TekHVC color space displayable by the screen. It returns the minimum Value and the actual Hue and Chroma at which @@ -6490,7 +6490,7 @@ Device-Independent Color Spaces Device-independent color spaces that are derivable to CIE XYZ space can be added using the -XcmsAddColorSpace + function. @@ -6506,7 +6506,7 @@ device-dependent color spaces and their functions that convert between these color spaces and the CIE XYZ color space, bundled together for a specific class of output devices. A function set can be added using the -XcmsAddFunctionSet + function. @@ -6550,11 +6550,11 @@ thus bypassing conversion between CIE u*v*Y and CIE< To add a device-independent color space, use -XcmsAddColorSpace. +. XcmsAddColorSpace - + Status XcmsAddColorSpace XcmsColorSpace *color_space @@ -6578,7 +6578,7 @@ Specifies the device-independent color space to add. The -XcmsAddColorSpace + function makes a device-independent color space (actually an XcmsColorSpace structure) accessible by the color management system. @@ -6589,16 +6589,16 @@ outside the client (for example, storing color specifications in a file using the unregistered color space), then reference should be made by color space prefix (see -XcmsFormatOfPrefix + and -XcmsPrefixOfFormat). +). If the XcmsColorSpace structure is already accessible in the color management system, -XcmsAddColorSpace + returns XcmsSuccess. @@ -6618,11 +6618,11 @@ must be retained for reference by Xlib. To obtain the format associated with the color space associated with a specified color string prefix, use -XcmsFormatOfPrefix. +. XcmsFormatOfPrefix - + XcmsColorFormat XcmsFormatOfPrefix char *prefix @@ -6646,12 +6646,12 @@ Specifies the string that contains the color space prefix. The -XcmsFormatOfPrefix + function returns the format for the specified color space prefix (for example, the string ``CIEXYZ''). The prefix is case-insensitive. If the color space is not accessible in the color management system, -XcmsFormatOfPrefix + returns XcmsUndefinedFormat. @@ -6660,11 +6660,11 @@ returns To obtain the color string prefix associated with the color space specified by a color format, use -XcmsPrefixOfFormat. +. XcmsPrefixOfFormat - + char *XcmsPrefixOfFormat XcmsColorFormat format @@ -6688,7 +6688,7 @@ Specifies the color specification format. The -XcmsPrefixOfFormat + function returns the string prefix associated with the color specification encoding specified by the format argument. Otherwise, if no encoding is found, it returns NULL. @@ -6711,7 +6711,7 @@ for each additional color space. In the case of device-independent color spaces, a handle to this new structure (that is, by means of a global variable) is usually made accessible to the client program for use with the -XcmsAddColorSpace + function. @@ -6725,9 +6725,9 @@ If references to an unregistered color space must be made outside the client (for example, storing color specifications in a file using the unregistered color space), then reference should be made by color space prefix (see -XcmsFormatOfPrefix + and -XcmsPrefixOfFormat). +). @@ -6808,7 +6808,7 @@ adhere to the following software interface specification: XcmsParseStringProc - + Status XcmsParseStringProc char *color_string @@ -6858,7 +6858,7 @@ spaces must adhere to the following software interface specification: - + Status ConversionProc XcmsCCC ccc @@ -7126,11 +7126,11 @@ its corresponding data may be stored on different root window properties. To add a function set, use -XcmsAddFunctionSet. +. XcmsAddFunctionSet - + Status XcmsAddFunctionSet XcmsFunctionSet *function_set @@ -7154,12 +7154,12 @@ Specifies the function set to add. The -XcmsAddFunctionSet + function adds a function set to the color management system. If the function set uses device-dependent XcmsColorSpace structures not accessible in the color management system, -XcmsAddFunctionSet + adds them. If an added XcmsColorSpace @@ -7172,9 +7172,9 @@ client (for example, storing color specifications in a file using the unregistered color space), then reference should be made by color space prefix (see -XcmsFormatOfPrefix + and -XcmsPrefixOfFormat). +). @@ -7207,7 +7207,7 @@ This data is stored in an structure. A handle to this structure (that is, by means of global variable) is usually made accessible to the client program for use with -XcmsAddFunctionSet. +. diff --git a/libX11/specs/libX11/CH07.xml b/libX11/specs/libX11/CH07.xml index 0b873078a..4941db32f 100644 --- a/libX11/specs/libX11/CH07.xml +++ b/libX11/specs/libX11/CH07.xml @@ -1,7 +1,7 @@ - + Graphics Context Functions @@ -25,7 +25,7 @@ This chapter discusses how to: Use graphics context convenience functions - + Manipulating Graphics Context/State @@ -47,9 +47,9 @@ resource IDs to allow Xlib to implement the transparent coalescing of changes to GCs. For example, a call to -XSetForeground + of a GC followed by a call to -XSetLineAttributes + results in only a single-change GC protocol request to the server. GCs are neither expected nor encouraged to be shared between client applications, so this write-back caching should present no problems. @@ -63,7 +63,7 @@ To set an attribute of a GC, set the appropriate member of the XGCValues structure and OR in the corresponding value bitmask in your subsequent calls to -XCreateGC. +. The symbols for the value mask bits and the XGCValues structure are: @@ -720,20 +720,20 @@ any size pixmap can be used for tiling or stippling. The fill-style defines the contents of the source for line, text, and fill requests. For all text and fill requests (for example, -XDrawText, -XDrawText16, -XFillRectangle, -XFillPolygon, +, +, +, +, and -XFillArc); +); for line requests with line-style LineSolid (for example, -XDrawLine, -XDrawSegments, -XDrawRectangle, -XDrawArc); +, +, +, +); and for the even dashes for line requests with line-style LineOnOffDash or @@ -825,10 +825,10 @@ of GCs. The dashes value is actually a simplified form of the more general patterns that can be set with -XSetDashes. +. Specifying a value of N is equivalent to specifying the two-element list [N, N] in -XSetDashes. +. The value must be nonzero, or a BadValue @@ -846,9 +846,9 @@ If clip-mask is set to None, the pixels are always drawn regardless of the clip origin. The clip-mask also can be set by calling the -XSetClipRectangles + or -XSetRegion + functions. Only pixels where the clip-mask has a bit set to 1 are drawn. Pixels are not drawn outside the area covered by the clip-mask @@ -885,7 +885,7 @@ undefined by the core protocol. The fill-rule defines what pixels are inside (drawn) for paths given in -XFillPolygon + requests and can be set to EvenOddRule or @@ -928,7 +928,7 @@ and are inside if and only if the polygon interior is immediately below The arc-mode controls filling in the -XFillArcs + function and can be set to ArcPieSlice or @@ -946,9 +946,9 @@ The graphics-exposure flag controls GraphicsExpose event generation for -XCopyArea + and -XCopyPlane + requests (and any similar requests defined by extensions). @@ -956,12 +956,12 @@ requests (and any similar requests defined by extensions). To create a new GC that is usable on a given screen with a depth of drawable, use -XCreateGC. +. Graphics contextinitializing XCreateGC - + GC XCreateGC Display *display @@ -1020,7 +1020,7 @@ Specifies any values as specified by the valuemask. The -XCreateGC + function creates a graphics context and returns a GC. The GC can be used with any destination drawable having the same root and depth as the specified drawable. @@ -1030,7 +1030,7 @@ error. -XCreateGC + can generate BadAlloc, BadDrawable, @@ -1045,11 +1045,11 @@ errors. To copy components from a source GC to a destination GC, use -XCopyGC. +. XCopyGC - + XCopyGC Display *display @@ -1107,7 +1107,7 @@ Specifies the destination GC. The -XCopyGC + function copies the specified components from the source GC to the destination GC. The source and destination GCs must have the same root and depth, @@ -1115,11 +1115,11 @@ or a BadMatch error results. The valuemask specifies which component to copy, as for -XCreateGC. +. -XCopyGC + can generate BadAlloc, BadGC, @@ -1131,11 +1131,11 @@ errors. To change the components in a given GC, use -XChangeGC. +. XChangeGC - + XChangeGC Display *display @@ -1194,25 +1194,25 @@ Specifies any values as specified by the valuemask. The -XChangeGC + function changes the components specified by valuemask for the specified GC. The values argument contains the values to be set. The values and restrictions are the same as for -XCreateGC. +. Changing the clip-mask overrides any previous -XSetClipRectangles + request on the context. Changing the dash-offset or dash-list overrides any previous -XSetDashes + request on the context. The order in which components are verified and altered is server dependent. If an error is generated, a subset of the components may have been altered. -XChangeGC + can generate BadAlloc, BadFont, @@ -1227,11 +1227,11 @@ errors. To obtain components of a given GC, use -XGetGCValues. +. XGetGCValues - + Status XGetGCValues Display *display @@ -1292,7 +1292,7 @@ structure. The -XGetGCValues + function returns the components specified by valuemask for the specified GC. If the valuemask contains a valid set of GC mask bits (GCFunction, @@ -1318,7 +1318,7 @@ If the valuemask contains a valid set of GC mask bits or GCArcMode) and no error occurs, -XGetGCValues + sets the requested components in values_return and returns a nonzero status. Otherwise, it returns a zero status. Note that the clip-mask and dash-list (represented by the @@ -1339,11 +1339,11 @@ if the component has never been explicitly set by the client. To free a given GC, use -XFreeGC. +. XFreeGC - + XFreeGC Display *display @@ -1377,12 +1377,12 @@ Specifies the GC. The -XFreeGC + function destroys the specified GC as well as all the associated storage. -XFreeGC + can generate a BadGC error. @@ -1393,11 +1393,11 @@ error. To obtain the GContext resource ID for a given GC, use -XGContextFromGC. +. XGContextFromGC - + GContext XGContextFromGC GC gc @@ -1429,11 +1429,11 @@ to explicitly force sending the changes to the server. An example might be when a protocol extension uses the GC indirectly, in such a way that the extension interface cannot know what GC will be used. To force sending GC component changes, use -XFlushGC. +. XFlushGC - + void XFlushGC Display *display @@ -1523,11 +1523,11 @@ Arc mode, subwindow mode, and graphics exposure components To set the foreground, background, plane mask, and function components for a given GC, use -XSetState. +. XSetState - + XSetState Display *display @@ -1604,7 +1604,7 @@ Specifies the plane mask. -XSetState + can generate BadAlloc, BadGC, @@ -1616,11 +1616,11 @@ errors. To set the foreground of a given GC, use -XSetForeground. +. XSetForeground - + XSetForeground Display *display @@ -1664,7 +1664,7 @@ Specifies the foreground you want to set for the specified GC. -XSetForeground + can generate BadAlloc and @@ -1675,11 +1675,11 @@ errors. To set the background of a given GC, use -XSetBackground. +. XSetBackground - + XSetBackground Display *display @@ -1723,7 +1723,7 @@ Specifies the background you want to set for the specified GC. -XSetBackground + can generate BadAlloc and @@ -1734,11 +1734,11 @@ errors. To set the display function in a given GC, use -XSetFunction. +. XSetFunction - + XSetFunction Display *display @@ -1782,7 +1782,7 @@ Specifies the function you want to set for the specified GC. -XSetFunction + can generate BadAlloc, BadGC, @@ -1794,11 +1794,11 @@ errors. To set the plane mask of a given GC, use -XSetPlaneMask. +. XSetPlaneMask - + XSetPlaneMask Display *display @@ -1843,7 +1843,7 @@ Specifies the plane mask. -XSetPlaneMask + can generate BadAlloc and @@ -1859,11 +1859,11 @@ errors. To set the line drawing components of a given GC, use -XSetLineAttributes. +. XSetLineAttributes - + XSetLineAttributes Display *display @@ -1956,7 +1956,7 @@ or -XSetLineAttributes + can generate BadAlloc, BadGC, @@ -1968,11 +1968,11 @@ errors. To set the dash-offset and dash-list for dashed line styles of a given GC, use -XSetDashes. +. XSetDashes - + XSetDashes Display *display @@ -2041,7 +2041,7 @@ Specifies the number of elements in dash_list. The -XSetDashes + function sets the dash-offset and dash-list attributes for dashed line styles in the specified GC. There must be at least one element in the specified dash_list, @@ -2080,7 +2080,7 @@ For all other lines, the major axis is the y axis. -XSetDashes + can generate BadAlloc, BadGC, @@ -2089,19 +2089,19 @@ and errors. - -Setting the Fill Style and Fill Rule + +Setting the Fill Style and Fill Rule To set the fill-style of a given GC, use -XSetFillStyle. +. XSetFillStyle - + XSetFillStyle Display *display @@ -2151,7 +2151,7 @@ or -XSetFillStyle + can generate BadAlloc, BadGC, @@ -2163,11 +2163,11 @@ errors. To set the fill-rule of a given GC, use -XSetFillRule. +. XSetFillRule - + XSetFillRule Display *display @@ -2215,7 +2215,7 @@ or -XSetFillRule + can generate BadAlloc, BadGC, @@ -2224,8 +2224,8 @@ and errors. - -Setting the Fill Tile and Stipple + +Setting the Fill Tile and Stipple @@ -2243,11 +2243,11 @@ as well as to set the tile or stipple shape and the tile or stipple origin. To obtain the best size of a tile, stipple, or cursor, use -XQueryBestSize. +. XQueryBestSize - + Status XQueryBestSize Display *display @@ -2342,7 +2342,7 @@ by the display hardware. The -XQueryBestSize + function returns the best or closest size to the specified size. For CursorShape, @@ -2374,7 +2374,7 @@ error results. -XQueryBestSize + can generate BadDrawable, BadMatch, @@ -2386,11 +2386,11 @@ errors. To obtain the best fill tile shape, use -XQueryBestTile. +. XQueryBestTile - + Status XQueryBestTile Display *display @@ -2469,7 +2469,7 @@ by the display hardware. The -XQueryBestTile + function returns the best or closest size, that is, the size that can be tiled fastest on the screen specified by which_screen. The drawable indicates the screen and possibly the window class and depth. @@ -2481,7 +2481,7 @@ error results. -XQueryBestTile + can generate BadDrawable and @@ -2492,11 +2492,11 @@ errors. To obtain the best stipple shape, use -XQueryBestStipple. +. XQueryBestStipple - + Status XQueryBestStipple Display *display @@ -2575,7 +2575,7 @@ by the display hardware. The -XQueryBestStipple + function returns the best or closest size, that is, the size that can be stippled fastest on the screen specified by which_screen. The drawable indicates the screen and possibly the window class and depth. @@ -2587,7 +2587,7 @@ error results. -XQueryBestStipple + can generate BadDrawable and @@ -2598,11 +2598,11 @@ errors. To set the fill tile of a given GC, use -XSetTile. +. XSetTile - + XSetTile Display *display @@ -2653,7 +2653,7 @@ error results. -XSetTile + can generate BadAlloc, BadGC, @@ -2666,11 +2666,11 @@ errors. To set the stipple of a given GC, use -XSetStipple. +. XSetStipple - + XSetStipple Display *display @@ -2721,7 +2721,7 @@ error results. -XSetStipple + can generate BadAlloc, BadGC, @@ -2734,11 +2734,11 @@ errors. To set the tile or stipple origin of a given GC, use -XSetTSOrigin. +. XSetTSOrigin - + XSetTSOrigin Display *display @@ -2799,7 +2799,7 @@ drawable is specified in the graphics request. -XSetTSOrigin + can generate BadAlloc and @@ -2807,19 +2807,19 @@ and errors. - -Setting the Current Font + +Setting the Current Font To set the current font of a given GC, use -XSetFont. +. XSetFont - + XSetFont Display *display @@ -2863,7 +2863,7 @@ Specifies the font. -XSetFont + can generate BadAlloc, BadFont, @@ -2886,11 +2886,11 @@ and the clip-mask or set the clip-mask to a list of rectangles. To set the clip-origin of a given GC, use -XSetClipOrigin. +. XSetClipOrigin - + XSetClipOrigin Display *display @@ -2950,7 +2950,7 @@ destination drawable is specified in the graphics request. -XSetClipOrigin + can generate BadAlloc and @@ -2961,11 +2961,11 @@ errors. To set the clip-mask of a given GC to the specified pixmap, use -XSetClipMask. +. XSetClipMask - + XSetClipMask Display *display @@ -3016,7 +3016,7 @@ the pixels are always drawn (regardless of the clip-origin). -XSetClipMask + can generate BadAlloc, BadGC, @@ -3029,11 +3029,11 @@ errors. To set the clip-mask of a given GC to the specified list of rectangles, use -XSetClipRectangles. +. XSetClipRectangles - + XSetClipRectangles Display *display @@ -3128,7 +3128,7 @@ or The -XSetClipRectangles + function changes the clip-mask in the specified GC to the specified list of rectangles and sets the clip origin. The output is clipped to remain contained within the @@ -3143,10 +3143,10 @@ which effectively disables output. This is the opposite of passing None as the clip-mask in -XCreateGC, -XChangeGC, +, +, and -XSetClipMask. +. @@ -3178,7 +3178,7 @@ scanline have an identical Y origins and Y extents. -XSetClipRectangles + can generate BadAlloc, BadGC, @@ -3195,19 +3195,19 @@ For information about these functions, see section 16.5. - -Setting the Arc Mode, Subwindow Mode, and Graphics Exposure + +Setting the Arc Mode, Subwindow Mode, and Graphics Exposure To set the arc mode of a given GC, use -XSetArcMode. +. XSetArcMode - + XSetArcMode Display *display @@ -3255,7 +3255,7 @@ or -XSetArcMode + can generate BadAlloc, BadGC, @@ -3267,11 +3267,11 @@ errors. To set the subwindow mode of a given GC, use -XSetSubwindowMode. +. XSetSubwindowMode - + XSetSubwindowMode Display *display @@ -3319,7 +3319,7 @@ or -XSetSubwindowMode + can generate BadAlloc, BadGC, @@ -3331,11 +3331,11 @@ errors. To set the graphics-exposures flag of a given GC, use -XSetGraphicsExposures. +. XSetGraphicsExposures - + XSetGraphicsExposures Display *display @@ -3376,9 +3376,9 @@ Specifies a Boolean value that indicates whether you want and NoExpose events to be reported when calling -XCopyArea + and -XCopyPlane + with this GC. @@ -3387,7 +3387,7 @@ with this GC. -XSetGraphicsExposures + can generate BadAlloc, BadGC, diff --git a/libX11/specs/libX11/CH08.xml b/libX11/specs/libX11/CH08.xml index 8e0bae629..b2348b5ae 100644 --- a/libX11/specs/libX11/CH08.xml +++ b/libX11/specs/libX11/CH08.xml @@ -1,7 +1,7 @@ - + Graphics Functions Once you have established a connection to a display, you can use the Xlib graphics functions to: @@ -31,20 +31,20 @@ Because pixmaps do not have defined backgrounds, they cannot be filled by using the functions described in this section. Instead, to accomplish an analogous operation on a pixmap, you should use -XFillRectangle, +, which sets the pixmap to a known value. To clear a rectangular area of a given window, use -XClearArea. +. Areasclearing Clearingareas XClearArea - + XClearArea Display *display @@ -138,7 +138,7 @@ events are to be generated. The -XClearArea + function paints a rectangular area in the specified window according to the specified dimensions with the window's background pixel or pixmap. The subwindow-mode effectively is @@ -168,7 +168,7 @@ error results. -XClearArea + can generate BadMatch, BadValue, @@ -180,13 +180,13 @@ errors. To clear the entire area in a given window, use -XClearWindow. +. Windowclearing Clearingwindows XClearWindow - + XClearWindow Display *display @@ -220,10 +220,10 @@ Specifies the window. The -XClearWindow + function clears the entire area in the specified window and is equivalent to -XClearArea + (display, w, 0, 0, 0, 0, False). If the window has a defined background tile, the rectangle is tiled with a @@ -242,7 +242,7 @@ error results. -XClearWindow + can generate BadMatch and @@ -264,13 +264,13 @@ Xlib provides functions that you can use to copy an area or a bit plane. To copy an area between drawables of the same root and depth, use -XCopyArea. +. Areascopying Copyingareas XCopyArea - + XCopyArea Display *display @@ -398,7 +398,7 @@ Specify the x and y coordinates(Dx. The -XCopyArea + function combines the specified rectangle of src with the specified rectangle of dest. The drawables must have the same root and depth, @@ -447,7 +447,7 @@ clip-y-origin, and clip-mask. -XCopyArea + can generate BadDrawable, BadGC, @@ -459,13 +459,13 @@ errors. To copy a single bit plane of a given drawable, use -XCopyPlane. +. Planecopying Copyingplanes XCopyPlane - + XCopyPlane Display *display @@ -604,7 +604,7 @@ You must set exactly one bit to 1. The -XCopyPlane + function uses a single bit plane of the specified source rectangle combined with the specified GC to modify the specified rectangle of dest. The drawables must have the same root but need not have the same depth. @@ -619,7 +619,7 @@ error results. Effectively, -XCopyPlane + forms a pixmap of the same depth as the rectangle of dest and with a size specified by the source region. It uses the foreground/background pixels in the GC (foreground @@ -641,7 +641,7 @@ and clip-mask. -XCopyPlane + can generate BadDrawable, BadGC, @@ -765,11 +765,11 @@ for these values. To draw a single point in a given drawable, use -XDrawPoint. +. XDrawPoint - + XDrawPoint Display *display @@ -837,11 +837,11 @@ Specify the x and y coordinates where you want the point drawn. To draw multiple points in a given drawable, use -XDrawPoints. +. XDrawPoints - + XDrawPoints Display *display @@ -923,17 +923,17 @@ or The -XDrawPoint + function uses the foreground pixel and function components of the GC to draw a single point into the specified drawable; -XDrawPoints + draws multiple points this way. CoordModeOrigin treats all coordinates as relative to the origin, and CoordModePrevious treats all coordinates after the first as relative to the previous point. -XDrawPoints + draws the points in the order listed in the array. @@ -943,14 +943,14 @@ foreground, subwindow-mode, clip-x-origin, clip-y-origin, and clip-mask. -XDrawPoint + can generate BadDrawable, BadGC, and BadMatch errors. -XDrawPoints + can generate BadDrawable, BadGC, @@ -978,11 +978,11 @@ errors. To draw a single line between two points in a given drawable, use -XDrawLine. +. XDrawLine - + XDrawLine Display *display @@ -1072,11 +1072,11 @@ Specify the points (x1, y1) and (x2, y2) to be connected. To draw multiple lines in a given drawable, use -XDrawLines. +. XDrawLines - + XDrawLines Display *display @@ -1160,11 +1160,11 @@ or To draw multiple, unconnected lines in a given drawable, use -XDrawSegments. +. XDrawSegments - + XDrawSegments Display *display @@ -1231,19 +1231,19 @@ Specifies the number of segments in the array. The -XDrawLine + function uses the components of the specified GC to draw a line between the specified set of points (x1, y1) and (x2, y2). It does not perform joining at coincident endpoints. For any given line, -XDrawLine + does not draw a pixel more than once. If lines intersect, the intersecting pixels are drawn multiple times. The -XDrawLines + function uses the components of the specified GC to draw npoints-1 lines between each pair of points (point[i], point[i+1]) in the array of @@ -1253,7 +1253,7 @@ It draws the lines in the order listed in the array. The lines join correctly at all intermediate points, and if the first and last points coincide, the first and last lines also join correctly. For any given line, -XDrawLines + does not draw a pixel more than once. If thin (zero line-width) lines intersect, the intersecting pixels are drawn multiple times. @@ -1270,17 +1270,17 @@ treats all coordinates after the first as relative to the previous point. The -XDrawSegments + function draws multiple, unconnected lines. For each segment, -XDrawSegments + draws a line between (x1, y1) and (x2, y2). It draws the lines in the order listed in the array of XSegment structures and does not perform joining at coincident endpoints. For any given line, -XDrawSegments + does not draw a pixel more than once. If lines intersect, the intersecting pixels are drawn multiple times. @@ -1291,7 +1291,7 @@ function, plane-mask, line-width, line-style, cap-style, fill-style, subwindow-mode, clip-x-origin, clip-y-origin, and clip-mask. The -XDrawLines + function also uses the join-style GC component. All three functions also use these GC mode-dependent components: foreground, background, tile, stipple, tile-stipple-x-origin, @@ -1299,24 +1299,24 @@ tile-stipple-y-origin, dash-offset, and dash-list. -XDrawLine, -XDrawLines, +, +, and -XDrawSegments + can generate BadDrawable, BadGC, and BadMatch errors. -XDrawLines + also can generate BadValue errors. - -Drawing Single and Multiple Rectangles + +Drawing Single and Multiple Rectangles @@ -1330,11 +1330,11 @@ errors. To draw the outline of a single rectangle in a given drawable, use -XDrawRectangle. +. XDrawRectangle - + XDrawRectangle Display *display @@ -1427,11 +1427,11 @@ Specify the width and height(Wh. To draw the outline of multiple rectangles in a given drawable, use -XDrawRectangles. +. XDrawRectangles - + XDrawRectangles Display *display @@ -1498,9 +1498,9 @@ Specifies the number of rectangles in the array. The -XDrawRectangle + and -XDrawRectangles + functions draw the outlines of the specified rectangle or rectangles as if a five-point PolyLine @@ -1517,7 +1517,7 @@ protocol request were specified for each rectangle: For the specified rectangle or rectangles, these functions do not draw a pixel more than once. -XDrawRectangles + draws the rectangles in the order listed in the array. If rectangles intersect, the intersecting pixels are drawn multiple times. @@ -1534,9 +1534,9 @@ tile-stipple-y-origin, dash-offset, and dash-list. -XDrawRectangle + and -XDrawRectangles + can generate BadDrawable, BadGC, @@ -1561,11 +1561,11 @@ errors. To draw a single arc in a given drawable, use -XDrawArc. +. XDrawArc - + XDrawArc Display *display @@ -1681,11 +1681,11 @@ arc, in units of degrees * 64. To draw multiple arcs in a given drawable, use -XDrawArcs. +. XDrawArcs - + XDrawArcs Display *display @@ -1754,9 +1754,9 @@ Specifies the number of arcs in the array. delim %% -XDrawArc + draws a single circular or elliptical arc, and -XDrawArcs + draws multiple circular or elliptical arcs. Each arc is specified by a rectangle and two angles. The center of the circle or ellipse is the center of the @@ -1764,9 +1764,9 @@ rectangle, and the major and minor axes are specified by the width and height. Positive angles indicate counterclockwise motion, and negative angles indicate clockwise motion. If the magnitude of angle2 is greater than 360 degrees, -XDrawArc + or -XDrawArcs + truncates it to 360 degrees. @@ -1827,15 +1827,15 @@ and adjust is: For any given arc, -XDrawArc + and -XDrawArcs + do not draw a pixel more than once. If two arcs join correctly and if the line-width is greater than zero and the arcs intersect, -XDrawArc + and -XDrawArcs + do not draw a pixel more than once. Otherwise, the intersecting pixels of intersecting arcs are drawn multiple times. @@ -1865,9 +1865,9 @@ tile-stipple-y-origin, dash-offset, and dash-list. -XDrawArc + and -XDrawArcs + can generate BadDrawable, BadGC, @@ -1919,11 +1919,11 @@ A single arc or multiple arcs To fill a single rectangular area in a given drawable, use -XFillRectangle. +. XFillRectangle - + XFillRectangle Display *display @@ -2016,11 +2016,11 @@ Specify the width and height(Wh. To fill multiple rectangular areas in a given drawable, use -XFillRectangles. +. XFillRectangles - + XFillRectangles Display *display @@ -2087,9 +2087,9 @@ Specifies the number of rectangles in the array. The -XFillRectangle + and -XFillRectangles + functions fill the specified rectangle or rectangles as if a four-point FillPolygon @@ -2108,12 +2108,12 @@ width and height dimensions, and GC you specify. -XFillRectangles + fills the rectangles in the order listed in the array. For any given rectangle, -XFillRectangle + and -XFillRectangles + do not draw a pixel more than once. If rectangles intersect, the intersecting pixels are drawn multiple times. @@ -2129,9 +2129,9 @@ and tile-stipple-y-origin. -XFillRectangle + and -XFillRectangles + can generate BadDrawable, BadGC, @@ -2149,13 +2149,13 @@ errors. To fill a polygon area in a given drawable, use -XFillPolygon. +. Polygonsfilling Fillingpolygon XFillPolygon - + XFillPolygon Display *display @@ -2252,12 +2252,12 @@ or -XFillPolygon + fills the region closed by the specified path. The path is closed automatically if the last point in the list does not coincide with the first point. -XFillPolygon + does not draw a pixel of the region more than once. CoordModeOrigin treats all coordinates as relative to the origin, @@ -2329,7 +2329,7 @@ and tile-stipple-y-origin. -XFillPolygon + can generate BadDrawable, BadGC, @@ -2350,11 +2350,11 @@ errors. Arcsfilling Fillingarcs To fill a single arc in a given drawable, use -XFillArc. +. XFillArc - + XFillArc Display *display @@ -2470,11 +2470,11 @@ arc, in units of degrees * 64. To fill multiple arcs in a given drawable, use -XFillArcs. +. XFillArcs - + XFillArcs Display *display @@ -2541,9 +2541,9 @@ Specifies the number of arcs in the array. For each arc, -XFillArc + or -XFillArcs + fills the region closed by the infinitely thin path described by the specified arc and, depending on the arc-mode specified in the GC, one or two line segments. @@ -2554,12 +2554,12 @@ For ArcPieSlice, the two line segments joining the endpoints of the arc with the center point are used. -XFillArcs + fills the arcs in the order listed in the array. For any given arc, -XFillArc + and -XFillArcs + do not draw a pixel more than once. If regions intersect, the intersecting pixels are drawn multiple times. @@ -2575,9 +2575,9 @@ and tile-stipple-y-origin. -XFillArc + and -XFillArcs + can generate BadDrawable, BadGC, @@ -2637,7 +2637,7 @@ The server can cache fonts for quick lookup. Fonts are global across all screens in a server. Several levels are possible when dealing with fonts. Most applications simply use -XLoadQueryFont + to load a font and query the font metrics. @@ -3017,11 +3017,11 @@ resource ID or a font ID interchangeably. To load a given font, use -XLoadFont. +. XLoadFont - + Font XLoadFont Display *display @@ -3056,7 +3056,7 @@ which is a null-terminated string. The -XLoadFont + 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. @@ -3069,7 +3069,7 @@ and the ``*'' character will match any number of characters. A structured format for font names is specified in the X Consortium standard X Logical Font Description Conventions. If -XLoadFont + was unsuccessful at loading the specified font, a BadName @@ -3078,11 +3078,11 @@ Fonts are not associated with a particular screen and can be stored as a component of any GC. When the font is no longer needed, call -XUnloadFont. +. -XLoadFont + can generate BadAlloc and @@ -3093,11 +3093,11 @@ errors. To return information about an available font, use -XQueryFont. +. XQueryFont - + XFontStruct *XQueryFont Display *display @@ -3133,7 +3133,7 @@ ID. The -XQueryFont + function returns a pointer to the XFontStruct structure, which contains information associated with the font. @@ -3144,26 +3144,26 @@ structure will be the GContext ID, and you need to be careful when using this ID in other functions (see -XGContextFromGC). +). If the font does not exist, -XQueryFont + returns NULL. To free this data, use -XFreeFontInfo. +. To perform a -XLoadFont + and -XQueryFont + in a single operation, use -XLoadQueryFont. +. XLoadQueryFont - + XFontStruct *XLoadQueryFont Display *display @@ -3198,9 +3198,9 @@ which is a null-terminated string. The -XLoadQueryFont + function provides the most common way for accessing a font. -XLoadQueryFont + both opens (loads) the specified font and returns a pointer to the appropriate XFontStruct @@ -3208,12 +3208,12 @@ structure. If the font name is not in the Host Portable Character Encoding, the result is implementation-dependent. If the font does not exist, -XLoadQueryFont + returns NULL. -XLoadQueryFont + can generate a BadAlloc error. @@ -3223,15 +3223,15 @@ error. To unload the font and free the storage used by the font structure that was allocated by -XQueryFont + or -XLoadQueryFont, +, use -XFreeFont. +. XFreeFont - + XFreeFont Display *display @@ -3265,7 +3265,7 @@ Specifies the storage associated with the font. The -XFreeFont + function deletes the association between the font resource ID and the specified font and frees the XFontStruct @@ -3275,7 +3275,7 @@ The data and the font should not be referenced again. -XFreeFont + can generate a BadFont error. @@ -3284,11 +3284,11 @@ error. To return a given font property, use -XGetFontProperty. +. XGetFontProperty - + Bool XGetFontProperty XFontStruct *font_struct @@ -3334,9 +3334,9 @@ Returns the value of the font property. Given the atom for that property, the -XGetFontProperty + function returns the value of the specified font property. -XGetFontProperty + also returns False if the property was not defined or @@ -3357,13 +3357,13 @@ it is likely that the predefined font properties will be present. To unload a font that was loaded by -XLoadFont, +, use -XUnloadFont. +. XUnloadFont - + XUnloadFont Display *display @@ -3397,14 +3397,14 @@ Specifies the font. The -XUnloadFont + function deletes the association between the font resource ID and the specified font. The font itself will be freed when no other resource references it. The font should not be referenced again. -XUnloadFont + can generate a BadFont error. @@ -3424,11 +3424,11 @@ when querying a font type for a list of available sizes and so on. To return a list of the available font names, use -XListFonts. +. XListFonts - + char **XListFonts Display *display @@ -3485,10 +3485,10 @@ Returns the actual number of font names. The -XListFonts + function returns an array of available font names (as controlled by the font search path; see -XSetFontPath) +) that match the string you passed to the pattern argument. The pattern string can contain any characters, but each asterisk (*) is a wildcard for any number of characters, @@ -3501,21 +3501,21 @@ If the data returned by the server is in the Latin Portable Character Encoding, then the returned strings are in the Host Portable Character Encoding. Otherwise, the result is implementation-dependent. If there are no matching font names, -XListFonts + returns NULL. The client should call -XFreeFontNames + when finished with the result to free the memory. To free a font name array, use -XFreeFontNames. +. XFreeFontNames - + XFreeFontNames char *list[] @@ -3538,21 +3538,21 @@ Specifies the array of strings you want to free. The -XFreeFontNames + function frees the array and strings returned by -XListFonts + or -XListFontsWithInfo. +. To obtain the names and information about available fonts, use -XListFontsWithInfo. +. XListFontsWithInfo - + char **XListFontsWithInfo Display *display @@ -3620,12 +3620,12 @@ Returns the font information. The -XListFontsWithInfo + function returns a list of font names that match the specified pattern and their associated font information. The list of names is limited to size specified by maxnames. The information returned for each font is identical to what -XLoadQueryFont + would return except that the per-character metrics are not returned. The pattern string can contain any characters, but each asterisk (*) is a wildcard for any number of characters, @@ -3638,28 +3638,28 @@ If the data returned by the server is in the Latin Portable Character Encoding, then the returned strings are in the Host Portable Character Encoding. Otherwise, the result is implementation-dependent. If there are no matching font names, -XListFontsWithInfo + returns NULL. To free only the allocated name array, the client should call -XFreeFontNames. +. To free both the name array and the font information array or to free just the font information array, the client should call -XFreeFontInfo. +. To free font structures and font names, use -XFreeFontInfo. +. XFreeFontInfo - + XFreeFontInfo char **names @@ -3707,15 +3707,15 @@ Specifies the actual number of font names. The -XFreeFontInfo + function frees a font structure or an array of font structures and optionally an array of font names. If NULL is passed for names, no font names are freed. If a font structure for an open font (returned by -XLoadQueryFont) +) is passed, the structure is freed, but the font is not closed; use -XUnloadFont + to close the font. @@ -3739,11 +3739,11 @@ These functions return the sum of the character metrics in pixels. To determine the width of an 8-bit character string, use -XTextWidth. +. XTextWidth - + int XTextWidth XFontStruct *font_struct @@ -3789,11 +3789,11 @@ Specifies the character count in the specified string. To determine the width of a 2-byte character string, use -XTextWidth16. +. XTextWidth16 - + int XTextWidth16 XFontStruct *font_struct @@ -3847,11 +3847,11 @@ Specifies the character count in the specified string. To compute the bounding box of an 8-bit character string in a given font, use -XTextExtents. +. XTextExtents - + XTextExtents XFontStruct *font_struct @@ -3947,11 +3947,11 @@ structure. To compute the bounding box of a 2-byte character string in a given font, use -XTextExtents16. +. XTextExtents16 - + XTextExtents16 XFontStruct *font_struct @@ -4046,15 +4046,15 @@ structure. The -XTextExtents + and -XTextExtents16 + functions perform the size computation locally and, thereby, avoid the round-trip overhead of -XQueryTextExtents + and -XQueryTextExtents16. +. Both functions return an XCharStruct structure, whose members are set to the values as follows. @@ -4094,11 +4094,11 @@ undefined characters in the string are taken to have all zero metrics. To query the server for the bounding box of an 8-bit character string in a given font, use -XQueryTextExtents. +. XQueryTextExtents - + XQueryTextExtents Display *display @@ -4206,11 +4206,11 @@ structure. To query the server for the bounding box of a 2-byte character string in a given font, use -XQueryTextExtents16. +. XQueryTextExtents16 - + XQueryTextExtents16 Display *display @@ -4316,17 +4316,17 @@ structure. The -XQueryTextExtents + and -XQueryTextExtents16 + functions return the bounding box of the specified 8-bit and 16-bit character string in the specified font or the font contained in the specified GC. These functions query the X server and, therefore, suffer the round-trip overhead that is avoided by -XTextExtents + and -XTextExtents16. +. Both functions return a XCharStruct structure, whose members are set to the values as follows. @@ -4364,9 +4364,9 @@ the undefined characters in the string are also ignored. -XQueryTextExtents + and -XQueryTextExtents16 + can generate BadFont and @@ -4404,9 +4404,9 @@ Image text characters The fundamental text functions -XDrawText + and -XDrawText16 + use the following structures: @@ -4452,7 +4452,7 @@ coordinates that you pass in the text drawing functions. For example, consider the background rectangle drawn by -XDrawImageString. +. If you want the upper-left corner of the background rectangle to be at pixel coordinate (x,y), pass the (x,y + ascent) as the baseline origin coordinates to the text functions. @@ -4479,11 +4479,11 @@ structure. To draw 8-bit characters in a given drawable, use -XDrawText. +. XDrawText - + XDrawText Display *display @@ -4575,11 +4575,11 @@ Specifies the number of text items in the array. To draw 2-byte characters in a given drawable, use -XDrawText16. +. XDrawText16 - + XDrawText16 Display *display @@ -4670,9 +4670,9 @@ Specifies the number of text items in the array. The -XDrawText16 + function is similar to -XDrawText + except that it uses 2-byte or 16-bit characters. Both functions allow complex spacing and font shifts between counted strings. @@ -4713,9 +4713,9 @@ and tile-stipple-y-origin. -XDrawText + and -XDrawText16 + can generate BadDrawable, BadFont, @@ -4735,11 +4735,11 @@ errors. Stringsdrawing Drawingstrings To draw 8-bit characters in a given drawable, use -XDrawString. +. XDrawString - + XDrawString Display *display @@ -4832,11 +4832,11 @@ Specifies the number of characters in the string argument. To draw 2-byte characters in a given drawable, use -XDrawString16. +. XDrawString16 - + XDrawString16 Display *display @@ -4931,7 +4931,7 @@ additional mask for a fill operation on the drawable. The drawable is modified only where the font character has a bit set to 1. For fonts defined with 2-byte matrix indexing and used with -XDrawString16, +, each byte is used as a byte2 with a byte1 of zero. @@ -4945,9 +4945,9 @@ and tile-stipple-y-origin. -XDrawString + and -XDrawString16 + can generate BadDrawable, BadGC, @@ -4976,11 +4976,11 @@ This prevents annoying flicker on many displays. To draw 8-bit image text characters in a given drawable, use -XDrawImageString. +. XDrawImageString - + XDrawImageString Display *display @@ -5072,11 +5072,11 @@ Specifies the number of characters in the string argument. To draw 2-byte image text characters in a given drawable, use -XDrawImageString16. +. XDrawImageString16 - + XDrawImageString16 Display *display @@ -5167,9 +5167,9 @@ Specifies the number of characters in the string argument. The -XDrawImageString16 + function is similar to -XDrawImageString + except that it uses 2-byte or 16-bit characters. Both functions also use both the foreground and background pixels of the GC in the destination. @@ -5211,7 +5211,7 @@ font-ascent + font-descent The overall-width, font-ascent, and font-descent are as would be returned by -XQueryTextExtents + using gc and string. The function and fill-style defined in the GC are ignored for these functions. The effective function is @@ -5223,7 +5223,7 @@ and the effective fill-style is For fonts defined with 2-byte matrix indexing and used with -XDrawImageString, +, each byte is used as a byte2 with a byte1 of zero. @@ -5234,9 +5234,9 @@ clip-y-origin, and clip-mask. -XDrawImageString + and -XDrawImageString16 + can generate BadDrawable, BadGC, @@ -5317,11 +5317,11 @@ typedef struct _XImage { To initialize the image manipulation routines of an image structure, use -XInitImage. +. XInitImage - + Status XInitImage XImage *image @@ -5344,12 +5344,12 @@ Specifies the image. The -XInitImage + function initializes the internal image manipulation routines of an image structure, based on the values of the various structure members. All fields other than the manipulation routines must already be initialized. If the bytes_per_line member is zero, -XInitImage + will assume the image data is contiguous in memory and set the bytes_per_line member to an appropriate value based on the other members; otherwise, the value of bytes_per_line is not changed. @@ -5375,11 +5375,11 @@ or inconsistency in the structure, in which case the image is not changed. To combine an image with a rectangle of a drawable on the display, use -XPutImage. +. XPutImage - + XPutImage Display *display @@ -5509,7 +5509,7 @@ Specify the width and height(Wh. The -XPutImage + function combines an image with a rectangle of the specified drawable. The section of the image defined by the src_x, src_y, width, and height @@ -5535,7 +5535,7 @@ error results. If the characteristics of the image (for example, byte_order and bitmap_unit) differ from what the server requires, -XPutImage + automatically makes the appropriate conversions. @@ -5549,7 +5549,7 @@ foreground and background. -XPutImage + can generate BadDrawable, BadGC, @@ -5563,12 +5563,12 @@ errors. To return the contents of a rectangle in a given drawable on the display, use -XGetImage. +. This function specifically supports rudimentary screen dumps. XGetImage - + XImage *XGetImage Display *display @@ -5676,7 +5676,7 @@ or The -XGetImage + function returns a pointer to an XImage structure. @@ -5690,7 +5690,7 @@ display, the depth of the returned image will be the number of planes requested. If the format argument is ZPixmap, -XGetImage + returns as zero the bits in all planes not specified in the plane_mask argument. The function performs no range checking on the values in plane_mask and ignores @@ -5698,7 +5698,7 @@ extraneous bits. -XGetImage + returns the depth of the image to the depth member of the XImage structure. @@ -5733,12 +5733,12 @@ The returned contents of visible regions of inferiors of a different depth than the specified window's depth are also undefined. The pointer cursor image is not included in the returned contents. If a problem occurs, -XGetImage + returns NULL. -XGetImage + can generate BadDrawable, BadMatch, @@ -5751,11 +5751,11 @@ errors. To copy the contents of a rectangle on the display to a location within a preexisting image structure, use -XGetSubImage. +. XGetSubImage - + XImage *XGetSubImage Display *display @@ -5899,21 +5899,21 @@ Specify the x and y coordinates(Dx. The -XGetSubImage + function updates dest_image with the specified subimage in the same manner as -XGetImage. +. If the format argument is XYPixmap, the image contains only the bit planes you passed to the plane_mask argument. If the format argument is ZPixmap, -XGetSubImage + returns as zero the bits in all planes not specified in the plane_mask argument. The function performs no range checking on the values in plane_mask and ignores extraneous bits. As a convenience, -XGetSubImage + returns a pointer to the same XImage structure specified by dest_image. @@ -5946,12 +5946,12 @@ the returned contents of such obscured regions are undefined. The returned contents of visible regions of inferiors of a different depth than the specified window's depth are also undefined. If a problem occurs, -XGetSubImage + returns NULL. -XGetSubImage + can generate BadDrawable, BadGC, diff --git a/libX11/specs/libX11/CH09.xml b/libX11/specs/libX11/CH09.xml index d37e0863a..e239db2e9 100644 --- a/libX11/specs/libX11/CH09.xml +++ b/libX11/specs/libX11/CH09.xml @@ -1,7 +1,7 @@ - + Window and Session Manager Functions @@ -31,12 +31,12 @@ management functions to: To change a window's parent to another window on the same screen, use -XReparentWindow. +. There is no way to move a window between screens. XReparentWindow - + XReparentWindow Display *display @@ -104,7 +104,7 @@ Specify the x and y coordinates(Xy. If the specified window is mapped, -XReparentWindow + automatically performs an UnmapWindow request on it, removes it from its current position in the hierarchy, @@ -115,7 +115,7 @@ sibling windows. After reparenting the specified window, -XReparentWindow + causes the X server to generate a ReparentNotify event. @@ -175,7 +175,7 @@ specified window. -XReparentWindow + can generate BadMatch and @@ -194,7 +194,7 @@ The save-set of a client is a list of other clients' windows that, if they are inferiors of one of the client's windows at connection close, should not be destroyed and should be remapped if they are unmapped. For further information about close-connection processing, -see section 2.6. +see section 2.6. To allow an application's window to survive when a window manager that has reparented a window fails, Xlib provides the save-set functions that you can @@ -216,11 +216,11 @@ when they are destroyed. To add or remove a window from the client's save-set, use -XChangeSaveSet. +. XChangeSaveSet - + XChangeSaveSet Display *display @@ -270,7 +270,7 @@ or Depending on the specified mode, -XChangeSaveSet + either inserts or deletes the specified window from the client's save-set. The specified window must have been created by some other client, or a @@ -279,7 +279,7 @@ error results. -XChangeSaveSet + can generate BadMatch, BadValue, @@ -291,11 +291,11 @@ errors. To add a window to the client's save-set, use -XAddToSaveSet. +. XAddToSaveSet - + XAddToSaveSet Display *display @@ -330,7 +330,7 @@ Specifies the window (Wi. The -XAddToSaveSet + function adds the specified window to the client's save-set. The specified window must have been created by some other client, or a @@ -339,7 +339,7 @@ error results. -XAddToSaveSet + can generate BadMatch and @@ -350,11 +350,11 @@ errors. To remove a window from the client's save-set, use -XRemoveFromSaveSet. +. XRemoveFromSaveSet - + XRemoveFromSaveSet Display *display @@ -389,7 +389,7 @@ Specifies the window (Wi. The -XRemoveFromSaveSet + function removes the specified window from the client's save-set. The specified window must have been created by some other client, or a @@ -398,7 +398,7 @@ error results. -XRemoveFromSaveSet + can generate BadMatch and @@ -430,12 +430,12 @@ where M is the minimum number of installed colormaps specified for the screen in the connection setup. The required list is maintained as follows. When a colormap is specified to -XInstallColormap, +, it is added to the head of the list; the list is truncated at the tail, if necessary, to keep its length to at most M. When a colormap is specified to -XUninstallColormap + and it is in the required list, it is removed from the list. A colormap is not added to the required list when it is implicitly installed @@ -447,11 +447,11 @@ required list. To install a colormap, use -XInstallColormap. +. XInstallColormap - + XInstallColormap Display *display @@ -485,16 +485,16 @@ Specifies the colormap. The -XInstallColormap + function installs the specified colormap for its associated screen. All windows associated with this colormap immediately display with true colors. You associated the windows with this colormap when you created them by calling -XCreateWindow, -XCreateSimpleWindow, -XChangeWindowAttributes, +, +, +, or -XSetWindowColormap. +. @@ -504,14 +504,14 @@ the X server generates a event on each window that has that colormap. In addition, for every other colormap that is installed as a result of a call to -XInstallColormap, +, the X server generates a ColormapNotify event on each window that has that colormap. -XInstallColormap + can generate a BadColor error. @@ -520,11 +520,11 @@ error. To uninstall a colormap, use -XUninstallColormap. +. XUninstallColormap - + XUninstallColormap Display *display @@ -558,7 +558,7 @@ Specifies the colormap. The -XUninstallColormap + function removes the specified colormap from the required list for its screen. As a result, @@ -575,14 +575,14 @@ the X server generates a event on each window that has that colormap. In addition, for every other colormap that is installed or uninstalled as a result of a call to -XUninstallColormap, +, the X server generates a ColormapNotify event on each window that has that colormap. -XUninstallColormap + can generate a BadColor error. @@ -591,11 +591,11 @@ error. To obtain a list of the currently installed colormaps for a given screen, use -XListInstalledColormaps. +. XListInstalledColormaps - + Colormap *XListInstalledColormaps Display *display @@ -641,18 +641,18 @@ Returns the number of currently installed colormaps. The -XListInstalledColormaps + function returns a list of the currently installed colormaps for the screen of the specified window. The order of the colormaps in the list is not significant and is no explicit indication of the required list. When the allocated list is no longer needed, free it by using -XFree. +. -XListInstalledColormaps + can generate a BadWindow error. @@ -673,11 +673,11 @@ search path for a server. To set the font search path, use -XSetFontPath. +. XSetFontPath - + XSetFontPath Display *display @@ -724,7 +724,7 @@ Specifies the number of directories in the path. The -XSetFontPath + function defines the directory search path for font lookup. There is only one search path per X server, not one per client. The encoding and interpretation of the strings are implementation-dependent, @@ -742,7 +742,7 @@ The meaning of an error from this request is implementation-dependent. -XSetFontPath + can generate a BadValue error. @@ -751,11 +751,11 @@ error. To get the current font search path, use -XGetFontPath. +. XGetFontPath - + char **XGetFontPath Display *display @@ -789,25 +789,25 @@ Returns the number of strings in the font path array. The -XGetFontPath + function allocates and returns an array of strings containing the search path. The contents of these strings are implementation-dependent and are not intended to be interpreted by client applications. When it is no longer needed, the data in the font path should be freed by using -XFreeFontPath. +. To free data returned by -XGetFontPath, +, use -XFreeFontPath. +. XFreeFontPath - + XFreeFontPath char **list @@ -830,14 +830,14 @@ Specifies the array of strings you want to free. The -XFreeFontPath + function frees the data allocated by -XGetFontPath. +. - -Grabbing the Server + +Grabbing the Server @@ -857,13 +857,13 @@ Although grabbing the server is highly discouraged, it is sometimes necessary. To grab the server, use -XGrabServer. +. Servergrabbing Grabbingserver XGrabServer - + XGrabServer Display *display @@ -886,7 +886,7 @@ Specifies the connection to the X server. The -XGrabServer + function disables processing of requests and close downs on all other connections than the one this request arrived on. You should not grab the X server any more than is absolutely necessary. @@ -895,11 +895,11 @@ You should not grab the X server any more than is absolutely necessary. To ungrab the server, use -XUngrabServer. +. XUngrabServer - + XUngrabServer Display *display @@ -922,7 +922,7 @@ Specifies the connection to the X server. The -XUngrabServer + function restarts processing of requests and close downs on other connections. You should avoid grabbing the X server as much as possible. @@ -937,11 +937,11 @@ You should avoid grabbing the X server as much as possible. Xlib provides a function to cause the connection to a client to be closed and its resources to be destroyed. To destroy a client, use -XKillClient. +. XKillClient - + XKillClient Display *display @@ -976,7 +976,7 @@ Specifies any resource associated with the client that you want to destroy or The -XKillClient + function forces a close down of the client that created the resource @@ -1003,14 +1003,14 @@ and use the window manager to destroy the zombie windows. -XKillClient + can generate a BadValue error. - -Controlling the Screen Saver + +Controlling the Screen Saver @@ -1024,11 +1024,11 @@ or to obtain the current screen saver values. To set the screen saver mode, use -XSetScreenSaver. +. XSetScreenSaver - + XSetScreenSaver Display *display @@ -1111,7 +1111,7 @@ Other negative values generate a BadValue error. If the timeout value is nonzero, -XSetScreenSaver + enables the screen saver. An interval of 0 disables the random-pattern motion. If no input from devices (keyboard, mouse, and so on) is generated @@ -1134,7 +1134,7 @@ and the screen saver is not activated. The screen saver is deactivated, and all screen states are restored at the next keyboard or pointer input or at the next call to -XForceScreenSaver + with mode ScreenSaverReset. @@ -1150,7 +1150,7 @@ periodically. -XSetScreenSaver + can generate a BadValue error. @@ -1159,11 +1159,11 @@ error. To force the screen saver on or off, use -XForceScreenSaver. +. XForceScreenSaver - + XForceScreenSaver Display *display @@ -1203,20 +1203,20 @@ or If the specified mode is ScreenSaverActive and the screen saver currently is deactivated, -XForceScreenSaver + activates the screen saver even if the screen saver had been disabled with a timeout of zero. If the specified mode is ScreenSaverReset and the screen saver currently is enabled, -XForceScreenSaver + deactivates the screen saver if it was activated, and the activation timer is reset to its initial state (as if device input had been received). -XForceScreenSaver + can generate a BadValue error. @@ -1225,11 +1225,11 @@ error. To activate the screen saver, use -XActivateScreenSaver. +. XActivateScreenSaver - + XActivateScreenSaver Display *display @@ -1253,11 +1253,11 @@ Specifies the connection to the X server. To reset the screen saver, use -XResetScreenSaver. +. XResetScreenSaver - + XResetScreenSaver Display *display @@ -1281,11 +1281,11 @@ Specifies the connection to the X server. To get the current screen saver values, use -XGetScreenSaver. +. XGetScreenSaver - + XGetScreenSaver Display *display @@ -1528,11 +1528,11 @@ specify the length in byte of the type and value strings. To add a single host, use -XAddHost. +. XAddHost - + XAddHost Display *display @@ -1567,7 +1567,7 @@ Specifies the host that is to be (Ho. The -XAddHost + function adds the specified host to the access control list for that display. The server must be on the same host as the client issuing the command, or a BadAccess @@ -1575,7 +1575,7 @@ error results. -XAddHost + can generate BadAccess and @@ -1586,11 +1586,11 @@ errors. To add multiple hosts at one time, use -XAddHosts. +. XAddHosts - + XAddHosts Display *display @@ -1636,7 +1636,7 @@ Specifies the number of hosts. The -XAddHosts + function adds each specified host to the access control list for that display. The server must be on the same host as the client issuing the command, or a BadAccess @@ -1644,7 +1644,7 @@ error results. -XAddHosts + can generate BadAccess and @@ -1655,11 +1655,11 @@ errors. To obtain a host list, use -XListHosts. +. XListHosts - + XHostAddress *XListHosts Display *display @@ -1704,26 +1704,26 @@ Returns the state of the access control. The -XListHosts + function returns the current access control list as well as whether the use of the list at connection setup was enabled or disabled. -XListHosts + allows a program to find out what machines can make connections. It also returns a pointer to a list of host structures that were allocated by the function. When no longer needed, this memory should be freed by calling -XFree. +. To remove a single host, use -XRemoveHost. +. XRemoveHost - + XRemoveHost Display *display @@ -1758,7 +1758,7 @@ Specifies the host that is to be (Ho. The -XRemoveHost + function removes the specified host from the access control list for that display. The server must be on the same host as the client process, or a @@ -1770,7 +1770,7 @@ and this operation cannot be reversed unless you reset the server. -XRemoveHost + can generate BadAccess and @@ -1781,11 +1781,11 @@ errors. To remove multiple hosts at one time, use -XRemoveHosts. +. XRemoveHosts - + XRemoveHosts Display *display @@ -1831,7 +1831,7 @@ Specifies the number of hosts. The -XRemoveHosts + function removes each specified host from the access control list for that display. The X server must be on the same host as the client process, or a @@ -1843,7 +1843,7 @@ and this operation cannot be reversed unless you reset the server. -XRemoveHosts + can generate BadAccess and @@ -1872,11 +1872,11 @@ at connection setup. To change access control, use -XSetAccessControl. +. XSetAccessControl - + XSetAccessControl Display *display @@ -1914,13 +1914,13 @@ or The -XSetAccessControl + function either enables or disables the use of the access control list at each connection setup. -XSetAccessControl + can generate BadAccess and @@ -1931,11 +1931,11 @@ errors. To enable access control, use -XEnableAccessControl. +. XEnableAccessControl - + XEnableAccessControl Display *display @@ -1958,12 +1958,12 @@ Specifies the connection to the X server. The -XEnableAccessControl + function enables the use of the access control list at each connection setup. -XEnableAccessControl + can generate a BadAccess error. @@ -1972,11 +1972,11 @@ error. To disable access control, use -XDisableAccessControl. +. XDisableAccessControl - + XDisableAccessControl Display *display @@ -1999,12 +1999,12 @@ Specifies the connection to the X server. The -XDisableAccessControl + function disables the use of the access control list at each connection setup. -XDisableAccessControl + can generate a BadAccess error. diff --git a/libX11/specs/libX11/CH10.xml b/libX11/specs/libX11/CH10.xml index d3ddd3407..0230549d4 100644 --- a/libX11/specs/libX11/CH10.xml +++ b/libX11/specs/libX11/CH10.xml @@ -1,7 +1,7 @@ - + Events @@ -25,7 +25,7 @@ This chapter discusses the following topics associated with events: Functions for handling events are dealt with in -the next chapter. +the next chapter. @@ -341,9 +341,9 @@ Unless the client suppresses them by setting graphics-exposures in the GC to and NoExpose are reported by default as a result of -XCopyPlane + and -XCopyArea. +. SelectionClear, SelectionRequest, SelectionNotify, @@ -887,7 +887,7 @@ If no matching passive grab on the button exists, the X server automatically starts an active grab for the client receiving the event and sets the last-pointer-grab time to the current server time. The effect is essentially equivalent to an -XGrabButton + with these client passed arguments: @@ -943,9 +943,9 @@ with these client passed arguments: The active grab is automatically terminated when the logical state of the pointer has all buttons released. Clients can modify the active grab by calling -XUngrabPointer + and -XChangeActivePointerGrab. +. @@ -972,7 +972,7 @@ and the pointer events and MotionNotify. For information about the keyboard event-handling utilities, -see chapter 11. +see chapter 11. @@ -1092,9 +1092,9 @@ structure set to to the client for the event window, until either the key or button state changes, the pointer leaves the event window, or the client calls -XQueryPointer + or -XGetMotionEvents. +. The server still may send MotionNotify events without is_hint set to @@ -1396,7 +1396,7 @@ follows: - + Window Entry/Exit Events @@ -1452,9 +1452,9 @@ An or LeaveNotify event also can be generated when some client application calls -XGrabPointer + and -XUngrabPointer. +. @@ -1620,7 +1620,7 @@ The detail member is set to indicate the notify detail and can be or NotifyNonlinearVirtual. - + Normal Entry/Exit Events @@ -1827,7 +1827,7 @@ structure set to - + Grab and Ungrab Entry/Exit Events @@ -1854,7 +1854,7 @@ or structures whose mode member is set to NotifyUngrab (see -XGrabPointer). +). @@ -1875,7 +1875,7 @@ It generates EnterNotify and LeaveNotify -events (see section 10.6.1) +events (see section 10.6.1) with the mode members of the XEnterWindowEvent and @@ -1907,7 +1907,7 @@ It generates EnterNotify and LeaveNotify -events (see section 10.6.1) +events (see section 10.6.1) with the mode members of the XEnterWindowEvent and @@ -2044,8 +2044,8 @@ the detail member is set to indicate the notify detail and can be or NotifyDetailNone. - -Normal Focus Events and Focus Events While Grabbed + +Normal Focus Events and Focus Events While Grabbed @@ -2560,7 +2560,7 @@ or structures whose mode member is set to NotifyUngrab (see -XGrabKeyboard). +). @@ -2814,9 +2814,9 @@ The X server can report GraphicsExpose events to clients wanting information about when a destination region could not be computed during certain graphics requests: -XCopyArea + or -XCopyPlane. +. The X server generates this event whenever a destination region could not be computed because of an obscured or out-of-bounds source region. In addition, the X server guarantees to report contiguously all of the regions exposed by @@ -2850,9 +2850,9 @@ attribute of the graphics context to True. You also can set the graphics-expose attribute when creating a graphics context using -XCreateGC + or by calling -XSetGraphicsExposures. +. @@ -2910,12 +2910,12 @@ or If it is X_CopyArea, a call to -XCopyArea + initiated the request. If it is X_CopyPlane, a call to -XCopyPlane + initiated the request. These constants are defined in <X11/Xproto.h>. @@ -2950,8 +2950,8 @@ events (and possibly more) are to follow for this window. - -Window State Change Events + +Window State Change Events @@ -3037,10 +3037,10 @@ events to clients wanting information about when a window changes its position in the stack. The X server generates this event type whenever a window is actually restacked as a result of a client application calling -XCirculateSubwindows, -XCirculateSubwindowsUp, +, +, or -XCirculateSubwindowsDown. +. @@ -3120,47 +3120,47 @@ window requests made by a client application actually completes: A window's size, position, border, and/or stacking order is reconfigured by calling -XConfigureWindow. +. The window's position in the stacking order is changed by calling -XLowerWindow, -XRaiseWindow, +, +, or -XRestackWindows. +. A window is moved by calling -XMoveWindow. +. A window's size is changed by calling -XResizeWindow. +. A window's size and location is changed by calling -XMoveResizeWindow. +. A window is mapped and its position in the stacking order is changed by calling -XMapRaised. +. A window's border width is changed by calling -XSetWindowBorderWidth. +. @@ -3256,9 +3256,9 @@ The X server can report events to clients wanting information about creation of windows. The X server generates this event whenever a client application creates a window by calling -XCreateWindow + or -XCreateSimpleWindow. +. @@ -3326,9 +3326,9 @@ The X server can report events to clients wanting information about which windows are destroyed. The X server generates this event whenever a client application destroys a window by calling -XDestroyWindow + or -XDestroySubwindows. +. @@ -3400,10 +3400,10 @@ events to clients wanting information about when a window is moved because of a change in the size of its parent. The X server generates this event whenever a client application actually moves a child window as a result of resizing its parent by calling -XConfigureWindow, -XMoveResizeWindow, +, +, or -XResizeWindow. +. @@ -3469,10 +3469,10 @@ The X server can report events to clients wanting information about which windows are mapped. The X server generates this event type whenever a client application changes the window's state from unmapped to mapped by calling -XMapWindow, -XMapRaised, -XMapSubwindows, -XReparentWindow, +, +, +, +, or as a result of save-set processing. @@ -3546,19 +3546,19 @@ successfully calls: -XSetModifierMapping + to indicate which KeyCodes are to be used as modifiers -XChangeKeyboardMapping + to change the keyboard mapping -XSetPointerMapping + to set the pointer mapping @@ -3616,7 +3616,7 @@ and count represents the number of keycodes altered. To update the client application's knowledge of the keyboard, you should call -XRefreshKeyboardMapping. +. @@ -3633,7 +3633,7 @@ The X server can report events to clients wanting information about changing a window's parent. The X server generates this event whenever a client application calls -XReparentWindow + and the window is actually reparented. @@ -3936,10 +3936,10 @@ on a specified window. The X server generates this event type whenever a client initiates a circulate window request on a window and a subwindow actually needs to be restacked. The client initiates a circulate window request on the window by calling -XCirculateSubwindows, -XCirculateSubwindowsUp, +, +, or -XCirculateSubwindowsDown. +. @@ -3952,7 +3952,7 @@ Then, in the future, the circulate window request for the specified window is not executed, and thus, any subwindow's position in the stack is not changed. For example, suppose a client application calls -XCirculateSubwindowsUp + to raise a subwindow to the top of the stack. If you had selected SubstructureRedirectMask @@ -4017,16 +4017,16 @@ The configure window request attempts to reconfigure a window's size, position, border, and stacking order. The X server generates this event whenever a different client initiates a configure window request on a window by calling -XConfigureWindow, -XLowerWindow, -XRaiseWindow, -XMapRaised, -XMoveResizeWindow, -XMoveWindow, -XResizeWindow, -XRestackWindows, +, +, +, +, +, +, +, +, or -XSetWindowBorderWidth. +. @@ -4040,7 +4040,7 @@ events are generated when a ConfigureWindow protocol request is issued on a child window by another client. For example, suppose a client application calls -XLowerWindow + to lower a window. If you had selected SubstructureRedirectMask @@ -4116,10 +4116,10 @@ a map window request on an unmapped window whose override_redirect member is set to False. Clients initiate map window requests by calling -XMapWindow, -XMapRaised, +, +, or -XMapSubwindows. +. @@ -4133,7 +4133,7 @@ the map window request functions is intercepted, and you are sent a MapRequest instead. For example, suppose a client application calls -XMapWindow + to map a window. If you (usually a window manager) had selected SubstructureRedirectMask @@ -4190,10 +4190,10 @@ events to clients wanting information about another client's attempts to change size of a window. The X server generates this event whenever some other client attempts to change the size of the specified window by calling -XConfigureWindow, -XResizeWindow, +, +, or -XMoveResizeWindow. +. @@ -4257,18 +4257,18 @@ Changes the colormap member of the XSetWindowAttributes structure by calling -XChangeWindowAttributes, -XFreeColormap, +, +, or -XSetWindowColormap + Installs or uninstalls the colormap by calling -XInstallColormap + or -XUninstallColormap + @@ -4311,7 +4311,7 @@ colormap is changed, installed, or uninstalled. For a colormap that is changed, installed, or uninstalled, the colormap member is set to the colormap associated with the window. For a colormap that is changed by a call to -XFreeColormap, +, the colormap member is set to None. The new member is set to indicate whether the colormap @@ -4386,7 +4386,7 @@ events The X server generates ClientMessage events only when a client calls the function -XSendEvent. +. @@ -4491,22 +4491,22 @@ or The state member is set to PropertyNewValue when a property of the window is changed using -XChangeProperty + or -XRotateWindowProperties + (even when adding zero-length data using -XChangeProperty) +) and when replacing all or part of a property with identical data using -XChangeProperty + or -XRotateWindowProperties. +. The state member is set to PropertyDelete when a property of the window is deleted using -XDeleteProperty + or, if the delete argument is True, -XGetWindowProperty. +. @@ -4523,7 +4523,7 @@ The X server reports events to the client losing ownership of a selection. The X server generates this event type when another client asserts ownership of the selection by calling -XSetSelectionOwner. +. @@ -4555,7 +4555,7 @@ The time member is set to the last change time recorded for the selection. The window member is the window that was specified by the current owner (the owner losing the selection) in its -XSetSelectionOwner + call. @@ -4573,7 +4573,7 @@ The X server reports events to the owner of a selection. The X server generates this event whenever a client requests a selection conversion by calling -XConvertSelection + for the owned selection. @@ -4606,7 +4606,7 @@ typedef struct { The owner member is set to the window that was specified by the current owner in its -XSetSelectionOwner + call. The requestor member is set to the window requesting the selection. The selection member is set to the atom that names the selection. @@ -4645,7 +4645,7 @@ This event is generated by the X server in response to a protocol request when there is no owner for the selection. When there is an owner, it should be generated by the owner of the selection by using -XSendEvent. +. The owner of a selection should send this event to a requestor when a selection has been converted and stored as a property or when a selection conversion could diff --git a/libX11/specs/libX11/CH11.xml b/libX11/specs/libX11/CH11.xml index f203f6f10..9795c3220 100644 --- a/libX11/specs/libX11/CH11.xml +++ b/libX11/specs/libX11/CH11.xml @@ -1,7 +1,7 @@ - + Event Handling Functions @@ -38,15 +38,15 @@ application. One way is to set the event_mask member of the XSetWindowAttributes structure when you call -XCreateWindow + and -XChangeWindowAttributes. +. Another way is to use -XSelectInput. +. XSelectInput - + XSelectInput Display *display @@ -92,7 +92,7 @@ Specifies the event mask. The -XSelectInput + function requests that the X server report the events associated with the specified event mask. Initially, X will not report any of these events. @@ -156,7 +156,7 @@ The server reports the event to all interested clients. -XSelectInput + can generate a BadWindow error. @@ -180,11 +180,11 @@ These functions differ in the additional tasks they might perform. To flush the output buffer, use -XFlush. +. XFlush - + XFlush Display *display @@ -207,15 +207,15 @@ Specifies the connection to the X server. The -XFlush + function flushes the output buffer. Most client applications need not use this function because the output buffer is automatically flushed as needed by calls to -XPending, -XNextEvent, +, +, and -XWindowEvent. +. XPending XNextEvent XWindowEvent @@ -226,11 +226,11 @@ Events generated by the server may be enqueued into the library's event queue. To flush the output buffer and then wait until all requests have been processed, use -XSync. +. XSync - + XSync Display *display @@ -256,7 +256,7 @@ Specifies the connection to the X server. Specifies a Boolean value that indicates whether -XSync + discards all events on the event queue. @@ -266,13 +266,13 @@ discards all events on the event queue. The -XSync + function flushes the output buffer and then waits until all requests have been received and processed by the X server. Any errors generated must be handled by the error handler. For each protocol error received by Xlib, -XSync + calls the client application's error handling routine (see section 11.8.2). Any events generated by the server are enqueued into the library's @@ -282,17 +282,17 @@ event queue. Finally, if you passed False, -XSync + does not discard the events in the queue. If you passed True, -XSync + discards all events in the queue, including those events that were on the queue before -XSync + was called. Client applications seldom need to call -XSync. +. @@ -310,11 +310,11 @@ in its network connection that is not yet read into the event queue. To check the number of events in the event queue, use -XEventsQueued. +. XEventsQueued - + int XEventsQueued Display *display @@ -354,53 +354,53 @@ or If mode is QueuedAlready, -XEventsQueued + returns the number of events already in the event queue (and never performs a system call). If mode is QueuedAfterFlush, -XEventsQueued + returns the number of events already in the queue if the number is nonzero. If there are no events in the queue, -XEventsQueued + flushes the output buffer, attempts to read more events out of the application's connection, and returns the number read. If mode is QueuedAfterReading, -XEventsQueued + returns the number of events already in the queue if the number is nonzero. If there are no events in the queue, -XEventsQueued + attempts to read more events out of the application's connection without flushing the output buffer and returns the number read. -XEventsQueued + always returns immediately without I/O if there are events already in the queue. -XEventsQueued + with mode QueuedAfterFlush is identical in behavior to -XPending. -XEventsQueued +. + with mode QueuedAlready is identical to the -XQLength + function. To return the number of events that are pending, use -XPending. +. XPending - + int XPending Display *display @@ -423,12 +423,12 @@ Specifies the connection to the X server. The -XPending + function returns the number of events that have been received from the X server but have not been removed from the event queue. -XPending + is identical to -XEventsQueued + with the mode QueuedAfterFlush specified. @@ -470,11 +470,11 @@ predicate procedures that you provide To get the next event and remove it from the queue, use -XNextEvent. +. XNextEvent - + XNextEvent Display *display @@ -508,23 +508,23 @@ Returns the next event in the queue. The -XNextEvent + function copies the first event from the event queue into the specified XEvent structure and then removes it from the queue. If the event queue is empty, -XNextEvent + flushes the output buffer and blocks until an event is received. To peek at the event queue, use -XPeekEvent. +. XPeekEvent - + XPeekEvent Display *display @@ -558,11 +558,11 @@ Returns a copy of the matched event's associated structure. The -XPeekEvent + function returns the first event from the event queue, but it does not remove the event from the queue. If the queue is empty, -XPeekEvent + flushes the output buffer and blocks until an event is received. It then copies the event into the client-supplied XEvent @@ -633,10 +633,10 @@ structure. Specifies the argument passed in from the -XIfEvent, -XCheckIfEvent, +, +, or -XPeekIfEvent + function. @@ -657,11 +657,11 @@ If it did not find a match, it must return To check the event queue for a matching event and, if found, remove the event from the queue, use -XIfEvent. +. XIfEvent - + XIfEvent Display *display @@ -718,15 +718,15 @@ Specifies the user-supplied argument that will be passed to the predicate proced The -XIfEvent + function completes only when the specified predicate procedure returns True for an event, which indicates an event in the queue matches. -XIfEvent + flushes the output buffer if it blocks waiting for additional events. -XIfEvent + removes the matching event from the queue and copies the structure into the client-supplied XEvent @@ -736,11 +736,11 @@ structure. To check the event queue for a matching event without blocking, use -XCheckIfEvent. +. XCheckIfEvent - + Bool XCheckIfEvent Display *display @@ -797,14 +797,14 @@ Specifies the user-supplied argument that will be passed to the predicate proced When the predicate procedure finds a match, -XCheckIfEvent + copies the matched event into the client-supplied XEvent structure and returns True. (This event is removed from the queue.) If the predicate procedure finds no match, -XCheckIfEvent + returns False, and the output buffer will have been flushed. @@ -815,11 +815,11 @@ All earlier events stored in the queue are not discarded. To check the event queue for a matching event without removing the event from the queue, use -XPeekIfEvent. +. XPeekIfEvent - + XPeekIfEvent Display *display @@ -876,17 +876,17 @@ Specifies the user-supplied argument that will be passed to the predicate proced The -XPeekIfEvent + function returns only when the specified predicate procedure returns True for an event. After the predicate procedure finds a match, -XPeekIfEvent + copies the matched event into the client-supplied XEvent structure without removing the event from the queue. -XPeekIfEvent + flushes the output buffer if it blocks waiting for additional events. @@ -904,11 +904,11 @@ or event types, allowing you to process events out of order. To remove the next event that matches both a window and an event mask, use -XWindowEvent. +. XWindowEvent - + XWindowEvent Display *display @@ -965,17 +965,17 @@ Returns the matched event's associated structure. The -XWindowEvent + function searches the event queue for an event that matches both the specified window and event mask. When it finds a match, -XWindowEvent + removes that event from the queue and copies it into the specified XEvent structure. The other events stored in the queue are not discarded. If a matching event is not in the queue, -XWindowEvent + flushes the output buffer and blocks until one is received. @@ -983,17 +983,17 @@ flushes the output buffer and blocks until one is received. To remove the next event that matches both a window and an event mask (if any), use -XCheckWindowEvent. +. XCheckWindowEvent This function is similar to -XWindowEvent + except that it never blocks and it returns a Bool indicating if the event was returned. XCheckWindowEvent - + Bool XCheckWindowEvent Display *display @@ -1050,19 +1050,19 @@ Returns the matched event's associated structure. The -XCheckWindowEvent + function searches the event queue and then the events available on the server connection for the first event that matches the specified window and event mask. If it finds a match, -XCheckWindowEvent + removes that event, copies it into the specified XEvent structure, and returns True. The other events stored in the queue are not discarded. If the event you requested is not available, -XCheckWindowEvent + returns False, and the output buffer will have been flushed. @@ -1071,11 +1071,11 @@ and the output buffer will have been flushed. To remove the next event that matches an event mask, use -XMaskEvent. +. XMaskEvent - + XMaskEvent Display *display @@ -1120,33 +1120,33 @@ Returns the matched event's associated structure. The -XMaskEvent + function searches the event queue for the events associated with the specified mask. When it finds a match, -XMaskEvent + removes that event and copies it into the specified XEvent structure. The other events stored in the queue are not discarded. If the event you requested is not in the queue, -XMaskEvent + flushes the output buffer and blocks until one is received. To return and remove the next event that matches an event mask (if any), use -XCheckMaskEvent. +. This function is similar to -XMaskEvent + except that it never blocks and it returns a Bool indicating if the event was returned. XCheckMaskEvent - + Bool XCheckMaskEvent Display *display @@ -1191,18 +1191,18 @@ Returns the matched event's associated structure. The -XCheckMaskEvent + function searches the event queue and then any events available on the server connection for the first event that matches the specified mask. If it finds a match, -XCheckMaskEvent + removes that event, copies it into the specified XEvent structure, and returns True. The other events stored in the queue are not discarded. If the event you requested is not available, -XCheckMaskEvent + returns False, and the output buffer will have been flushed. @@ -1211,11 +1211,11 @@ and the output buffer will have been flushed. To return and remove the next event in the queue that matches an event type, use -XCheckTypedEvent. +. XCheckTypedEvent - + Bool XCheckTypedEvent Display *display @@ -1261,18 +1261,18 @@ Returns the matched event's associated structure. The -XCheckTypedEvent + function searches the event queue and then any events available on the server connection for the first event that matches the specified type. If it finds a match, -XCheckTypedEvent + removes that event, copies it into the specified XEvent structure, and returns True. The other events in the queue are not discarded. If the event is not available, -XCheckTypedEvent + returns False, and the output buffer will have been flushed. @@ -1282,11 +1282,11 @@ and the output buffer will have been flushed. To return and remove the next event in the queue that matches an event type and a window, use -XCheckTypedWindowEvent. +. XCheckTypedWindowEvent - + Bool XCheckTypedWindowEvent Display *display @@ -1343,19 +1343,19 @@ Returns the matched event's associated structure. The -XCheckTypedWindowEvent + function searches the event queue and then any events available on the server connection for the first event that matches the specified type and window. If it finds a match, -XCheckTypedWindowEvent + removes the event from the queue, copies it into the specified XEvent structure, and returns True. The other events in the queue are not discarded. If the event is not available, -XCheckTypedWindowEvent + returns False, and the output buffer will have been flushed. @@ -1370,11 +1370,11 @@ and the output buffer will have been flushed. To push an event back into the event queue, use -XPutBackEvent. +. XPutBackEvent - + XPutBackEvent Display *display @@ -1408,13 +1408,13 @@ Specifies the event. The -XPutBackEvent + function pushes an event back onto the head of the display's event queue by copying the event into the queue. This can be useful if you read an event and then decide that you would rather deal with it later. There is no limit to the number of times in succession that you can call -XPutBackEvent. +. @@ -1425,11 +1425,11 @@ There is no limit to the number of times in succession that you can call To send an event to a specified window, use -XSendEvent. +. XSendEvent This function is often used in selection processing. For example, the owner of a selection should use -XSendEvent + to send a SelectionNotify event to a requestor when a selection has been converted @@ -1437,7 +1437,7 @@ and stored as a property. XSendEvent - + Status XSendEvent Display *display @@ -1507,7 +1507,7 @@ Specifies the event that is to be sent. The -XSendEvent + function identifies the destination window, determines which clients should receive the specified events, and ignores any active grabs. @@ -1537,7 +1537,7 @@ otherwise, the destination window is the focus window. To determine which clients should receive the specified events, -XSendEvent + uses the propagate argument as follows: @@ -1591,17 +1591,17 @@ otherwise unaltered and unchecked by the X server except to force send_event to in the forwarded event and to set the serial number in the event correctly; therefore these fields and the display field are ignored by -XSendEvent. +. -XSendEvent + returns zero if the conversion to wire protocol format failed and returns nonzero otherwise. -XSendEvent + can generate BadValue and @@ -1635,7 +1635,7 @@ use XDisplayMotionBufferSize - + unsigned long Display *display @@ -1662,14 +1662,14 @@ and do so to a finer granularity than is reported by MotionNotify events. The -XGetMotionEvents + function makes this history available. To get the motion history for a specified window and time, use -XGetMotionEvents. +. XGetMotionEvents @@ -1743,7 +1743,7 @@ Returns the number of events from the motion history buffer. The -XGetMotionEvents + function returns all events in the motion history buffer that fall between the specified start and stop times, inclusive, and that have coordinates that lie within the specified window (including its borders) at its present @@ -1752,7 +1752,7 @@ If the server does not support motion history, if the start time is later than the stop time, or if the start time is in the future, no events are returned; -XGetMotionEvents + returns NULL. If the stop time is in the future, it is equivalent to specifying CurrentTime. @@ -1779,11 +1779,11 @@ The x and y members are set to the coordinates of the pointer and are reported relative to the origin of the specified window. To free the data returned from this call, use -XFree. +. -XGetMotionEvents + can generate a BadWindow error. @@ -1824,12 +1824,12 @@ synchronous library behavior. After completing their work, all Xlib functions that generate protocol requests call what is known as an after function. -XSetAfterFunction + sets which function is to be called. XSetAfterFunction - + int Display *display @@ -1863,7 +1863,7 @@ Specifies the procedure to be called. The specified procedure is called with only a display pointer. -XSetAfterFunction + returns the previous after function. @@ -1946,11 +1946,11 @@ message and exit. To set the error handler, use -XSetErrorHandler. +. XSetErrorHandler - + int *XSetErrorHandler int *handler @@ -2213,12 +2213,12 @@ fixed alternatives. To obtain textual descriptions of the specified error code, use -XGetErrorText. +. XGetErrorText Debuggingerror message strings - + XGetErrorText Display *display @@ -2274,7 +2274,7 @@ Specifies the size of the buffer. The -XGetErrorText + function copies a null-terminated string describing the specified error code into the specified buffer. The returned text is in the encoding of the current locale. @@ -2286,11 +2286,11 @@ and error strings. To obtain error messages from the error database, use -XGetErrorDatabaseText. +. XGetErrorDatabaseText - + XGetErrorDatabaseText Display *display @@ -2367,7 +2367,7 @@ Specifies the size of the buffer. The -XGetErrorDatabaseText + function returns a null-terminated message (or the default message) from the error message database. @@ -2431,11 +2431,11 @@ the default_string is returned to the buffer argument. To report an error to the user when the requested display does not exist, use -XDisplayName. +. XDisplayName - + char *XDisplayName char *string @@ -2458,14 +2458,14 @@ Specifies the character string. The -XDisplayName + function returns the name of the display that -XOpenDisplay + would attempt to use. If a NULL string is specified, -XDisplayName + looks in the environment for the display and returns the display name that -XOpenDisplay + would attempt to use. This makes it easier to report to the user precisely which display the program attempted to open when the initial connection attempt failed. diff --git a/libX11/specs/libX11/CH12.xml b/libX11/specs/libX11/CH12.xml index 8334e9eb9..e65bebc0c 100644 --- a/libX11/specs/libX11/CH12.xml +++ b/libX11/specs/libX11/CH12.xml @@ -1,7 +1,7 @@ - + Input Device Functions @@ -18,8 +18,8 @@ You can use the Xlib input device functions to: Manipulate the keyboard encoding - -Pointer Grabbing + +Pointer Grabbing @@ -47,7 +47,7 @@ further mouse and keyboard events will continue to be processed. If the keyboard or pointer is in synchronous mode, no further events are processed until the grabbing client allows them (see -XAllowEvents). +). The keyboard or pointer is considered frozen during this interval. The event that triggered the grab can also be replayed. @@ -64,9 +64,9 @@ There are two kinds of grabs: active and passive. An active grab occurs when a single client grabs the keyboard and/or pointer explicitly (see -XGrabPointer + and -XGrabKeyboard). +). Passive grab A passive grab occurs when clients grab a particular keyboard key or pointer button in a window, @@ -154,13 +154,13 @@ and To grab the pointer, use -XGrabPointer. +. Grabbingpointer Pointergrabbing XGrabPointer - + int XGrabPointer Display *display @@ -285,12 +285,12 @@ You can pass either a timestamp or The -XGrabPointer + function actively grabs control of the pointer and returns GrabSuccess if the grab was successful. Further pointer events are reported only to the grabbing client. -XGrabPointer + overrides any active pointer grab by this client. If owner_events is False, @@ -319,7 +319,7 @@ the state of the pointer, as seen by client applications, appears to freeze, and the X server generates no further pointer events until the grabbing client calls -XAllowEvents + or until the pointer grab is released. Actual pointer changes are not lost while the pointer is frozen; they are simply queued in the server for later processing. @@ -335,7 +335,7 @@ the state of the keyboard, as seen by client applications, appears to freeze, and the X server generates no further keyboard events until the grabbing client calls -XAllowEvents + or until the pointer grab is released. Actual keyboard changes are not lost while the pointer is frozen; they are simply queued in the server for later processing. @@ -378,7 +378,7 @@ grabbed the pointer before its request was processed. -XGrabPointer + generates EnterNotify and @@ -390,7 +390,7 @@ events. Either if grab_window or confine_to window is not viewable or if the confine_to window lies completely outside the boundaries of the root window, -XGrabPointer + fails and returns GrabNotViewable. If the pointer is actively grabbed by some other client, @@ -408,7 +408,7 @@ is replaced by the current X server time). -XGrabPointer + can generate BadCursor, BadValue, @@ -420,13 +420,13 @@ errors. To ungrab the pointer, use -XUngrabPointer. +. Ungrabbingpointer Pointerungrabbing XUngrabPointer - + XUngrabPointer Display *display @@ -462,13 +462,13 @@ You can pass either a timestamp or The -XUngrabPointer + function releases the pointer and any queued events if this client has actively grabbed the pointer from -XGrabPointer, -XGrabButton, +, +, or from a normal button press. -XUngrabPointer + does not release the pointer if the specified time is earlier than the last-pointer-grab time or is later than the current X server time. @@ -488,13 +488,13 @@ outside the boundaries of the root window. To change an active pointer grab, use -XChangeActivePointerGrab. +. Pointergrabbing Changingpointer grab XChangeActivePointerGrab - + XChangeActivePointerGrab Display *display @@ -554,18 +554,18 @@ You can pass either a timestamp or The -XChangeActivePointerGrab + function changes the specified dynamic parameters if the pointer is actively grabbed by the client and if the specified time is no earlier than the last-pointer-grab time and no later than the current X server time. This function has no effect on the passive parameters of an -XGrabButton. +. The interpretation of event_mask and cursor is the same as described in -XGrabPointer. +. -XChangeActivePointerGrab + can generate BadCursor and @@ -576,13 +576,13 @@ errors. To grab a pointer button, use -XGrabButton. +. Grabbingbuttons Buttongrabbing XGrabButton - + XGrabButton Display *display @@ -720,11 +720,11 @@ Specifies the cursor that is to be displayed or The -XGrabButton + function establishes a passive grab. In the future, the pointer is actively grabbed (as for -XGrabPointer), +), the last-pointer-grab time is set to the time at which the button was pressed (as transmitted in the ButtonPress @@ -760,7 +760,7 @@ on any ancestor of grab_window. The interpretation of the remaining arguments is as for -XGrabPointer. +. The active grab is terminated automatically when the logical state of the pointer has all buttons released (independent of the state of the logical modifier keys). @@ -790,7 +790,7 @@ to a physical button. If some other client has already issued an -XGrabButton + with the same button/key combination on the same window, a BadAccess error results. @@ -803,12 +803,12 @@ and a BadAccess error results (no grabs are established) if there is a conflicting grab for any combination. -XGrabButton + has no effect on an active grab. -XGrabButton + can generate BadCursor, BadValue, @@ -820,13 +820,13 @@ errors. To ungrab a pointer button, use -XUngrabButton. +. Ungrabbingbuttons Buttonungrabbing XUngrabButton - + XUngrabButton Display *display @@ -886,7 +886,7 @@ Specifies the grab window. The -XUngrabButton + function releases the passive button/key combination on the specified window if it was grabbed by this client. A modifiers of @@ -899,12 +899,12 @@ A button of AnyButton is equivalent to issuing the request for all possible buttons. -XUngrabButton + has no effect on an active grab. -XUngrabButton + can generate BadValue and @@ -912,8 +912,8 @@ and errors. - -Keyboard Grabbing + +Keyboard Grabbing @@ -941,13 +941,13 @@ and To grab the keyboard, use -XGrabKeyboard. +. Keyboardgrabbing Grabbingkeyboard XGrabKeyboard - + int XGrabKeyboard Display *display @@ -1035,7 +1035,7 @@ You can pass either a timestamp or The -XGrabKeyboard + function actively grabs control of the keyboard and generates FocusIn and @@ -1043,7 +1043,7 @@ and events. Further key events are reported only to the grabbing client. -XGrabKeyboard + overrides any active keyboard grab by this client. If owner_events is False, @@ -1075,7 +1075,7 @@ If the keyboard_mode argument is the state of the keyboard (as seen by client applications) appears to freeze, and the X server generates no further keyboard events until the grabbing client issues a releasing -XAllowEvents + call or until the keyboard grab is released. Actual keyboard changes are not lost while the keyboard is frozen; they are simply queued in the server for later processing. @@ -1091,7 +1091,7 @@ If pointer_mode is the state of the pointer (as seen by client applications) appears to freeze, and the X server generates no further pointer events until the grabbing client issues a releasing -XAllowEvents + call or until the keyboard grab is released. Actual pointer changes are not lost while the pointer is frozen; they are simply queued in the server for later processing. @@ -1099,7 +1099,7 @@ they are simply queued in the server for later processing. If the keyboard is actively grabbed by some other client, -XGrabKeyboard + fails and returns AlreadyGrabbed. If grab_window is not viewable, @@ -1118,7 +1118,7 @@ is replaced by the current X server time). -XGrabKeyboard + can generate BadValue and @@ -1129,13 +1129,13 @@ errors. To ungrab the keyboard, use -XUngrabKeyboard. +. Keyboardungrabbing Ungrabbingkeyboard XUngrabKeyboard - + XUngrabKeyboard Display *display @@ -1171,14 +1171,14 @@ You can pass either a timestamp or The -XUngrabKeyboard + function releases the keyboard and any queued events if this client has it actively grabbed from either -XGrabKeyboard + or -XGrabKey. -XUngrabKeyboard +. + does not release the keyboard and any queued events if the specified time is earlier than the last-keyboard-grab time or is later than the current X server time. @@ -1196,13 +1196,13 @@ active keyboard grab becomes not viewable. To passively grab a single key of the keyboard, use -XGrabKey. +. Keygrabbing Grabbingkeys XGrabKey - + XGrabKey Display *display @@ -1302,11 +1302,11 @@ or The -XGrabKey + function establishes a passive grab on the keyboard. In the future, the keyboard is actively grabbed (as for -XGrabKeyboard), +), the last-keyboard-grab time is set to the time at which the key was pressed (as transmitted in the KeyPress @@ -1339,7 +1339,7 @@ on any ancestor of grab_window. The interpretation of the remaining arguments is as for -XGrabKeyboard. +. The active grab is terminated automatically when the logical state of the keyboard has the specified key released (independent of the logical state of the modifier keys). @@ -1372,7 +1372,7 @@ error results. If some other client has issued a -XGrabKey + with the same key combination on the same window, a BadAccess error results. @@ -1388,7 +1388,7 @@ if there is a conflicting grab for any combination. -XGrabKey + can generate BadAccess, BadValue, @@ -1400,13 +1400,13 @@ errors. To ungrab a key, use -XUngrabKey. +. Keyungrabbing Ungrabbingkeys XUngrabKey - + XUngrabKey Display *display @@ -1465,7 +1465,7 @@ Specifies the grab window. The -XUngrabKey + function releases the key combination on the specified window if it was grabbed by this client. It has no effect on an active grab. @@ -1480,7 +1480,7 @@ is equivalent to issuing the request for all possible key codes. -XUngrabKey + can generate BadValue and @@ -1503,11 +1503,11 @@ describes the mechanism for resuming event processing. To allow further events to be processed when the device has been frozen, use -XAllowEvents. +. XAllowEvents - + XAllowEvents Display *display @@ -1564,7 +1564,7 @@ You can pass either a timestamp or The -XAllowEvents + function releases some queued events if the client has caused a device to freeze. It has no effect if the specified time is earlier than the last-grab @@ -1608,13 +1608,13 @@ Depending on the event_mode argument, the following occurs: ReplayPointer If the pointer is actively grabbed by the client and is frozen as the result of an event having been sent to the client (either from the activation of an - XGrabButton + or from a previous - XAllowEvents + with mode SyncPointer but not from an - XGrabPointer), + ), the pointer grab is released and that event is completely reprocessed. This time, however, the function ignores any passive grabs at or above (toward the root of) the grab_window of the grab just released. @@ -1653,13 +1653,13 @@ Depending on the event_mode argument, the following occurs: If the keyboard is actively grabbed by the client and is frozen as the result of an event having been sent to the client (either from the activation of an - XGrabKey + or from a previous - XAllowEvents + with mode SyncKeyboard but not from an - XGrabKeyboard), + ), the keyboard grab is released and that event is completely reprocessed. This time, however, the function ignores any passive grabs at or above (toward the root of) @@ -1732,12 +1732,12 @@ the freeze must be released on behalf of both grabs before events can again be processed. If a device is frozen twice by a single client, then a single -XAllowEvents + releases both. -XAllowEvents + can generate a BadValue error. @@ -1758,11 +1758,11 @@ pointer to a new position under program control. To move the pointer to an arbitrary point in a window, use -XWarpPointer. +. XWarpPointer - + XWarpPointer Display *display @@ -1876,11 +1876,11 @@ Specify the x and y coordinates within the destination window. If dest_w is None, -XWarpPointer + moves the pointer by the offsets (dest_x, dest_y) relative to the current position of the pointer. If dest_w is a window, -XWarpPointer + moves the pointer to the offsets (dest_x, dest_y) relative to the origin of dest_w. However, if src_w is a window, @@ -1902,14 +1902,14 @@ The pointer should normally be left to the user. If you do use this function, however, it generates events just as if the user had instantaneously moved the pointer from one position to another. Note that you cannot use -XWarpPointer + to move the pointer outside the confine_to window of an active pointer grab. An attempt to do so will only move the pointer as far as the closest edge of the confine_to window. -XWarpPointer + can generate a BadWindow error. @@ -1932,11 +1932,11 @@ for input focus policy. To set the input focus, use -XSetInputFocus. +. XSetInputFocus - + XSetInputFocus Display *display @@ -2003,14 +2003,14 @@ You can pass either a timestamp or The -XSetInputFocus + function changes the input focus and the last-focus-change time. It has no effect if the specified time is earlier than the current last-focus-change time or is later than the current X server time. Otherwise, the last-focus-change time is set to the specified time (CurrentTime is replaced by the current X server time). -XSetInputFocus + causes the X server to generate FocusIn and @@ -2053,7 +2053,7 @@ In this case, the revert_to argument is ignored. The specified focus window must be viewable at the time -XSetInputFocus + is called, or a BadMatch @@ -2094,7 +2094,7 @@ events, but the last-focus-change time is not affected. -XSetInputFocus + can generate BadMatch, BadValue, @@ -2106,11 +2106,11 @@ errors. To obtain the current input focus, use -XGetInputFocus. +. XGetInputFocus - + XGetInputFocus Display *display @@ -2162,7 +2162,7 @@ or The -XGetInputFocus + function returns the focus window and the current focus state. @@ -2195,7 +2195,7 @@ parameters. The -XChangeKeyboardControl + function changes control of a keyboard and operates on a XKeyboardControl structure: @@ -2325,7 +2325,7 @@ If an error is generated, a subset of the controls may have been altered. XChangeKeyboardControl - + XChangeKeyboardControl Display *display @@ -2371,7 +2371,7 @@ Specifies one value for each bit set to 1 in the mask. The -XChangeKeyboardControl + function controls the keyboard characteristics defined by the XKeyboardControl structure. @@ -2379,7 +2379,7 @@ The value_mask argument specifies which values are to be changed. -XChangeKeyboardControl + can generate BadMatch and @@ -2390,11 +2390,11 @@ errors. To obtain the current control values for the keyboard, use -XGetKeyboardControl. +. XGetKeyboardControl - + XGetKeyboardControl Display *display @@ -2430,7 +2430,7 @@ structure. The -XGetKeyboardControl + function returns the current control values for the keyboard to the XKeyboardState structure. @@ -2474,11 +2474,11 @@ with the least significant bit in the byte representing key 8N. To turn on keyboard auto-repeat, use -XAutoRepeatOn. +. XAutoRepeatOn - + XAutoRepeatOn Display *display @@ -2501,18 +2501,18 @@ Specifies the connection to the X server. The -XAutoRepeatOn + function turns on auto-repeat for the keyboard on the specified display. To turn off keyboard auto-repeat, use -XAutoRepeatOff. +. XAutoRepeatOff - + XAutoRepeatOff Display *display @@ -2535,18 +2535,18 @@ Specifies the connection to the X server. The -XAutoRepeatOff + function turns off auto-repeat for the keyboard on the specified display. To ring the bell, use -XBell. +. XBell - + XBell Display *display @@ -2581,7 +2581,7 @@ which can range from -100 to 100 inclusive. The -XBell + function rings the bell on the keyboard on the specified display, if possible. The specified volume is relative to the base volume for the keyboard. If the value for the percent argument is not in the range -100 to 100 @@ -2613,11 +2613,11 @@ base + [(base * percent) / 100] To change the base volume of the bell, use -XChangeKeyboardControl. +. -XBell + can generate a BadValue error. @@ -2626,11 +2626,11 @@ error. To obtain a bit vector that describes the state of the keyboard, use -XQueryKeymap. +. XQueryKeymap - + XQueryKeymap Display *display @@ -2665,7 +2665,7 @@ Each bit represents one key of the keyboard. The -XQueryKeymap + function returns a bit vector for the logical state of the keyboard, where each bit set to 1 indicates that the corresponding key is currently pressed down. @@ -2682,11 +2682,11 @@ may lag the physical state if device event processing is frozen. To set the mapping of the pointer buttons, use -XSetPointerMapping. +. XSetPointerMapping - + int XSetPointerMapping Display *display @@ -2731,18 +2731,18 @@ Specifies the number of items in the mapping list. The -XSetPointerMapping + function sets the mapping of the pointer. If it succeeds, the X server generates a MappingNotify event, and -XSetPointerMapping + returns MappingSuccess. Element map[i] defines the logical button number for the physical button i+1. The length of the list must be the same as -XGetPointerMapping + would return, or a BadValue @@ -2754,14 +2754,14 @@ or a BadValue error results. If any of the buttons to be altered are logically in the down state, -XSetPointerMapping + returns MappingBusy, and the mapping is not changed. -XSetPointerMapping + can generate a BadValue error. @@ -2770,11 +2770,11 @@ error. To get the pointer mapping, use -XGetPointerMapping. +. XGetPointerMapping - + int XGetPointerMapping Display *display @@ -2819,10 +2819,10 @@ Specifies the number of items in the mapping list. The -XGetPointerMapping + function returns the current mapping of the pointer. Pointer buttons are numbered starting from one. -XGetPointerMapping + returns the number of physical buttons actually on the pointer. The nominal mapping for a pointer is map[i]=i+1. The nmap argument specifies the length of the array where the pointer @@ -2833,11 +2833,11 @@ in map_return. To control the pointer's interactive feel, use -XChangePointerControl. +. XChangePointerControl - + XChangePointerControl Display *display @@ -2915,7 +2915,7 @@ Specifies the acceleration threshold. The -XChangePointerControl + function defines how the pointing device moves. The acceleration, expressed as a fraction, is a multiplier for movement. @@ -2937,7 +2937,7 @@ for the accel_denominator argument. -XChangePointerControl + can generate a BadValue error. @@ -2946,11 +2946,11 @@ error. To get the current pointer parameters, use -XGetPointerControl. +. XGetPointerControl - + XGetPointerControl Display *display @@ -3005,7 +3005,7 @@ Returns the acceleration threshold. The -XGetPointerControl + function returns the pointer's current acceleration multiplier and acceleration threshold. @@ -3221,11 +3221,11 @@ Rather, it merely stores it for reading and writing by clients. To obtain the legal KeyCodes for a display, use -XDisplayKeycodes. +. XDisplayKeycodes - + XDisplayKeycodes Display *display @@ -3269,7 +3269,7 @@ Returns the maximum number of KeyCodes. The -XDisplayKeycodes + function returns the min-keycodes and max-keycodes supported by the specified display. The minimum number of KeyCodes returned is never less than 8, @@ -3280,11 +3280,11 @@ Not all KeyCodes in this range are required to have corresponding keys. To obtain the symbols for the specified KeyCodes, use -XGetKeyboardMapping. +. XGetKeyboardMapping - + KeySym *XGetKeyboardMapping Display *display @@ -3341,18 +3341,18 @@ Returns the number of KeySyms per KeyCode. The -XGetKeyboardMapping + function returns the symbols for the specified number of KeyCodes starting with first_keycode. The value specified in first_keycode must be greater than or equal to min_keycode as returned by -XDisplayKeycodes, +, or a BadValue error results. In addition, the following expression must be less than or equal to max_keycode as returned by -XDisplayKeycodes: +: @@ -3390,13 +3390,13 @@ A special KeySym value of is used to fill in unused elements for individual KeyCodes. To free the storage returned by -XGetKeyboardMapping, +, use -XFree. +. -XGetKeyboardMapping + can generate a BadValue error. @@ -3405,11 +3405,11 @@ error. To change the keyboard mapping, use -XChangeKeyboardMapping. +. XChangeKeyboardMapping - + XChangeKeyboardMapping Display *display @@ -3477,7 +3477,7 @@ Specifies the number of KeyCodes that are to be changed. The -XChangeKeyboardMapping + function defines the symbols for the specified number of KeyCodes starting with first_keycode. The symbols for KeyCodes outside this range remain unchanged. @@ -3493,13 +3493,13 @@ num_codes * keysyms_per_keycode The specified first_keycode must be greater than or equal to min_keycode returned by -XDisplayKeycodes, +, or a BadValue error results. In addition, the following expression must be less than or equal to max_keycode as returned by -XDisplayKeycodes, +, or a BadValue error results: @@ -3533,7 +3533,7 @@ It is legal for NoSymbol to appear in nontrailing positions of the effective list for a KeyCode. -XChangeKeyboardMapping + generates a MappingNotify event. @@ -3545,7 +3545,7 @@ It is merely stored for reading and writing by clients. -XChangeKeyboardMapping + can generate BadAlloc and @@ -3577,11 +3577,11 @@ typedef struct { To create an XModifierKeymap structure, use -XNewModifiermap. +. XNewModifiermap - + XModifierKeymap *XNewModifiermap int max_keys_per_mod @@ -3605,7 +3605,7 @@ in the map. The -XNewModifiermap + function returns a pointer to XModifierKeymap structure for later use. @@ -3616,11 +3616,11 @@ structure for later use. To add a new entry to an XModifierKeymap structure, use -XInsertModifiermapEntry. +. XInsertModifiermapEntry - + XModifierKeymap *XInsertModifiermapEntry XModifierKeymap *modmap @@ -3667,7 +3667,7 @@ Specifies the modifier. The -XInsertModifiermapEntry + function adds the specified KeyCode to the set that controls the specified modifier and returns the resulting XModifierKeymap @@ -3679,11 +3679,11 @@ structure (expanded as needed). To delete an entry from an XModifierKeymap structure, use -XDeleteModifiermapEntry. +. XDeleteModifiermapEntry - + XModifierKeymap *XDeleteModifiermapEntry XModifierKeymap *modmap @@ -3730,7 +3730,7 @@ Specifies the modifier. The -XDeleteModifiermapEntry + function deletes the specified KeyCode from the set that controls the specified modifier and returns a pointer to the resulting XModifierKeymap @@ -3742,11 +3742,11 @@ structure. To destroy an XModifierKeymap structure, use -XFreeModifiermap. +. XFreeModifiermap - + XFreeModifiermap XModifierKeymap *modmap @@ -3771,7 +3771,7 @@ structure. The -XFreeModifiermap + function frees the specified XModifierKeymap structure. @@ -3780,11 +3780,11 @@ structure. To set the KeyCodes to be used as modifiers, use -XSetModifierMapping. +. XSetModifierMapping - + int XSetModifierMapping Display *display @@ -3820,14 +3820,14 @@ structure. The -XSetModifierMapping + function specifies the KeyCodes of the keys (if any) that are to be used as modifiers. If it succeeds, the X server generates a MappingNotify event, and -XSetModifierMapping + returns MappingSuccess. X permits at most 8 modifier keys. @@ -3876,14 +3876,14 @@ and none of the modifiers are changed. If the new KeyCodes specified for a modifier differ from those currently defined and any (current or new) keys for that modifier are in the logically down state, -XSetModifierMapping + returns MappingBusy, and none of the modifiers is changed. -XSetModifierMapping + can generate BadAlloc and @@ -3894,11 +3894,11 @@ errors. To obtain the KeyCodes used as modifiers, use -XGetModifierMapping. +. XGetModifierMapping - + XModifierKeymap *XGetModifierMapping Display *display @@ -3921,12 +3921,12 @@ Specifies the connection to the X server. The -XGetModifierMapping + function returns a pointer to a newly created XModifierKeymap structure that contains the keys being used as modifiers. The structure should be freed after use by calling -XFreeModifiermap. +. If only zero values appear in the set for any modifier, that modifier is disabled. diff --git a/libX11/specs/libX11/CH13.xml b/libX11/specs/libX11/CH13.xml index 65a92e729..3a53f1f62 100644 --- a/libX11/specs/libX11/CH13.xml +++ b/libX11/specs/libX11/CH13.xml @@ -1,7 +1,7 @@ - + Locales and Internationalized Text Functions @@ -128,7 +128,7 @@ They will configure the locale by calling three functions: the host locale configuration function, XSupportsLocale, and -XSetLocaleModifiers. +. @@ -142,11 +142,11 @@ is selecting one of several styles of keyboard input method. To configure Xlib locale modifiers for the current locale, use -XSetLocaleModifiers. +. XSetLocaleModifiers - + char *XSetLocaleModifiers char *modifier_list @@ -169,7 +169,7 @@ Specifies the modifiers. The -XSetLocaleModifiers + function sets the X modifiers for the current locale setting. The modifier_list argument is a null-terminated string of the form ``{@category=value}'', that is, @@ -198,7 +198,7 @@ If the function is successful, it returns a pointer to a string. The contents of the string are such that a subsequent call with that string (in the same locale) will restore the modifiers to the same settings. If modifier_list is a NULL pointer, -XSetLocaleModifiers + also returns a pointer to such a string, and the current locale modifiers are not changed. @@ -216,7 +216,7 @@ the first successful call to set them. Whenever the locale is changed, the modifiers that are in effect become unspecified until the next successful call to set them. Clients should always call -XSetLocaleModifiers + with a non-NULL modifier_list after setting the locale before they call any locale-dependent Xlib routine. @@ -279,7 +279,7 @@ overriding any category-specific settings in the local host environment. The internationalized Xlib functions operate in the current locale configured by the host environment and X locale modifiers set by -XSetLocaleModifiers + or in the locale and modifiers configured at the time some object supplied to the function was created. For each locale-dependent function, @@ -309,7 +309,7 @@ the following table describes the locale (and modifiers) dependency: Locale queried - XSetLocaleModifiers + Locale modified @@ -319,16 +319,16 @@ the following table describes the locale (and modifiers) dependency: setlocale - XrmGetFileDatabase - XrmGetStringDatabase + + Locale of XrmDatabase XrmDatabase - XrmPutFileDatabase - XrmLocaleOfDatabase + + Locale of XrmDatabase @@ -338,7 +338,7 @@ the following table describes the locale (and modifiers) dependency: setlocale - XmbSetWMProperties + Encoding of supplied/returned text (some WM_ property text in environment locale) @@ -346,10 +346,10 @@ the following table describes the locale (and modifiers) dependency: setlocale - XmbTextPropertyToTextList - XwcTextPropertyToTextList - XmbTextListToTextProperty - XwcTextListToTextProperty + + + + Encoding of supplied/returned text @@ -359,33 +359,33 @@ the following table describes the locale (and modifiers) dependency: setlocale - XOpenIM + XIM input method selection - XRegisterIMInstantiateCallback + XIM selection - XUnregisterIMInstantiateCallback + XIM selection XIM - XCreateIC + XIC input method configuration - XLocaleOfIM, and so on + , and so on Queried locale XIC - XmbLookupString + Keyboard layout - XwcLookupString + Encoding of returned text @@ -394,35 +394,35 @@ the following table describes the locale (and modifiers) dependency: setlocale - XOpenOM + XOM output method selection - XCreateFontSet + Charsets of fonts in XFontSet XOM - XCreateOC + XOC output method configuration - XLocaleOfOM, and so on + , and so on Queried locale XFontSet - XmbDrawText, + , Locale of supplied text - XwcDrawText, and so on + , and so on Locale of supplied text - XExtentsOfFontSet, and so on - XmbTextExtents, + , and so on + , XwcTextExtents, and so on Locale-dependent metrics @@ -434,8 +434,8 @@ the following table describes the locale (and modifiers) dependency: setlocale - XGetErrorDatabaseText, - XGetErrorText, and so on + , + , and so on Locale of error message @@ -460,7 +460,7 @@ is state-dependent. All Xlib functions behave as if they do not change the current locale or X modifier setting. (This means that if they do change locale or call -XSetLocaleModifiers + with a non-NULL argument, they must save and restore the current state on entry and exit.) Also, Xlib functions on implementations that conform to the ANSI C library do @@ -503,11 +503,11 @@ A NULL identifies the end of a nested list. To allocate a nested variable argument list dynamically, use -XVaCreateNestedList. +. XVaCreateNestedList - + XVaNestedList XVaCreateNestedList int dummy @@ -541,7 +541,7 @@ Specifies the variable length argument list(Al. The -XVaCreateNestedList + function allocates memory and copies its arguments into a single list pointer, which may be used as a value for arguments requiring a list value. @@ -550,7 +550,7 @@ Data passed by reference is not copied; the caller must ensure data remains valid for the lifetime of the nested list. The list should be freed using -XFree + when it is no longer needed. @@ -690,11 +690,11 @@ a broader, more generalized abstraction. To open an output method, use -XOpenOM. +. XOpenOM - + XOM XOpenOM Display *display @@ -750,12 +750,12 @@ Specifies the full class name of the application. The -XOpenOM + function opens an output method matching the current locale and modifiers specification. The current locale and modifiers are bound to the output method when -XOpenOM + is called. The locale associated with an output method cannot be changed. @@ -763,11 +763,11 @@ The locale associated with an output method cannot be changed. The specific output method to which this call will be routed is identified on the basis of the current locale and modifiers. -XOpenOM + will identify a default output method corresponding to the current locale. That default can be modified using -XSetLocaleModifiers + to set the output method modifier. @@ -795,24 +795,24 @@ if res_name or res_class is NULL. The res_name and res_class arguments are not assumed to exist beyond the call to -XOpenOM. +. The specified resource database is assumed to exist for the lifetime of the output method. -XOpenOM + returns NULL if no output method could be opened. To close an output method, use -XCloseOM. +. XCloseOM - + Status XCloseOM XOM om @@ -835,18 +835,18 @@ Specifies the output method. The -XCloseOM + function closes the specified output method. To set output method attributes, use -XSetOMValues. +. XSetOMValues - + char *XSetOMValues XOM om @@ -880,7 +880,7 @@ Specifies the variable-length argument list(Al. The -XSetOMValues + function presents a variable argument list programming interface for setting properties or features of the specified output method. This function returns NULL if it succeeds; @@ -895,11 +895,11 @@ No standard arguments are currently defined by Xlib. To query an output method, use -XGetOMValues. +. XGetOMValues - + char *XGetOMValues XOM om @@ -933,7 +933,7 @@ Specifies the variable-length argument list(Al. The -XGetOMValues + function presents a variable argument list programming interface for querying properties or features of the specified output method. This function returns NULL if it succeeds; @@ -943,11 +943,11 @@ it returns the name of the first argument that could not be obtained. To obtain the display associated with an output method, use -XDisplayOfOM. +. XDisplayOfOM - + Display *XDisplayOfOM XOM om @@ -970,18 +970,18 @@ Specifies the output method. The -XDisplayOfOM + function returns the display associated with the specified output method. To get the locale associated with an output method, use -XLocaleOfOM. +. XLocaleOfOM - + char *XLocaleOfOM XOM om @@ -1004,7 +1004,7 @@ Specifies the output method. The -XLocaleOfOM + returns the locale associated with the specified output method. @@ -1041,7 +1041,7 @@ The following key applies to this table. G - This value may be read using XGetOMValues. + This value may be read using . @@ -1127,7 +1127,7 @@ charset names. The required charset list is owned by Xlib and should not be modified or freed by the client. It will be freed by a call to -XCloseOM + with the associated XOM. Until freed, its contents will not be modified by Xlib. @@ -1154,7 +1154,7 @@ The value of the argument is a pointer to a structure of type Clients are responsible for freeing the XOMOrientation structure by using -XFree; +; this also frees the contents of the structure. @@ -1247,7 +1247,7 @@ of the drawing origin. This OM value presents functionality identical to the -XDirectionalDependentDrawing + function. @@ -1271,7 +1271,7 @@ dependent on the locale implementation and the font set used. This OM value presents functionality identical to the -XContextualDrawing + function. @@ -1315,11 +1315,11 @@ is defined as an upward compatible type of To create an output context, use -XCreateOC. +. XCreateOC - + XOC XCreateOC XOM om @@ -1353,7 +1353,7 @@ Specifies the variable-length argument list(Al. The -XCreateOC + function creates an output context within the specified output method. @@ -1364,7 +1364,7 @@ All other output context values can be set later. -XCreateOC + returns NULL if no output context could be created. NULL can be returned for any of the following reasons: @@ -1392,7 +1392,7 @@ The output method encountered an output method implementation-dependent error. -XCreateOC + can generate a BadAtom error. @@ -1401,11 +1401,11 @@ error. To destroy an output context, use -XDestroyOC. +. XDestroyOC - + void XDestroyOC XOC oc @@ -1428,18 +1428,18 @@ Specifies the output context. The -XDestroyOC + function destroys the specified output context. To get the output method associated with an output context, use -XOMOfOC. +. XOMOfOC - + XOM XOMOfOC XOC oc @@ -1462,7 +1462,7 @@ Specifies the output context. The -XOMOfOC + function returns the output method associated with the specified output context. @@ -1471,9 +1471,9 @@ specified output context. Xlib provides two functions for setting and reading output context values, respectively, -XSetOCValues + and -XGetOCValues. +. Both functions have a variable-length argument list. In that argument list, any XOC value's name must be denoted with a character string using the X Portable Character Set. @@ -1482,11 +1482,11 @@ with a character string using the X Portable Character Set. To set XOC values, use -XSetOCValues. +. XSetOCValues - + char *XSetOCValues XOC oc @@ -1520,7 +1520,7 @@ Specifies the variable-length argument list(Al. The -XSetOCValues + function returns NULL if no error occurred; otherwise, it returns the name of the first argument that could not be set. @@ -1550,7 +1550,7 @@ matching the data type imposed by the semantics of the argument. -XSetOCValues + can generate a BadAtom error. @@ -1559,11 +1559,11 @@ error. To obtain XOC values, use -XGetOCValues. +. XGetOCValues - + char *XGetOCValues XOC oc @@ -1597,7 +1597,7 @@ Specifies the variable-length argument list(Al. The -XGetOCValues + function returns NULL if no error occurred; otherwise, it returns the name of the first argument that could not be obtained. An argument might not be obtained for any of the following reasons: @@ -1652,20 +1652,20 @@ The following keys apply to this table. C - This value must be set with XCreateOC. + This value must be set with . D - This value may be set using XCreateOC. + This value may be set using . If it is not set,a default is provided. G - This value may be read using XGetOCValues. + This value may be read using . S - This value must be set using XSetOCValues. + This value must be set using . @@ -1688,17 +1688,17 @@ The following keys apply to this table. BaseFontName - XCreateFontSet + C-G MissingCharSet - XCreateFontSet + G DefaultString - XCreateFontSet + G @@ -1718,7 +1718,7 @@ The following keys apply to this table. FontInfo - XFontsOfFontSet + G @@ -1768,7 +1768,7 @@ If a base font name is not an XLFD name, Xlib will attempt to obtain an XLFD name from the font properties for the font. If Xlib is successful, the -XGetOCValues + function will return this XLFD name instead of the client-supplied name. @@ -1778,7 +1778,7 @@ and cannot be changed. If no fonts exist for any of the required charsets, or if the locale definition in Xlib requires that a font exist for a particular charset and a font is not found for that charset, -XCreateOC + returns NULL. @@ -1786,13 +1786,13 @@ returns NULL. When querying for the XNBaseFontName XOC value, -XGetOCValues + returns a null-terminated string identifying the base font names that Xlib used to load the fonts needed for the locale. This string is owned by Xlib and should not be modified or freed by the client. The string will be freed by a call to -XDestroyOC + with the associated XOC. Until freed, the string contents will not be modified by Xlib. @@ -1829,7 +1829,7 @@ may be able to remap a required charset. The missing charset list is owned by Xlib and should not be modified or freed by the client. It will be freed by a call to -XDestroyOC + with the associated XOC. Until freed, its contents will not be modified by Xlib. @@ -1869,7 +1869,7 @@ no glyphs are drawn and the escapement is zero. The returned string is null-terminated. It is owned by Xlib and should not be modified or freed by the client. It will be freed by a call to -XDestroyOC + with the associated XOC. Until freed, its contents will not be modified by Xlib. @@ -1886,7 +1886,7 @@ The XNOrientation argument specifies the current orientation of text when drawn. The value of this argument is one of the values returned by the -XGetOMValues + function with the XNQueryOrientation argument specified in the @@ -1950,16 +1950,16 @@ When querying for the or XNResourceClass XOC value, -XGetOCValues + returns a null-terminated string. This string is owned by Xlib and should not be modified or freed by the client. The string will be freed by a call to -XDestroyOC + with the associated XOC or when the associated value is changed via -XSetOCValues. +. Until freed, the string contents will not be modified by Xlib. @@ -2051,23 +2051,23 @@ is closed. The XNOMAutomatic argument returns whether the associated output context was created by -XCreateFontSet + or not. Because the -XFreeFontSet + function not only destroys the output context but also closes the implicit output method associated with it, -XFreeFontSet + should be used with any output context created by -XCreateFontSet. +. However, it is possible that a client does not know how the output context was created. Before a client destroys the output context, it can query whether XNOMAutomatic is set to determine whether -XFreeFontSet + or -XDestroyOC + should be used to destroy the output context. @@ -2093,7 +2093,7 @@ and is equivalent to the type The -XCreateFontSet + function is a convenience function for creating an output context using only default values. The returned XFontSet @@ -2106,13 +2106,13 @@ has an OM value automatically set to True so that the output context self indicates whether it was created by -XCreateOC + or -XCreateFontSet. +. XCreateFontSet - + XFontSet XCreateFontSet Display *display @@ -2179,10 +2179,10 @@ Returns the string drawn for missing charsets. The -XCreateFontSet + function creates a font set for the specified display. The font set is bound to the current locale when -XCreateFontSet + is called. The font set may be used in subsequent calls to obtain font and character information and to image text in the locale of the font set. @@ -2216,7 +2216,7 @@ If a base font name is not an XLFD name, Xlib will attempt to obtain an XLFD name from the font properties for the font. If this action is successful in obtaining an XLFD name, the -XBaseFontNameListOfFontSet + function will return this XLFD name instead of the client-supplied name. @@ -2340,16 +2340,16 @@ For example: If -XCreateFontSet + is unable to create the font set, either because there is insufficient memory or because the current locale is not supported, -XCreateFontSet + returns NULL, missing_charset_list_return is set to NULL, and missing_charset_count_return is set to zero. If fonts exist for all of the charsets required by the current locale, -XCreateFontSet + returns a valid XFontSet, missing_charset_list_return is set to NULL, @@ -2358,7 +2358,7 @@ and missing_charset_count_return is set to zero. If no font exists for one or more of the required charsets, -XCreateFontSet + sets missing_charset_list_return to a list of one or more null-terminated charset names for which no font exists and sets missing_charset_count_return to the number of missing fonts. @@ -2371,10 +2371,10 @@ may be able to remap a required charset. If no font exists for any of the required charsets or if the locale definition in Xlib requires that a font exist for a particular charset and a font is not found for that charset, -XCreateFontSet + returns NULL. Otherwise, -XCreateFontSet + returns a valid XFontSet to font_set. @@ -2386,7 +2386,7 @@ When an Xmb/wc drawing or measuring function is called with an that has missing charsets, some characters in the locale will not be drawable. If def_string_return is non-NULL, -XCreateFontSet + returns a pointer to a string that represents the glyphs that are drawn with this XFontSet @@ -2406,7 +2406,7 @@ no glyphs are drawn, and the escapement is zero. The returned string is null-terminated. It is owned by Xlib and should not be modified or freed by the client. It will be freed by a call to -XFreeFontSet + with the associated XFontSet. Until freed, its contents will not be modified by Xlib. @@ -2422,13 +2422,13 @@ operation in the case that some fonts did not exist. The returned XFontSet and missing charset list should be freed with -XFreeFontSet + and -XFreeStringList, +, respectively. The client-supplied base_font_name_list may be freed by the client after calling -XCreateFontSet. +. @@ -2438,11 +2438,11 @@ To obtain a list of structures and full font names given an XFontSet, use -XFontsOfFontSet. +. XFontsOfFontSet - + int XFontsOfFontSet XFontSet font_set @@ -2487,7 +2487,7 @@ Returns the list of font names. The -XFontsOfFontSet + function returns a list of one or more XFontStructs and font names for the fonts used by the Xmb and Xwc layers @@ -2536,7 +2536,7 @@ The and font name lists are owned by Xlib and should not be modified or freed by the client. They will be freed by a call to -XFreeFontSet + with the associated XFontSet. Until freed, their contents will not be modified by Xlib. @@ -2547,11 +2547,11 @@ Until freed, their contents will not be modified by Xlib. To obtain the base font name list and the selected font name list given an XFontSet, use -XBaseFontNameListOfFontSet. +. XBaseFontNameListOfFontSet - + char *XBaseFontNameListOfFontSet XFontSet font_set @@ -2574,7 +2574,7 @@ Specifies the font set. The -XBaseFontNameListOfFontSet + function returns the original base font name list supplied by the client when the XFontSet @@ -2587,10 +2587,10 @@ White space may appear immediately on either side of separating commas. If -XCreateFontSet + obtained an XLFD name from the font properties for the font specified by a non-XLFD base name, the -XBaseFontNameListOfFontSet + function will return the XLFD name instead of the non-XLFD base name. @@ -2598,7 +2598,7 @@ function will return the XLFD name instead of the non-XFreeFontSet + with the associated XFontSet. Until freed, its contents will not be modified by Xlib. @@ -2609,11 +2609,11 @@ Until freed, its contents will not be modified by Xlib. To obtain the locale name given an XFontSet, use -XLocaleOfFontSet. +. XLocaleOfFontSet - + char *XLocaleOfFontSet XFontSet font_set @@ -2636,7 +2636,7 @@ Specifies the font set. The -XLocaleOfFontSet + function returns the name of the locale bound to the specified XFontSet, @@ -2647,7 +2647,7 @@ as a null-terminated string. The returned locale name string is owned by Xlib and should not be modified or freed by the client. It may be freed by a call to -XFreeFontSet + with the associated XFontSet. Until freed, it will not be modified by Xlib. @@ -2656,17 +2656,17 @@ Until freed, it will not be modified by Xlib. The -XFreeFontSet + function is a convenience function for freeing an output context. -XFreeFontSet + also frees its associated XOM if the output context was created by -XCreateFontSet. +. XFreeFontSet - + void XFreeFontSet Display *display @@ -2700,7 +2700,7 @@ Specifies the font set. The -XFreeFontSet + function frees the specified font set. The associated base font name list, font name list, XFontStruct @@ -2743,9 +2743,9 @@ Regardless of the character rendering order, the origins of all characters are on the primary draw direction side of the drawing origin. The screen location of a particular character image may be determined with -XmbTextPerCharExtents + or -XwcTextPerCharExtents. +. @@ -2753,10 +2753,10 @@ The drawing functions are allowed to implement context-dependent rendering, where the glyphs drawn for a string are not simply a concatenation of the glyphs that represent each individual character. A string of two characters drawn with -XmbDrawString + may render differently than if the two characters were drawn with separate calls to -XmbDrawString. +. If the client appends or inserts a character in a previously drawn string, the client may need to redraw some adjacent characters @@ -2766,11 +2766,11 @@ to obtain proper rendering. To find out about direction-dependent rendering, use -XDirectionalDependentDrawing. +. XDirectionalDependentDrawing - + Bool XDirectionalDependentDrawing XFontSet font_set @@ -2793,7 +2793,7 @@ Specifies the font set. The -XDirectionalDependentDrawing + function returns True if the drawing functions implement implicit text directionality; @@ -2804,11 +2804,11 @@ otherwise, it returns To find out about context-dependent rendering, use -XContextualDrawing. +. XContextualDrawing - + Bool XContextualDrawing XFontSet font_set @@ -2831,7 +2831,7 @@ Specifies the font set. The -XContextualDrawing + function returns True if text drawn with the font set might include context-dependent drawing; @@ -2842,11 +2842,11 @@ otherwise, it returns To find out about context-dependent or direction-dependent rendering, use -XContextDependentDrawing. +. XContextDependentDrawing - + Bool XContextDependentDrawing XFontSet font_set @@ -2869,7 +2869,7 @@ Specifies the font set. The -XContextDependentDrawing + function returns True if the drawing functions implement implicit text directionality or @@ -2919,7 +2919,7 @@ The max_ink_extent member gives the maximum extent, over all drawable characters the rectangles that bound the character glyph image drawn in the foreground color, relative to a constant origin. See -XmbTextExtents + and XwcTextExtents for detailed semantics. @@ -2946,9 +2946,9 @@ individual extent. The rectangles for a given character in a string can be obtained from -XmbTextPerCharExtents + or -XwcTextPerCharExtents. +. @@ -2956,11 +2956,11 @@ or To obtain the maximum extents structure given an XFontSet, use -XExtentsOfFontSet. +. XExtentsOfFontSet - + XFontSetExtents *XExtentsOfFontSet XFontSet font_set @@ -2983,7 +2983,7 @@ Specifies the font set. The -XExtentsOfFontSet + function returns an XFontSetExtents structure for the fonts used by the Xmb and Xwc layers @@ -2996,7 +2996,7 @@ The structure is owned by Xlib and should not be modified or freed by the client. It will be freed by a call to -XFreeFontSet + with the associated XFontSet. Until freed, its contents will not be modified by Xlib. @@ -3006,14 +3006,14 @@ Until freed, its contents will not be modified by Xlib. To obtain the escapement in pixels of the specified text as a value, use -XmbTextEscapement + or -XwcTextEscapement. +. XmbTextEscapement XwcTextEscapement - + int XmbTextEscapement XFontSet font_set @@ -3022,7 +3022,7 @@ or - + int XwcTextEscapement XFontSet font_set @@ -3077,9 +3077,9 @@ Specifies the number of characters in the string argument. The -XmbTextEscapement + and -XwcTextEscapement + functions return the escapement in pixels of the specified string as a value, using the fonts loaded for the specified font set. The escapement is the distance in pixels in the primary draw @@ -3098,14 +3098,14 @@ the escapement is always positive. To obtain the overall_ink_return and overall_logical_return arguments, the overall bounding box of the string's image, and a logical bounding box, use -XmbTextExtents + or XwcTextExtents. XmbTextExtents XwcTextExtents - + int XmbTextExtents XFontSet font_set @@ -3194,7 +3194,7 @@ Returns the overall logical dimensions. The -XmbTextExtents + and XwcTextExtents functions set the components of the specified overall_ink_return and @@ -3202,9 +3202,9 @@ overall_logical_return arguments to the overall bounding box of the string's image and a logical bounding box for spacing purposes, respectively. They return the value returned by -XmbTextEscapement + or -XwcTextEscapement. +. These metrics are relative to the drawing origin of the string, using the fonts loaded for the specified font set. @@ -3236,7 +3236,7 @@ When the has missing charsets, metrics for each unavailable character are taken from the default string returned by -XCreateFontSet + so that the metrics represent the text as it will actually be drawn. The behavior for an invalid codepoint is undefined. @@ -3244,7 +3244,7 @@ The behavior for an invalid codepoint is undefined. To determine the effective drawing origin for a character in a drawn string, the client should call -XmbTextPerCharExtents + on the entire string, then on the character, and subtract the x values of the returned rectangles for the character. @@ -3258,14 +3258,14 @@ and get the same rendering. To obtain per-character information for a text string, use -XmbTextPerCharExtents + or -XwcTextPerCharExtents. +. XmbTextPerCharExtents XwcTextPerCharExtents - + Status XmbTextPerCharExtents XFontSet font_set @@ -3280,7 +3280,7 @@ or - + Status XwcTextPerCharExtents XFontSet font_set @@ -3403,9 +3403,9 @@ Returns the overall logical dimensions. The -XmbTextPerCharExtents + and -XwcTextPerCharExtents + functions return the text dimensions of each character of the specified text, using the fonts loaded for the specified font set. Each successive element of ink_array_return and logical_array_return @@ -3444,7 +3444,7 @@ When the XFontSet has missing charsets, metrics for each unavailable character are taken from the default string returned by -XCreateFontSet + so that the metrics represent the text as it will actually be drawn. The behavior for an invalid codepoint is undefined. @@ -3458,12 +3458,12 @@ Otherwise, the functions return a nonzero value. If the overall_ink_return or overall_logical_return argument is non-NULL, -XmbTextPerCharExtents + and -XwcTextPerCharExtents + return the maximum extent of the string's metrics to overall_ink_return or overall_logical_return, as returned by -XmbTextExtents + or XwcTextExtents. @@ -3478,10 +3478,10 @@ or The functions defined in this section draw text at a specified location in a drawable. They are similar to the functions -XDrawText, -XDrawString, +, +, and -XDrawImageString + except that they work with font sets instead of single fonts and interpret the text based on the locale of the font set instead of treating the bytes of the string as direct font indexes. @@ -3502,9 +3502,9 @@ No validation that all fonts conform to some width rule is performed. The text functions -XmbDrawText + and -XwcDrawText + use the following structures: @@ -3541,14 +3541,14 @@ typedef struct { To draw text using multiple font sets in a given drawable, use -XmbDrawText + or -XwcDrawText. +. XmbDrawText XwcDrawText - + void XmbDrawText Display *display @@ -3560,7 +3560,7 @@ or - + void XwcDrawText Display *display @@ -3650,9 +3650,9 @@ Specifies the number of text items in the array. The -XmbDrawText + and -XwcDrawText + functions allow complex spacing and font set shifts between text strings. Each text item is processed in turn, with the origin of a text element advanced in the primary draw direction by the escapement of the @@ -3669,37 +3669,37 @@ will not be drawn. -XmbDrawText + and -XwcDrawText + do not perform any context-dependent rendering between text segments. Clients may compute the drawing metrics by passing each text segment to -XmbTextExtents + and XwcTextExtents or -XmbTextPerCharExtents + and -XwcTextPerCharExtents. +. When the XFontSet has missing charsets, each unavailable character is drawn with the default string returned by -XCreateFontSet. +. The behavior for an invalid codepoint is undefined. To draw text using a single font set in a given drawable, use -XmbDrawString + or -XwcDrawString. +. XmbDrawString XwcDrawString - + void XmbDrawString Display *display @@ -3712,7 +3712,7 @@ or - + void XwcDrawString Display *display @@ -3823,29 +3823,29 @@ Specifies the number of characters in the string argument. The -XmbDrawString + and -XwcDrawString + functions draw the specified text with the foreground pixel. When the XFontSet has missing charsets, each unavailable character is drawn with the default string returned by -XCreateFontSet. +. The behavior for an invalid codepoint is undefined. To draw image text using a single font set in a given drawable, use -XmbDrawImageString + or -XwcDrawImageString. +. XmbDrawImageString XwcDrawImageString - + void XmbDrawImageString Display *display @@ -3858,7 +3858,7 @@ or - + void XwcDrawImageString Display *display @@ -3969,13 +3969,13 @@ Specifies the number of characters in the string argument. The -XmbDrawImageString + and -XwcDrawImageString + functions fill a destination rectangle with the background pixel defined in the GC and then paint the text with the foreground pixel. The filled rectangle is the rectangle returned to overall_logical_return by -XmbTextExtents + or XwcTextExtents for the same text and @@ -3987,7 +3987,7 @@ When the XFontSet has missing charsets, each unavailable character is drawn with the default string returned by -XCreateFontSet. +. The behavior for an invalid codepoint is undefined. @@ -4358,7 +4358,7 @@ is an opaque data structure represented by the XIM data type. This data structure is returned by the -XOpenIM + function, which opens an input method on a given display. Subsequent operations on this data structure encapsulate all communication between client and input method. @@ -4410,13 +4410,13 @@ possibly with the same client window. An XIC is created with the -XCreateIC + function, providing an XIM argument and affiliating the input context to the input method for its lifetime. When an input method is closed with -XCloseIM, +, all of its affiliated input contexts should not be used any more (and should preferably be destroyed before closing the input method). @@ -4458,16 +4458,16 @@ according to the needs of their application. To obtain characters from an input method, a client must call the function -XmbLookupString + or -XwcLookupString + with an input context created from that input method. Both a locale and display are bound to an input method when it is opened, and an input context inherits this locale and display. Any strings returned by -XmbLookupString + or -XwcLookupString + will be encoded in that locale. @@ -4479,9 +4479,9 @@ will be encoded in that locale. For each text entry area in which the -XmbLookupString + or -XwcLookupString + functions are used, there will be an associated input context. @@ -4491,7 +4491,7 @@ When the application focus moves to a text entry area, the application must set the input context focus to the input context associated with that area. The input context focus is set by calling -XSetICFocus + with the appropriate input context. @@ -4499,9 +4499,9 @@ with the appropriate input context. Also, when the application focus moves out of a text entry area, the application should unset the focus for the associated input context by calling -XUnsetICFocus. +. As an optimization, if -XSetICFocus + is called successively on two different input contexts, setting the focus on the second will automatically unset the focus on the first. @@ -4580,7 +4580,7 @@ or in its XIMStyles value returned by -XGetIMValues. +. When a client has decided that it will provide geometry management for an input method, it indicates that decision by setting the @@ -4661,9 +4661,9 @@ by which an input method can initiate a geometry change. A filtering mechanism is provided to allow input methods to capture X events transparently to clients. It is expected that toolkits (or clients) using -XmbLookupString + or -XwcLookupString + will call this filter at some point in the event processing mechanism to make sure that events needed by an input method can be filtered by that input method. @@ -4720,9 +4720,9 @@ by the client itself, tightly coupled with the input method logic. When the user enters a keystroke, the client calls -XmbLookupString + or -XwcLookupString. +. At this point, in the on-the-spot case, the echo of the keystroke in the preedit has not yet been done. Before returning to the client logic that handles the input characters, @@ -4780,9 +4780,9 @@ As highlighted before, the input method architecture provides preediting, which supports a type of preprocessor input composition. In this case, composition consists of interpreting a sequence of key events and returning a committed string via -XmbLookupString + or -XwcLookupString. +. This provides the basics for input methods. @@ -4866,9 +4866,9 @@ and starts editing again. For this reason, an input method supporting this type of conversion should take notice of when the client calls -XmbResetIC + or -XwcResetIC, +, which is usually an indication of a context change. @@ -4880,9 +4880,9 @@ while other conversions replace the client's text with new text to achieve the reconversion or transliteration. Yet in all cases the result of a conversion, either immediately or via preediting, is returned by the -XmbLookupString + and -XwcLookupString + functions. @@ -4895,7 +4895,7 @@ or Because the input method may not support string conversions, clients have to query the availability of string conversion operations by checking the supported XIC values list by calling -XGetIMValues + with the XNQueryICValuesList IM value. @@ -4961,9 +4961,9 @@ additional text. The interface to input methods might appear to be simply creating an input method -(XOpenIM) +() and freeing an input method -(XCloseIM). +(). However, input methods may require complex communication with input method servers (IM servers), for example: @@ -5007,17 +5007,17 @@ functions are provided: - XRegisterIMInstantiateCallback + This function allows clients to register a callback procedure to be called when Xlib detects that an IM server is up and available. - XOpenIM + A client calls this function as a result of the callback procedure being called. - XSetIMValues, XSetICValues + , These functions use the XIM and XIC values, XNDestroyCallback, to allow a client @@ -5030,7 +5030,7 @@ functions are provided: switching IM servers. - XUnregisterIMInstantiateCallback + This function removes a callback procedure registered by the client. @@ -5082,7 +5082,7 @@ to specify a set of keys for this purpose. However, the input method might not allow clients to specify hot keys. Therefore, clients have to query support of hot keys by checking the supported XIC values list by calling -XGetIMValues + with the XNQueryICValuesList IM value. @@ -5109,20 +5109,20 @@ Xlib provides the ability for an application to manage the preedit state programmatically. Two methods are provided for retrieving the preedit state of an input context. One method is to query the state by calling -XGetICValues + with the XNPreeditState XIC value. Another method is to receive notification whenever the preedit state is changed. To receive such notification, an application needs to register a callback by calling -XSetICValues + with the XNPreeditStateNotifyCallback XIC value. In order to change the preedit state programmatically, an application needs to call -XSetICValues + with XNPreeditState. @@ -5133,7 +5133,7 @@ method may not provide the ability to set the state or to retrieve the state programmatically. Therefore, clients have to query availability of preedit state operations by checking the supported XIC values list by calling -XGetIMValues + with the XNQueryICValuesList IM value. @@ -5148,11 +5148,11 @@ IM value. To open a connection, use -XOpenIM. +. XOpenIM - + XIM XOpenIM Display *display @@ -5208,15 +5208,15 @@ Specifies the full class name of the application. The -XOpenIM + function opens an input method, matching the current locale and modifiers specification. Current locale and modifiers are bound to the input method at opening time. The locale associated with an input method cannot be changed dynamically. This implies that the strings returned by -XmbLookupString + or -XwcLookupString, +, for any input context affiliated with a given input method, will be encoded in the locale current at the time the input method is opened. @@ -5224,11 +5224,11 @@ will be encoded in the locale current at the time the input method is opened. The specific input method to which this call will be routed is identified on the basis of the current locale. -XOpenIM + will identify a default input method corresponding to the current locale. That default can be modified using -XSetLocaleModifiers + for the input method modifier. @@ -5256,24 +5256,24 @@ if res_name or res_class is NULL. The res_name and res_class arguments are not assumed to exist beyond the call to -XOpenIM. +. The specified resource database is assumed to exist for the lifetime of the input method. -XOpenIM + returns NULL if no input method could be opened. To close a connection, use -XCloseIM. +. XCloseIM - + Status XCloseIM XIM im @@ -5296,18 +5296,18 @@ Specifies the input method. The -XCloseIM + function closes the specified input method. To set input method attributes, use -XSetIMValues. +. XSetIMValues - + char *XSetIMValues XIM im @@ -5341,7 +5341,7 @@ Specifies the variable-length argument list(Al. The -XSetIMValues + function presents a variable argument list programming interface for setting attributes of the specified input method. It returns NULL if it succeeds; @@ -5356,11 +5356,11 @@ correctly. To query an input method, use -XGetIMValues. +. XGetIMValues - + char *XGetIMValues XIM im @@ -5394,7 +5394,7 @@ Specifies the variable length argument list(Al. The -XGetIMValues + function presents a variable argument list programming interface for querying properties or features of the specified input method. This function returns NULL if it succeeds; @@ -5409,21 +5409,21 @@ That is, if the XIM value is of type T, the argument must be of type T*. If T itself is a pointer type, then -XGetIMValues + allocates memory to store the actual data, and the client is responsible for freeing this data by calling -XFree + with the returned pointer. To obtain the display associated with an input method, use -XDisplayOfIM. +. XDisplayOfIM - + Display *XDisplayOfIM XIM im @@ -5446,18 +5446,18 @@ Specifies the input method. The -XDisplayOfIM + function returns the display associated with the specified input method. To get the locale associated with an input method, use -XLocaleOfIM. +. XLocaleOfIM - + char *XLocaleOfIM XIM im @@ -5480,18 +5480,18 @@ Specifies the input method. The -XLocaleOfIM + function returns the locale associated with the specified input method. To register an input method instantiate callback, use -XRegisterIMInstantiateCallback. +. XRegisterIMInstantiateCallback - + Bool XRegisterIMInstantiateCallback Display *display @@ -5569,7 +5569,7 @@ Specifies the additional client data. The -XRegisterIMInstantiateCallback + function registers a callback to be invoked whenever a new input method becomes available for the specified display that matches the current locale and modifiers. @@ -5587,7 +5587,7 @@ The generic prototype is as follows: IMInstantiateCallback - + void IMInstantiateCallback Display *display @@ -5632,11 +5632,11 @@ Not used for this callback and always passed as NULL. To unregister an input method instantiation callback, use -XUnregisterIMInstantiateCallback. +. XUnregisterIMInstantiateCallback - + Bool XUnregisterIMInstantiateCallback Display *display @@ -5714,7 +5714,7 @@ Specifies the additional client data. The -XUnregisterIMInstantiateCallback + function removes an input method instantiation callback previously registered. The function returns @@ -5757,17 +5757,17 @@ The following keys apply to this table. D This value may be set using - XSetIMValues. + . If it is not set, a default is provided. S - This value may be set using XSetIMValues. + This value may be set using . G - This value may be read using XGetIMValues. + This value may be read using . @@ -5856,7 +5856,7 @@ Clients are responsible for freeing the XIMStyles structure. To do so, use -XFree. +. @@ -6068,9 +6068,9 @@ is triggered when an input method stops its service for any reason. After the callback is invoked, the input method is closed and the associated input context(s) are destroyed by Xlib. Therefore, the client should not call -XCloseIM + or -XDestroyIC. +. @@ -6078,7 +6078,7 @@ The generic prototype of this callback function is as follows: DestroyCallback - + void DestroyCallback XIM im @@ -6128,7 +6128,7 @@ A DestroyCallback is always called with a NULL call_data argument. - + Query IM/IC Values List @@ -6150,7 +6150,7 @@ Clients are responsible for freeing the XIMValuesList structure. To do so, use -XFree. +. @@ -6203,7 +6203,7 @@ otherwise, the input method does not use the masks. Because this XIM value is optional, a client should call -XGetIMValues + with argument XNQueryIMValuesList before using this argument. @@ -6273,7 +6273,7 @@ must be set to Because this XIM value is optional, a client should call -XGetIMValues + with argument XNQueryIMValuesList before using this argument. @@ -6310,11 +6310,11 @@ they should be registered with the X Consortium. To create an input context, use -XCreateIC. +. XCreateIC - + XIC XCreateIC XIM im @@ -6348,7 +6348,7 @@ Specifies the variable length argument list(Al. The -XCreateIC + function creates a context within the specified input method. @@ -6361,7 +6361,7 @@ All other input context values can be set later. -XCreateIC + returns a NULL value if no input context could be created. A NULL value could be returned for any of the following reasons: @@ -6390,7 +6390,7 @@ The input method encountered an input method implementation-dependent error. -XCreateIC + can generate BadAtom, BadColor, @@ -6403,11 +6403,11 @@ errors. To destroy an input context, use -XDestroyIC. +. XDestroyIC - + void XDestroyIC XIC ic @@ -6429,7 +6429,7 @@ Specifies the input context. -XDestroyIC + destroys the specified input context. @@ -6438,13 +6438,13 @@ destroys the specified input context. To communicate to and synchronize with input method for any changes in keyboard focus from the client side, use -XSetICFocus + and -XUnsetICFocus. +. XSetICFocus - + void XSetICFocus XIC ic @@ -6467,7 +6467,7 @@ Specifies the input context. The -XSetICFocus + function allows a client to notify an input method that the focus window attached to the specified input context has received keyboard focus. The input method should take action to provide appropriate feedback. @@ -6476,12 +6476,12 @@ Complete feedback specification is a matter of user interface policy. Calling -XSetICFocus + does not affect the focus window value. XUnsetICFocus - + void XUnsetICFocus XIC ic @@ -6504,7 +6504,7 @@ Specifies the input context. The -XUnsetICFocus + function allows a client to notify an input method that the specified input context has lost the keyboard focus and that no more input is expected on the focus window attached to that input context. @@ -6514,7 +6514,7 @@ Complete feedback specification is a matter of user interface policy. Calling -XUnsetICFocus + does not affect the focus window value; the client may still receive events from the input method that are directed to the focus window. @@ -6523,21 +6523,21 @@ events from the input method that are directed to the focus window. To reset the state of an input context to its initial state, use -XmbResetIC + or -XwcResetIC. +. XmbResetIC XwcResetIC - + char *XmbResetIC XIC ic - + wchar_t *XwcResetIC XIC ic @@ -6563,9 +6563,9 @@ When XNResetState is set to XIMInitialState, -XmbResetIC + and -XwcResetIC + reset an input context to its initial state; when XNResetState @@ -6576,15 +6576,15 @@ In both cases, any input pending on that context is deleted. The input method is required to clear the preedit area, if any, and update the status accordingly. Calling -XmbResetIC + or -XwcResetIC + does not change the focus. The return value of -XmbResetIC + is its current preedit string as a multibyte string. If there is any preedit text drawn or visible to the user, then these procedures must return a non-NULL string. @@ -6595,17 +6595,17 @@ whether these procedures return a non-NULL string or NULL. The client should free the returned string by calling -XFree. +. To get the input method associated with an input context, use -XIMOfIC. +. XIMOfIC - + XIM XIMOfIC XIC ic @@ -6628,16 +6628,16 @@ Specifies the input context. The -XIMOfIC + function returns the input method associated with the specified input context. Xlib provides two functions for setting and reading XIC values, respectively, -XSetICValues + and -XGetICValues. +. Both functions have a variable-length argument list. In that argument list, any XIC value's name must be denoted with a character string using the X Portable Character Set. @@ -6646,11 +6646,11 @@ with a character string using the X Portable Character Set. To set XIC values, use -XSetICValues. +. XSetICValues - + char *XSetICValues XIC ic @@ -6684,7 +6684,7 @@ Specifies the variable length argument list(Al. The -XSetICValues + function returns NULL if no error occurred; otherwise, it returns the name of the first argument that could not be set. @@ -6715,7 +6715,7 @@ matching the data type imposed by the semantics of the argument. -XSetICValues + can generate BadAtom, BadColor, @@ -6729,11 +6729,11 @@ errors. To obtain XIC values, use -XGetICValues. +. XGetICValues - + char *XGetICValues XIC ic @@ -6767,7 +6767,7 @@ Specifies the variable length argument list(Al. The -XGetICValues + function returns NULL if no error occurred; otherwise, it returns the name of the first argument that could not be obtained. An argument could not be obtained for any of the following reasons: @@ -6792,10 +6792,10 @@ That is, if the IC value is of type T, the argument must be of type T*. If T itself is a pointer type, then -XGetICValues + allocates memory to store the actual data, and the client is responsible for freeing this data by calling -XFree + with the returned pointer. The exception to this rule is for an IC value of type XVaNestedList @@ -6844,26 +6844,26 @@ The following keys apply to these tables. C - This value must be set with XCreateIC. + This value must be set with . D This value may be set using - XCreateIC.> + .> If it is not set,> a default is provided. G This value may be read using - XGetICValues. + . GN This value may cause geometry negotiation when its value is set by means of - XCreateIC + or - XSetICValues. + . GR @@ -6882,7 +6882,7 @@ The following keys apply to these tables. S This value may be set with - XSetICValues. + . Ignored @@ -7332,7 +7332,7 @@ The XNInputStyle argument specifies the input style to be used. The value of this argument must be one of the values returned by the -XGetIMValues + function with the XNQueryInputStyle argument specified in the supported_styles list. @@ -7367,11 +7367,11 @@ the input method may not operate correctly. If an attempt is made to set this value a second time with -XSetICValues, +, the string XNClientWindow will be returned by -XSetICValues, +, and the client window will not be changed. @@ -7538,9 +7538,9 @@ stops its service for any reason; for example, when a connection to an IM server is broken. After the destroy callback is called, the input context is destroyed and the input method is closed. Therefore, the client should not call -XDestroyIC + and -XCloseIM. +. @@ -7573,7 +7573,7 @@ will filter any events that it uses to initiate the conversion. Because this XIC value is optional, a client should call -XGetIMValues + with argument XNQueryICValuesList before using this argument. @@ -7582,8 +7582,8 @@ before using this argument. - -String Conversion + +String Conversion @@ -7613,7 +7613,7 @@ reconversion, or transliteration conversion on it. Because this XIC value is optional, a client should call -XGetIMValues + with argument XNQueryICValuesList before using this argument. @@ -7665,16 +7665,16 @@ element to NULL. The XNResetState argument specifies the state the input context will return to after calling -XmbResetIC + or -XwcResetIC. +. The XIC state may be set to its initial state, as specified by the XNPreeditState value when -XCreateIC + was called, or it may be set to preserve the current state. @@ -7703,9 +7703,9 @@ typedef unsigned long XIMResetState; If XIMInitialState is set, then -XmbResetIC + and -XwcResetIC + will return to the initial XNPreeditState state of the XIC. @@ -7715,9 +7715,9 @@ state of the XIC. If XIMPreserveState is set, then -XmbResetIC + and -XwcResetIC + will preserve the current state of the XIC. @@ -7736,7 +7736,7 @@ values other than those specified above will default to Because this XIC value is optional, a client should call -XGetIMValues + with argument XNQueryICValuesList before using this argument. @@ -7768,7 +7768,7 @@ to Because this XIC value is optional, a client should call -XGetIMValues + with argument XNQueryICValuesList before using this functionality. @@ -7904,9 +7904,9 @@ arguments specify to an input method the attributes to be used for the preedit and status areas, if any. Those attributes are passed to -XSetICValues + or -XGetICValues + as a nested variable-length list. The names to be used in these lists are described in the following sections. @@ -8077,7 +8077,7 @@ in which the input method should allocate colors. The argument value is an Atom that should be a valid atom for calling -XGetRGBColormaps. +. An invalid argument may generate a BadAtom error when it is used by the input method. @@ -8263,14 +8263,14 @@ is set to the XNPreeditState value specified at the creation time will be reflected as the initial state for -XmbResetIC + and -XwcResetIC. +. Because this XIC value is optional, a client should call -XGetIMValues + with argument XNQueryICValuesList before using this argument. @@ -8293,7 +8293,7 @@ The generic prototype is as follows: PreeditStateNotifyCallback - + void PreeditStateNotifyCallback XIC ic @@ -8360,7 +8360,7 @@ typedef struct _XIMPreeditStateNotifyCallbackStruct { Because this XIC value is optional, a client should call -XGetIMValues + with argument XNQueryICValuesList before using this argument. @@ -8644,7 +8644,7 @@ The generic prototype is as follows: DestroyCallback - + void DestroyCallback XIC ic @@ -8706,7 +8706,7 @@ The callback prototype is as follows: StringConversionCallback - + void StringConversionCallback XIC ic @@ -8755,14 +8755,14 @@ The callback is passed an structure in the call_data argument. The text member is an XIMStringConversionText -structure (see section 13.5.6.9) +structure (see section 13.5.6.9) to be filled in by the client and describes the text to be sent to the input method. The data pointed to by the string and feedback elements of the XIMStringConversionText structure will be freed using -XFree + by the input method after the callback returns. So the client should not point to internal buffers that are critical to the client. @@ -8860,15 +8860,15 @@ conversion. When the input method turns preediting on or off, a -PreeditStartCallback + or -PreeditDoneCallback + callback is triggered to let the toolkit do the setup or the cleanup for the preedit region. PreeditStartCallback - + int PreeditStartCallback XIC ic @@ -8914,7 +8914,7 @@ Not used for this callback and always passed as NULL. When preedit starts on the specified input context, the callback is called with a NULL call_data argument. -PreeditStartCallback + will return the maximum size of the preedit string. A positive number indicates the maximum number of bytes allowed in the preedit string, @@ -8922,7 +8922,7 @@ and a value of -1 indicates there is no limit. PreeditDoneCallback - + void PreeditDoneCallback XIC ic @@ -8969,19 +8969,19 @@ Not used for this callback and always passed as NULL. When preedit stops on the specified input context, the callback is called with a NULL call_data argument. The client can release the data allocated by -PreeditStartCallback. +. -PreeditStartCallback + should initialize appropriate data needed for displaying preedit information and for handling further -PreeditDrawCallback + calls. Once -PreeditStartCallback + is called, it will not be called again before -PreeditDoneCallback + has been called. @@ -9003,7 +9003,7 @@ is as follows: PreeditDrawCallback - + void PreeditDrawCallback XIC ic @@ -9390,7 +9390,7 @@ It then calls the PreeditCaretCallback. PreeditCaretCallback - + void PreeditCaretCallback XIC ic @@ -9606,7 +9606,7 @@ the input method calls the StatusStartCallback callback. StatusStartCallback - + void StatusStartCallback XIC ic @@ -9663,7 +9663,7 @@ is destroyed or when it loses focus, the input method calls StatusDoneCallback. StatusDoneCallback - + void StatusDoneCallback XIC ic @@ -9718,7 +9718,7 @@ StatusDrawCallback. StatusDrawCallback - + void StatusDrawCallback XIC ic @@ -9827,13 +9827,13 @@ structure. Xlib provides the ability for an input method to register a filter internal to Xlib. This filter is called by a client (or toolkit) by calling -XFilterEvent + after calling -XNextEvent. +. Any client that uses the XIM interface should call -XFilterEvent + to allow input methods to process their events without knowledge of the client's dispatching mechanism. A client's user interface policy may determine the priority @@ -9845,18 +9845,18 @@ of event filters with respect to other event-handling mechanisms Clients may not know how many filters there are, if any, and what they do. They may only know if an event has been filtered on return of -XFilterEvent. +. Clients should discard filtered events. To filter an event, use -XFilterEvent. +. XFilterEvent - + Bool XFilterEvent XEvent *event @@ -9893,7 +9893,7 @@ Specifies the window (Wi. If the window argument is None, -XFilterEvent + applies the filter to the window specified in the XEvent structure. @@ -9904,13 +9904,13 @@ has been redirected. If -XFilterEvent + returns True, then some input method has filtered the event, and the client should discard the event. If -XFilterEvent + returns False, then the client should continue processing the event. @@ -9918,7 +9918,7 @@ then the client should continue processing the event. If a grab has occurred in the client and -XFilterEvent + returns True, the client should ungrab the keyboard. @@ -9933,14 +9933,14 @@ the client should ungrab the keyboard. To get composed input from an input method, use -XmbLookupString + or -XwcLookupString. +. XmbLookupString XwcLookupString - + int XmbLookupString XIC ic @@ -9952,7 +9952,7 @@ or - + int XwcLookupString XIC ic @@ -10043,9 +10043,9 @@ Returns a value indicating what kind of data is returned. The -XmbLookupString + and -XwcLookupString + functions return the string from the input method specified in the buffer_return argument. If no string is returned, @@ -10061,23 +10061,23 @@ the KeySym value does not necessarily correspond to the string returned. -XmbLookupString + returns the length of the string in bytes, and -XwcLookupString + returns the length of the string in characters. Both -XmbLookupString + and -XwcLookupString + return text in the encoding of the locale bound to the input method of the specified input context. Each string returned by -XmbLookupString + and -XwcLookupString + begins in the initial state of the encoding of the locale (if the encoding of the locale is state-dependent). @@ -10086,9 +10086,9 @@ To insure proper input processing, it is essential that the client pass only KeyPress events to -XmbLookupString + and -XwcLookupString. +. Their behavior when a client passes a KeyRelease event is undefined. @@ -10113,9 +10113,9 @@ The possible values returned are: XBufferOverflow The input string to be returned is too large for the supplied buffer_return. The required size - (XmbLookupString + ( in bytes; - XwcLookupString + in characters) is returned as the value of the function, and the contents of buffer_return and keysym_return are not modified. The client should recall the function with the same event @@ -10157,15 +10157,15 @@ The possible values returned are: It does not make any difference if the input context passed as an argument to -XmbLookupString + and -XwcLookupString + is the one currently in possession of the focus or not. Input may have been composed within an input context before it lost the focus, and that input may be returned on subsequent calls to -XmbLookupString + or -XwcLookupString + even though it does not have any more keyboard focus. @@ -10207,9 +10207,9 @@ A KeyPress event with a KeyCode of zero is used exclusively as a signal that an input method has composed input that can be returned by -XmbLookupString + or -XwcLookupString. +. No other use is made of a KeyPress event with KeyCode of zero. diff --git a/libX11/specs/libX11/CH14.xml b/libX11/specs/libX11/CH14.xml index 20693eb13..5e6f72da7 100644 --- a/libX11/specs/libX11/CH14.xml +++ b/libX11/specs/libX11/CH14.xml @@ -1,7 +1,7 @@ - + Inter-Client Communication Functions The Inter-Client Communication Conventions Manual, hereafter referred to as the ICCCM, @@ -252,17 +252,17 @@ of the root window). Note that the subwindows that you create are ignored by window managers. Therefore, you should use the basic window functions described in -chapter 3 +chapter 3 to manipulate your application's subwindows. To request that a top-level window be iconified, use -XIconifyWindow. +. XIconifyWindow - + Status XIconifyWindow Display *display @@ -307,7 +307,7 @@ Specifies the appropriate screen number on the host server. The -XIconifyWindow + function sends a WM_CHANGE_STATE ClientMessage event with a format of 32 and a first data element of @@ -323,7 +323,7 @@ Window managers may elect to receive this message and if the window is in its normal state, may treat it as a request to change the window's state from normal to iconic. If the WM_CHANGE_STATE property cannot be interned, -XIconifyWindow + does not send a message and returns a zero status. It returns a nonzero status if the client message is sent successfully; otherwise, it returns a zero status. @@ -332,11 +332,11 @@ otherwise, it returns a zero status. To request that a top-level window be withdrawn, use -XWithdrawWindow. +. XWithdrawWindow - + Status XWithdrawWindow Display *display @@ -381,7 +381,7 @@ Specifies the appropriate screen number on the host server. The -XWithdrawWindow + function unmaps the specified window and sends a synthetic UnmapNotify @@ -397,7 +397,7 @@ otherwise, it returns a zero status. -XWithdrawWindow + can generate a BadWindow error. @@ -406,11 +406,11 @@ error. To request that a top-level window be reconfigured, use -XReconfigureWMWindow. +. XReconfigureWMWindow - + Status XReconfigureWMWindow Display *display @@ -481,7 +481,7 @@ structure. The -XReconfigureWMWindow + function issues a ConfigureWindow request on the specified top-level window. @@ -499,7 +499,7 @@ otherwise, it returns a zero status. -XReconfigureWMWindow + can generate BadValue and @@ -577,14 +577,14 @@ typedef enum { To convert a list of text strings to an XTextProperty structure, use -XmbTextListToTextProperty + or -XwcTextListToTextProperty. +. XmbTextListToTextProperty XwcTextListToTextProperty - + int XmbTextListToTextProperty Display *display @@ -595,7 +595,7 @@ or - + int XwcTextListToTextProperty Display *display @@ -664,9 +664,9 @@ structure. The -XmbTextListToTextProperty + and -XwcTextListToTextProperty + functions set the specified XTextProperty value to a set of null-separated elements representing the concatenation @@ -731,7 +731,7 @@ is guaranteed. To free the storage for the value field, use -XFree. +. @@ -739,14 +739,14 @@ To free the storage for the value field, use To obtain a list of text strings from an XTextProperty structure, use -XmbTextPropertyToTextList + or -XwcTextPropertyToTextList. +. XmbTextPropertyToTextList XwcTextPropertyToTextList - + int XmbTextPropertyToTextList Display *display @@ -756,7 +756,7 @@ or - + int XwcTextPropertyToTextList Display *display @@ -815,9 +815,9 @@ Returns the number of (Cn. The -XmbTextPropertyToTextList + and -XwcTextPropertyToTextList + functions return a list of text strings in the current locale representing the null-separated elements of the specified XTextProperty @@ -834,9 +834,9 @@ any terminating null should not be included in text_prop.nitems. If insufficient memory is available for the list and its elements, -XmbTextPropertyToTextList + and -XwcTextPropertyToTextList + return XNoMemory. If the current locale is not supported, @@ -861,9 +861,9 @@ the functions do not set any return values. Otherwise, -XmbTextPropertyToTextList + and -XwcTextPropertyToTextList + return the list of null-terminated text strings to list_return and the number of text strings to count_return. @@ -878,33 +878,33 @@ To obtain the value of this string, use XDefaultString. Otherwise, -XmbTextPropertyToTextList + and -XwcTextPropertyToTextList + return Success. To free the storage for the list and its contents returned by -XmbTextPropertyToTextList, +, use -XFreeStringList. +. To free the storage for the list and its contents returned by -XwcTextPropertyToTextList, +, use -XwcFreeStringList. +. To free the in-memory data associated with the specified wide character string list, use -XwcFreeStringList. +. XwcFreeStringList - + void XwcFreeStringList wchar_t **list @@ -927,9 +927,9 @@ Specifies the list of strings to be freed. The -XwcFreeStringList + function frees memory allocated by -XwcTextPropertyToTextList. +. @@ -946,7 +946,7 @@ The XDefaultString function returns the default string used by Xlib for text conversion (for example, in -XmbTextPropertyToTextList). +). The default string is the string in the current locale that is output when an unconvertible character is found during text conversion. If the string returned by @@ -962,7 +962,7 @@ The string returned by XDefaultString is independent of the default string for text drawing; see -XCreateFontSet + to obtain the default string for an XFontSet. @@ -984,11 +984,11 @@ Until freed, it will not be modified by Xlib. To set the specified list of strings in the STRING encoding to a XTextProperty structure, use -XStringListToTextProperty. +. XStringListToTextProperty - + Status XStringListToTextProperty char **list @@ -1036,7 +1036,7 @@ structure. The -XStringListToTextProperty + function sets the specified XTextProperty to be of type STRING (format 8) with a value representing the @@ -1045,13 +1045,13 @@ An extra null byte (which is not included in the nitems member) is stored at the end of the value field of text_prop_return. The strings are assumed (without verification) to be in the STRING encoding. If insufficient memory is available for the new value string, -XStringListToTextProperty + does not set any fields in the XTextProperty structure and returns a zero status. Otherwise, it returns a nonzero status. To free the storage for the value field, use -XFree. +. @@ -1059,11 +1059,11 @@ To free the storage for the value field, use To obtain a list of strings from a specified XTextProperty structure in the STRING encoding, use -XTextPropertyToStringList. +. XTextPropertyToStringList - + Status XTextPropertyToStringList XTextProperty *text_prop @@ -1111,7 +1111,7 @@ Returns the number of (Cn. The -XTextPropertyToStringList + function returns a list of strings representing the null-separated elements of the specified XTextProperty @@ -1122,21 +1122,21 @@ Multiple elements of the property are separated by NULL (encoding 0). The contents of the property are not null-terminated. If insufficient memory is available for the list and its elements, -XTextPropertyToStringList + sets no return values and returns a zero status. Otherwise, it returns a nonzero status. To free the storage for the list and its contents, use -XFreeStringList. +. To free the in-memory data associated with the specified string list, use -XFreeStringList. +. XFreeStringList - + void XFreeStringList char **list @@ -1159,13 +1159,13 @@ Specifies the list of strings to be freed. The -XFreeStringList + function releases memory allocated by -XmbTextPropertyToTextList + and -XTextPropertyToStringList + and the missing charset list allocated by -XCreateFontSet. +. @@ -1194,11 +1194,11 @@ respectively. To set one of a window's text properties, use -XSetTextProperty. +. XSetTextProperty - + void XSetTextProperty Display *display @@ -1256,7 +1256,7 @@ Specifies the property name. The -XSetTextProperty + function replaces the existing specified property for the named window with the data, type, format, and number of items determined by the value field, the encoding field, the format field, @@ -1264,12 +1264,12 @@ and the nitems field, respectively, of the specified XTextProperty structure. If the property does not already exist, -XSetTextProperty + sets it for the specified window. -XSetTextProperty + can generate BadAlloc, BadAtom, @@ -1282,11 +1282,11 @@ errors. To read one of a window's text properties, use -XGetTextProperty. +. XGetTextProperty - + Status XGetTextProperty Display *display @@ -1344,7 +1344,7 @@ Specifies the property name. The -XGetTextProperty + function reads the specified property from the window and stores the data in the returned XTextProperty @@ -1358,7 +1358,7 @@ is stored at the end of the value field of text_prop_return. The particular interpretation of the property's encoding and data as text is left to the calling application. If the specified property does not exist on the window, -XGetTextProperty + sets the value field to NULL, the encoding field to None, @@ -1370,13 +1370,13 @@ and the nitems field to zero. If it was able to read and store the data in the XTextProperty structure, -XGetTextProperty + returns a nonzero status; otherwise, it returns a zero status. -XGetTextProperty + can generate BadAtom and @@ -1398,11 +1398,11 @@ the WM_NAME property for a given window. To set a window's WM_NAME property with the supplied convenience function, use -XSetWMName. +. XSetWMName - + void XSetWMName Display *display @@ -1449,20 +1449,20 @@ structure to be used. The -XSetWMName + convenience function calls -XSetTextProperty + to set the WM_NAME property. To read a window's WM_NAME property with the supplied convenience function, use -XGetWMName. +. XGetWMName - + Status XGetWMName Display *display @@ -1509,9 +1509,9 @@ structure. The -XGetWMName + convenience function calls -XGetTextProperty + to obtain the WM_NAME property. It returns a nonzero status on success; otherwise, it returns a zero status. @@ -1519,9 +1519,9 @@ otherwise, it returns a zero status. The following two functions have been superseded by -XSetWMName + and -XGetWMName, +, respectively. You can use these additional convenience functions for window names that are encoded as STRING properties. @@ -1530,12 +1530,12 @@ for window names that are encoded as STRING properties. To assign a name to a window, use -XStoreName. +. Windowname XStoreName - + XStoreName Display *display @@ -1581,7 +1581,7 @@ which should be a null-terminated string. The -XStoreName + function assigns the name passed to window_name to the specified window. A window manager can display the window name in some prominent place, such as the title bar, to allow users to identify windows easily. @@ -1593,7 +1593,7 @@ the result is implementation-dependent. -XStoreName + can generate BadAlloc and @@ -1604,11 +1604,11 @@ errors. To get the name of a window, use -XFetchName. +. XFetchName - + Status XFetchName Display *display @@ -1653,25 +1653,25 @@ Returns the window name, which is a null-terminated string. The -XFetchName + function returns the name of the specified window. If it succeeds, it returns a nonzero status; otherwise, no name has been set for the window, and it returns zero. If the WM_NAME property has not been set for this window, -XFetchName + sets window_name_return to NULL. If the data returned by the server is in the Latin Portable Character Encoding, then the returned string is in the Host Portable Character Encoding. Otherwise, the result is implementation-dependent. When finished with it, a client must free the window name string using -XFree. +. -XFetchName + can generate a BadWindow error. @@ -1692,11 +1692,11 @@ the WM_ICON_NAME property for a given window. To set a window's WM_ICON_NAME property, use -XSetWMIconName. +. XSetWMIconName - + void XSetWMIconName Display *display @@ -1743,9 +1743,9 @@ structure to be used. The -XSetWMIconName + convenience function calls -XSetTextProperty + to set the WM_ICON_NAME property. @@ -1753,11 +1753,11 @@ to set the WM_ICON_NAME property. To read a window's WM_ICON_NAME property, use -XGetWMIconName. +. XGetWMIconName - + Status XGetWMIconName Display *display @@ -1804,9 +1804,9 @@ structure. The -XGetWMIconName + convenience function calls -XGetTextProperty + to obtain the WM_ICON_NAME property. It returns a nonzero status on success; otherwise, it returns a zero status. @@ -1814,9 +1814,9 @@ otherwise, it returns a zero status. The next two functions have been superseded by -XSetWMIconName + and -XGetWMIconName, +, respectively. You can use these additional convenience functions for window names that are encoded as STRING properties. @@ -1826,12 +1826,12 @@ for window names that are encoded as STRING properties. To set the name to be displayed in a window's icon, use -XSetIconName. +. Windowicon name XSetIconName - + XSetIconName Display *display @@ -1878,7 +1878,7 @@ which should be a null-terminated string. If the string is not in the Host Portable Character Encoding, the result is implementation-dependent. -XSetIconName + can generate BadAlloc and @@ -1889,11 +1889,11 @@ errors. To get the name a window wants displayed in its icon, use -XGetIconName. +. XGetIconName - + Status XGetIconName Display *display @@ -1939,24 +1939,24 @@ which is a null-terminated string. The -XGetIconName + function returns the name to be displayed in the specified window's icon. If it succeeds, it returns a nonzero status; otherwise, if no icon name has been set for the window, it returns zero. If you never assigned a name to the window, -XGetIconName + sets icon_name_return to NULL. If the data returned by the server is in the Latin Portable Character Encoding, then the returned string is in the Host Portable Character Encoding. Otherwise, the result is implementation-dependent. When finished with it, a client must free the icon name string using -XFree. +. -XGetIconName + can generate a BadWindow error. @@ -2009,7 +2009,7 @@ If insufficient memory is available, returns NULL. To free the memory allocated to this structure, use -XFree. +. @@ -2127,11 +2127,11 @@ or the window to be withdrawn. To set a window's WM_HINTS property, use -XSetWMHints. +. XSetWMHints - + XSetWMHints Display *display @@ -2178,14 +2178,14 @@ structure to be used. The -XSetWMHints + function sets the window manager hints that include icon information and location, the initial state of the window, and whether the application relies on the window manager to get keyboard input. -XSetWMHints + can generate BadAlloc and @@ -2196,11 +2196,11 @@ errors. To read a window's WM_HINTS property, use -XGetWMHints. +. XGetWMHints - + XWMHints *XGetWMHints Display *display @@ -2234,7 +2234,7 @@ Specifies the window. The -XGetWMHints + function reads the window manager hints and returns NULL if no WM_HINTS property was set on the window or returns a pointer to an @@ -2242,11 +2242,11 @@ or returns a pointer to an structure if it succeeds. When finished with the data, free the space used for it by calling -XFree. +. -XGetWMHints + can generate a BadWindow error. @@ -2310,7 +2310,7 @@ If insufficient memory is available, returns NULL. To free the memory allocated to this structure, use -XFree. +. @@ -2393,11 +2393,11 @@ macro is highly discouraged. To set a window's WM_NORMAL_HINTS property, use -XSetWMNormalHints. +. XSetWMNormalHints - + void XSetWMNormalHints Display *display @@ -2442,17 +2442,17 @@ Specifies the size hints for the window in its normal state. The -XSetWMNormalHints + function replaces the size hints for the WM_NORMAL_HINTS property on the specified window. If the property does not already exist, -XSetWMNormalHints + sets the size hints for the WM_NORMAL_HINTS property on the specified window. The property is stored with a type of WM_SIZE_HINTS and a format of 32. -XSetWMNormalHints + can generate BadAlloc and @@ -2463,11 +2463,11 @@ errors. To read a window's WM_NORMAL_HINTS property, use -XGetWMNormalHints. +. XGetWMNormalHints - + Status XGetWMNormalHints Display *display @@ -2523,13 +2523,13 @@ Returns the hints that were supplied by the user. The -XGetWMNormalHints + function returns the size hints stored in the WM_NORMAL_HINTS property on the specified window. If the property is of type WM_SIZE_HINTS, is of format 32, and is long enough to contain either an old (pre-ICCCM) or new size hints structure, -XGetWMNormalHints + sets the various fields of the XSizeHints structure, sets the supplied_return argument to the list of fields @@ -2540,7 +2540,7 @@ Otherwise, it returns a zero status. If -XGetWMNormalHints + returns successfully and a pre-ICCCM size hints property is read, the supplied_return argument will contain the following bits: @@ -2565,7 +2565,7 @@ PBaseSize|PWinGravity -XGetWMNormalHints + can generate a BadWindow error. @@ -2574,11 +2574,11 @@ error. To set a window's WM_SIZE_HINTS property, use -XSetWMSizeHints. +. XSetWMSizeHints - + void XSetWMSizeHints Display *display @@ -2636,22 +2636,22 @@ Specifies the property name. The -XSetWMSizeHints + function replaces the size hints for the specified property on the named window. If the specified property does not already exist, -XSetWMSizeHints + sets the size hints for the specified property on the named window. The property is stored with a type of WM_SIZE_HINTS and a format of 32. To set a window's normal size hints, you can use the -XSetWMNormalHints + function. -XSetWMSizeHints + can generate BadAlloc, BadAtom, @@ -2663,11 +2663,11 @@ errors. To read a window's WM_SIZE_HINTS property, use -XGetWMSizeHints. +. XGetWMSizeHints - + Status XGetWMSizeHints Display *display @@ -2736,13 +2736,13 @@ Specifies the property name. The -XGetWMSizeHints + function returns the size hints stored in the specified property on the named window. If the property is of type WM_SIZE_HINTS, is of format 32, and is long enough to contain either an old (pre-ICCCM) or new size hints structure, -XGetWMSizeHints + sets the various fields of the XSizeHints structure, sets the supplied_return argument to the @@ -2752,13 +2752,13 @@ and returns a nonzero status. Otherwise, it returns a zero status. To get a window's normal size hints, you can use the -XGetWMNormalHints + function. If -XGetWMSizeHints + returns successfully and a pre-ICCCM size hints property is read, the supplied_return argument will contain the following bits: @@ -2783,7 +2783,7 @@ PBaseSize|PWinGravity -XGetWMSizeHints + can generate BadAtom and @@ -2840,7 +2840,7 @@ If insufficient memory is available, returns NULL. To free the memory allocated to this structure, use -XFree. +. @@ -2879,11 +2879,11 @@ resource database. To set a window's WM_CLASS property, use -XSetClassHint. +. XSetClassHint - + XSetClassHint Display *display @@ -2930,14 +2930,14 @@ structure that is to be used. The -XSetClassHint + function sets the class hint for the specified window. If the strings are not in the Host Portable Character Encoding, the result is implementation-dependent. -XSetClassHint + can generate BadAlloc and @@ -2948,11 +2948,11 @@ errors. To read a window's WM_CLASS property, use -XGetClassHint. +. XGetClassHint - + Status XGetClassHint Display *display @@ -2999,7 +2999,7 @@ structure. The -XGetClassHint + function returns the class hint of the specified window to the members of the supplied structure. If the data returned by the server is in the Latin Portable Character Encoding, @@ -3009,12 +3009,12 @@ It returns a nonzero status on success; otherwise, it returns a zero status. To free res_name and res_class when finished with the strings, use -XFree + on each individually. -XGetClassHint + can generate a BadWindow error. @@ -3034,11 +3034,11 @@ the WM_TRANSIENT_FOR property for a given window. To set a window's WM_TRANSIENT_FOR property, use -XSetTransientForHint. +. XSetTransientForHint - + XSetTransientForHint Display *display @@ -3083,13 +3083,13 @@ Specifies the window that the WM_TRANSIENT_FOR property is The -XSetTransientForHint + function sets the WM_TRANSIENT_FOR property of the specified window to the specified prop_window. -XSetTransientForHint + can generate BadAlloc and @@ -3100,11 +3100,11 @@ errors. To read a window's WM_TRANSIENT_FOR property, use -XGetTransientForHint. +. XGetTransientForHint - + Status XGetTransientForHint Display *display @@ -3149,14 +3149,14 @@ Returns the WM_TRANSIENT_FOR property of the specified wind The -XGetTransientForHint + function returns the WM_TRANSIENT_FOR property for the specified window. It returns a nonzero status on success; otherwise, it returns a zero status. -XGetTransientForHint + can generate a BadWindow error. @@ -3176,11 +3176,11 @@ the WM_PROTOCOLS property for a given window. To set a window's WM_PROTOCOLS property, use -XSetWMProtocols. +. XSetWMProtocols - + Status XSetWMProtocols Display *display @@ -3237,22 +3237,22 @@ Specifies the number of (Cn. The -XSetWMProtocols + function replaces the WM_PROTOCOLS property on the specified window with the list of atoms specified by the protocols argument. If the property does not already exist, -XSetWMProtocols + sets the WM_PROTOCOLS property on the specified window to the list of atoms specified by the protocols argument. The property is stored with a type of ATOM and a format of 32. If it cannot intern the WM_PROTOCOLS atom, -XSetWMProtocols + returns a zero status. Otherwise, it returns a nonzero status. -XSetWMProtocols + can generate BadAlloc and @@ -3263,11 +3263,11 @@ errors. To read a window's WM_PROTOCOLS property, use -XGetWMProtocols. +. XGetWMProtocols - + Status XGetWMProtocols Display *display @@ -3324,25 +3324,25 @@ Returns the number of (Cn. The -XGetWMProtocols + function returns the list of atoms stored in the WM_PROTOCOLS property on the specified window. These atoms describe window manager protocols in which the owner of this window is willing to participate. If the property exists, is of type ATOM, is of format 32, and the atom WM_PROTOCOLS can be interned, -XGetWMProtocols + sets the protocols_return argument to a list of atoms, sets the count_return argument to the number of elements in the list, and returns a nonzero status. Otherwise, it sets neither of the return arguments and returns a zero status. To release the list of atoms, use -XFree. +. -XGetWMProtocols + can generate a BadWindow error. @@ -3362,11 +3362,11 @@ the WM_COLORMAP_WINDOWS property for a given window. To set a window's WM_COLORMAP_WINDOWS property, use -XSetWMColormapWindows. +. XSetWMColormapWindows - + Status XSetWMColormapWindows Display *display @@ -3423,22 +3423,22 @@ Specifies the number of (Cn. The -XSetWMColormapWindows + function replaces the WM_COLORMAP_WINDOWS property on the specified window with the list of windows specified by the colormap_windows argument. If the property does not already exist, -XSetWMColormapWindows + sets the WM_COLORMAP_WINDOWS property on the specified window to the list of windows specified by the colormap_windows argument. The property is stored with a type of WINDOW and a format of 32. If it cannot intern the WM_COLORMAP_WINDOWS atom, -XSetWMColormapWindows + returns a zero status. Otherwise, it returns a nonzero status. -XSetWMColormapWindows + can generate BadAlloc and @@ -3449,11 +3449,11 @@ errors. To read a window's WM_COLORMAP_WINDOWS property, use -XGetWMColormapWindows. +. XGetWMColormapWindows - + Status XGetWMColormapWindows Display *display @@ -3510,25 +3510,25 @@ Returns the number of (Cn. The -XGetWMColormapWindows + function returns the list of window identifiers stored in the WM_COLORMAP_WINDOWS property on the specified window. These identifiers indicate the colormaps that the window manager may need to install for this window. If the property exists, is of type WINDOW, is of format 32, and the atom WM_COLORMAP_WINDOWS can be interned, -XGetWMColormapWindows + sets the windows_return argument to a list of window identifiers, sets the count_return argument to the number of elements in the list, and returns a nonzero status. Otherwise, it sets neither of the return arguments and returns a zero status. To release the list of window identifiers, use -XFree. +. -XGetWMColormapWindows + can generate a BadWindow error. @@ -3582,7 +3582,7 @@ If insufficient memory is available, returns NULL. To free the memory allocated to this structure, use -XFree. +. @@ -3614,11 +3614,11 @@ sizes (minimum to maximum) that represent the supported icon sizes. To set a window's WM_ICON_SIZE property, use -XSetIconSizes. +. XSetIconSizes - + XSetIconSizes Display *display @@ -3674,12 +3674,12 @@ Specifies the number of items in the size list. The -XSetIconSizes + function is used only by window managers to set the supported icon sizes. -XSetIconSizes + can generate BadAlloc and @@ -3690,11 +3690,11 @@ errors. To read a window's WM_ICON_SIZE property, use -XGetIconSizes. +. XGetIconSizes - + Status XGetIconSizes Display *display @@ -3750,24 +3750,24 @@ Returns the number of items in the size list. The -XGetIconSizes + function returns zero if a window manager has not set icon sizes; otherwise, it returns nonzero. -XGetIconSizes + should be called by an application that wants to find out what icon sizes would be most appreciated by the window manager under which the application is running. The application should then use -XSetWMHints + to supply the window manager with an icon pixmap or window in one of the supported sizes. To free the data allocated in size_list_return, use -XFree. +. -XGetIconSizes + can generate a BadWindow error. @@ -3781,7 +3781,7 @@ error. The -XmbSetWMProperties + function stores the standard set of window manager properties, with text properties in standard encodings for internationalized text communication. @@ -3791,7 +3791,7 @@ The standard window manager properties for a given window are XmbSetWMProperties - + void XmbSetWMProperties Display *display @@ -3908,7 +3908,7 @@ structure to be used. The -XmbSetWMProperties + convenience function provides a simple programming interface for setting those essential window properties that are used for communicating with other clients @@ -3917,10 +3917,10 @@ for communicating with other clients If the window_name argument is non-NULL, -XmbSetWMProperties + sets the WM_NAME property. If the icon_name argument is non-NULL, -XmbSetWMProperties + sets the WM_ICON_NAME property. The window_name and icon_name arguments are null-terminated strings in the encoding of the current locale. @@ -3932,35 +3932,35 @@ and the properties are created with type ``COMPOUND_TEXT''. If the normal_hints argument is non-NULL, -XmbSetWMProperties + calls -XSetWMNormalHints, +, which sets the WM_NORMAL_HINTS property (see section 14.1.7). If the wm_hints argument is non-NULL, -XmbSetWMProperties + calls -XSetWMHints, +, which sets the WM_HINTS property (see section 14.1.6). If the argv argument is non-NULL, -XmbSetWMProperties + sets the WM_COMMAND property from argv and argc. An argc of zero indicates a zero-length command. The hostname of the machine is stored using -XSetWMClientMachine + (see section 14.2.2). If the class_hints argument is non-NULL, -XmbSetWMProperties + sets the WM_CLASS property. If the res_name member in the XClassHint @@ -3985,14 +3985,14 @@ No encoding conversion is performed prior to storage in the properties. For clients that need to process the property text in a locale, -XmbSetWMProperties + sets the WM_LOCALE_NAME property to be the name of the current locale. The name is assumed to be in the Host Portable Character Encoding and is converted to STRING for storage in the property. -XmbSetWMProperties + can generate BadAlloc and @@ -4004,14 +4004,14 @@ errors. To set a window's standard window manager properties with strings in client-specified encodings, use -XSetWMProperties. +. The standard window manager properties for a given window are WM_NAME, WM_ICON_NAME, WM_HINTS, WM_NORMAL_HINTS, WM_CLASS, WM_COMMAND, and WM_CLIENT_MACHINE. XSetWMProperties - + void XSetWMProperties Display *display @@ -4128,7 +4128,7 @@ structure to be used. The -XSetWMProperties + convenience function provides a single programming interface for setting those essential window properties that are used for communicating with other clients (particularly window and session @@ -4137,49 +4137,49 @@ managers). If the window_name argument is non-NULL, -XSetWMProperties + calls -XSetWMName, +, which, in turn, sets the WM_NAME property (see section 14.1.4). If the icon_name argument is non-NULL, -XSetWMProperties + calls -XSetWMIconName, +, which sets the WM_ICON_NAME property (see section 14.1.5). If the argv argument is non-NULL, -XSetWMProperties + calls -XSetCommand, +, which sets the WM_COMMAND property (see section 14.2.1). Note that an argc of zero is allowed to indicate a zero-length command. Note also that the hostname of this machine is stored using -XSetWMClientMachine + (see section 14.2.2). If the normal_hints argument is non-NULL, -XSetWMProperties + calls -XSetWMNormalHints, +, which sets the WM_NORMAL_HINTS property (see section 14.1.7). If the wm_hints argument is non-NULL, -XSetWMProperties + calls -XSetWMHints, +, which sets the WM_HINTS property (see section 14.1.6). If the class_hints argument is non-NULL, -XSetWMProperties + calls -XSetClassHint, +, which sets the WM_CLASS property (see section 14.1.8). If the res_name member in the @@ -4195,7 +4195,7 @@ any directory prefixes, is substituted for res_name. -XSetWMProperties + can generate BadAlloc and @@ -4239,11 +4239,11 @@ the WM_COMMAND property for a given window. To set a window's WM_COMMAND property, use -XSetCommand. +. XSetCommand - + XSetCommand Display *display @@ -4299,7 +4299,7 @@ Specifies the number of arguments. The -XSetCommand + function sets the command and arguments used to invoke the application. (Typically, argv is the argv array of your main program.) @@ -4308,7 +4308,7 @@ the result is implementation-dependent. -XSetCommand + can generate BadAlloc and @@ -4319,11 +4319,11 @@ errors. To read a window's WM_COMMAND property, use -XGetCommand. +. XGetCommand - + Status XGetCommand Display *display @@ -4379,13 +4379,13 @@ Returns the number of arguments returned. The -XGetCommand + function reads the WM_COMMAND property from the specified window and returns a string list. If the WM_COMMAND property exists, it is of type STRING and format 8. If sufficient memory can be allocated to contain the string list, -XGetCommand + fills in the argv_return and argc_return arguments and returns a nonzero status. Otherwise, it returns a zero status. @@ -4393,7 +4393,7 @@ If the data returned by the server is in the Latin Portable Character Encoding, then the returned strings are in the Host Portable Character Encoding. Otherwise, the result is implementation-dependent. To free the memory allocated to the string list, use -XFreeStringList. +. @@ -4410,11 +4410,11 @@ the WM_CLIENT_MACHINE property for a given window. To set a window's WM_CLIENT_MACHINE property, use -XSetWMClientMachine. +. XSetWMClientMachine - + void XSetWMClientMachine Display *display @@ -4461,20 +4461,20 @@ structure to be used. The -XSetWMClientMachine + convenience function calls -XSetTextProperty + to set the WM_CLIENT_MACHINE property. To read a window's WM_CLIENT_MACHINE property, use -XGetWMClientMachine. +. XGetWMClientMachine - + Status XGetWMClientMachine Display *display @@ -4521,9 +4521,9 @@ structure. The -XGetWMClientMachine + convenience function performs an -XGetTextProperty + on the WM_CLIENT_MACHINE property. It returns a nonzero status on success; otherwise, it returns a zero status. @@ -4659,7 +4659,7 @@ If insufficient memory is available, returns NULL. To free the memory allocated to this structure, use -XFree. +. @@ -4692,7 +4692,7 @@ typedef struct { The colormap member is the colormap created by the -XCreateColormap + function. The red_max, green_max, and blue_max members give the maximum red, green, and blue values, respectively. @@ -4720,7 +4720,7 @@ green_mult might be 6, and blue_mult might be 1. The base_pixel member gives the base pixel value used to compose a full pixel value. Usually, the base_pixel is obtained from a call to the -XAllocColorPlanes + function. Given integer red, green, and blue coefficients in their appropriate ranges, one then can compute a corresponding pixel value by @@ -4771,7 +4771,7 @@ colormap was created. The killid member gives a resource ID that indicates whether the cells held by this standard colormap are to be released by freeing the colormap ID or by calling the -XKillClient + function on the indicated resource. (Note that this method is necessary for allocating out of an existing colormap.) @@ -4932,11 +4932,11 @@ structure. To set an XStandardColormap structure, use -XSetRGBColormaps. +. XSetRGBColormaps - + void XSetRGBColormaps Display *display @@ -5006,11 +5006,11 @@ Specifies the property name. The -XSetRGBColormaps + function replaces the RGB colormap definition in the specified property on the named window. If the property does not already exist, -XSetRGBColormaps + sets the RGB colormap definition in the specified property on the named window. The property is stored with a type of RGB_COLOR_MAP and a format of 32. @@ -5020,7 +5020,7 @@ restriction that only RGB_DEFAULT_MAP contain more than one definition. The -XSetRGBColormaps + function usually is only used by window or session managers. To create a standard colormap, follow this procedure: @@ -5066,7 +5066,7 @@ Allocate cells in the colormap (or create it with Call -XStoreColors + to store appropriate color values in the colormap. @@ -5085,7 +5085,7 @@ Attach the property to the root window. Use -XSetCloseDownMode + to make the resource permanent. @@ -5098,7 +5098,7 @@ Ungrab the server. -XSetRGBColormaps + can generate BadAlloc, BadAtom, @@ -5112,11 +5112,11 @@ errors. To obtain the XStandardColormap structure associated with the specified property, use -XGetRGBColormaps. +. XGetRGBColormaps - + Status XGetRGBColormaps Display *display @@ -5186,30 +5186,30 @@ Specifies the property name. The -XGetRGBColormaps + function returns the RGB colormap definitions stored in the specified property on the named window. If the property exists, is of type RGB_COLOR_MAP, is of format 32, and is long enough to contain a colormap definition, -XGetRGBColormaps + allocates and fills in space for the returned colormaps and returns a nonzero status. If the visualid is not present, -XGetRGBColormaps + assumes the default visual for the screen on which the window is located; if the killid is not present, None is assumed, which indicates that the resources cannot be released. Otherwise, none of the fields are set, and -XGetRGBColormaps + returns a zero status. Note that it is the caller's responsibility to honor the ICCCM restriction that only RGB_DEFAULT_MAP contain more than one definition. -XGetRGBColormaps + can generate BadAtom and diff --git a/libX11/specs/libX11/CH15.xml b/libX11/specs/libX11/CH15.xml index 3c4a29695..f6c76a481 100644 --- a/libX11/specs/libX11/CH15.xml +++ b/libX11/specs/libX11/CH15.xml @@ -1,7 +1,7 @@ - + Resource Manager Functions @@ -406,7 +406,7 @@ typedef XrmQuarkList XrmClassList; To convert a string to a quark, use -XrmStringToQuark + or XrmPermStringToQuark. @@ -419,7 +419,7 @@ or XrmStringToQuark XrmPermStringToQuark - + XrmQuark XrmStringToQuark char *string @@ -446,20 +446,20 @@ These functions can be used to convert from string to quark representation. If the string is not in the Host Portable Character Encoding, the conversion is implementation-dependent. The string argument to -XrmStringToQuark + need not be permanently allocated storage. XrmPermStringToQuark is just like -XrmStringToQuark, +, except that Xlib is permitted to assume the string argument is permanently allocated, and, hence, that it can be used as the value to be returned by -XrmQuarkToString. +. For any given quark, if -XrmStringToQuark + returns a non-NULL value, all future calls will return the same value (identical address). @@ -467,7 +467,7 @@ all future calls will return the same value (identical address). To convert a quark to a string, use -XrmQuarkToString. +. @@ -477,7 +477,7 @@ To convert a quark to a string, use XrmQuarkToString - + char *XrmQuarkToString XrmQuark quark @@ -503,10 +503,10 @@ The string pointed to by the return value must not be modified or freed. The returned string is byte-for-byte equal to the original string passed to one of the string-to-quark routines. If no string exists for that quark, -XrmQuarkToString + returns NULL. For any given quark, if -XrmQuarkToString + returns a non-NULL value, all future calls will return the same value (identical address). @@ -514,7 +514,7 @@ all future calls will return the same value (identical address). To convert a string with one or more components to a quark list, use -XrmStringToQuarkList. +. @@ -524,7 +524,7 @@ To convert a string with one or more components to a quark list, use XrmStringToQuarkList - + void XrmStringToQuarkList char *string @@ -552,7 +552,7 @@ Specifies the string for which a quark(Ql is to be allocated. Returns the list of quarks. The caller must allocate sufficient space for the quarks list before calling -XrmStringToQuarkList. +. @@ -562,7 +562,7 @@ The caller must allocate sufficient space for the quarks list before calling The -XrmStringToQuarkList + function converts the null-terminated string (generally a fully qualified name) to a list of quarks. Note that the string must be in the valid ResourceName format @@ -595,11 +595,11 @@ indicates that an asterisk separates the components. To convert a string with one or more components to a binding list and a quark list, use -XrmStringToBindingQuarkList. +. XrmStringToBindingQuarkList - + XrmStringToBindingQuarkList char *string @@ -628,7 +628,7 @@ Specifies the string for which a quark(Ql is to be allocated. Returns the binding list. The caller must allocate sufficient space for the binding list before calling -XrmStringToBindingQuarkList. +. @@ -640,7 +640,7 @@ The caller must allocate sufficient space for the binding list before calling Returns the list of quarks. The caller must allocate sufficient space for the quarks list before calling -XrmStringToBindingQuarkList. +. @@ -706,10 +706,10 @@ typedef struct { To initialize the resource manager, use -XrmInitialize. +. XrmInitialize - + void XrmInitialize void XrmInitialize(\|) @@ -721,11 +721,11 @@ To initialize the resource manager, use To retrieve a database from disk, use -XrmGetFileDatabase. +. XrmGetFileDatabase - + XrmDatabase XrmGetFileDatabase char *filename @@ -748,7 +748,7 @@ Specifies the resource database file name. The -XrmGetFileDatabase + function opens the specified file, creates a new resource database, and loads it with the specifications read in from the specified file. @@ -759,18 +759,18 @@ with incorrect syntax is implementation-dependent. The file is parsed in the current locale, and the database is created in the current locale. If it cannot open the specified file, -XrmGetFileDatabase + returns NULL. To store a copy of a database to disk, use -XrmPutFileDatabase. +. XrmPutFileDatabase - + void XrmPutFileDatabase XrmDatabase database @@ -804,7 +804,7 @@ Specifies the file name for the stored database. The -XrmPutFileDatabase + function stores a copy of the specified database in the specified file. Text is written to the file as a sequence of entries in valid ResourceLine format @@ -820,11 +820,11 @@ Entries with representation types other than ``String'' are ignored. To obtain a pointer to the screen-independent resources of a display, use -XResourceManagerString. +. XResourceManagerString - + char *XResourceManagerString Display *display @@ -847,28 +847,28 @@ Specifies the connection to the X server. The -XResourceManagerString + function returns the RESOURCE_MANAGER property from the server's root window of screen zero, which was returned when the connection was opened using -XOpenDisplay. +. The property is converted from type STRING to the current locale. The conversion is identical to that produced by -XmbTextPropertyToTextList + for a single element STRING property. The returned string is owned by Xlib and should not be freed by the client. The property value must be in a format that is acceptable to -XrmGetStringDatabase. +. If no property exists, NULL is returned. To obtain a pointer to the screen-specific resources of a screen, use -XScreenResourceString. +. XScreenResourceString - + char *XScreenResourceString Screen *screen @@ -891,28 +891,28 @@ Specifies the screen. The -XScreenResourceString + function returns the SCREEN_RESOURCES property from the root window of the specified screen. The property is converted from type STRING to the current locale. The conversion is identical to that produced by -XmbTextPropertyToTextList + for a single element STRING property. The property value must be in a format that is acceptable to -XrmGetStringDatabase. +. If no property exists, NULL is returned. The caller is responsible for freeing the returned string by using -XFree. +. To create a database from a string, use -XrmGetStringDatabase. +. XrmGetStringDatabase - + XrmDatabase XrmGetStringDatabase char *data @@ -935,12 +935,12 @@ Specifies the database contents using a string. The -XrmGetStringDatabase + function creates a new database and stores the resources specified in the specified null-terminated string. -XrmGetStringDatabase + is similar to -XrmGetFileDatabase + except that it reads the information out of a string instead of out of a file. The string should contain a sequence of entries in valid ResourceLine format (see section 15.1) @@ -954,11 +954,11 @@ and the database is created in the current locale. To obtain the locale name of a database, use -XrmLocaleOfDatabase. +. XrmLocaleOfDatabase - + char *XrmLocaleOfDatabase XrmDatabase database @@ -981,7 +981,7 @@ Specifies the resource database. The -XrmLocaleOfDatabase + function returns the name of the locale bound to the specified database, as a null-terminated string. The returned locale name string is owned by Xlib and should not be @@ -994,11 +994,11 @@ it will not be modified by Xlib. To destroy a resource database and free its allocated memory, use -XrmDestroyDatabase. +. XrmDestroyDatabase - + void XrmDestroyDatabase XrmDatabase database @@ -1021,18 +1021,18 @@ Specifies the resource database. If database is NULL, -XrmDestroyDatabase + returns immediately. To associate a resource database with a display, use -XrmSetDatabase. +. XrmSetDatabase - + void XrmSetDatabase Display *display @@ -1066,7 +1066,7 @@ Specifies the resource database. The -XrmSetDatabase + function associates the specified resource database (or NULL) with the specified display. The database previously associated with the display (if any) is not destroyed. @@ -1077,11 +1077,11 @@ once it is constructed. To get the resource database associated with a display, use -XrmGetDatabase. +. XrmGetDatabase - + XrmDatabase XrmGetDatabase Display *display @@ -1104,7 +1104,7 @@ Specifies the connection to the X server. The -XrmGetDatabase + function returns the database associated with the specified display. It returns NULL if a database has not yet been set. @@ -1117,11 +1117,11 @@ It returns NULL if a database has not yet been set. To merge the contents of a resource file into a database, use -XrmCombineFileDatabase. +. XrmCombineFileDatabase - + Status XrmCombineFileDatabase char *filename @@ -1167,7 +1167,7 @@ Specifies whether source entries override target ones. The -XrmCombineFileDatabase + function merges the contents of a resource file into a database. If the same specifier is used for an entry in both the file and the database, @@ -1180,7 +1180,7 @@ If the file cannot be read, a zero status is returned; otherwise, a nonzero status is returned. If target_db contains NULL, -XrmCombineFileDatabase + creates and returns a new database to it. Otherwise, the database pointed to by target_db is not destroyed by the merge. The database entries are merged without changing values or types, @@ -1191,11 +1191,11 @@ The locale of the target database is not modified. To merge the contents of one database into another database, use -XrmCombineDatabase. +. XrmCombineDatabase - + void XrmCombineDatabase XrmDatabasesource_db, *target_db @@ -1240,7 +1240,7 @@ Specifies whether source entries override target ones. The -XrmCombineDatabase + function merges the contents of one database into another. If the same specifier is used for an entry in both databases, the entry in the source_db will replace the entry in the target_db @@ -1248,7 +1248,7 @@ if override is True; otherwise, the entry in source_db is discarded. If target_db contains NULL, -XrmCombineDatabase + simply stores source_db in it. Otherwise, source_db is destroyed by the merge, but the database pointed to by target_db is not destroyed. @@ -1261,11 +1261,11 @@ The locale of the target database is not modified. To merge the contents of one database into another database with override semantics, use -XrmMergeDatabases. +. XrmMergeDatabases - + void XrmMergeDatabases XrmDatabasesource_db, *target_db @@ -1299,9 +1299,9 @@ database is to be merged. Calling the -XrmMergeDatabases + function is equivalent to calling the -XrmCombineDatabase + function with an override argument of True. @@ -1314,14 +1314,14 @@ function with an override argument of To retrieve a resource from a resource database, use -XrmGetResource, -XrmQGetResource, +, +, or -XrmQGetSearchResource. +. XrmGetResource - + Bool XrmGetResource XrmDatabase database @@ -1386,7 +1386,7 @@ Returns the value in the database. XrmQGetResource - + Bool XrmQGetResource XrmDatabase database @@ -1453,9 +1453,9 @@ Returns the value in the database. The -XrmGetResource + and -XrmQGetResource + functions retrieve a resource from the specified database. Both take a fully qualified name/class pair, a destination resource representation, and the address of a value @@ -1466,17 +1466,17 @@ therefore, you must not modify the data. The database only frees or overwrites entries on -XrmPutResource, -XrmQPutResource, +, +, or -XrmMergeDatabases. +. A client that is not storing new values into the database or is not merging the database should be safe using the address passed back at any time until it exits. If a resource was found, both -XrmGetResource + and -XrmQGetResource + return True; otherwise, they return @@ -1491,7 +1491,7 @@ The X toolkit access pattern for a resource database is quite stylized. A series of from 1 to 20 probes is made with only the last name/class differing in each probe. The -XrmGetResource + function is at worst a 2n algorithm, where n is the length of the name/class list. @@ -1506,7 +1506,7 @@ To obtain a list of database levels, use XrmQGetSearchList - + Bool XrmQGetSearchResource XrmDatabase database @@ -1580,7 +1580,7 @@ function takes a list of names and classes and returns a list of database levels where a match might occur. The returned list is in best-to-worst order and uses the same algorithm as -XrmGetResource + for determining precedence. If list_return was large enough for the search list, XrmQGetSearchList @@ -1611,11 +1611,11 @@ only the common prefix should be specified in the name and class list to To search resource database levels for a given resource, use -XrmQGetSearchResource. +. XrmQGetSearchResource - + Bool XrmQGetSearchResource XrmSearchList list @@ -1683,11 +1683,11 @@ Returns the value in the database. The -XrmQGetSearchResource + function searches the specified database levels for the resource that is fully identified by the specified name and class. The search stops with the first match. -XrmQGetSearchResource + returns True if the resource was found; @@ -1700,11 +1700,11 @@ A call to XrmQGetSearchList with a name and class list containing all but the last component of a resource name followed by a call to -XrmQGetSearchResource + with the last component name and class returns the same database entry as -XrmGetResource + and -XrmQGetResource + with the fully qualified name and class. @@ -1716,9 +1716,9 @@ with the fully qualified name and class. To store resources into the database, use -XrmPutResource + or -XrmQPutResource. +. Both functions take a partial resource specification, a representation type, and a value. This value is copied into the specified database. @@ -1727,7 +1727,7 @@ This value is copied into the specified database. XrmPutResource - + void XrmPutResource XrmDatabase *database @@ -1783,11 +1783,11 @@ Specifies the value of the resource, which is specified as a string. If database contains NULL, -XrmPutResource + creates a new database and returns a pointer to it. -XrmPutResource + is a convenience function that calls -XrmStringToBindingQuarkList + followed by: @@ -1803,7 +1803,7 @@ The value is stored in the database without modification. XrmQPutResource - + void XrmQPutResource XrmDatabase *database @@ -1870,7 +1870,7 @@ Specifies the value of the resource, which is specified as a string. If database contains NULL, -XrmQPutResource + creates a new database and returns a pointer to it. If a resource entry with the identical bindings and quarks already exists in the database, the previous type and value are replaced by the new @@ -1881,11 +1881,11 @@ The value is stored in the database without modification. To add a resource that is specified as a string, use -XrmPutStringResource. +. XrmPutStringResource - + void XrmPutStringResource XrmDatabase *database @@ -1930,15 +1930,15 @@ Specifies the value of the resource, which is specified as a string. If database contains NULL, -XrmPutStringResource + creates a new database and returns a pointer to it. -XrmPutStringResource + adds a resource with the specified value to the specified database. -XrmPutStringResource + is a convenience function that first calls -XrmStringToBindingQuarkList + on the specifier and then calls -XrmQPutResource, +, using a ``String'' representation type. If the specifier is not in the Host Portable Character Encoding, the result is implementation-dependent. @@ -1948,11 +1948,11 @@ The value is stored in the database without modification. To add a string resource using quarks as a specification, use -XrmQPutStringResource. +. XrmQPutStringResource - + void XrmQPutStringResource XrmDatabase *database @@ -2008,16 +2008,16 @@ Specifies the value of the resource, which is specified as a string. If database contains NULL, -XrmQPutStringResource + creates a new database and returns a pointer to it. -XrmQPutStringResource + is a convenience routine that constructs an XrmValue for the value string (by calling strlen to compute the size) and then calls -XrmQPutResource, +, using a ``String'' representation type. The value is stored in the database without modification. @@ -2026,11 +2026,11 @@ The value is stored in the database without modification. To add a single resource entry that is specified as a string that contains both a name and a value, use -XrmPutLineResource. +. XrmPutLineResource - + void XrmPutLineResource XrmDatabase *database @@ -2064,9 +2064,9 @@ Specifies the resource name and value pair as a single string. If database contains NULL, -XrmPutLineResource + creates a new database and returns a pointer to it. -XrmPutLineResource + adds a single resource entry to the specified database. The line should be in valid ResourceLine format (see section 15.1) @@ -2089,7 +2089,7 @@ Note that comment lines are not stored. To enumerate the entries of a database, use -XrmEnumerateDatabase. +. XrmEnumerateDatabase @@ -2099,7 +2099,7 @@ To enumerate the entries of a database, use #define XrmEnumOneLevel 0 - + Bool XrmEnumerateDatabase XrmDatabase database @@ -2178,7 +2178,7 @@ Specifies the user-supplied argument that will be passed to the procedure. The -XrmEnumerateDatabase + function calls the specified procedure for each resource in the database that would match some completion of the given name/class resource prefix. The order in which resources are found is implementation-dependent. @@ -2241,7 +2241,7 @@ Xlib function using the same database is not defined. The -XrmParseCommand + function can be used to parse the command line arguments to a program and modify a resource database with selected entries from the command line. @@ -2300,11 +2300,11 @@ typedef struct { To load a resource database from a C command line, use -XrmParseCommand. +. XrmParseCommand - + void XrmParseCommand XrmDatabase *database @@ -2383,12 +2383,12 @@ and returns the remaining arguments. The -XrmParseCommand + function parses an (argc, argv) pair according to the specified option table, loads recognized options into the specified database with type ``String,'' and modifies the (argc, argv) pair to remove all recognized options. If database contains NULL, -XrmParseCommand + creates a new database and returns a pointer to it. Otherwise, entries are added to the database specified. If a database is created, it is created in the current locale. diff --git a/libX11/specs/libX11/CH16.xml b/libX11/specs/libX11/CH16.xml index 01f25d4b4..e70b79939 100644 --- a/libX11/specs/libX11/CH16.xml +++ b/libX11/specs/libX11/CH16.xml @@ -1,7 +1,7 @@ - + Application Utility Functions @@ -97,11 +97,11 @@ use the functions described in section 12.7. To obtain a KeySym for the KeyCode of an event, use -XLookupKeysym. +. XLookupKeysym - + KeySym XLookupKeysym XKeyEvent *key_event @@ -139,7 +139,7 @@ Specifies the index into the KeySyms list for the event's KeyCode. The -XLookupKeysym + function uses a given keyboard event and the index you specified to return the KeySym from the list that corresponds to the KeyCode member in the XKeyPressedEvent @@ -147,7 +147,7 @@ or XKeyReleasedEvent structure. If no KeySym is defined for the KeyCode of the event, -XLookupKeysym + returns NoSymbol. @@ -155,11 +155,11 @@ returns To obtain a KeySym for a specific KeyCode, use -XKeycodeToKeysym. +. XKeycodeToKeysym - + KeySym XKeycodeToKeysym Display *display @@ -204,12 +204,12 @@ Specifies the element of KeyCode vector. The -XKeycodeToKeysym + function uses internal Xlib tables and returns the KeySym defined for the specified KeyCode and the element of the KeyCode vector. If no symbol is defined, -XKeycodeToKeysym + returns NoSymbol. @@ -217,11 +217,11 @@ returns To obtain a KeyCode for a key having a specific KeySym, use -XKeysymToKeycode. +. XKeysymToKeycode - + KeyCode XKeysymToKeycode Display *display @@ -255,7 +255,7 @@ Specifies the KeySym that is to be searched for. If the specified KeySym is not defined for any KeyCode, -XKeysymToKeycode + returns zero. @@ -265,11 +265,11 @@ The mapping between KeyCodes and KeySyms is cached internal to Xlib. When this information is changed at the server, an Xlib function must be called to refresh the cache. To refresh the stored modifier and keymap information, use -XRefreshKeyboardMapping. +. XRefreshKeyboardMapping - + XRefreshKeyboardMapping XMappingEvent *event_map @@ -292,7 +292,7 @@ Specifies the mapping event that is to be used. The -XRefreshKeyboardMapping + function refreshes the stored modifier and keymap information. You usually call this function when a MappingNotify @@ -307,11 +307,11 @@ The result is to update Xlib's knowledge of the keyboard. To obtain the uppercase and lowercase forms of a KeySym, use -XConvertCase. +. XConvertCase - + void XConvertCase KeySym keysym @@ -357,7 +357,7 @@ Returns the uppercase form of keysym, or keysym. The -XConvertCase + function returns the uppercase and lowercase forms of the specified Keysym, if the KeySym is subject to case conversion; otherwise, the specified KeySym is returned to both lower_return and @@ -370,11 +370,11 @@ implementation-dependent. KeySyms have string names as well as numeric codes. To convert the name of the KeySym to the KeySym code, use -XStringToKeysym. +. XStringToKeysym - + KeySym XStringToKeysym char *string @@ -412,7 +412,7 @@ and the mechanisms by which Xlib obtains them is implementation-dependent. If the KeySym name is not in the Host Portable Character Encoding, the result is implementation-dependent. If the specified string does not match a valid KeySym, -XStringToKeysym + returns NoSymbol. @@ -420,11 +420,11 @@ returns To convert a KeySym code to the name of the KeySym, use -XKeysymToString. +. XKeysymToString - + char *XKeysymToString KeySym keysym @@ -450,7 +450,7 @@ Specifies the KeySym that is to be (Fn. The returned string is in a static area and must not be modified. The returned string is in the Host Portable Character Encoding. If the specified KeySym is not defined, -XKeysymToString + returns a NULL. @@ -648,19 +648,19 @@ if the specified KeySym is a PF key. - + Using Latin-1 Keyboard Event Functions -Chapter 13 +Chapter 13 describes internationalized text input facilities, but sometimes it is expedient to write an application that only deals with Latin-1 characters and ASCII controls, so Xlib provides a simple function for that purpose. -XLookupString + handles the standard modifier semantics described in section 12.7. This function does not use any of the input method facilities described in chapter 13 and does not depend on the current locale. @@ -669,11 +669,11 @@ described in chapter 13 and does not depend on the current locale. To map a key event to an ISO Latin-1 string, use -XLookupString. +. XLookupString - + int XLookupString XKeyEvent *event_struct @@ -747,19 +747,19 @@ structure or NULL. The -XLookupString + function translates a key event to a KeySym and a string. The KeySym is obtained by using the standard interpretation of the Shift, Lock, group, and numlock modifiers as defined in the X Protocol specification. If the KeySym has been rebound (see -XRebindKeysym), +), the bound string will be stored in the buffer. Otherwise, the KeySym is mapped, if possible, to an ISO Latin-1 character or (if the Control modifier is on) to an ASCII control character, and that character is stored in the buffer. -XLookupString + returns the number of characters that are stored in the buffer. @@ -770,7 +770,7 @@ the structure records the state, which is private to Xlib, that needs preservation across calls to -XLookupString + to implement compose processing. The creation of XComposeStatus @@ -779,23 +779,23 @@ a portable program must pass NULL for this argument. -XLookupString + depends on the cached keyboard information mentioned in the previous section, so it is necessary to use -XRefreshKeyboardMapping + to keep this information up-to-date. To rebind the meaning of a KeySym for -XLookupString, +, use -XRebindKeysym. +. XRebindKeysym - + XRebindKeysym Display *display @@ -856,7 +856,7 @@ Specifies the number of modifiers in the modifier list. Specifies the string that is copied and will be returned by -XLookupString. +. @@ -875,11 +875,11 @@ Specifies the number of bytes in the string argument. The -XRebindKeysym + function can be used to rebind the meaning of a KeySym for the client. It does not redefine any key in the X server but merely provides an easy way for long strings to be attached to keys. -XLookupString + returns this string when the appropriate set of modifier keys are pressed and when the KeySym would have been used for the translation. @@ -896,10 +896,10 @@ Note that you can rebind a KeySym that may not exist. To allocate some memory you will never give back, use -Xpermalloc. +. Xpermalloc - + char *Xpermalloc unsignedint size @@ -911,7 +911,7 @@ To allocate some memory you will never give back, use The -Xpermalloc + function allocates storage that can never be freed for the life of the program. The memory is allocated with alignment for the C type double. This function may provide some performance and space savings over @@ -926,13 +926,13 @@ the standard operating system memory allocator. To parse standard window geometry strings, use -XParseGeometry. +. Windowdetermining location XParseGeometry - + int XParseGeometry char *parsestring @@ -1000,7 +1000,7 @@ Return the width and height determined. By convention, X applications use a standard string to indicate window size and placement. -XParseGeometry + makes it easier to conform to this standard because it allows you to parse the standard window geometry. Specifically, this function lets you parse strings of the form: @@ -1025,7 +1025,7 @@ the result is implementation-dependent. The -XParseGeometry + 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. @@ -1062,11 +1062,11 @@ you should place the window at the requested position. To construct a window's geometry information, use -XWMGeometry. +. XWMGeometry - + int XWMGeometry Display *display @@ -1200,9 +1200,9 @@ Returns the window gravity. The -XWMGeometry + function combines any geometry information (given in the format used by -XParseGeometry) +) specified by the user and by the calling program with size hints (usually the ones to be stored in WM_NORMAL_HINTS) and returns the position, size, and gravity @@ -1220,7 +1220,7 @@ Otherwise, a base size of zero is assumed. If no minimum size is set in the hints structure, the base size is used. A mask (in the form returned by -XParseGeometry) +) that describes which values came from the user specification and whether or not the position coordinates are relative to the right and bottom edges is returned. @@ -1300,11 +1300,11 @@ To create a new empty region, use To generate a region from a polygon, use -XPolygonRegion. +. XPolygonRegion - + Region XPolygonRegion XPoint points[] @@ -1354,21 +1354,21 @@ or The -XPolygonRegion + function returns a region for the polygon defined by the points array. For an explanation of fill_rule, see -XCreateGC. +. To set the clip-mask of a GC to a region, use -XSetRegion. +. XSetRegion - + XSetRegion Display *display @@ -1413,7 +1413,7 @@ Specifies the region. The -XSetRegion + function sets the clip-mask in the GC to the specified region. The region is specified relative to the drawable's origin. The resulting GC clip origin is implementation-dependent. @@ -1424,11 +1424,11 @@ the region can be destroyed. To deallocate the storage associated with a specified region, use -XDestroyRegion. +. XDestroyRegion - + XDestroyRegion Region r @@ -1460,11 +1460,11 @@ Specifies the region. To move a region by a specified amount, use -XOffsetRegion. +. XOffsetRegion - + XOffsetRegion Region r @@ -1512,11 +1512,11 @@ which define the amount you want to (Dy the specified region. To reduce a region by a specified amount, use -XShrinkRegion. +. XShrinkRegion - + XShrinkRegion Region r @@ -1575,11 +1575,11 @@ and negative values expand the region. To generate the smallest rectangle enclosing a region, use -XClipBox. +. XClipBox - + XClipBox Region r @@ -1613,18 +1613,18 @@ Returns the smallest enclosing rectangle. The -XClipBox + function returns the smallest rectangle enclosing the specified region. To compute the intersection of two regions, use -XIntersectRegion. +. XIntersectRegion - + XIntersectRegion Regionsra,srb, dr_return @@ -1669,11 +1669,11 @@ Returns the result of the computation. To compute the union of two regions, use -XUnionRegion. +. XUnionRegion - + XUnionRegion Regionsra,srb, dr_return @@ -1718,11 +1718,11 @@ Returns the result of the computation. To create a union of a source region and a rectangle, use -XUnionRectWithRegion. +. XUnionRectWithRegion - + XUnionRectWithRegion XRectangle *rectangle @@ -1767,7 +1767,7 @@ Returns the destination region. The -XUnionRectWithRegion + function updates the destination region from a union of the specified rectangle and the specified source region. @@ -1775,11 +1775,11 @@ and the specified source region. To subtract two regions, use -XSubtractRegion. +. XSubtractRegion - + XSubtractRegion Regionsra,srb, dr_return @@ -1823,7 +1823,7 @@ Returns the result of the computation. The -XSubtractRegion + function subtracts srb from sra and stores the results in dr_return. @@ -1831,11 +1831,11 @@ function subtracts srb from sra and stores the results in dr_return. To calculate the difference between the union and intersection of two regions, use -XXorRegion. +. XXorRegion - + XXorRegion Regionsra,srb, dr_return @@ -1888,11 +1888,11 @@ Returns the result of the computation. To determine if the specified region is empty, use -XEmptyRegion. +. XEmptyRegion - + Bool XEmptyRegion Region r @@ -1915,7 +1915,7 @@ Specifies the region. The -XEmptyRegion + function returns True if the region is empty. @@ -1924,11 +1924,11 @@ if the region is empty. To determine if two regions have the same offset, size, and shape, use -XEqualRegion. +. XEqualRegion - + Bool XEqualRegion Regionr1, r2 @@ -1962,7 +1962,7 @@ Specify the two regions. The -XEqualRegion + function returns True if the two regions have the same offset, size, and shape. @@ -1976,11 +1976,11 @@ if the two regions have the same offset, size, and shape. To determine if a specified point resides in a specified region, use -XPointInRegion. +. XPointInRegion - + Bool XPointInRegion Region r @@ -2026,7 +2026,7 @@ Specify the x and y coordinates(Xy. The -XPointInRegion + function returns True if the point (x, y) is contained in the region r. @@ -2035,11 +2035,11 @@ if the point (x, y) is contained in the region r. To determine if a specified rectangle is inside a region, use -XRectInRegion. +. XRectInRegion - + int XRectInRegion Region r @@ -2108,7 +2108,7 @@ Specify the width and height(Wh. The -XRectInRegion + function returns RectangleIn if the rectangle is entirely in the specified region, @@ -2148,11 +2148,11 @@ and can be accessed as a ring or as explicit buffers (numbered 0 through 7). To store data in cut buffer 0, use -XStoreBytes. +. XStoreBytes - + XStoreBytes Display *display @@ -2200,11 +2200,11 @@ The data can have embedded null characters and need not be null-terminated. The cut buffer's contents can be retrieved later by any client calling -XFetchBytes. +. -XStoreBytes + can generate a BadAlloc error. @@ -2213,11 +2213,11 @@ error. To store data in a specified cut buffer, use -XStoreBuffer. +. XStoreBuffer - + XStoreBuffer Display *display @@ -2279,7 +2279,7 @@ and need not be null-terminated. -XStoreBuffer + can generate a BadAlloc error. @@ -2288,11 +2288,11 @@ error. To return data from cut buffer 0, use -XFetchBytes. +. XFetchBytes - + char *XFetchBytes Display *display @@ -2326,7 +2326,7 @@ Returns the number of bytes in the buffer. The -XFetchBytes + function returns the number of bytes in the nbytes_return argument, if the buffer contains data. @@ -2334,17 +2334,17 @@ Otherwise, the function returns NULL and sets nbytes to 0. The appropriate amount of storage is allocated and the pointer returned. The client must free this storage when finished with it by calling -XFree. +. To return data from a specified cut buffer, use -XFetchBuffer. +. XFetchBuffer - + char *XFetchBuffer Display *display @@ -2390,7 +2390,7 @@ Specifies the buffer (Fn. The -XFetchBuffer + function returns zero to the nbytes_return argument if there is no data in the buffer or if an invalid buffer is specified. @@ -2399,11 +2399,11 @@ buffer is specified. To rotate the cut buffers, use -XRotateBuffers. +. XRotateBuffers - + XRotateBuffers Display *display @@ -2437,13 +2437,13 @@ Specifies how much to rotate the cut buffers. The -XRotateBuffers + function rotates the cut buffers, such that buffer 0 becomes buffer n, buffer 1 becomes n + 1 mod 8, and so on. This cut buffer numbering is global to the display. Note that -XRotateBuffers + generates BadMatch errors if any of the eight buffers have not been created. @@ -2519,11 +2519,11 @@ typedef struct { To obtain a list of visual information structures that match a specified template, use -XGetVisualInfo. +. XGetVisualInfo - + XVisualInfo *XGetVisualInfo Display *display @@ -2580,25 +2580,25 @@ Returns the number of matching visual structures. The -XGetVisualInfo + function returns a list of visual structures that have attributes equal to the attributes specified by vinfo_template. If no visual structures match the template using the specified vinfo_mask, -XGetVisualInfo + returns a NULL. To free the data returned by this function, use -XFree. +. To obtain the visual information that matches the specified depth and class of the screen, use -XMatchVisualInfo. +. XMatchVisualInfo - + Status XMatchVisualInfo Display *display @@ -2665,16 +2665,16 @@ Returns the matched visual information. The -XMatchVisualInfo + function returns the visual information for a visual that matches the specified depth and class for a screen. Because multiple visuals that match the specified depth and class can exist, the exact visual chosen is undefined. If a visual is found, -XMatchVisualInfo + returns nonzero and the information on the visual to vinfo_return. Otherwise, when a visual is not found, -XMatchVisualInfo + returns zero. @@ -2707,9 +2707,9 @@ processing. Rather, they are here to provide minimal functions on screen format images. The basic operations for getting and putting images are -XGetImage + and -XPutImage. +. @@ -2729,7 +2729,7 @@ Other members (for example, byte order, bitmap_unit, and so forth) are characteristics of both the image and the server. If these members differ between the image and the server, -XPutImage + makes the appropriate conversions. The first byte of the first line of plane n must be located at the address (data + (n * height * bytes_per_line)). @@ -2744,11 +2744,11 @@ see section 8.7XImage structure and initialize it with image format values from a display, use -XCreateImage. +. XCreateImage - + XImage *XCreateImage Display *display @@ -2880,7 +2880,7 @@ the start of one scanline and the start of the next. The -XCreateImage + function allocates the memory needed for an XImage structure for the @@ -2903,12 +2903,12 @@ in memory and calculates the value of bytes_per_line itself. Note that when the image is created using -XCreateImage, -XGetImage, +, +, or -XSubImage, +, the destroy procedure that the -XDestroyImage + function calls frees both the image structure and the data pointed to by the image structure. @@ -2927,11 +2927,11 @@ in the image object and are defined in To obtain a pixel value in an image, use -XGetPixel. +. XGetPixel - + unsigned long XGetPixel XImage *ximage @@ -2977,7 +2977,7 @@ Specify the x and y coordinates. The -XGetPixel + function returns the specified pixel from the named image. The pixel value is returned in normalized format (that is, the least significant byte of the long is the least significant byte @@ -2988,11 +2988,11 @@ The image must contain the x and y coordinates. To set a pixel value in an image, use -XPutPixel. +. XPutPixel - + XPutPixel XImage *ximage @@ -3049,7 +3049,7 @@ Specifies the new pixel value. The -XPutPixel + function overwrites the pixel in the named image with the specified pixel value. The input pixel value must be in normalized format (that is, the least significant byte of the long is the least significant @@ -3060,11 +3060,11 @@ The image must contain the x and y coordinates. To create a subimage, use -XSubImage. +. XSubImage - + XImage *XSubImage XImage *ximage @@ -3132,7 +3132,7 @@ Specifies the height of the new subimage, in pixels. The -XSubImage + function creates a new image that is a subsection of an existing one. It allocates the memory necessary for the new XImage @@ -3146,11 +3146,11 @@ and subimage_height. To increment each pixel in an image by a constant value, use -XAddPixel. +. XAddPixel - + XAddPixel XImage *ximage @@ -3184,7 +3184,7 @@ Specifies the constant value that is to be added. The -XAddPixel + function adds a constant value to every pixel in an image. It is useful when you have a base pixel value from allocating color resources and need to manipulate the image to that form. @@ -3193,13 +3193,13 @@ color resources and need to manipulate the image to that form. To deallocate the memory allocated in a previous call to -XCreateImage, +, use -XDestroyImage. +. XDestroyImage - + XDestroyImage XImage *ximage @@ -3222,7 +3222,7 @@ Specifies the image. The -XDestroyImage + function deallocates the memory associated with the XImage structure. @@ -3230,10 +3230,10 @@ structure. Note that when the image is created using -XCreateImage, -XGetImage, +, +, or -XSubImage, +, the destroy procedure that this macro calls frees both the image structure and the data pointed to by the image structure. @@ -3282,11 +3282,11 @@ The bitmap unit is 8. To read a bitmap from a file and store it in a pixmap, use -XReadBitmapFile. +. XReadBitmapFile - + int XReadBitmapFile Display *display @@ -3388,13 +3388,13 @@ Return the hotspot coordinates. The -XReadBitmapFile + function reads in a file containing a bitmap. The file is parsed in the encoding of the current locale. The ability to read other than the standard format is implementation-dependent. If the file cannot be opened, -XReadBitmapFile + returns BitmapOpenFailed. If the file can be opened but does not contain valid bitmap data, @@ -3409,23 +3409,23 @@ it returns -XReadBitmapFile + returns the bitmap's height and width, as read from the file, to width_return and height_return. It then creates a pixmap of the appropriate size, reads the bitmap data from the file into the pixmap, and assigns the pixmap to the caller's variable bitmap. The caller must free the bitmap using -XFreePixmap + when finished. If name_x_hot and name_y_hot exist, -XReadBitmapFile + returns them to x_hot_return and y_hot_return; otherwise, it returns −1,−1. -XReadBitmapFile + can generate BadAlloc, BadDrawable, @@ -3437,11 +3437,11 @@ errors. To read a bitmap from a file and return it as data, use -XReadBitmapFileData. +. XReadBitmapFileData - + int XReadBitmapFileData char *filename @@ -3520,25 +3520,25 @@ Return the hotspot coordinates. The -XReadBitmapFileData + function reads in a file containing a bitmap, in the same manner as -XReadBitmapFile, +, but returns the data directly rather than creating a pixmap in the server. The bitmap data is returned in data_return; the client must free this storage when finished with it by calling -XFree. +. The status and other return values are the same as for -XReadBitmapFile. +. To write out a bitmap from a pixmap to a file, use -XWriteBitmapFile. +. XWriteBitmapFile - + int XWriteBitmapFile Display *display @@ -3629,7 +3629,7 @@ in the file. The -XWriteBitmapFile + function writes a bitmap out to a file in the X Version 11 format. The name used in the output file is derived from the file name by deleting the directory prefix. @@ -3638,19 +3638,19 @@ If the file cannot be opened for writing, it returns BitmapOpenFailed. If insufficient memory is allocated, -XWriteBitmapFile + returns BitmapNoMemory; otherwise, on no error, it returns BitmapSuccess. If x_hot and y_hot are not −1, −1, -XWriteBitmapFile + writes them out as the hotspot coordinates for the bitmap. -XWriteBitmapFile + can generate BadDrawable and @@ -3661,11 +3661,11 @@ errors. To create a pixmap and then store bitmap-format data into it, use -XCreatePixmapFromBitmapData. +. XCreatePixmapFromBitmapData - + Pixmap XCreatePixmapFromBitmapData Display *display @@ -3766,9 +3766,9 @@ Specifies the depth of the pixmap. The -XCreatePixmapFromBitmapData + function creates a pixmap of the given depth and then does a bitmap-format -XPutImage + of the data into it. The depth must be supported by the screen of the specified drawable, or a @@ -3777,7 +3777,7 @@ error results. -XCreatePixmapFromBitmapData + can generate BadAlloc, BadDrawable, @@ -3790,14 +3790,14 @@ errors. To include a bitmap written out by -XWriteBitmapFile + XWriteBitmapFile in a program directly, as opposed to reading it in every time at run time, use -XCreateBitmapFromData. +. XCreateBitmapFromData - + Pixmap XCreateBitmapFromData Display *display @@ -3865,11 +3865,11 @@ Specify the width and height. The -XCreateBitmapFromData + function allows you to include in your C program (using #include) a bitmap file that was written out by -XWriteBitmapFile + (X version 11 format only) without reading in the bitmap file. The following example creates a gray bitmap: @@ -3885,17 +3885,17 @@ bitmap = XCreateBitmapFromData(display, window, gray_bits, gray_width, gray_heig If insufficient working storage was allocated, -XCreateBitmapFromData + returns None. It is your responsibility to free the bitmap using -XFreePixmap + when finished. -XCreateBitmapFromData + can generate BadAlloc and @@ -3939,11 +3939,11 @@ The symbols used are in To save a data value that corresponds to a resource ID and context type, use -XSaveContext. +. XSaveContext - + int XSaveContext Display *display @@ -3999,10 +3999,10 @@ Specifies the data to be associated with the window and type. If an entry with the specified resource ID and type already exists, -XSaveContext + overrides it with the specified context. The -XSaveContext + function returns a nonzero error code if an error has occurred and zero otherwise. Possible errors are @@ -4013,11 +4013,11 @@ Possible errors are To get the data associated with a resource ID and type, use -XFindContext. +. XFindContext - + int XFindContext Display *display @@ -4075,7 +4075,7 @@ Returns the data. Because it is a return value, the data is a pointer. The -XFindContext + function returns a nonzero error code if an error has occurred and zero otherwise. Possible errors are @@ -4086,11 +4086,11 @@ Possible errors are To delete an entry for a given resource ID and type, use -XDeleteContext. +. XDeleteContext - + int XDeleteContext Display *display @@ -4135,22 +4135,22 @@ Specifies the context type to which the data belongs. The -XDeleteContext + function deletes the entry for the given resource ID and type from the data structure. This function returns the same error codes that -XFindContext + returns if called with the same arguments. -XDeleteContext + does not free the data whose address was saved. To create a unique context type that may be used in subsequent calls to -XSaveContext + and -XFindContext, +, use XUniqueContext. diff --git a/libX11/specs/libX11/credits.xml b/libX11/specs/libX11/credits.xml index 753a6cce2..c8fdfecb4 100644 --- a/libX11/specs/libX11/credits.xml +++ b/libX11/specs/libX11/credits.xml @@ -17,9 +17,7 @@ and recognition for their work on Xlib. Our apologies to anyone inadvertently overlooked. - -Release 1 - +Release 1 Our thanks does to Ron Newman (MIT Project Athena), who contributed substantially to the @@ -96,9 +94,7 @@ and IBM for providing the environment where it could happen. - -Release 4 - +Release 4 Our thanks go to Jim Fulton (MIT X Consortium) for designing and specifying the new Xlib functions for Inter-Client Communication @@ -111,9 +107,7 @@ for their much-appreciated efforts in reviewing the changes. - -Release 5 - +Release 5 The principal authors of the Input Method facilities are Vania Joloboff (Open Software Foundation) and Bill McMahon (Hewlett-Packard). @@ -171,9 +165,7 @@ number of small errors. - -Release 6 - +Release 6 Stephen Gildea (X Consortium) authored the threads support. Ovais Ashraf (Sun) and Greg Olsen (Sun) contributed substantially diff --git a/libX11/specs/libX11/glossary.xml b/libX11/specs/libX11/glossary.xml index 0ad46b73c..51fa30293 100644 --- a/libX11/specs/libX11/glossary.xml +++ b/libX11/specs/libX11/glossary.xml @@ -1,1764 +1,1754 @@ - - - -Glossary - - Access control list -Access control list - - -X maintains a list of hosts from which client programs can be run. -By default, -only programs on the local host and hosts specified in an initial list read -by the server can use the display. -This access control list can be changed by clients on the local host. -Some server implementations can also implement other authorization mechanisms -in addition to or in place of this mechanism. -The action of this mechanism can be conditional based on the authorization -protocol name and data received by the server at connection setup. - - - - - Active grab -Active grab - - -A grab is active when the pointer or keyboard is actually owned by the -single grabbing client. - - - - - Ancestors -Ancestors - - -If W is an inferior of A, then A is an ancestor of W. - - - - - Atom -Atom - - -An atom is a unique ID corresponding to a string name. -Atoms are used to identify properties, types, and selections. - - - - - Background -Background - - -An -InputOutput -window can have a background, which is defined as a pixmap. -When regions of the window have their contents lost -or invalidated, -the server automatically tiles those regions with the background. - - - - - Backing store -Backing store - - -When a server maintains the contents of a window, -the pixels saved off-screen are known as a backing store. - - - - - Base font name -Base font name - - -A font name used to select a family of fonts whose members may be encoded -in various charsets. -The -CharSetRegistry -and -CharSetEncoding -fields of an XLFD name identify the charset of the font. -A base font name may be a full XLFD name, with all fourteen '-' delimiters, -or an abbreviated XLFD name containing only the first 12 fields of an XLFD name, -up to but not including -CharSetRegistry, -with or without the thirteenth '-', or a non-XLFD name. -Any XLFD fields may contain wild cards. - - -When creating an -XFontSet, -Xlib accepts from the client a list of one or more base font names -which select one or more font families. -They are combined with charset names obtained from the encoding of the locale -to load the fonts required to render text. - - - - - Bit gravity -Bitgravity - - -When a window is resized, -the contents of the window are not necessarily discarded. -It is possible to request that the server relocate the previous contents -to some region of the window (though no guarantees are made). -This attraction of window contents for some location of -a window is known as bit gravity. - - - - - Bit plane -Bitplane - - -When a pixmap or window is thought of as a stack of bitmaps, -each bitmap is called a bit plane or plane. - - - - - Bitmap -Bitmap - - -A bitmap is a pixmap of depth one. - - - - - Border -Border - - -An -InputOutput -window can have a border of equal thickness on all four sides of the window. -The contents of the border are defined by a pixmap, -and the server automatically maintains the contents of the border. -Exposure events are never generated for border regions. - - - - - Button grabbing -Buttongrabbing - - -Buttons on the pointer can be passively grabbed by a client. -When the button is pressed, -the pointer is then actively grabbed by the client. - - - - - Byte order -Byteorder - - -For image (pixmap/bitmap) data, -the server defines the byte order, -and clients with different native byte ordering must swap bytes as -necessary. -For all other parts of the protocol, -the client defines the byte order, -and the server swaps bytes as necessary. - - - - - Character -Character - - -A member of a set of elements used for the organization, -control, or representation of text (ISO2022, as adapted by XPG3). -Note that in ISO2022 terms, a character is not bound to a coded value -until it is identified as part of a coded character set. - - - - - Character glyph -Character glyph - - -The abstract graphical symbol for a character. -Character glyphs may or may not map one-to-one to font glyphs, -and may be context-dependent, varying with the adjacent characters. -Multiple characters may map to a single character glyph. - - - - - Character set -Character set - - -A collection of characters. - - - - - Charset -Charset - - -An encoding with a uniform, state-independent mapping from characters -to codepoints. -A coded character set. - - -For display in X, -there can be a direct mapping from a charset to one font, -if the width of all characters in the charset is either one or two bytes. -A text string encoded in an encoding such as Shift-JIS cannot be passed -directly to the X server, because the text imaging requests accept only -single-width charsets (either 8 or 16 bits). -Charsets which meet these restrictions can serve as ``font charsets''. -Font charsets strictly speaking map font indices to font glyphs, -not characters to character glyphs. - - -Note that a single font charset is sometimes used as the encoding of a locale, -for example, ISO8859-1. - - - - - Children -Children - - -The children of a window are its first-level subwindows. - - - - - Class -Class - - -Windows can be of different classes or types. -See the entries for -InputOnly -and -InputOutput -windows for further information about valid window types. - - - - - Client -Client - - -An application program connects to the window system server by some -interprocess communication (IPC) path, such as a TCP connection or a -shared memory buffer. -This program is referred to as a client of the window system server. -More precisely, -the client is the IPC path itself. -A program with multiple paths open to the server is viewed as -multiple clients by the protocol. -Resource lifetimes are controlled by -connection lifetimes, not by program lifetimes. - - - - - Clipping region -Clipping region - - -In a graphics context, -a bitmap or list of rectangles can be specified -to restrict output to a particular region of the window. -The image defined by the bitmap or rectangles is called a clipping region. - - - - - Coded character -Coded character - - -A character bound to a codepoint. - - - - - Coded character set -Coded character set - - -A set of unambiguous rules that establishes a character set -and the one-to-one relationship between each character of the set -and its bit representation. -(ISO2022, as adapted by XPG3) -A definition of a one-to-one mapping of a set of characters to a set of -codepoints. - - - - - Codepoint -Codepoint - - -The coded representation of a single character in a coded character set. - - - - - Colormap -Colormap - - -A colormap consists of a set of entries defining color values. -The colormap associated with a window is used to display the contents of -the window; each pixel value indexes the colormap to produce an RGB value -that drives the guns of a monitor. -Depending on hardware limitations, -one or more colormaps can be installed at one time so -that windows associated with those maps display with true colors. - - - - - Connection -Connection - - -The IPC path between the server and client program is known as a connection. -A client program typically (but not necessarily) has one -connection to the server over which requests and events are sent. - - - - - Containment -Containment - - -A window contains the pointer if the window is viewable and the -hotspot of the cursor is within a visible region of the window or a -visible region of one of its inferiors. -The border of the window is included as part of the window for containment. -The pointer is in a window if the window contains the pointer -but no inferior contains the pointer. - - - - - Coordinate system -Coordinate system - - -The coordinate system has X horizontal and Y vertical, -with the origin [0, 0] at the upper left. -Coordinates are integral and coincide with pixel centers. -Each window and pixmap has its own coordinate system. -For a window, -the origin is inside the border at the inside upper-left corner. - - - - - Cursor -Cursor - - -A cursor is the visible shape of the pointer on a screen. -It consists of a hotspot, a source bitmap, a shape bitmap, -and a pair of colors. -The cursor defined for a window controls the visible -appearance when the pointer is in that window. - - - - - Depth -Depth - - -The depth of a window or pixmap is the number of bits per pixel it has. -The depth of a graphics context is the depth of the drawables it can be -used in conjunction with graphics output. - - - - - Device -Device - - -Keyboards, mice, tablets, track-balls, button boxes, and so on are all -collectively known as input devices. -Pointers can have one or more buttons -(the most common number is three). -The core protocol only deals with two devices: the keyboard -and the pointer. - - - - - DirectColor -DirectColor - - -DirectColor -is a class of colormap in which a pixel value is decomposed into three -separate subfields for indexing. -The first subfield indexes an array to produce red intensity values. -The second subfield indexes a second array to produce blue intensity values. -The third subfield indexes a third array to produce green intensity values. -The RGB (red, green, and blue) values in the colormap entry can be -changed dynamically. - - - - - Display -Display -Displaystructure - - -A server, together with its screens and input devices, is called a display. -The Xlib -Display -structure contains all information about the particular display and its screens -as well as the state that Xlib needs to communicate with the display over a -particular connection. - - - - - Drawable -Drawable - - -Both windows and pixmaps can be used as sources and destinations -in graphics operations. -These windows and pixmaps are collectively known as drawables. -However, an -InputOnly -window cannot be used as a source or destination in a -graphics operation. - - - - - Encoding -Encoding - - -A set of unambiguous rules that establishes a character set -and a relationship between the characters and their representations. -The character set does not have to be fixed to a finite pre-defined set of -characters. -The representations do not have to be of uniform length. -Examples are an ISO2022 graphic set, a state-independent -or state-dependent combination of graphic sets, possibly including control -sets, and the X Compound Text encoding. - - -In X, encodings are identified by a string -which appears as: the -CharSetRegistry -and -CharSetEncoding -components of an XLFD -name; the name of a charset of the locale for which a font could not be -found; or an atom which identifies the encoding of a text property or -which names an encoding for a text selection target type. -Encoding names should be composed of characters from the X Portable -Character Set. - - - - - Escapement -Escapement - - -The escapement of a string is the distance in pixels in the -primary draw direction from the drawing origin to the origin of the next -character (that is, the one following the given string) to be drawn. - - - - - Event -Event - - -Clients are informed of information asynchronously by means of events. -These events can be either asynchronously generated from devices or -generated as side effects of client requests. -Events are grouped into types. -The server never sends an event to a client unless the -client has specifically asked to be informed of that type of event. -However, clients can force events to be sent to other clients. -Events are typically reported relative to a window. - - - - - Event mask -Eventmask - - -Events are requested relative to a window. -The set of event types a client requests relative to a window is described -by using an event mask. - - - - - Event propagation -Eventpropagation - - -Device-related events propagate from the source window to ancestor -windows until some client has expressed interest in handling that type -of event or until the event is discarded explicitly. - - - - - Event source -Eventsource - - -The deepest viewable window that the pointer is in is called -the source of a device-related event. - - - - - Event synchronization -Eventsynchronization - - -There are certain race conditions possible when demultiplexing device -events to clients (in particular, deciding where pointer and keyboard -events should be sent when in the middle of window management -operations). -The event synchronization mechanism allows synchronous processing of -device events. - - - - - Exposure event -EventExposure - - -Servers do not guarantee to preserve the contents of windows when -windows are obscured or reconfigured. -Exposure events are sent to clients to inform them when contents of regions -of windows have been lost. - - - - - Extension -Extension - - -Named extensions to the core protocol can be defined to extend the system. -Extensions to output requests, resources, and event types are all possible -and expected. - - - - - Font -Font - - -A font is an array of glyphs (typically characters). -The protocol does no translation or interpretation of character sets. -The client simply indicates values used to index the glyph array. -A font contains additional metric information to determine interglyph -and interline spacing. - - - - - Font glyph -Font glyph - - -The abstract graphical symbol for an index into a font. - - - - - Frozen events -Frozen events - - -Clients can freeze event processing during keyboard and pointer grabs. - - - - - GC -GC - - -GC is an abbreviation for graphics context. -See Graphics context. - - - - - Glyph -Glyph - - -An identified abstract graphical symbol independent of any actual image. -(ISO/IEC/DIS 9541-1) -An abstract visual representation of a graphic character, -not bound to a codepoint. - - - - - Glyph image -Glyph image - - -An image of a glyph, as obtained from a glyph representation displayed -on a presentation surface. -(ISO/IEC/DIS 9541-1) - - - - - Grab -Grab - - -Keyboard keys, the keyboard, pointer buttons, the pointer, -and the server can be grabbed for exclusive use by a client. -In general, -these facilities are not intended to be used by normal applications -but are intended for various input and window managers to implement various -styles of user interfaces. - - - - - Graphics context -Graphics context - - -Various information for graphics output is stored in a graphics -context (GC), such as foreground pixel, background -pixel, line width, clipping region, and so on. -A graphics context can only -be used with drawables that have the same root and the same depth as -the graphics context. - - - - - Gravity -Gravity - - -The contents of windows and windows themselves have a gravity, -which determines how the contents move when a window is resized. -See Bit gravity and -Window gravity. - - - - - GrayScale -GrayScale - - -GrayScale -can be viewed as a degenerate case of -PseudoColor, -in which the red, green, and blue values in any given colormap entry -are equal and thus, produce shades of gray. -The gray values can be changed dynamically. - - - - - Host Portable Character Encoding -Host Portable Character Encoding - - -The encoding of the X Portable Character Set on the host. -The encoding itself is not defined by this standard, -but the encoding must be the same in all locales supported by Xlib on the host. -If a string is said to be in the Host Portable Character Encoding, -then it only contains characters from the X Portable Character Set, -in the host encoding. - - - - - Hotspot -Hotspot - - -A cursor has an associated hotspot, which defines the point in the -cursor corresponding to the coordinates reported for the pointer. - - - - - Identifier -Identifier - - -An identifier is a unique value associated with a resource -that clients use to name that resource. -The identifier can be used over any connection to name the resource. - - - - - Inferiors -Inferiors - - -The inferiors of a window are all of the subwindows nested below it: -the children, the children's children, and so on. - - - - - Input focus -Inputfocus - - -The input focus is usually a window defining the scope for processing -of keyboard input. -If a generated keyboard event usually would be reported to this window -or one of its inferiors, -the event is reported as usual. -Otherwise, the event is reported with respect to the focus window. -The input focus also can be set such that all keyboard events are discarded -and such that the focus window is dynamically taken to be the root window -of whatever screen the pointer is on at each keyboard event. - - - - - Input manager -Inputmanager - - -Control over keyboard input is typically provided by an input manager -client, which usually is part of a window manager. - - - - - InputOnly window -WindowInputOnly - - -An -InputOnly -window is a window that cannot be used for graphics requests. -InputOnly -windows are invisible and are used to control such things as cursors, -input event generation, and grabbing. -InputOnly -windows cannot have -InputOutput -windows as inferiors. - - - - - InputOutput window -WindowInputOutput - - -An -InputOutput -window is the normal kind of window that is used for both input and output. -InputOutput -windows can have both -InputOutput -and -InputOnly -windows as inferiors. - - - - - Internationalization -Internationalization - - -The process of making software adaptable to the requirements -of different native languages, local customs, and character string encodings. -Making a computer program adaptable to different locales -without program source modifications or recompilation. - - - - - ISO2022 -ISO2022 - - -ISO standard for code extension techniques for 7-bit and 8-bit coded -character sets. - - - - - Key grabbing -Keygrabbing - - -Keys on the keyboard can be passively grabbed by a client. -When the key is pressed, -the keyboard is then actively grabbed by the client. - - - - - Keyboard grabbing -Keyboardgrabbing - - -A client can actively grab control of the keyboard, and key events -will be sent to that client rather than the client the events would -normally have been sent to. - - - - - Keysym -Keysym - - -An encoding of a symbol on a keycap on a keyboard. - - - - - Latin-1 -Latin-1 - - -The coded character set defined by the ISO8859-1 standard. - - - - - Latin Portable Character Encoding -Latin Portable Character Encoding - - -The encoding of the X Portable Character Set using the Latin-1 codepoints -plus ASCII control characters. -If a string is said to be in the Latin Portable Character Encoding, -then it only contains characters from the X Portable Character Set, -not all of Latin-1. - - - - - Locale -Locale - - -The international environment of a computer program defining the ``localized'' -behavior of that program at run-time. -This information can be established from one or more sets of localization data. -ANSI C defines locale-specific processing by C system library calls. -See ANSI C and the X/Open Portability Guide specifications for more details. -In this specification, on implementations that conform to the ANSI C library, -the ``current locale'' is the current setting of the LC_CTYPE -setlocale -category. -Associated with each locale is a text encoding. When text is processed -in the context of a locale, the text must be in the encoding of the locale. -The current locale affects Xlib in its: - - -Encoding and processing of input method text - - -Encoding of resource files and values - - -Encoding and imaging of text strings - - -Encoding and decoding for inter-client text communication - - - - - - Locale name -Locale name - - -The identifier used to select the desired locale for the host C library -and X library functions. -On ANSI C library compliant systems, -the locale argument to the -setlocale -function. - - - - - Localization -Localization - - -The process of establishing information within a computer system specific -to the operation of particular native languages, local customs -and coded character sets. -(XPG3) - - - - - Mapped -Mapped window - - -A window is said to be mapped if a map call has been performed on it. -Unmapped windows and their inferiors are never viewable or visible. - - - - - Modifier keys -Modifier keys - - -Shift, Control, Meta, Super, Hyper, Alt, Compose, Apple, CapsLock, -ShiftLock, and similar keys are called modifier keys. - - - - - Monochrome -Monochrome - - -Monochrome is a special case of -StaticGray -in which there are only two colormap entries. - - - - - Multibyte -Multibyte - - -A character whose codepoint is stored in more than one byte; -any encoding which can contain multibyte characters; -text in a multibyte encoding. -The ``char *'' null-terminated string datatype in ANSI C. -Note that references in this document to multibyte strings -imply only that the strings may contain multibyte characters. - - - - - Obscure -Obscure - - -A window is obscured if some other window obscures it. -A window can be partially obscured and so still have visible regions. -Window A obscures window B if both are viewable -InputOutput -windows, if A is higher in the global stacking order, -and if the rectangle defined by the outside -edges of A intersects the rectangle defined by the outside edges of B. -Note the distinction between obscures and occludes. -Also note that window borders are included in the calculation. - - - - - Occlude -Occlude - - -A window is occluded if some other window occludes it. -Window A occludes window B if both are mapped, -if A is higher in the global stacking order, -and if the rectangle defined by the outside edges of A intersects the rectangle defined -by the outside edges of B. -Note the distinction between occludes and obscures. -Also note that window borders are included in the calculation -and that -InputOnly -windows never obscure other windows but can occlude other windows. - - - - - Padding -Padding - - -Some padding bytes are inserted in the data stream to maintain -alignment of the protocol requests on natural boundaries. -This increases ease of portability to some machine architectures. - - - - - Parent window -Windowparent - - -If C is a child of P, then P is the parent of C. - - - - - Passive grab -Passive grab - - -Grabbing a key or button is a passive grab. -The grab activates when the key or button is actually pressed. - - - - - Pixel value -Pixel value - - -A pixel is an N-bit value, -where N is the number of bit planes used in a particular window or pixmap -(that is, is the depth of the window or pixmap). -A pixel in a window indexes a colormap to derive an actual color to be -displayed. - - - - - Pixmap -Pixmap - - -A pixmap is a three-dimensional array of bits. -A pixmap is normally thought of as a two-dimensional array of pixels, -where each pixel can be a value from 0 to 2N-1, -and where N is the depth (z axis) of the pixmap. -A pixmap can also be thought of as a stack of N bitmaps. -A pixmap can only be used on the screen that it was created in. - - - - - Plane -Plane - - -When a pixmap or window is thought of as a stack of bitmaps, each -bitmap is called a plane or bit plane. - - - - - Plane mask -Planemask - - -Graphics operations can be restricted to only affect a subset of bit -planes of a destination. -A plane mask is a bit mask describing which planes are to be modified. -The plane mask is stored in a graphics context. - - - - - Pointer -Pointer - - -The pointer is the pointing device currently attached to the cursor -and tracked on the screens. - - - - - Pointer grabbing -Pointergrabbing - - -A client can actively grab control of the pointer. -Then button and motion events will be sent to that client -rather than the client the events would normally have been sent to. - - - - - Pointing device -Pointing device - - -A pointing device is typically a mouse, tablet, or some other -device with effective dimensional motion. -The core protocol defines only one visible cursor, -which tracks whatever pointing device is attached as the pointer. - - - - - POSIX -POSIX - - -Portable Operating System Interface, ISO/IEC 9945-1 (IEEE Std 1003.1). - - - - - POSIX Portable Filename Character Set -POSIX Portable Filename Character Set - - -The set of 65 characters which can be used in naming files on a POSIX-compliant -host that are correctly processed in all locales. -The set is: - - - -a..z A..Z 0..9 ._- - - - - - - Property -Property - - -Windows can have associated properties that consist of a name, a type, -a data format, and some data. -The protocol places no interpretation on properties. -They are intended as a general-purpose naming mechanism for clients. -For example, clients might use properties to share information such as resize -hints, program names, and icon formats with a window manager. - - - - - Property list -Property list - - -The property list of a window is the list of properties that have -been defined for the window. - - - - - PseudoColor -PseudoColor - - -PseudoColor -is a class of colormap in which a pixel value indexes the colormap entry to -produce an independent RGB value; -that is, the colormap is viewed as an array of triples (RGB values). -The RGB values can be changed dynamically. - - - - - Rectangle -Rectangle - - -A rectangle specified by [x,y,w,h] has an infinitely thin -outline path with corners at [x,y], [x+w,y], [x+w,y+h], and [x, y+h]. -When a rectangle is filled, -the lower-right edges are not drawn. -For example, -if w=h=0, -nothing would be drawn. -For w=h=1, -a single pixel would be drawn. - - - - - Redirecting control -Redirecting control - - -Window managers (or client programs) may enforce window layout -policy in various ways. -When a client attempts to change the size or position of a window, -the operation may be redirected to a specified client -rather than the operation actually being performed. - - - - - Reply -Reply - - -Information requested by a client program using the X protocol -is sent back to the client with a reply. -Both events and replies are multiplexed on the same connection. -Most requests do not generate replies, -but some requests generate multiple replies. - - - - - Request -Request - - -A command to the server is called a request. -It is a single block of data sent over a connection. - - - - - Resource -Resource - - -Windows, pixmaps, cursors, fonts, graphics contexts, and colormaps are -known as resources. -They all have unique identifiers associated with them for naming purposes. -The lifetime of a resource usually is bounded by the lifetime of the -connection over which the resource was created. - - - - - RGB values -RGB values - - -RGB values are the red, green, and blue intensity values that are used -to define a color. -These values are always represented as 16-bit, unsigned numbers, with 0 -the minimum intensity and 65535 the maximum intensity. -The X server scales these values to match the display hardware. - - - - - Root -Root - - -The root of a pixmap or graphics context is the same as the root -of whatever drawable was used when the pixmap or GC was created. -The root of a window is the root window under which the window was created. - - - - - Root window -Windowroot - - -Each screen has a root window covering it. -The root window cannot be reconfigured or unmapped, -but otherwise it acts as a full-fledged window. -A root window has no parent. - - - - - Save set -Save set - - -The save set of a client is a list of other clients' windows that, -if they are inferiors of one of the client's windows at connection -close, should not be destroyed and that should be remapped -if currently unmapped. -Save sets are typically used by window managers to avoid -lost windows if the manager should terminate abnormally. - - - - - Scanline -Scanline - - -A scanline is a list of pixel or bit values viewed as a horizontal -row (all values having the same y coordinate) of an image, with the -values ordered by increasing the x coordinate. - - - - - Scanline order -Scanlineorder - - -An image represented in scanline order contains scanlines ordered by -increasing the y coordinate. - - - - - Screen -Screen -Screenstructure -Displaystructure - - -A server can provide several independent screens, -which typically have physically independent monitors. -This would be the expected configuration when there is only a single keyboard -and pointer shared among the screens. -A -Screen -structure contains the information about that screen -and is linked to the -Display -structure. - - - - - Selection -Selection - - -A selection can be thought of as an indirect property with dynamic -type. -That is, rather than having the property stored in the X server, -it is maintained by some client (the owner). -A selection is global and is thought of as belonging to the user -and being maintained by clients, -rather than being private to a particular window subhierarchy -or a particular set of clients. -When a client asks for the contents of -a selection, it specifies a selection target type, -which can be used to control the transmitted representation of the contents. -For example, if the selection is ``the last thing the user clicked on,'' -and that is currently an image, then the target type might specify -whether the contents of the image should be sent in XY format or -Z format. - - -The target type can also be used to control the class of -contents transmitted; for example, -asking for the ``looks'' (fonts, line -spacing, indentation, and so forth) of a paragraph selection, rather than the -text of the paragraph. -The target type can also be used for other -purposes. -The protocol does not constrain the semantics. - - - - - Server -Server - - -The server, which is also referred to as the X server, -provides the basic windowing mechanism. -It handles IPC connections from clients, -multiplexes graphics requests onto the screens, -and demultiplexes input back to the appropriate clients. - - - - - Server grabbing -Servergrabbing - - -The server can be grabbed by a single client for exclusive use. -This prevents processing of any requests from other client connections until -the grab is completed. -This is typically only a transient state for such things as rubber-banding, -pop-up menus, or executing requests indivisibly. - - - - - Shift sequence -Shift sequence - - -ISO2022 defines control characters and escape sequences -which temporarily (single shift) or permanently (locking shift) cause a -different character set to be in effect (``invoking'' a character set). - - - - - Sibling -Sibling - - -Children of the same parent window are known as sibling windows. - - - - - Stacking order -Stacking order - - -Sibling windows, similar to sheets of paper on a desk, -can stack on top of each other. -Windows above both obscure and occlude lower windows. -The relationship between sibling windows is known as the stacking order. - - - - - State-dependent encoding -State-dependent encoding - - -An encoding in which an invocation of a charset can apply to multiple -characters in sequence. -A state-dependent encoding begins in an ``initial state'' -and enters other ``shift states'' when specific ``shift sequences'' -are encountered in the byte sequence. -In ISO2022 terms, -this means use of locking shifts, not single shifts. - - - - - State-independent encoding -State-independent encoding - - -Any encoding in which the invocations of the charsets are fixed, -or span only a single character. -In ISO2022 terms, -this means use of at most single shifts, not locking shifts. - - - - - StaticColor -StaticColor - - -StaticColor -can be viewed as a degenerate case of -PseudoColor -in which the RGB values are predefined and read-only. - - - - - StaticGray -StaticGray - - -StaticGray -can be viewed as a degenerate case of -GrayScale -in which the gray values are predefined and read-only. -The values are typically linear or near-linear increasing ramps. - - - - - Status -Status - - -Many Xlib functions return a success status. -If the function does not succeed, -however, its arguments are not disturbed. - - - - - Stipple -Stipple - - -A stipple pattern is a bitmap that is used to tile a region to serve -as an additional clip mask for a fill operation with the foreground -color. - - - - - STRING encoding - - -Latin-1, plus tab and newline. - - - - - String Equivalence -String Equivalence - - -Two ISO Latin-1 STRING8 values are considered equal if they are the same -length and if corresponding bytes are either equal or are equivalent as -follows: decimal values 65 to 90 inclusive (characters ``A'' to ``Z'') are -pairwise equivalent to decimal values 97 to 122 inclusive -(characters ``a'' to ``z''), decimal values 192 to 214 inclusive -(characters ``A grave'' to ``O diaeresis'') are pairwise equivalent to decimal -values 224 to 246 inclusive (characters ``a grave'' to ``o diaeresis''), -and decimal values 216 to 222 inclusive (characters ``O oblique'' to ``THORN'') -are pairwise equivalent to decimal values 246 to 254 inclusive -(characters ``o oblique'' to ``thorn''). - - - - - Tile -Tile - - -A pixmap can be replicated in two dimensions to tile a region. -The pixmap itself is also known as a tile. - - - - - Timestamp -Timestamp - - -A timestamp is a time value expressed in milliseconds. -It is typically the time since the last server reset. -Timestamp values wrap around (after about 49.7 days). -The server, given its current time is represented by timestamp T, -always interprets timestamps from clients by treating half -of the timestamp space as being earlier in time than T -and half of the timestamp space as being later in time than T. -One timestamp value, represented by the constant -CurrentTime, -is never generated by the server. -This value is reserved for use in requests to represent the current server time. - - - - - TrueColor -TrueColor - - -TrueColor -can be viewed as a degenerate case of -DirectColor -in which the subfields in the pixel value directly encode the corresponding RGB -values. -That is, the colormap has predefined read-only RGB values. -The values are typically linear or near-linear increasing ramps. - - - - - Type -Type - - -A type is an arbitrary atom used to identify the interpretation of property -data. -Types are completely uninterpreted by the server. -They are solely for the benefit of clients. -X predefines type atoms for many frequently used types, -and clients also can define new types. - - - - - Viewable -Viewable - - -A window is viewable if it and all of its ancestors are mapped. -This does not imply that any portion of the window is actually visible. -Graphics requests can be performed on a window when it is not -viewable, but output will not be retained unless the server is maintaining -backing store. - - - - - Visible -Visible - - -A region of a window is visible if someone looking at the screen can -actually see it; that is, the window is viewable and the region is not occluded -by any other window. - - - - - Whitespace -Whitespace - - -Any spacing character. -On implementations that conform to the ANSI C library, -whitespace is any character for which -isspace -returns true. - - - - - Window gravity -Windowgravity - - -When windows are resized, -subwindows may be repositioned automatically relative to some position in the -window. -This attraction of a subwindow to some part of its parent is known -as window gravity. - - - - - Window manager -Windowmanager - - -Manipulation of windows on the screen and much of the user interface -(policy) is typically provided by a window manager client. - - - - - X Portable Character Set -X Portable Character Set - - -A basic set of 97 characters which are assumed to exist in all -locales supported by Xlib. This set contains the following characters: - -a..z A..Z 0..9 -!"#$%&'()*+,-./:;<=>?@[\\]^_`{|}~ -<space>, <tab>, and <newline> - - - -This is the left/lower half (also called the G0 set) -of the graphic character set of ISO8859-1 plus <space>, <tab>, and <newline>. -It is also the set of graphic characters in 7-bit ASCII plus the same -three control characters. -The actual encoding of these characters on the host is system dependent; -see the Host Portable Character Encoding. - - - - - XLFD -XLFD - - -The X Logical Font Description Conventions that define a standard syntax -for structured font names. - - - - - XY format -XY format - - -The data for a pixmap is said to be in XY format if it is organized as -a set of bitmaps representing individual bit planes with the planes -appearing from most-significant to least-significant bit order. - - - - - Z format -Z format - - -The data for a pixmap is said to be in Z format if it is organized as -a set of pixel values in scanline order. - - - - - -References - -Draft Proposed Multibyte Extension of ANSI C, Draft 1.1 -November 30, 1989 SC22/C WG/SWG IPSJ/ITSCJ Japan - - - - -ISO2022: Information processing - ISO 7-bit and 8-bit coded character -sets - Code extension techniques. - - - - - -ISO8859-1: Information processing - 8-bit single-byte coded graphic -character sets - Part 1: Latin alphabet No. 1. - - - - - -<acronym>POSIX</acronym>: Information Technology - Portable Operating System Interface (<acronym>POSIX</acronym>) - -Part 1: System Application Program Interface (API) [C Language], -ISO/IEC 9945-1. - - - - - -Text of ISO/IEC/DIS 9541-1, Information Processing - Font Information -Interchange - Part 1: Architecture. - - - - - -X/Open Portability Guide, Issue 3, December 1988 (XPG3), X/Open Company, -Ltd, Prentice-Hall, Inc. 1989. ISBN 0-13-685835-8. -(See especially Volume 3: XSI Supplementary Definitions.) - - - - - + + + +Glossary + + Access control list +Access control list + + +X maintains a list of hosts from which client programs can be run. +By default, +only programs on the local host and hosts specified in an initial list read +by the server can use the display. +This access control list can be changed by clients on the local host. +Some server implementations can also implement other authorization mechanisms +in addition to or in place of this mechanism. +The action of this mechanism can be conditional based on the authorization +protocol name and data received by the server at connection setup. + + + + + Active grab +Active grab + + +A grab is active when the pointer or keyboard is actually owned by the +single grabbing client. + + + + + Ancestors +Ancestors + + +If W is an inferior of A, then A is an ancestor of W. + + + + + Atom +Atom + + +An atom is a unique ID corresponding to a string name. +Atoms are used to identify properties, types, and selections. + + + + + Background +Background + + +An +InputOutput +window can have a background, which is defined as a pixmap. +When regions of the window have their contents lost +or invalidated, +the server automatically tiles those regions with the background. + + + + + Backing store +Backing store + + +When a server maintains the contents of a window, +the pixels saved off-screen are known as a backing store. + + + + + Base font name +Base font name + + +A font name used to select a family of fonts whose members may be encoded +in various charsets. +The +CharSetRegistry +and +CharSetEncoding +fields of an XLFD name identify the charset of the font. +A base font name may be a full XLFD name, with all fourteen '-' delimiters, +or an abbreviated XLFD name containing only the first 12 fields of an XLFD name, +up to but not including +CharSetRegistry, +with or without the thirteenth '-', or a non-XLFD name. +Any XLFD fields may contain wild cards. + + +When creating an +XFontSet, +Xlib accepts from the client a list of one or more base font names +which select one or more font families. +They are combined with charset names obtained from the encoding of the locale +to load the fonts required to render text. + + + + + Bit gravity +Bitgravity + + +When a window is resized, +the contents of the window are not necessarily discarded. +It is possible to request that the server relocate the previous contents +to some region of the window (though no guarantees are made). +This attraction of window contents for some location of +a window is known as bit gravity. + + + + + Bit plane +Bitplane + + +When a pixmap or window is thought of as a stack of bitmaps, +each bitmap is called a bit plane or plane. + + + + + Bitmap +Bitmap + + +A bitmap is a pixmap of depth one. + + + + + Border +Border + + +An +InputOutput +window can have a border of equal thickness on all four sides of the window. +The contents of the border are defined by a pixmap, +and the server automatically maintains the contents of the border. +Exposure events are never generated for border regions. + + + + + Button grabbing +Buttongrabbing + + +Buttons on the pointer can be passively grabbed by a client. +When the button is pressed, +the pointer is then actively grabbed by the client. + + + + + Byte order +Byteorder + + +For image (pixmap/bitmap) data, +the server defines the byte order, +and clients with different native byte ordering must swap bytes as +necessary. +For all other parts of the protocol, +the client defines the byte order, +and the server swaps bytes as necessary. + + + + + Character +Character + + +A member of a set of elements used for the organization, +control, or representation of text (ISO2022, as adapted by XPG3). +Note that in ISO2022 terms, a character is not bound to a coded value +until it is identified as part of a coded character set. + + + + + Character glyph +Character glyph + + +The abstract graphical symbol for a character. +Character glyphs may or may not map one-to-one to font glyphs, +and may be context-dependent, varying with the adjacent characters. +Multiple characters may map to a single character glyph. + + + + + Character set +Character set + + +A collection of characters. + + + + + Charset +Charset + + +An encoding with a uniform, state-independent mapping from characters +to codepoints. +A coded character set. + + +For display in X, +there can be a direct mapping from a charset to one font, +if the width of all characters in the charset is either one or two bytes. +A text string encoded in an encoding such as Shift-JIS cannot be passed +directly to the X server, because the text imaging requests accept only +single-width charsets (either 8 or 16 bits). +Charsets which meet these restrictions can serve as ``font charsets''. +Font charsets strictly speaking map font indices to font glyphs, +not characters to character glyphs. + + +Note that a single font charset is sometimes used as the encoding of a locale, +for example, ISO8859-1. + + + + + Children +Children + + +The children of a window are its first-level subwindows. + + + + + Class +Class + + +Windows can be of different classes or types. +See the entries for +InputOnly +and +InputOutput +windows for further information about valid window types. + + + + + Client +Client + + +An application program connects to the window system server by some +interprocess communication (IPC) path, such as a TCP connection or a +shared memory buffer. +This program is referred to as a client of the window system server. +More precisely, +the client is the IPC path itself. +A program with multiple paths open to the server is viewed as +multiple clients by the protocol. +Resource lifetimes are controlled by +connection lifetimes, not by program lifetimes. + + + + + Clipping region +Clipping region + + +In a graphics context, +a bitmap or list of rectangles can be specified +to restrict output to a particular region of the window. +The image defined by the bitmap or rectangles is called a clipping region. + + + + + Coded character +Coded character + + +A character bound to a codepoint. + + + + + Coded character set +Coded character set + + +A set of unambiguous rules that establishes a character set +and the one-to-one relationship between each character of the set +and its bit representation. +(ISO2022, as adapted by XPG3) +A definition of a one-to-one mapping of a set of characters to a set of +codepoints. + + + + + Codepoint +Codepoint + + +The coded representation of a single character in a coded character set. + + + + + Colormap +Colormap + + +A colormap consists of a set of entries defining color values. +The colormap associated with a window is used to display the contents of +the window; each pixel value indexes the colormap to produce an RGB value +that drives the guns of a monitor. +Depending on hardware limitations, +one or more colormaps can be installed at one time so +that windows associated with those maps display with true colors. + + + + + Connection +Connection + + +The IPC path between the server and client program is known as a connection. +A client program typically (but not necessarily) has one +connection to the server over which requests and events are sent. + + + + + Containment +Containment + + +A window contains the pointer if the window is viewable and the +hotspot of the cursor is within a visible region of the window or a +visible region of one of its inferiors. +The border of the window is included as part of the window for containment. +The pointer is in a window if the window contains the pointer +but no inferior contains the pointer. + + + + + Coordinate system +Coordinate system + + +The coordinate system has X horizontal and Y vertical, +with the origin [0, 0] at the upper left. +Coordinates are integral and coincide with pixel centers. +Each window and pixmap has its own coordinate system. +For a window, +the origin is inside the border at the inside upper-left corner. + + + + + Cursor +Cursor + + +A cursor is the visible shape of the pointer on a screen. +It consists of a hotspot, a source bitmap, a shape bitmap, +and a pair of colors. +The cursor defined for a window controls the visible +appearance when the pointer is in that window. + + + + + Depth +Depth + + +The depth of a window or pixmap is the number of bits per pixel it has. +The depth of a graphics context is the depth of the drawables it can be +used in conjunction with graphics output. + + + + + Device +Device + + +Keyboards, mice, tablets, track-balls, button boxes, and so on are all +collectively known as input devices. +Pointers can have one or more buttons +(the most common number is three). +The core protocol only deals with two devices: the keyboard +and the pointer. + + + + + DirectColor +DirectColor + + +DirectColor +is a class of colormap in which a pixel value is decomposed into three +separate subfields for indexing. +The first subfield indexes an array to produce red intensity values. +The second subfield indexes a second array to produce blue intensity values. +The third subfield indexes a third array to produce green intensity values. +The RGB (red, green, and blue) values in the colormap entry can be +changed dynamically. + + + + + Display +Display +Displaystructure + + +A server, together with its screens and input devices, is called a display. +The Xlib +Display +structure contains all information about the particular display and its screens +as well as the state that Xlib needs to communicate with the display over a +particular connection. + + + + + Drawable +Drawable + + +Both windows and pixmaps can be used as sources and destinations +in graphics operations. +These windows and pixmaps are collectively known as drawables. +However, an +InputOnly +window cannot be used as a source or destination in a +graphics operation. + + + + + Encoding +Encoding + + +A set of unambiguous rules that establishes a character set +and a relationship between the characters and their representations. +The character set does not have to be fixed to a finite pre-defined set of +characters. +The representations do not have to be of uniform length. +Examples are an ISO2022 graphic set, a state-independent +or state-dependent combination of graphic sets, possibly including control +sets, and the X Compound Text encoding. + + +In X, encodings are identified by a string +which appears as: the +CharSetRegistry +and +CharSetEncoding +components of an XLFD +name; the name of a charset of the locale for which a font could not be +found; or an atom which identifies the encoding of a text property or +which names an encoding for a text selection target type. +Encoding names should be composed of characters from the X Portable +Character Set. + + + + + Escapement +Escapement + + +The escapement of a string is the distance in pixels in the +primary draw direction from the drawing origin to the origin of the next +character (that is, the one following the given string) to be drawn. + + + + + Event +Event + + +Clients are informed of information asynchronously by means of events. +These events can be either asynchronously generated from devices or +generated as side effects of client requests. +Events are grouped into types. +The server never sends an event to a client unless the +client has specifically asked to be informed of that type of event. +However, clients can force events to be sent to other clients. +Events are typically reported relative to a window. + + + + + Event mask +Eventmask + + +Events are requested relative to a window. +The set of event types a client requests relative to a window is described +by using an event mask. + + + + + Event propagation +Eventpropagation + + +Device-related events propagate from the source window to ancestor +windows until some client has expressed interest in handling that type +of event or until the event is discarded explicitly. + + + + + Event source +Eventsource + + +The deepest viewable window that the pointer is in is called +the source of a device-related event. + + + + + Event synchronization +Eventsynchronization + + +There are certain race conditions possible when demultiplexing device +events to clients (in particular, deciding where pointer and keyboard +events should be sent when in the middle of window management +operations). +The event synchronization mechanism allows synchronous processing of +device events. + + + + + Exposure event +EventExposure + + +Servers do not guarantee to preserve the contents of windows when +windows are obscured or reconfigured. +Exposure events are sent to clients to inform them when contents of regions +of windows have been lost. + + + + + Extension +Extension + + +Named extensions to the core protocol can be defined to extend the system. +Extensions to output requests, resources, and event types are all possible +and expected. + + + + + Font +Font + + +A font is an array of glyphs (typically characters). +The protocol does no translation or interpretation of character sets. +The client simply indicates values used to index the glyph array. +A font contains additional metric information to determine interglyph +and interline spacing. + + + + + Font glyph +Font glyph + + +The abstract graphical symbol for an index into a font. + + + + + Frozen events +Frozen events + + +Clients can freeze event processing during keyboard and pointer grabs. + + + + + GC +GC + + +GC is an abbreviation for graphics context. +See Graphics context. + + + + + Glyph +Glyph + + +An identified abstract graphical symbol independent of any actual image. +(ISO/IEC/DIS 9541-1) +An abstract visual representation of a graphic character, +not bound to a codepoint. + + + + + Glyph image +Glyph image + + +An image of a glyph, as obtained from a glyph representation displayed +on a presentation surface. +(ISO/IEC/DIS 9541-1) + + + + + Grab +Grab + + +Keyboard keys, the keyboard, pointer buttons, the pointer, +and the server can be grabbed for exclusive use by a client. +In general, +these facilities are not intended to be used by normal applications +but are intended for various input and window managers to implement various +styles of user interfaces. + + + + + Graphics context +Graphics context + + +Various information for graphics output is stored in a graphics +context (GC), such as foreground pixel, background +pixel, line width, clipping region, and so on. +A graphics context can only +be used with drawables that have the same root and the same depth as +the graphics context. + + + + + Gravity +Gravity + + +The contents of windows and windows themselves have a gravity, +which determines how the contents move when a window is resized. +See Bit gravity and +Window gravity. + + + + + GrayScale +GrayScale + + +GrayScale +can be viewed as a degenerate case of +PseudoColor, +in which the red, green, and blue values in any given colormap entry +are equal and thus, produce shades of gray. +The gray values can be changed dynamically. + + + + + Host Portable Character Encoding +Host Portable Character Encoding + + +The encoding of the X Portable Character Set on the host. +The encoding itself is not defined by this standard, +but the encoding must be the same in all locales supported by Xlib on the host. +If a string is said to be in the Host Portable Character Encoding, +then it only contains characters from the X Portable Character Set, +in the host encoding. + + + + + Hotspot +Hotspot + + +A cursor has an associated hotspot, which defines the point in the +cursor corresponding to the coordinates reported for the pointer. + + + + + Identifier +Identifier + + +An identifier is a unique value associated with a resource +that clients use to name that resource. +The identifier can be used over any connection to name the resource. + + + + + Inferiors +Inferiors + + +The inferiors of a window are all of the subwindows nested below it: +the children, the children's children, and so on. + + + + + Input focus +Inputfocus + + +The input focus is usually a window defining the scope for processing +of keyboard input. +If a generated keyboard event usually would be reported to this window +or one of its inferiors, +the event is reported as usual. +Otherwise, the event is reported with respect to the focus window. +The input focus also can be set such that all keyboard events are discarded +and such that the focus window is dynamically taken to be the root window +of whatever screen the pointer is on at each keyboard event. + + + + + Input manager +Inputmanager + + +Control over keyboard input is typically provided by an input manager +client, which usually is part of a window manager. + + + + + InputOnly window +WindowInputOnly + + +An +InputOnly +window is a window that cannot be used for graphics requests. +InputOnly +windows are invisible and are used to control such things as cursors, +input event generation, and grabbing. +InputOnly +windows cannot have +InputOutput +windows as inferiors. + + + + + InputOutput window +WindowInputOutput + + +An +InputOutput +window is the normal kind of window that is used for both input and output. +InputOutput +windows can have both +InputOutput +and +InputOnly +windows as inferiors. + + + + + Internationalization +Internationalization + + +The process of making software adaptable to the requirements +of different native languages, local customs, and character string encodings. +Making a computer program adaptable to different locales +without program source modifications or recompilation. + + + + + ISO2022 +ISO2022 + + +ISO standard for code extension techniques for 7-bit and 8-bit coded +character sets. + + + + + Key grabbing +Keygrabbing + + +Keys on the keyboard can be passively grabbed by a client. +When the key is pressed, +the keyboard is then actively grabbed by the client. + + + + + Keyboard grabbing +Keyboardgrabbing + + +A client can actively grab control of the keyboard, and key events +will be sent to that client rather than the client the events would +normally have been sent to. + + + + + Keysym +Keysym + + +An encoding of a symbol on a keycap on a keyboard. + + + + + Latin-1 +Latin-1 + + +The coded character set defined by the ISO8859-1 standard. + + + + + Latin Portable Character Encoding +Latin Portable Character Encoding + + +The encoding of the X Portable Character Set using the Latin-1 codepoints +plus ASCII control characters. +If a string is said to be in the Latin Portable Character Encoding, +then it only contains characters from the X Portable Character Set, +not all of Latin-1. + + + + + Locale +Locale + + +The international environment of a computer program defining the ``localized'' +behavior of that program at run-time. +This information can be established from one or more sets of localization data. +ANSI C defines locale-specific processing by C system library calls. +See ANSI C and the X/Open Portability Guide specifications for more details. +In this specification, on implementations that conform to the ANSI C library, +the ``current locale'' is the current setting of the LC_CTYPE +setlocale +category. +Associated with each locale is a text encoding. When text is processed +in the context of a locale, the text must be in the encoding of the locale. +The current locale affects Xlib in its: + + +Encoding and processing of input method text + + +Encoding of resource files and values + + +Encoding and imaging of text strings + + +Encoding and decoding for inter-client text communication + + + + + + Locale name +Locale name + + +The identifier used to select the desired locale for the host C library +and X library functions. +On ANSI C library compliant systems, +the locale argument to the +setlocale +function. + + + + + Localization +Localization + + +The process of establishing information within a computer system specific +to the operation of particular native languages, local customs +and coded character sets. +(XPG3) + + + + + Mapped +Mapped window + + +A window is said to be mapped if a map call has been performed on it. +Unmapped windows and their inferiors are never viewable or visible. + + + + + Modifier keys +Modifier keys + + +Shift, Control, Meta, Super, Hyper, Alt, Compose, Apple, CapsLock, +ShiftLock, and similar keys are called modifier keys. + + + + + Monochrome +Monochrome + + +Monochrome is a special case of +StaticGray +in which there are only two colormap entries. + + + + + Multibyte +Multibyte + + +A character whose codepoint is stored in more than one byte; +any encoding which can contain multibyte characters; +text in a multibyte encoding. +The ``char *'' null-terminated string datatype in ANSI C. +Note that references in this document to multibyte strings +imply only that the strings may contain multibyte characters. + + + + + Obscure +Obscure + + +A window is obscured if some other window obscures it. +A window can be partially obscured and so still have visible regions. +Window A obscures window B if both are viewable +InputOutput +windows, if A is higher in the global stacking order, +and if the rectangle defined by the outside +edges of A intersects the rectangle defined by the outside edges of B. +Note the distinction between obscures and occludes. +Also note that window borders are included in the calculation. + + + + + Occlude +Occlude + + +A window is occluded if some other window occludes it. +Window A occludes window B if both are mapped, +if A is higher in the global stacking order, +and if the rectangle defined by the outside edges of A intersects the rectangle defined +by the outside edges of B. +Note the distinction between occludes and obscures. +Also note that window borders are included in the calculation +and that +InputOnly +windows never obscure other windows but can occlude other windows. + + + + + Padding +Padding + + +Some padding bytes are inserted in the data stream to maintain +alignment of the protocol requests on natural boundaries. +This increases ease of portability to some machine architectures. + + + + + Parent window +Windowparent + + +If C is a child of P, then P is the parent of C. + + + + + Passive grab +Passive grab + + +Grabbing a key or button is a passive grab. +The grab activates when the key or button is actually pressed. + + + + + Pixel value +Pixel value + + +A pixel is an N-bit value, +where N is the number of bit planes used in a particular window or pixmap +(that is, is the depth of the window or pixmap). +A pixel in a window indexes a colormap to derive an actual color to be +displayed. + + + + + Pixmap +Pixmap + + +A pixmap is a three-dimensional array of bits. +A pixmap is normally thought of as a two-dimensional array of pixels, +where each pixel can be a value from 0 to 2N-1, +and where N is the depth (z axis) of the pixmap. +A pixmap can also be thought of as a stack of N bitmaps. +A pixmap can only be used on the screen that it was created in. + + + + + Plane +Plane + + +When a pixmap or window is thought of as a stack of bitmaps, each +bitmap is called a plane or bit plane. + + + + + Plane mask +Planemask + + +Graphics operations can be restricted to only affect a subset of bit +planes of a destination. +A plane mask is a bit mask describing which planes are to be modified. +The plane mask is stored in a graphics context. + + + + + Pointer +Pointer + + +The pointer is the pointing device currently attached to the cursor +and tracked on the screens. + + + + + Pointer grabbing +Pointergrabbing + + +A client can actively grab control of the pointer. +Then button and motion events will be sent to that client +rather than the client the events would normally have been sent to. + + + + + Pointing device +Pointing device + + +A pointing device is typically a mouse, tablet, or some other +device with effective dimensional motion. +The core protocol defines only one visible cursor, +which tracks whatever pointing device is attached as the pointer. + + + + + POSIX +POSIX + + +Portable Operating System Interface, ISO/IEC 9945-1 (IEEE Std 1003.1). + + + + + POSIX Portable Filename Character Set +POSIX Portable Filename Character Set + + +The set of 65 characters which can be used in naming files on a POSIX-compliant +host that are correctly processed in all locales. +The set is: + + + +a..z A..Z 0..9 ._- + + + + + + Property +Property + + +Windows can have associated properties that consist of a name, a type, +a data format, and some data. +The protocol places no interpretation on properties. +They are intended as a general-purpose naming mechanism for clients. +For example, clients might use properties to share information such as resize +hints, program names, and icon formats with a window manager. + + + + + Property list +Property list + + +The property list of a window is the list of properties that have +been defined for the window. + + + + + PseudoColor +PseudoColor + + +PseudoColor +is a class of colormap in which a pixel value indexes the colormap entry to +produce an independent RGB value; +that is, the colormap is viewed as an array of triples (RGB values). +The RGB values can be changed dynamically. + + + + + Rectangle +Rectangle + + +A rectangle specified by [x,y,w,h] has an infinitely thin +outline path with corners at [x,y], [x+w,y], [x+w,y+h], and [x, y+h]. +When a rectangle is filled, +the lower-right edges are not drawn. +For example, +if w=h=0, +nothing would be drawn. +For w=h=1, +a single pixel would be drawn. + + + + + Redirecting control +Redirecting control + + +Window managers (or client programs) may enforce window layout +policy in various ways. +When a client attempts to change the size or position of a window, +the operation may be redirected to a specified client +rather than the operation actually being performed. + + + + + Reply +Reply + + +Information requested by a client program using the X protocol +is sent back to the client with a reply. +Both events and replies are multiplexed on the same connection. +Most requests do not generate replies, +but some requests generate multiple replies. + + + + + Request +Request + + +A command to the server is called a request. +It is a single block of data sent over a connection. + + + + + Resource +Resource + + +Windows, pixmaps, cursors, fonts, graphics contexts, and colormaps are +known as resources. +They all have unique identifiers associated with them for naming purposes. +The lifetime of a resource usually is bounded by the lifetime of the +connection over which the resource was created. + + + + + RGB values +RGB values + + +RGB values are the red, green, and blue intensity values that are used +to define a color. +These values are always represented as 16-bit, unsigned numbers, with 0 +the minimum intensity and 65535 the maximum intensity. +The X server scales these values to match the display hardware. + + + + + Root +Root + + +The root of a pixmap or graphics context is the same as the root +of whatever drawable was used when the pixmap or GC was created. +The root of a window is the root window under which the window was created. + + + + + Root window +Windowroot + + +Each screen has a root window covering it. +The root window cannot be reconfigured or unmapped, +but otherwise it acts as a full-fledged window. +A root window has no parent. + + + + + Save set +Save set + + +The save set of a client is a list of other clients' windows that, +if they are inferiors of one of the client's windows at connection +close, should not be destroyed and that should be remapped +if currently unmapped. +Save sets are typically used by window managers to avoid +lost windows if the manager should terminate abnormally. + + + + + Scanline +Scanline + + +A scanline is a list of pixel or bit values viewed as a horizontal +row (all values having the same y coordinate) of an image, with the +values ordered by increasing the x coordinate. + + + + + Scanline order +Scanlineorder + + +An image represented in scanline order contains scanlines ordered by +increasing the y coordinate. + + + + + Screen +Screen +Screenstructure +Displaystructure + + +A server can provide several independent screens, +which typically have physically independent monitors. +This would be the expected configuration when there is only a single keyboard +and pointer shared among the screens. +A +Screen +structure contains the information about that screen +and is linked to the +Display +structure. + + + + + Selection +Selection + + +A selection can be thought of as an indirect property with dynamic +type. +That is, rather than having the property stored in the X server, +it is maintained by some client (the owner). +A selection is global and is thought of as belonging to the user +and being maintained by clients, +rather than being private to a particular window subhierarchy +or a particular set of clients. +When a client asks for the contents of +a selection, it specifies a selection target type, +which can be used to control the transmitted representation of the contents. +For example, if the selection is ``the last thing the user clicked on,'' +and that is currently an image, then the target type might specify +whether the contents of the image should be sent in XY format or +Z format. + + +The target type can also be used to control the class of +contents transmitted; for example, +asking for the ``looks'' (fonts, line +spacing, indentation, and so forth) of a paragraph selection, rather than the +text of the paragraph. +The target type can also be used for other +purposes. +The protocol does not constrain the semantics. + + + + + Server +Server + + +The server, which is also referred to as the X server, +provides the basic windowing mechanism. +It handles IPC connections from clients, +multiplexes graphics requests onto the screens, +and demultiplexes input back to the appropriate clients. + + + + + Server grabbing +Servergrabbing + + +The server can be grabbed by a single client for exclusive use. +This prevents processing of any requests from other client connections until +the grab is completed. +This is typically only a transient state for such things as rubber-banding, +pop-up menus, or executing requests indivisibly. + + + + + Shift sequence +Shift sequence + + +ISO2022 defines control characters and escape sequences +which temporarily (single shift) or permanently (locking shift) cause a +different character set to be in effect (``invoking'' a character set). + + + + + Sibling +Sibling + + +Children of the same parent window are known as sibling windows. + + + + + Stacking order +Stacking order + + +Sibling windows, similar to sheets of paper on a desk, +can stack on top of each other. +Windows above both obscure and occlude lower windows. +The relationship between sibling windows is known as the stacking order. + + + + + State-dependent encoding +State-dependent encoding + + +An encoding in which an invocation of a charset can apply to multiple +characters in sequence. +A state-dependent encoding begins in an ``initial state'' +and enters other ``shift states'' when specific ``shift sequences'' +are encountered in the byte sequence. +In ISO2022 terms, +this means use of locking shifts, not single shifts. + + + + + State-independent encoding +State-independent encoding + + +Any encoding in which the invocations of the charsets are fixed, +or span only a single character. +In ISO2022 terms, +this means use of at most single shifts, not locking shifts. + + + + + StaticColor +StaticColor + + +StaticColor +can be viewed as a degenerate case of +PseudoColor +in which the RGB values are predefined and read-only. + + + + + StaticGray +StaticGray + + +StaticGray +can be viewed as a degenerate case of +GrayScale +in which the gray values are predefined and read-only. +The values are typically linear or near-linear increasing ramps. + + + + + Status +Status + + +Many Xlib functions return a success status. +If the function does not succeed, +however, its arguments are not disturbed. + + + + + Stipple +Stipple + + +A stipple pattern is a bitmap that is used to tile a region to serve +as an additional clip mask for a fill operation with the foreground +color. + + + + + STRING encoding + + +Latin-1, plus tab and newline. + + + + + String Equivalence +String Equivalence + + +Two ISO Latin-1 STRING8 values are considered equal if they are the same +length and if corresponding bytes are either equal or are equivalent as +follows: decimal values 65 to 90 inclusive (characters ``A'' to ``Z'') are +pairwise equivalent to decimal values 97 to 122 inclusive +(characters ``a'' to ``z''), decimal values 192 to 214 inclusive +(characters ``A grave'' to ``O diaeresis'') are pairwise equivalent to decimal +values 224 to 246 inclusive (characters ``a grave'' to ``o diaeresis''), +and decimal values 216 to 222 inclusive (characters ``O oblique'' to ``THORN'') +are pairwise equivalent to decimal values 246 to 254 inclusive +(characters ``o oblique'' to ``thorn''). + + + + + Tile +Tile + + +A pixmap can be replicated in two dimensions to tile a region. +The pixmap itself is also known as a tile. + + + + + Timestamp +Timestamp + + +A timestamp is a time value expressed in milliseconds. +It is typically the time since the last server reset. +Timestamp values wrap around (after about 49.7 days). +The server, given its current time is represented by timestamp T, +always interprets timestamps from clients by treating half +of the timestamp space as being earlier in time than T +and half of the timestamp space as being later in time than T. +One timestamp value, represented by the constant +CurrentTime, +is never generated by the server. +This value is reserved for use in requests to represent the current server time. + + + + + TrueColor +TrueColor + + +TrueColor +can be viewed as a degenerate case of +DirectColor +in which the subfields in the pixel value directly encode the corresponding RGB +values. +That is, the colormap has predefined read-only RGB values. +The values are typically linear or near-linear increasing ramps. + + + + + Type +Type + + +A type is an arbitrary atom used to identify the interpretation of property +data. +Types are completely uninterpreted by the server. +They are solely for the benefit of clients. +X predefines type atoms for many frequently used types, +and clients also can define new types. + + + + + Viewable +Viewable + + +A window is viewable if it and all of its ancestors are mapped. +This does not imply that any portion of the window is actually visible. +Graphics requests can be performed on a window when it is not +viewable, but output will not be retained unless the server is maintaining +backing store. + + + + + Visible +Visible + + +A region of a window is visible if someone looking at the screen can +actually see it; that is, the window is viewable and the region is not occluded +by any other window. + + + + + Whitespace +Whitespace + + +Any spacing character. +On implementations that conform to the ANSI C library, +whitespace is any character for which +isspace +returns true. + + + + + Window gravity +Windowgravity + + +When windows are resized, +subwindows may be repositioned automatically relative to some position in the +window. +This attraction of a subwindow to some part of its parent is known +as window gravity. + + + + + Window manager +Windowmanager + + +Manipulation of windows on the screen and much of the user interface +(policy) is typically provided by a window manager client. + + + + + X Portable Character Set +X Portable Character Set + + +A basic set of 97 characters which are assumed to exist in all +locales supported by Xlib. This set contains the following characters: + +a..z A..Z 0..9 +!"#$%&'()*+,-./:;<=>?@[\\]^_`{|}~ +<space>, <tab>, and <newline> + + + +This is the left/lower half (also called the G0 set) +of the graphic character set of ISO8859-1 plus <space>, <tab>, and <newline>. +It is also the set of graphic characters in 7-bit ASCII plus the same +three control characters. +The actual encoding of these characters on the host is system dependent; +see the Host Portable Character Encoding. + + + + + XLFD +XLFD + + +The X Logical Font Description Conventions that define a standard syntax +for structured font names. + + + + + XY format +XY format + + +The data for a pixmap is said to be in XY format if it is organized as +a set of bitmaps representing individual bit planes with the planes +appearing from most-significant to least-significant bit order. + + + + + Z format +Z format + + +The data for a pixmap is said to be in Z format if it is organized as +a set of pixel values in scanline order. + + + + + +References + +Draft Proposed Multibyte Extension of ANSI C, Draft 1.1 +November 30, 1989 SC22/C WG/SWG IPSJ/ITSCJ Japan + + + +ISO2022: Information processing - ISO 7-bit and 8-bit coded character +sets - Code extension techniques. + + + +ISO8859-1: Information processing - 8-bit single-byte coded graphic +character sets - Part 1: Latin alphabet No. 1. + + + +<acronym>POSIX</acronym>: Information Technology - Portable Operating System Interface (<acronym>POSIX</acronym>) - +Part 1: System Application Program Interface (API) [C Language], +ISO/IEC 9945-1. + + + +Text of ISO/IEC/DIS 9541-1, Information Processing - Font Information +Interchange - Part 1: Architecture. + + + +X/Open Portability Guide, Issue 3, December 1988 (XPG3), X/Open Company, +Ltd, Prentice-Hall, Inc. 1989. ISBN 0-13-685835-8. +(See especially Volume 3: XSI Supplementary Definitions.) + + + + -- cgit v1.2.3