[Feature Request] How to translate an element's id in ATE?

The detailed specific example was in my original question, but your new system gets rid of all specifics before posting. Very sad.

Here's an example: <h2 id="%D1%80%D0%D0%B0%D0%B7%D0%B4%D0%B5%D0%BB-i">РАЗДЕЛ I</h2>. WPML "sees" this string as wpml_string_wrapper: content.

Yes, I believe that is exactly what I am encountering. The string looks exactly as I have it. Like on my site, I can't translate it through ATE as it's not even detected through the search box/bar.

As for wizard, I like that it essentially understands what I wrote. At least I don't see any significant misrepresentations when paraphrasing. (That's exactly how the systems I know/use work: DeepL Write and Grammarly AI Writing Assistant.) However, your wizard gets rid of a lot of details that I find fundamentally important, because often (I've written to support several times and have encountered this wizard) it's what it excludes that turns out to be important: either support explicitly asks about it (which seems logical in the proper context), or it would help support understand my questions without further clarification. So for now, I rather dislike this wizard.

By manual translation, do you mean translation through the WP editor? If yes, this (as well as translation through the classic editor) is inconvenient, because this translation will disappear in case of further translation through ATE, and if you don't use ATE, you can't use the translation memory. All this causes additional inconvenience, which is already too much in WPML usage. It seems to me that html tag attributes are something that may need to be translated quite often. I've found in old tickets that some attributes are untranslatable because there is a high risk of errors (e.g. 'style'), but this is hardly the case for the 'id' attribute (at least it wasn't on the list of untranslatable attributes). I'm certainly happy to settle for a translation of the 'name' attribute of the 'a' tag, if that's easier.

BTW, I don't get support response notification emails today as I always have. I use a business email account from Microsoft, I check spam folders as well, and I have no problems with receiving other email on this account today. So maybe some issues with email are on your side (although, of course, it's possible that it could be on mine).

I would like to make one important clarification regarding my addition about the name attribute. I can translate it through ATE, but I am not satisfied with it. I would like to get a translation (id or name attribute) that is _necessary_ from ATE's point of view. I agree to create something custom for this, to prescribe something in functions, that sort of thing. I can't rely on translation, which ATE considers only optional (and done via search-box). Because such a translation can "disappear" under a number of circumstances (it's the subject of separate tickets - under what circumstances, but I assure you that on large pages translated into dozens of languages and not being top-level pages this is very likely, as well as not saving anything that is not explicitly prescribed in the translation; WPML simply can't handle making all the changes, even if I on my side allocate huge resources and remove many restrictions in WP, apache and mysql settings). I've asked an essentially similar question before about "plain text", as in, say, strings consisting entirely of numbers. I was answered: no, no, no, no, that's not possible. But I found a way to get what I wanted with them, by adding a meaningless tag to _part_ of the string, such as: "1234<cstm>5</cstm>". Since ATE needs to figure out which part of the string to tag, it has to register such a string for mandatory translation. I can "remove" this tag if I want, i.e. make, say, "54321<cstm></cstm>", ATE allows it, because the tag is formally preserved. But I can't make such arbitrary changes in html attributes. So I'm looking for some solution that would make ATE not just see this attribute, but require it to be translated. I'm ready to "attach" the id attribute to any tag, as long as the frontend doesn't reflect it (visually). Id is great because it can be attached to almost anything. And I'm ready to do it, if it allows to require translation of this attribute.