tolgee/tolgee-platform

Describe the bug A clear and concise description of what the bug is. To Reproduce Steps to reproduce the behavior: Go to Translations Click on the Search... box at the top Paste or type some very long content Text overflows on top of the search box Expected behavior Text should not overflow Screenshots Versions and environment Tolgee Platform version: Latest from https://app.tolgee.io/ as of 11/08/2026 Browser: Firefox 153.0 Additional context Just a minor UI bug.

Summary When exporting translations to JSON, supplementary-plane (astral) characters — most modern emoji (👋 😀 🎉 🚀 …) — are emitted as \uXXXX\uXXXX surrogate-pair escape sequences instead of raw UTF-8. BMP characters (e.g. ⭐ U+2B50) and all of YAML export are written raw. We want JSON export to escape only characters that actually require escaping in JSON (", \, control chars U+0000–U+001F), and pass everything else — including astral emoji — through as raw UTF-8. Reproduction Export keys with these values: key value code point star ⭐ U+2B50 (BMP, single UTF-16 unit) wave 👋 U+1F44B (supplementary, surrogate pair) JSON output (wave wrongly escaped): { "star": "⭐", "wave": "\uD83D\uDC4B" } YAML output (correct): star: "⭐" wave: "👋" Behavior is identical with ICU placeholder support on or off — it is not the message/ICU conversion. Root cause GenericStructuredFileExporter serializes JSON via objectMapper.writer(...).writeValueAsByte

Describe the bug Minor bug: Any <hr> element in the key description (from ----- in Markdown) renders as a single point not a 100% width horizontal rule. This renders correctly when the key description is expanded Affordance bug: it's quite hard to know how to expand the key description. There is nothing in the UI that hints to the user they should long hover their mouse over the box to see more details. Our key descriptions are a link, a horizontal rule, and then more text, that makes it even harder to see the additional text and know to expand. It would be good to either: a) keep rendering the markdown when you click on the key description or b) provide some explicit "Expand" button if the text overflows. To Reproduce Steps to reproduce the behavior: Any key with a long description and a horizontal rule Expected behavior See above Screenshots If applicable, add screenshots to help explain your problem. Versions and environment Tolgee Platform version: 3.190.0 Additional context A

Describe the bug: When the system UI language is set to English (UK), dates in the Tolgee interface are displayed in the MM/DD/YYYY format instead of the expected UK standard DD/MM/YYYY. This results in inconsistent localization behavior: the interface text uses UK English, but the date formatting follows the US convention. To Reproduce: Set the system UI language to English (UK) in Tolgee. Navigate to areas where dates are displayed (e.g., project activity, translations history, etc.). Observe the displayed date format. Expected behavior: Dates should follow the UK standard format (DD/MM/YYYY) when the UI language is set to English (UK). The regional formatting should match the selected language variant. Additional context: Triage note: Reported by a customer via Intercom.

Describe the bug When the number of keys is displayed on two lines (e.g., number on the first line and the word “Schlüssel” on the second line), the text becomes vertically misaligned compared to other project rows where the key count fits on one line. Expected behavior The key count (number + label) should remain properly vertically aligned with other elements in the row, regardless of whether it wraps to one or two lines. The layout of project rows should be visually consistent. Screenshots