# Символ & отображается неправильно в синхронизированных событиях

**URL:** https://meta.discourse.org/t/ampersand-not-displaying-properly-in-synchronised-events/400166
**Category:** Bug
**Tags:** events, fixed
**Created:** [08.Апрель.2026 00:00:42 UTC](https://meta.discourse.org/t/ampersand-not-displaying-properly-in-synchronised-events/400166 "2026-04-08T00:00:42Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![zogstrip](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/zogstrip/32/512781_2.png) [@zogstrip](https://meta.discourse.org/u/zogstrip)
#### Post date: [08.Апрель.2026 14:12:00 UTC](https://meta.discourse.org/t/ampersand-not-displaying-properly-in-synchronised-events/400166/2 "2026-04-08T14:12:00Z")

</div>

Спасибо за отчет @nathank 👍 Это будет исправлено в

> <https://github.com/discourse/discourse/pull/39152>
>
> ERB's \`\<%= %\>\` calls \`ERB::Util.html\_escape\` on all non-\`html\_safe\` strings, eve…n in non-HTML templates like \`.ics.erb\`. This caused ampersands (and potentially other special characters) to be double-encoded as \`&amp;\` in calendar subscription feeds, which external calendar apps like Google Calendar displayed verbatim.
> 
> Mark \`IcalEncoder.encode\` output as \`html\_safe\` since it already performs all necessary ICS encoding (HTML sanitization, entity decoding, RFC 5545 escaping). Also route the URL fields in both ICS templates through \`IcalEncoder.encode\` for consistency.
> 
> https://meta.discourse.org/t/400166

---

_[View the full topic](https://meta.discourse.org/t/ampersand-not-displaying-properly-in-synchronised-events/400166)._