etc

UI is not the only question - our entire model would change. Say, currently we send (via async request) the whole markup to update the `ID` link on the articles...

You could import them in a file from Crowdin?

We'd do it only once, on each txp release and supply with?

We could update it when Diagnostic pings home?

> No – unnecessary, unless I have misunderstood and we're thinking of dynamically updating language strings from within the admin-side, outside of a version update. Is that it? Dunno. What...

@jools-r thank you, should be fixed in dev. But I'm sure it's not the last php 8.1 surprise.

We recently had few demands for Textile in other fields (CF, image caption). I'd say, we need a more general mechanism for storing processed HTML markup, so I would drop...

We need to decide what can be in `Title`, this 4.6-tagged [issue](https://github.com/textpattern/textpattern/issues/672) is tied to our choice. Anyway, be it plain text or HTML, I wouldn't alter the **input** at...

I don't know why and how to escape Title. IMO, the main raison d'être of `_html` fields is textiling: it's rather expensive, and it's good to be able to preview...

It actually was in `any other tag attribute, just in case!` But there are also `description`, `expires`, `modified`, `override_form`, `is_first` and `is_last` to add to the list.