Branch : - branch - android master - tag -

• Show log

  Commit

• Author : Pierre Le Marre
  Date : 2025-08-16 12:59:20
  Hash : 135b3204
  Message : compose: Add fallback for custom locales Before this commit, loading a Compose file based on the locale would fail if the locale is not in the X11 Compose locale registry. While there are workarounds (e.g. `~/.XCompose` file or `$XCOMPOSEFILE`), it does not work if the corresponding file has `include "%L"`. This commit adds the fallback `en_US.UTF-8` in case the locale is installed but not registered in the X11 Compose locale registry. The choice is motivated by the fact that most locales use `en_US.UTF-8` anyway. Ideally we should have a mechanism to extend the Compose locale registry at the *system* level. Mechanisms at the user level (e.g. custom Compose file, environment variable) are deemed sufficient. We could still improve it by first trying to fallback to the locale without the country bits, but there is no function to do such function in the stdlib and we do not want to mess with locales manually. Unfortunately is not possible to test it in our test suite. One can still check it works following these instructions: 1. Create a custom locale, e.g. `en_XX.UTF-8`. `glibc-i18ndata` or similar package may be required to get the required files in `/usr/share/i18n/`. `sudo localedef -i en_US -f UTF-8 en_XX.UTF-8` 2. `xkbcli compile-compose --verbose --locale en_XX.UTF-8`

• Files
• README.md
• api
• build
• keymap-text-format
• rules-text-format
• tools

• README.md

• Fragments for the changelog

  This directory contains fragments for the future NEWS file.

  Introduction

  We use towncrier to produce useful, summarized news files.

  There are 3 sections types:

  • API: changes/api
  • Tools: changes/tools
  • Build System: changes/build

  There are 4 news fragments types:

  • Breaking changes: .breaking
  • Deprecated: .deprecated
  • New: .feature
  • Fixes: .bugfix

  Adding a fragment

  Add a short description of the change in a file changes/SECTION/ID.FRAGMENT.md, where:

  • SECTION and FRAGMENT values are described in the previous section.
  • ID is the corresponding issue identifier on Github, if relevant. If there is no such issue, then ID should start with + and some identifier that make the file unique in the directory.

  Examples:

  • A bug fix for the issue #463 is an API change, so the corresponding file should be named changes/api/463.bugfix.md.
  • A new feature for tools like #448 corresponds to e.g. changes/tools/+add-verbose-opt.feature.md.

  Guidelines for the fragment files:

  • Use the Markdown markup.
  • Use past tense, e.g. “Fixed a segfault”.
  • Look at the previous releases NEWS file for further examples.

  Build the changelog

  Install towncrier from Pypi:

  python3 -m pip install towncrier
  

  Then build the changelog:

  # Only check the result. Useful after adding a new fragment.
  towncrier build --draft --version 1.8.0
  # Write the changelog & delete the news fragments
  towncrier build --yes --version 1.8.0