Your event page in 14 languages

Selling across Europe means people arriving at your page in a language you did not write. There are two separate problems in that sentence — the platform's language and your language — and they have different answers.

Fourteen languages

The platform is available in Czech, Danish, German, English, Spanish, French, Italian, Japanese, Dutch, Polish, Portuguese, Swedish, Turkish and Chinese.

That covers the whole buying journey, which is the part that matters: browsing and search, the checkout form, payment, the confirmation email and the ticket itself. A translated homepage followed by an English checkout is worse than no translation, because it fails at the exact moment the buyer has to trust you with a card number.

Your own text

Your event title and description can be translated too. This is your copy rather than ours, so which languages are worth writing is your decision — and it is a real decision, not a box to tick.

• A local meetup in Munich probably needs German, and English if the scene is international.
• A European conference might genuinely warrant four or five.
• A neighbourhood event needs one.

Translating an event you cannot support in that language is a trap worth avoiding. If somebody buys a ticket from a Polish page, they may reasonably ask you a question in Polish. Translate the events you can actually serve.

What search engines are told

An event is advertised to search engines only in the languages it is genuinely translated into.

This is a deliberate restraint and it is worth understanding, because the tempting alternative actively harms you. It would be trivial to declare that every event exists in all fourteen languages — the URLs all resolve, after all. But thirteen of those pages would show the same untranslated text at different addresses, and a search engine encountering thirteen near-identical copies of a page does not reward the effort. It filters them as duplicates and spends less of its crawl budget on the site as a whole.

So: translate an event and it appears in that language. Do not, and it does not pretend to. Your listing quality is not diluted by twelve copies of itself.

Listing and location pages are treated differently, because their content genuinely is written fourteen times. The rule is not "fewer languages is better" — it is that a page should be advertised in a language when there is something in that language to find.

Tickets and emails

Confirmation emails go out in the buyer's language, and ticket PDFs carry the right fonts for non-Latin scripts.

That second point is less obvious than it sounds. A PDF embeds the fonts it draws with, and a font that has no Japanese glyphs cannot render a Japanese name — it produces a row of empty boxes. The attendee's own name, on their own ticket, replaced by rectangles. Ticket PDFs detect which scripts are actually present in your event title, venue and attendee names, and embed a matching font for each — including only the glyphs actually used, so a Japanese ticket does not carry a two-megabyte font for the sake of eleven characters.

One honest limit

Latin, Cyrillic, Greek, CJK and Thai render correctly on tickets. Indic scripts and Arabic and Hebrew render legibly but with imperfect letter positioning — the characters are right, the joining and vowel placement are not always.

This is a known limitation rather than a surprise, and it exists because correct shaping for those scripts requires a different rendering engine than the one that produces PDFs today. We would rather state it plainly here than have you discover it on an attendee's ticket. If your audience writes primarily in Arabic, Hebrew or an Indic script, this is worth knowing before you commit.