Convert http:// -> https:// where possible

Signed-off-by: Ran Benita <ran234@gmail.com>
master
Ran Benita 2017-12-21 14:18:07 +02:00
parent 4fccdee383
commit 767fa86d42
10 changed files with 17 additions and 17 deletions

4
NEWS
View File

@ -241,7 +241,7 @@ libxkbcommon 0.4.1 - 2014-03-27
is converted to an appropriate control character. is converted to an appropriate control character.
This matches the behavior of libX11's XLookupString(3), and This matches the behavior of libX11's XLookupString(3), and
required by the XKB specification: required by the XKB specification:
http://www.x.org/releases/current/doc/kbproto/xkbproto.html#Interpreting_the_Control_Modifier https://www.x.org/releases/current/doc/kbproto/xkbproto.html#Interpreting_the_Control_Modifier
https://bugs.freedesktop.org/show_bug.cgi?id=75892 https://bugs.freedesktop.org/show_bug.cgi?id=75892
@ -304,7 +304,7 @@ libxkbcommon 0.3.2 - 2013-11-22
- Apply capitalization transformation on keysyms in - Apply capitalization transformation on keysyms in
xkb_keysym_get_one_sym(), to match the behavior specified in the XKB xkb_keysym_get_one_sym(), to match the behavior specified in the XKB
specification: specification:
http://www.x.org/releases/current/doc/kbproto/xkbproto.html#Interpreting_the_Lock_Modifier https://www.x.org/releases/current/doc/kbproto/xkbproto.html#Interpreting_the_Lock_Modifier
- Support byacc for generating the parser, in addition to Bison. - Support byacc for generating the parser, in addition to Bison.

View File

@ -31,7 +31,7 @@ While libxkbcommon's API is somewhat derived from the classic XKB API as found
in X11/extensions/XKB.h and friends, it has been substantially reworked to in X11/extensions/XKB.h and friends, it has been substantially reworked to
expose fewer internal details to clients. expose fewer internal details to clients.
See the [API Documentation](http://xkbcommon.org/doc/current/modules.html). See the [API Documentation](https://xkbcommon.org/doc/current/modules.html).
## Dataset ## Dataset
@ -39,7 +39,7 @@ libxkbcommon does not distribute a keymap dataset itself, other than for
testing purposes. The most common dataset is xkeyboard-config, which is used testing purposes. The most common dataset is xkeyboard-config, which is used
by all current distributions for their X11 XKB data. More information on by all current distributions for their X11 XKB data. More information on
xkeyboard-config is available here: xkeyboard-config is available here:
http://www.freedesktop.org/wiki/Software/XKeyboardConfig https://www.freedesktop.org/wiki/Software/XKeyboardConfig
The dataset for Compose is distributed in libX11, as part of the X locale The dataset for Compose is distributed in libX11, as part of the X locale
data. data.
@ -51,7 +51,7 @@ See [Compatibility](doc/compat.md) notes.
## Development ## Development
An extremely rudimentary homepage can be found at An extremely rudimentary homepage can be found at
http://xkbcommon.org https://xkbcommon.org
xkbcommon is maintained in git at xkbcommon is maintained in git at
https://github.com/xkbcommon/libxkbcommon https://github.com/xkbcommon/libxkbcommon

View File

@ -24,7 +24,7 @@ dnl Process this file with autoconf to create configure.
AC_PREREQ([2.62]) AC_PREREQ([2.62])
AC_INIT([libxkbcommon], [0.8.0], AC_INIT([libxkbcommon], [0.8.0],
[https://bugs.freedesktop.org/enter_bug.cgi?product=libxkbcommon], [https://bugs.freedesktop.org/enter_bug.cgi?product=libxkbcommon],
[libxkbcommon], [http://xkbcommon.org]) [libxkbcommon], [https://xkbcommon.org])
AC_CONFIG_SRCDIR([Makefile.am]) AC_CONFIG_SRCDIR([Makefile.am])
AC_CONFIG_HEADERS([src/config.h]) AC_CONFIG_HEADERS([src/config.h])
AC_CONFIG_MACRO_DIR([m4]) AC_CONFIG_MACRO_DIR([m4])

View File

@ -23,7 +23,7 @@
#ifndef CCAN_DARRAY_H #ifndef CCAN_DARRAY_H
#define CCAN_DARRAY_H #define CCAN_DARRAY_H
/* Originally taken from: http://ccodearchive.net/info/darray.html /* Originally taken from: https://ccodearchive.net/info/darray.html
* But modified for libxkbcommon. */ * But modified for libxkbcommon. */
#include <stdlib.h> #include <stdlib.h>

View File

@ -876,7 +876,7 @@ err:
} }
/* /*
* http://www.x.org/releases/current/doc/kbproto/xkbproto.html#Interpreting_the_Lock_Modifier * https://www.x.org/releases/current/doc/kbproto/xkbproto.html#Interpreting_the_Lock_Modifier
*/ */
static bool static bool
should_do_caps_transformation(struct xkb_state *state, xkb_keycode_t kc) should_do_caps_transformation(struct xkb_state *state, xkb_keycode_t kc)
@ -890,7 +890,7 @@ should_do_caps_transformation(struct xkb_state *state, xkb_keycode_t kc)
} }
/* /*
* http://www.x.org/releases/current/doc/kbproto/xkbproto.html#Interpreting_the_Control_Modifier * https://www.x.org/releases/current/doc/kbproto/xkbproto.html#Interpreting_the_Control_Modifier
*/ */
static bool static bool
should_do_ctrl_transformation(struct xkb_state *state, xkb_keycode_t kc) should_do_ctrl_transformation(struct xkb_state *state, xkb_keycode_t kc)

View File

@ -80,7 +80,7 @@ is_valid_utf8(const char *ss, size_t len)
/* This beauty is from: /* This beauty is from:
* The Unicode Standard Version 6.2 - Core Specification, Table 3.7 * The Unicode Standard Version 6.2 - Core Specification, Table 3.7
* http://www.unicode.org/versions/Unicode6.2.0/ch03.pdf#G7404 * https://www.unicode.org/versions/Unicode6.2.0/ch03.pdf#G7404
* We can optimize if needed. */ * We can optimize if needed. */
while (i < len) while (i < len)
{ {

View File

@ -26,7 +26,7 @@
/* /*
* References for the lonesome traveler: * References for the lonesome traveler:
* Xkb protocol specification: * Xkb protocol specification:
* http://www.x.org/releases/current/doc/kbproto/xkbproto.html * https://www.x.org/releases/current/doc/kbproto/xkbproto.html
* The XCB xkb XML protocol file: * The XCB xkb XML protocol file:
* /user/share/xcb/xkb.xml * /user/share/xcb/xkb.xml
* The XCB xkb header file: * The XCB xkb header file:

View File

@ -36,7 +36,7 @@ test_is_valid_utf8(void)
{ {
/* /*
* Mostly taken from: * Mostly taken from:
* http://www.cl.cam.ac.uk/~mgk25/ucs/examples/UTF-8-test.txt * https://www.cl.cam.ac.uk/~mgk25/ucs/examples/UTF-8-test.txt
*/ */
VALID("ascii"); VALID("ascii");

View File

@ -78,7 +78,7 @@ extern "C" {
* *
* @note At this point, you may consider setting various XKB controls and * @note At this point, you may consider setting various XKB controls and
* XKB per-client flags. For example, enabling detectable autorepeat: \n * XKB per-client flags. For example, enabling detectable autorepeat: \n
* http://www.x.org/releases/current/doc/kbproto/xkbproto.html#Detectable_Autorepeat * https://www.x.org/releases/current/doc/kbproto/xkbproto.html#Detectable_Autorepeat
* *
* Next, you need to react to state changes (e.g. a modifier was pressed, * Next, you need to react to state changes (e.g. a modifier was pressed,
* the layout was changed) and to keymap changes (e.g. a tool like xkbcomp, * the layout was changed) and to keymap changes (e.g. a tool like xkbcomp,
@ -95,7 +95,7 @@ extern "C" {
* @note It is also possible to use the KeyPress/KeyRelease @p state * @note It is also possible to use the KeyPress/KeyRelease @p state
* field to find the effective modifier and layout state, instead of * field to find the effective modifier and layout state, instead of
* using XkbStateNotify: \n * using XkbStateNotify: \n
* http://www.x.org/releases/current/doc/kbproto/xkbproto.html#Computing_A_State_Field_from_an_XKB_State * https://www.x.org/releases/current/doc/kbproto/xkbproto.html#Computing_A_State_Field_from_an_XKB_State
* \n However, XkbStateNotify is more accurate. * \n However, XkbStateNotify is more accurate.
* *
* @note There is no need to call xkb_state_update_key(); the state is * @note There is no need to call xkb_state_update_key(); the state is

View File

@ -177,7 +177,7 @@ typedef uint32_t xkb_keycode_t;
* somewhat more general, in that they can also represent some "function", * somewhat more general, in that they can also represent some "function",
* such as "Left" or "Right" for the arrow keys. For more information, * such as "Left" or "Right" for the arrow keys. For more information,
* see: * see:
* http://www.x.org/releases/X11R7.7/doc/xproto/x11protocol.html#keysym_encoding * https://www.x.org/releases/current/doc/xproto/x11protocol.html#keysym_encoding
* *
* Specifically named keysyms can be found in the * Specifically named keysyms can be found in the
* xkbcommon/xkbcommon-keysyms.h header file. Their name does not include * xkbcommon/xkbcommon-keysyms.h header file. Their name does not include
@ -385,7 +385,7 @@ struct xkb_rule_names {
* Similarly, the UTF-8/UTF-32 string produced is capitalized. * Similarly, the UTF-8/UTF-32 string produced is capitalized.
* *
* This is described in: * This is described in:
* http://www.x.org/releases/current/doc/kbproto/xkbproto.html#Interpreting_the_Lock_Modifier * https://www.x.org/releases/current/doc/kbproto/xkbproto.html#Interpreting_the_Lock_Modifier
* *
* - Control transformation. If the Control modifier is active and * - Control transformation. If the Control modifier is active and
* was not consumed by the translation process, the string produced * was not consumed by the translation process, the string produced
@ -393,7 +393,7 @@ struct xkb_rule_names {
* applicable). Keysyms are not affected. * applicable). Keysyms are not affected.
* *
* This is described in: * This is described in:
* http://www.x.org/releases/current/doc/kbproto/xkbproto.html#Interpreting_the_Control_Modifier * https://www.x.org/releases/current/doc/kbproto/xkbproto.html#Interpreting_the_Control_Modifier
* *
* Each relevant function discusses which transformations it performs. * Each relevant function discusses which transformations it performs.
* *