WeblateOrg/weblate

Describe the issue In badges/shields#11783, a blurred shadow was added behind the text of badges to improve their WCAG contrast score, so they now look like: in contrast to Weblate's badges that still replicate their previous style: I already tried I've read and searched the documentation. I've searched for similar filed issues in this repository. Steps to reproduce the behavior . Expected behavior No response Screenshots No response Exception traceback How do you run Weblate? No response Weblate version reproduced in Hosted Weblate Weblate deploy checks Additional context No response

Describe the problem Codeberg's Weblate instance currently runs a slightly modified version of Weblate. Since the introduction of the new release convention there's been more releases and requires more effort every so often to update Weblate and this amount of effort is now so high it's better to get rid of this small modification and hopefully get it in supported by Weblate. The modification is quite simple, Codeberg's weblate is only accessible via OAuth2 of codeberg.org. However due to the email privacy, the email returned can be [email protected] and Forgejo does not recognize the noreply email for it's avatar via email hash route. Hence we use the avatar via username route which is always available. Solution brainstorm A setting to choose the method of fetching the avatar, e.g. md5email or username. Describe alternatives you have considered Running a soft-fork of Weblate, this however costs a lot of time. Screenshots N/A Additional context N/A

Describe the problem The Anthropic machinery sends the system prompt as a plain string, without any cache_control block. Anthropic's prompt caching is opt-in, so nothing gets cached at all right now. The system prompt built in BaseLLMTranslation (persona + style + language instructions + the JSON schema boilerplate) is identical for every request to a given target language. With a longer style guide it easily reaches 2-3k tokens. When automatic translation runs over a few thousand strings, that same prefix is billed at full input price on every single request. In our setup (~3.4k strings per language, ~8KB style prompt) this repeated prefix is the majority of the MT spend. Solution brainstorm Send the system prompt as a content block with a cache breakpoint in weblate/machinery/anthropic.py: "system": [ {"type": "text", "text": prompt, "cache_control": {"type": "ephemeral"}}, ], Cached reads are billed at roughly 10% of the normal input price with a 5 minute sliding TTL, which fits

Describe the problem In Godot Engine's class reference, we make great use of BBCode to format text. A lot of go beyond the standard [b], [i], [code] tags and require additional parameters. For example, the [url] tag can optionally accept a link, formatted as [url=https://github.com/WeblateOrg]. Our custom [codeblock] tag can also accept a language, formatted as [codeblock lang=csharp]. Unfortunately, the "highlighting" and "error reporting" systems cannot detect these tags. This can make it quite awkward to change several strings. BBCode-related changes are harder to spot, tags may be mistyped or missing in translations, shortcuts such as CTRL + number key to quickly insert tags do not work. Solution brainstorm I believe what mostly needs to change is this regex in this repository: weblate/weblate/checks/markup.py Lines 76 to 78 in 2b4eab3 BBCODE_MATCH = re.compile(

Describe the problem The keyword option in gettext can be defined multiple times to define more keywords. The addon currently only allows defining one additional keyword. Solution brainstorm Allow defining a list of keywords and add the --keyword option for each of these keywords. Describe alternatives you have considered No response Screenshots No response Additional context weblate/weblate/addons/gettext.py Line 1123 in 03f08b9 result.append(f"--keyword={keyword}") I can try implementing this if desired.