_Originally created by @sajolida on [#15461 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15461)_ Due to tails/tails#14962, we had to apply a temporary workaround: 08259afa449f3dcd916fe03db5775f3652f5a7e8, a02aafefe1c3850461d28a44befd2378fe527741, 527b2c3779e22a955d5c506dd02957c4ecbdbbcd. But that’s problematic: translators can’t easily update/fix translations in PO files for that web page, and newly enabled languages don’t get a translated page (e.g. we’ve enabled Spanish and guess what? of course nobody thought of manually translating that HTML file). So, we should: - either do something clever to avoid using markup/CSS that won’t render due to tails/tails#14962 (can we use a custom page template? last time I check we could not) and then reintegrate this HTML file into our ikiwiki+po setup to make that page translatable again; likely that won’t work so let’s not spend too much time of it before switching to: - or keep most of the current hacks, treat that web page as something outside of ikiwiki’s scope, and make it translatable via Transifex: - move the source page out of `wiki/src` - integrate it with our non-ikiwiki translation setup (`po/`, `refresh-translations`, etc.) - replace `fixup_14962_workaround` with something that copies the generated translated pages to `config/chroot_local-includes/usr/share/doc/tails/website/misc` - or find a nicer, cheap enough solution to this problem :) For future plans, see https://gitlab.tails.boum.org/tails/tails/-/issues/14962#note_30357 and follow-ups. Feature Branch: https://0xacab.org/Hefee/tails/tree/bugfix/15461-translate-unsafe-browser-homepage ### Related issues - **Related to** tails/tails#14962 - **Blocks** tails/accounting#15139