Aliases to itself don't make much sense.
This changes occurances of:
xy_UV.UTF-8: xy_UV.UTF-8
to
xy_UV: xy_UV.UTF-8
where applicable.
Signed-off-by: Egbert Eich <eich@freedesktop.org>
Reviewed-by: James Cloos <cloos@jhcloos.com>
- add an entry to include the default en_US compose file
for the ja_JP, ko_KR, th_TH, zh_CN, zh_HK and zh_TW locales.
- add missing entries for zh_CN. and zh_HK and am_ET.
- change entries for the UTF-8 encoding for ru_RU, ja_JP,
ko_KR, th_TH and zh_TW to point to their native directory
entries.
Signed-off-by: Egbert Eich <eich@freedesktop.org>
Reviewed-by: James Cloos <cloos@jhcloos.com>
Private is a struct member name in mingw-w64 <winioctl.h>, causing this
useless define in a private header to break the build.
Signed-off-by: Yaakov Selkowitz <yselkowitz@users.sourceforge.net>
Reviewed-by: Jon TURNEY <jon.turney@dronecode.org.uk>
Currently keysymdef.h is found by using the includedir of xproto. This doesn't
work when cross-compiling with a sysroot as that ends up being /usr/include/X11,
not a path into the cross-build environment.
So, add an option to allow explicitly specifying the location of keysymdef.h,
and verify that the specified or found path exists.
(original patch by Martin Jansa <martin.jansa@gmail.com>, revised by myself)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Reviewed-by: Dan Nicholson <dbn.lists@gmail.com>
Reviewed-by: Daniel Stone <daniel@fooishbar.org>
Also, SYNTAX -> SYNOPSIS so function prototypes get parsed by doclifter.
This appears to have been somebody's thinko, it's only in a few of the files.
Signed-off-by: Eric S. Raymond <esr@thyrsus.com>
The problem with these macros is that they rely on being able to
center the note label. That doesn't play well with modern HTML,
not anyway without coomplications like CSS. This use was just a cute
trick, not adding enough value to be kept.
Two steps: First, expand tabs to 8 spaces in code and structure
listings. Second, make the .Ds used to wrap code listings switch to
constant-width font (CW) rather than numeric font position 1, which
maps to R on most systems.
It is possible some archaic systems won't know what CW is, but the
only risk is that code listings won't look quite right on troff
devices; the PostScript and DVI drivers definitely grok it, so those
important cases are OK.
The purpose of these changes is to get rid of presentation-level
markup so these pages will lift clean to DocBook.
Signed-off-by: Eric S. Raymond <esr@thyrsus.com>
These sequences look sensible to me. I added them to the APL-related
section of Mathematical Operators—they're in that section of Unicode
anyway.
https://bugs.freedesktop.org/show_bug.cgi?id=51922
Signed-off-by: Will Thompson <will@willthompson.co.uk>
Reviewed-by: Daniel Stone <daniel@fooishbar.org>
Fixes leaks in error paths found by Parfait 1.0.0:
Error: X Resource Leak
Leaked X Resource pix
at line 62 of CrBFData.c in function 'XCreateBitmapFromData'.
pix initialized at line 60 with XCreatePixmap
Error: X Resource Leak
Leaked X Resource pix
at line 70 of CrPFBData.c in function 'XCreatePixmapFromBitmapData'.
pix initialized at line 66 with XCreatePixmap
Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>
Reviewed-by: Aaron Plattner <aplattner@nvidia.com>
Reassigned squences with minus and a or o (vice versa and lower and
upper case) to conform existing series and not resulting in tilde.
Also added noe missing underscore sequence.
Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>
The compose-check script only handles compiled Compose files, not
the Compose.pre files. One must remember to use:
./autogen.sh; make; make check
when reviewing patches to the Compose.pre files....
Signed-off-by: James Cloos <cloos@jhcloos.com>
autoconf 2.63 doesn't seem to like the nested AC_CHECK_DECL/FUNC. So do
the tests separately.
Reported-by: Dave Airlie
Signed-off-by: Julien Cristau <jcristau@debian.org>
GNU/kFreeBSD has issetugid in libc (for legacy apps?), but doesn't
declare it anywhere, causing gcc to error out with
-Werror=implicit-function-declaration. Use AC_CHECK_DECL in addition to
AC_CHECK_FUNC so we disable this code instead of failing to build it.
Debian bug#669670 <http://bugs.debian.org/669670>
Signed-off-by: Julien Cristau <jcristau@debian.org>
Reviewed-by: Alan Coopersmith <alan.coopersmith@oracle.com>
Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>
(Some of) the Dstroke and dstroke entries already were present as U011[01],
even though XK_Dstroke and XK_dstroke are part of the latin2 set in keysymdef.h.
The addition of <Multi_key> <o> <apostrophe> as a postfix version of
<Multi_key> <apostrophe> <o> blocks the existing entries for ǻ and Ǻ.
That prevents its and <Multi_key> <O> <apostrophe>’s addition.
Signed-off-by: James Cloos <cloos@jhcloos.com>
Wait for all other threads to release the user-level lock when
acquiring it. This ensures that only one thread at a time holds the
user-level lock, necessary as it is a nesting lock and a single
variable is used to determine when the lock is nesting and when it is
contended.
Signed-off-by: Keith Packard <keithp@keithp.com>
Reviewed-by: Jamey Sharp <jamey@minilop.net>
(caddr_t) isn't used anywhere else in xcb or libX11.
Cast to (char *) for consistency.
Removing this cast allows building for MinGW without patching.
v2: Cast to (char *) rather than just dropping the cast
Signed-off-by: Jon TURNEY <jon.turney@dronecode.org.uk>
Reviewed-by: Alan Coopersmith <alan.coopersmith@oracle.com>
This reverts commit f09c5299a3.
The TCP fallback ended up falling back to UNIX socket connection if
$DISPLAY was set to e.g. some.host:0 and the initial attempt failed.
Debian bug#659558 <http://bugs.debian.org/659558>
Signed-off-by: Julien Cristau <jcristau@debian.org>
Conflicts:
src/OpenDis.c
There is no XK_Ssharp symbol for U+1E9E LATIN CAPITAL LETTER SHARP S,
so use the U1e9e symbol in the Compose sequence.
(Compose sequences do not work when the target symbol is unknown.)
Signed-off-by: James Cloos <cloos@jhcloos.com>
Related: https://bugs.freedesktop.org/show_bug.cgi?id=19687
Signed-off-by: Marko Myllynen <myllynen@redhat.com>
Reviewed-by: Matt Dew <marcoz@osource.org>
Signed-off-by: James Cloos <cloos@jhcloos.com>
