Select Encode and HTML form component, then enter Ana + José. Each space uses the special raw plus spelling. The plus that was already part of the text cannot remain raw because a form decoder would read it as space, so it becomes %2B. The accented é still follows UTF-8 and becomes %C3%A9.
Compare the same source under RFC 3986
The form result is Ana+%2B+Jos%C3%A9. Under RFC 3986, the same source becomes Ana%20%2B%20Jos%C3%A9. Both decode to identical Unicode text when paired with their own profile, but the raw encoded strings differ. Keeping the profile visible is therefore part of the result, not an optional display preference.
Reproduce the round trip
Select the stated profile, run the plain-text input in Encode mode, and record the exact uppercase percent escapes. Switch to Decode without changing the profile and paste that output. The original Unicode text must return exactly, including spaces and literal plus signs. A lower-case escape may decode, but URLCodec marks it noncanonical and shows the unique uppercase spelling used by its round trip.