Unwanted HTML entities saved instead of special caracter in auto created page title (and queried tag in structure)

The CMS Questions
1

In a website I’m creating, I use the create: parameter for a page type blueprint. It allows quick creation of a page type that only has 3 simple fields and a title (which combines the 3 fields).
Here is an example:

title: Grade
icon: badge
create:
   title: "{{ page.class }} {{ page.year }} {{ page.score }}"
   slug: "{{ page.class.slug }}-{{ page.year.slug }}-{{ page.score }}"
   fields:
      - class
      - year
      - score
   redirect: false
   status: unlisted

The title generated looks like: Mathematics 2026 Gold Medal.
But in some cases I want to use special characters. In French we heavily rely on apostrophes for example : Mathématiques 2026 Médaille d'Or.

But in that case the rendered title in the panel is: Mathématiques 2026 Médaille d'Or, which is not ideal in a UX standpoint. Same goes if I use & as in: Geographie 2026 Médaille d'Or & Médaille d' Argent

I checked the generated grade.fr.txt and it looks like this:

Title: Mathématiques 2026 Médaille d'Or

----

Class: Mathématiques

----

Year: 2026

----

Score: Médaille d'Or

So the field is properly saved.. but no the title which seems to be escaped.
Is there a way to avoid that?

I noticed another very specific case in the interface where special characters were escaped in unwanted places in the panel. When you use a tag field inside an object field or a structure field, that fetches its content from a query. The preview has escaped special characters.
Here is an example to reproduce with attached screenshot:

grades:
   type: structure
   fields:
      gradeslist:
         label: Grades
         type: multiselect
         accept: options
         options:
             type: query
          max: 1
          options:
             query: site.templates.split

Capture d’écran2026-05-2112-27-23
Capture d’écran2026-05-2112-27-23986×108 2.86 KB

2

For the 1st problem.

The use of a query in the page creation dialog is by default escaped, and that includes converting special characters apparently.

To avoid having d' instead of my french apostrophes, I used the information provided here on the query language doc page

In my blueprint I replaced

title: "{{ page.class }} {{ page.year }} {{ page.score }}"
by
title: "{{ page.class }} {{ page.year }} {< page.score >}"

It solved it.

3

The 2nd problem had a fix related to that, also an escaping issue.

in the multiselect blueprint we fix it by adding the value unescaped:

grades:
   type: structure
   fields:
      gradeslist:
         label: Grades
         type: multiselect
         accept: options
         options:
             type: query
             text: "{< item.value >}" # grab the value from the tag field, but not escaped.
          max: 1
          options:
             query: site.templates.split