From 3f5e1072301f179a0bba52e09b49daa63bd46726 Mon Sep 17 00:00:00 2001 From: Hojun-Cho Date: Wed, 12 Aug 2026 16:24:22 +0900 Subject: [PATCH] docs: record data provenance and runtime constraints --- LICENSES/GPL-2.0-or-later.txt | 339 ++++++++++++++++++++++++++++++++++ LICENSES/README.md | 11 ++ README.md | 178 +++++++++++------- docs/PROVENANCE.md | 72 ++++++++ 4 files changed, 530 insertions(+), 70 deletions(-) create mode 100644 LICENSES/GPL-2.0-or-later.txt create mode 100644 LICENSES/README.md create mode 100644 docs/PROVENANCE.md diff --git a/LICENSES/GPL-2.0-or-later.txt b/LICENSES/GPL-2.0-or-later.txt new file mode 100644 index 0000000..d159169 --- /dev/null +++ b/LICENSES/GPL-2.0-or-later.txt @@ -0,0 +1,339 @@ + GNU GENERAL PUBLIC LICENSE + Version 2, June 1991 + + Copyright (C) 1989, 1991 Free Software Foundation, Inc., + 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + + Preamble + + The licenses for most software are designed to take away your +freedom to share and change it. By contrast, the GNU General Public +License is intended to guarantee your freedom to share and change free +software--to make sure the software is free for all its users. This +General Public License applies to most of the Free Software +Foundation's software and to any other program whose authors commit to +using it. (Some other Free Software Foundation software is covered by +the GNU Lesser General Public License instead.) You can apply it to +your programs, too. + + When we speak of free software, we are referring to freedom, not +price. Our General Public Licenses are designed to make sure that you +have the freedom to distribute copies of free software (and charge for +this service if you wish), that you receive source code or can get it +if you want it, that you can change the software or use pieces of it +in new free programs; and that you know you can do these things. + + To protect your rights, we need to make restrictions that forbid +anyone to deny you these rights or to ask you to surrender the rights. +These restrictions translate to certain responsibilities for you if you +distribute copies of the software, or if you modify it. + + For example, if you distribute copies of such a program, whether +gratis or for a fee, you must give the recipients all the rights that +you have. You must make sure that they, too, receive or can get the +source code. And you must show them these terms so they know their +rights. + + We protect your rights with two steps: (1) copyright the software, and +(2) offer you this license which gives you legal permission to copy, +distribute and/or modify the software. + + Also, for each author's protection and ours, we want to make certain +that everyone understands that there is no warranty for this free +software. If the software is modified by someone else and passed on, we +want its recipients to know that what they have is not the original, so +that any problems introduced by others will not reflect on the original +authors' reputations. + + Finally, any free program is threatened constantly by software +patents. We wish to avoid the danger that redistributors of a free +program will individually obtain patent licenses, in effect making the +program proprietary. To prevent this, we have made it clear that any +patent must be licensed for everyone's free use or not licensed at all. + + The precise terms and conditions for copying, distribution and +modification follow. + + GNU GENERAL PUBLIC LICENSE + TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION + + 0. This License applies to any program or other work which contains +a notice placed by the copyright holder saying it may be distributed +under the terms of this General Public License. The "Program", below, +refers to any such program or work, and a "work based on the Program" +means either the Program or any derivative work under copyright law: +that is to say, a work containing the Program or a portion of it, +either verbatim or with modifications and/or translated into another +language. (Hereinafter, translation is included without limitation in +the term "modification".) Each licensee is addressed as "you". + +Activities other than copying, distribution and modification are not +covered by this License; they are outside its scope. The act of +running the Program is not restricted, and the output from the Program +is covered only if its contents constitute a work based on the +Program (independent of having been made by running the Program). +Whether that is true depends on what the Program does. + + 1. You may copy and distribute verbatim copies of the Program's +source code as you receive it, in any medium, provided that you +conspicuously and appropriately publish on each copy an appropriate +copyright notice and disclaimer of warranty; keep intact all the +notices that refer to this License and to the absence of any warranty; +and give any other recipients of the Program a copy of this License +along with the Program. + +You may charge a fee for the physical act of transferring a copy, and +you may at your option offer warranty protection in exchange for a fee. + + 2. You may modify your copy or copies of the Program or any portion +of it, thus forming a work based on the Program, and copy and +distribute such modifications or work under the terms of Section 1 +above, provided that you also meet all of these conditions: + + a) You must cause the modified files to carry prominent notices + stating that you changed the files and the date of any change. + + b) You must cause any work that you distribute or publish, that in + whole or in part contains or is derived from the Program or any + part thereof, to be licensed as a whole at no charge to all third + parties under the terms of this License. + + c) If the modified program normally reads commands interactively + when run, you must cause it, when started running for such + interactive use in the most ordinary way, to print or display an + announcement including an appropriate copyright notice and a + notice that there is no warranty (or else, saying that you provide + a warranty) and that users may redistribute the program under + these conditions, and telling the user how to view a copy of this + License. (Exception: if the Program itself is interactive but + does not normally print such an announcement, your work based on + the Program is not required to print an announcement.) + +These requirements apply to the modified work as a whole. If +identifiable sections of that work are not derived from the Program, +and can be reasonably considered independent and separate works in +themselves, then this License, and its terms, do not apply to those +sections when you distribute them as separate works. But when you +distribute the same sections as part of a whole which is a work based +on the Program, the distribution of the whole must be on the terms of +this License, whose permissions for other licensees extend to the +entire whole, and thus to each and every part regardless of who wrote it. + +Thus, it is not the intent of this section to claim rights or contest +your rights to work written entirely by you; rather, the intent is to +exercise the right to control the distribution of derivative or +collective works based on the Program. + +In addition, mere aggregation of another work not based on the Program +with the Program (or with a work based on the Program) on a volume of +a storage or distribution medium does not bring the other work under +the scope of this License. + + 3. You may copy and distribute the Program (or a work based on it, +under Section 2) in object code or executable form under the terms of +Sections 1 and 2 above provided that you also do one of the following: + + a) Accompany it with the complete corresponding machine-readable + source code, which must be distributed under the terms of Sections + 1 and 2 above on a medium customarily used for software interchange; or, + + b) Accompany it with a written offer, valid for at least three + years, to give any third party, for a charge no more than your + cost of physically performing source distribution, a complete + machine-readable copy of the corresponding source code, to be + distributed under the terms of Sections 1 and 2 above on a medium + customarily used for software interchange; or, + + c) Accompany it with the information you received as to the offer + to distribute corresponding source code. (This alternative is + allowed only for noncommercial distribution and only if you + received the program in object code or executable form with such + an offer, in accord with Subsection b above.) + +The source code for a work means the preferred form of the work for +making modifications to it. For an executable work, complete source +code means all the source code for all modules it contains, plus any +associated interface definition files, plus the scripts used to +control compilation and installation of the executable. However, as a +special exception, the source code distributed need not include +anything that is normally distributed (in either source or binary +form) with the major components (compiler, kernel, and so on) of the +operating system on which the executable runs, unless that component +itself accompanies the executable. + +If distribution of executable or object code is made by offering +access to copy from a designated place, then offering equivalent +access to copy the source code from the same place counts as +distribution of the source code, even though third parties are not +compelled to copy the source along with the object code. + + 4. You may not copy, modify, sublicense, or distribute the Program +except as expressly provided under this License. Any attempt +otherwise to copy, modify, sublicense or distribute the Program is +void, and will automatically terminate your rights under this License. +However, parties who have received copies, or rights, from you under +this License will not have their licenses terminated so long as such +parties remain in full compliance. + + 5. You are not required to accept this License, since you have not +signed it. However, nothing else grants you permission to modify or +distribute the Program or its derivative works. These actions are +prohibited by law if you do not accept this License. Therefore, by +modifying or distributing the Program (or any work based on the +Program), you indicate your acceptance of this License to do so, and +all its terms and conditions for copying, distributing or modifying +the Program or works based on it. + + 6. Each time you redistribute the Program (or any work based on the +Program), the recipient automatically receives a license from the +original licensor to copy, distribute or modify the Program subject to +these terms and conditions. You may not impose any further +restrictions on the recipients' exercise of the rights granted herein. +You are not responsible for enforcing compliance by third parties to +this License. + + 7. If, as a consequence of a court judgment or allegation of patent +infringement or for any other reason (not limited to patent issues), +conditions are imposed on you (whether by court order, agreement or +otherwise) that contradict the conditions of this License, they do not +excuse you from the conditions of this License. If you cannot +distribute so as to satisfy simultaneously your obligations under this +License and any other pertinent obligations, then as a consequence you +may not distribute the Program at all. For example, if a patent +license would not permit royalty-free redistribution of the Program by +all those who receive copies directly or indirectly through you, then +the only way you could satisfy both it and this License would be to +refrain entirely from distribution of the Program. + +If any portion of this section is held invalid or unenforceable under +any particular circumstance, the balance of the section is intended to +apply and the section as a whole is intended to apply in other +circumstances. + +It is not the purpose of this section to induce you to infringe any +patents or other property right claims or to contest validity of any +such claims; this section has the sole purpose of protecting the +integrity of the free software distribution system, which is +implemented by public license practices. Many people have made +generous contributions to the wide range of software distributed +through that system in reliance on consistent application of that +system; it is up to the author/donor to decide if he or she is willing +to distribute software through any other system and a licensee cannot +impose that choice. + +This section is intended to make thoroughly clear what is believed to +be a consequence of the rest of this License. + + 8. If the distribution and/or use of the Program is restricted in +certain countries either by patents or by copyrighted interfaces, the +original copyright holder who places the Program under this License +may add an explicit geographical distribution limitation excluding +those countries, so that distribution is permitted only in or among +countries not thus excluded. In such case, this License incorporates +the limitation as if written in the body of this License. + + 9. The Free Software Foundation may publish revised and/or new versions +of the General Public License from time to time. Such new versions will +be similar in spirit to the present version, but may differ in detail to +address new problems or concerns. + +Each version is given a distinguishing version number. If the Program +specifies a version number of this License which applies to it and "any +later version", you have the option of following the terms and conditions +either of that version or of any later version published by the Free +Software Foundation. If the Program does not specify a version number of +this License, you may choose any version ever published by the Free Software +Foundation. + + 10. If you wish to incorporate parts of the Program into other free +programs whose distribution conditions are different, write to the author +to ask for permission. For software which is copyrighted by the Free +Software Foundation, write to the Free Software Foundation; we sometimes +make exceptions for this. Our decision will be guided by the two goals +of preserving the free status of all derivatives of our free software and +of promoting the sharing and reuse of software generally. + + NO WARRANTY + + 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY +FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN +OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES +PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED +OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF +MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS +TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE +PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, +REPAIR OR CORRECTION. + + 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING +WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR +REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, +INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING +OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED +TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY +YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER +PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE +POSSIBILITY OF SUCH DAMAGES. + + END OF TERMS AND CONDITIONS + + How to Apply These Terms to Your New Programs + + If you develop a new program, and you want it to be of the greatest +possible use to the public, the best way to achieve this is to make it +free software which everyone can redistribute and change under these terms. + + To do so, attach the following notices to the program. It is safest +to attach them to the start of each source file to most effectively +convey the exclusion of warranty; and each file should have at least +the "copyright" line and a pointer to where the full notice is found. + + + Copyright (C) + + This program is free software; you can redistribute it and/or modify + it under the terms of the GNU General Public License as published by + the Free Software Foundation; either version 2 of the License, or + (at your option) any later version. + + This program is distributed in the hope that it will be useful, + but WITHOUT ANY WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + GNU General Public License for more details. + + You should have received a copy of the GNU General Public License along + with this program; if not, write to the Free Software Foundation, Inc., + 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA. + +Also add information on how to contact you by electronic and paper mail. + +If the program is interactive, make it output a short notice like this +when it starts in an interactive mode: + + Gnomovision version 69, Copyright (C) year name of author + Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. + This is free software, and you are welcome to redistribute it + under certain conditions; type `show c' for details. + +The hypothetical commands `show w' and `show c' should show the appropriate +parts of the General Public License. Of course, the commands you use may +be called something other than `show w' and `show c'; they could even be +mouse-clicks or menu items--whatever suits your program. + +You should also get your employer (if you work as a programmer) or your +school, if any, to sign a "copyright disclaimer" for the program, if +necessary. Here is a sample; alter the names: + + Yoyodyne, Inc., hereby disclaims all copyright interest in the program + `Gnomovision' (which makes passes at compilers) written by James Hacker. + + , 1 April 1989 + Ty Coon, President of Vice + +This General Public License does not permit incorporating your program into +proprietary programs. If your program is a subroutine library, you may +consider it more useful to permit linking proprietary applications with the +library. If this is what you want to do, use the GNU Lesser General +Public License instead of this License. diff --git a/LICENSES/README.md b/LICENSES/README.md new file mode 100644 index 0000000..5b878c2 --- /dev/null +++ b/LICENSES/README.md @@ -0,0 +1,11 @@ +# License inventory + +- `GPL-2.0-or-later.txt` contains GNU GPL version 2. The header of + `map/kanji.dict` grants the option to use GPL version 2 or any later + version. +- Font license texts are stored in `font/` and associated with exact files + by `font/PROVENANCE`. +- `stb_truetype.h` includes its complete dual MIT/Public Domain terms. +- Generated Wayland files include their MIT-style notices in each file. + +No repository-wide license has been declared for original strans source. diff --git a/README.md b/README.md index 600402b..9d4f495 100644 --- a/README.md +++ b/README.md @@ -1,47 +1,103 @@ # strans -A small input method daemon for Japanese, Korean, Vietnamese, emoji, and -symbols on X11 and Wayland. Inspired by 9front's ktrans. +strans is a small, single-user input method for Korean, Japanese, English, +and emoji on X11 and Wayland. It provides one engine shared by XIM, GTK 3, +IBus, and Wayland input-method-v2 frontends. The existing Vietnamese Telex +mode remains available for compatibility, but is not an actively developed +language mode. -## Build +## Input behavior -The recommended build needs only Docker and Make on the host: +English is direct passthrough. Korean uses 2-beolsik composition. Japanese +Hiragana keeps the complete kana reading until it is committed, so `kanji` +forms `かんじ` and offers whole-reading candidates such as `漢字` and `幹事`. +An apostrophe resolves an ambiguous `n` without forwarding the apostrophe: +for example, `n'ya` forms `んや`. Katakana is direct Katakana composition +and does not perform Kanji dictionary conversion. -```sh -make docker -``` +A Japanese composition is committed by Enter, candidate selection, a real +input boundary, or an explicit mode change. Backspace first removes pending +romaji, then accumulated kana. The Japanese modes support doubled consonants +and combinations such as `nya`, `nnya`, and `matcha`. -This creates an Arch Linux build image, compiles all runtime components in one -disposable container, and writes three artifacts into the source tree: +Modes are selected with Ctrl and one letter: ```text -strans daemon, IBus and Wayland frontend +Ctrl+N Japanese Hiragana and Kanji conversion +Ctrl+K Japanese Katakana +Ctrl+S Korean Hangul +Ctrl+T English passthrough +Ctrl+V Vietnamese Telex compatibility mode +Ctrl+E Emoji and symbol search +Ctrl+P Toggle popup preedit +``` + +While candidates are visible, Up and Down move the selection, Enter accepts +the selected candidate, and an unmodified `1`-`9` selects the corresponding +visible row. Tab cycles emoji search results. `0` commits an unconverted +language reading. Escape cancels the current composition. Ctrl, Alt, or +Super combined with a number does not select a candidate. + +Emoji search is temporary and returns to the previous mode. Queries may use +English aliases or the active language's input rules, including Japanese +`egao` becoming `えがお` or `エガオ`: + +```text +Ctrl+E → smile → Enter → 😀 +``` + +## Build and test + +The supported build uses Docker so host and container toolchains are not +mixed. Only Docker and Make are needed on the host: + +```sh +git submodule update --init +make docker-image +make docker-build +make docker-check +``` + +`docker-image` creates the Arch Linux dependency image, `docker-build` +compiles the runtime components, and `docker-check` runs the map verifiers and +test suites. `docker` is a convenience alias for the image and build steps. +The resulting runtime artifacts are: + +```text +strans daemon, IBus and Wayland frontends xim/strans-xim XIM frontend gtk/im-strans.so GTK 3 frontend ``` -The build starts clean so host and container object files are never mixed. It -removes existing build and test outputs; the `strans-build` dependency image is -kept as a cache. No development packages are required on the host. +Use `make docker-check TESTARGS=hangul` to filter the C unit tests. A native +build is still possible with the dependencies and Plan 9 setup recorded in +`Dockerfile`; use `make all`, `make check`, and `make bench` inside that +environment. -Void Linux runtime dependencies: +After editing `map/emoji.src`, regenerate and verify its dictionary with: ```sh -sudo xbps-install -S dbus-libs wayland libxkbcommon libxcb xcb-imdkit gtk+3 +map/mkemoji >map/emoji.dict +make verify-map ``` -For a native Arch Linux build, use `Dockerfile` as the dependency and Plan 9 -setup checklist, then run `make`. Build the benchmark separately with -`make bench`. +Japanese dictionary regeneration and verification are documented in +[`map/README`](map/README). The converter output is deterministic UTF-8, +tab-separated data consumable by the runtime dictionary reader. -## Run +## Run and install -Start the daemon: +Start the daemon with the installed map and font directories: ```sh ./strans map font & ``` +The IPC socket is placed at `$XDG_RUNTIME_DIR/strans.sock` when +`XDG_RUNTIME_DIR` is an absolute path. Otherwise strans uses the per-user +fallback `/tmp/strans.`. A second daemon will not replace a live +daemon's socket. + For XIM applications: ```sh @@ -50,11 +106,11 @@ export XMODIFIERS=@im=strans xterm ``` -For GTK 3 applications: +For GTK 3 applications, install with normal `DESTDIR` semantics. A staged +install does not update the host GTK module cache: ```sh -sudo make -C gtk install -GTK_IM_MODULE=strans gedit +make -C gtk install DESTDIR="$pkgdir" ``` For IBus clients such as kitty: @@ -63,56 +119,38 @@ For IBus clients such as kitty: GLFW_IM_MODULE=ibus kitty ``` -Wayland needs no environment variable. Start `strans` after a wlroots -compositor that supports input-method-v2. Neither ibus-daemon nor fcitx is -required. +Wayland needs no environment variable. Start `strans` after a compositor +that supports input-method-v2. Neither ibus-daemon nor fcitx is required. +Starting without `DISPLAY` is supported: the optional X popup is disabled, +while input processing and non-X frontends continue to run. -## Keys +## Ownership and rendering constraints -Input modes are selected with Ctrl and one letter: +There is one global composition, not one independent engine per frontend +context. The first meaningful key from a new context resets the previous +composition and transfers ownership. Reset, focus loss, context destruction, +and disconnect affect the engine only when they come from its active owner; +stale events cannot clear a newer owner's preedit. -```text -Ctrl+N Hiragana -Ctrl+K Katakana -Ctrl+S Hangul -Ctrl+T English -Ctrl+V Vietnamese Telex -Ctrl+E Emoji and symbol search -Ctrl+P Toggle popup preedit -``` +The popup is an optional X window, including when the active frontend is +Wayland. It uses deterministic font fallback and fixed-width rune cells; +U+FE0E and U+FE0F variation selectors use zero cells. It does not perform +OpenType shaping, color-emoji rendering, or general grapheme clustering, and +there is no native Wayland popup renderer. Multi-rune emoji are committed +intact but are drawn as their constituent rune cells under this boundary. A +supplied caret rectangle is used when available, with the pointer as fallback. +The X renderer accepts only a 24-depth, 32-bpp TrueColor root format and +disables itself cleanly on other visuals. -Use `1`-`9` or the arrow keys to select a candidate. Tab moves through -candidates, Enter commits, and Escape cancels. +## Data, third-party code, and licensing -Emoji search is temporary and returns to the previous input mode: +Data and third-party provenance is recorded in +[`docs/PROVENANCE.md`](docs/PROVENANCE.md), with font-specific details in +[`font/PROVENANCE`](font/PROVENANCE). The historical SKK-derived Kanji +dictionary is distributed under GPL version 2 or later; its license text is +in [`LICENSES/GPL-2.0-or-later.txt`](LICENSES/GPL-2.0-or-later.txt). -```text -Ctrl+E → smile → Enter → 😀 -``` - -## Tests - -Tests use the sibling `cutest` repository as a submodule. Its relative URL -expects repository mirrors and forks to provide the same sibling. Initialize -it once, then run the checks in the build container: - -```sh -git submodule update --init -make docker-check -``` - -The native `make check` command needs plan9port and Python 3, but not the GUI -development packages. Use `make test TESTARGS=hangul` or -`make docker-check TESTARGS=hangul` to filter unit tests. After editing -`map/emoji.src`, regenerate and verify the dictionary with: - -```sh -map/mkemoji > map/emoji.dict -make verify-map -``` - -## Design - -`strans` owns the input engine and candidate window. The XIM and GTK frontends -forward keys to it over a Unix socket; the IBus and Wayland frontends are built -into the daemon. Internal threads communicate through CSP channels. +The repository does not currently declare a license for the strans project +source as a whole. The licenses of bundled data, fonts, generated protocol +code, and third-party components do not by themselves license the original +strans source. diff --git a/docs/PROVENANCE.md b/docs/PROVENANCE.md new file mode 100644 index 0000000..64c33e2 --- /dev/null +++ b/docs/PROVENANCE.md @@ -0,0 +1,72 @@ +# Data and third-party provenance + +This file records what can be established from repository contents and +history. It does not assign a license to original strans source code. + +## Input maps and dictionaries + +`map/hira.map`, `map/kata.map`, and the original map data entered the history +in commit `cc157c0b3c33506d1cbf5bd251ddc6a9ca909081`, whose subject says the +maps came from 9front. That commit does not identify a 9front revision or +carry a separate data license. `map/telex.map` is generated by +`map/mktelex.py`; Vietnamese behavior is retained for compatibility. + +`map/emoji.dict` is generated deterministically from the repository-maintained +`map/emoji.src` by `map/mkemoji`. No external dataset is required. + +`map/kanji.dict` identifies itself as SKK Medium dictionary version 8.1, +May 24, 1995, rearranged for Plan 9 ktrans by Kenji Okamoto on February 17, +2000. Its header names its copyright holders and grants GPL version 2 or +later. The complete GPL version 2 text is in +`LICENSES/GPL-2.0-or-later.txt`; the dictionary header supplies the +"or later" option. `map/README` records the exact repository history, +repairs made to this copy, and the reproducible procedure for importing a +new SKK revision. + +## Fonts + +The popup bundles Noto Sans, Japanese-region Noto Sans Mono CJK, and Noto +Emoji. Exact checksums, versions or source revisions, download locations +where known, fallback order, and license-file names are recorded in +`font/PROVENANCE`. The corresponding OFL 1.1 and Apache 2.0 texts are kept +beside the fonts. + +## stb_truetype + +`stb_truetype.h` is Sean Barrett's stb_truetype version 1.26, dated +August 28, 2021 in its header. Its exact repository checksum is: + +```text +ecd30b05e0dd4fea3a13c26810dd9e1992dc379049482c393d5a19e6b5090aab +``` + +The file was present in the repository's first commit, +`dcd1147638f908eca7e4b7616815e215022cc99d`. No upstream commit or download +URL was recorded. Its complete dual MIT/Public Domain terms are retained at +the end of the header. + +## Generated Wayland protocol code + +The four checked-in Wayland protocol C/header files were added in commit +`7629ec5fe8976812655c9d12b447a62abc8bb671`: + +- `input-method-unstable-v2-client-protocol.h` +- `input-method-unstable-v2-protocol.c` +- `virtual-keyboard-unstable-v1-client-protocol.h` +- `virtual-keyboard-unstable-v1-protocol.c` + +Their embedded notices identify the protocols as input-method-unstable-v2 +and virtual-keyboard-unstable-v1 and include the applicable MIT-style license +terms. The input-method files report generation by wayland-scanner 1.21.0; +the virtual-keyboard files report wayland-scanner 1.23.1. The source XML +files and their upstream repository revisions were not committed or recorded +in history, so these generated files cannot honestly be regenerated +byte-for-byte from repository artifacts. Do not edit them manually. A +future regeneration should commit the source XML or record its immutable +upstream revision and the scanner command/version. + +## Git submodules + +`cutest` is pinned by the repository as the unit-test framework. XIM uses +the system xcb-imdkit and xcb-util libraries at build time; those system +libraries are not bundled by this repository.