T-Correlative to a mv returns data space delimited - why?

yes you are correct 
since ever its return an SPACE
i usually use the swaps to fix that when its BASIC program
but as chatgpt just told me you can use this
T(FILEB;X;;n]MV) ( not tested)

and just to complemnty you can also do
FILEB;X1;;n
where X# ( # is the position you liked to retrive)

Hi Alberto,

Thank you. Yes, it has been around forever. Indeed the manual even states it for the syntax:

t{dict}file.reference;subcode{[vc[,svc]|*]};inac;outac{;breakac}

In respect of vc it says: "If the value count is not specified, all the MultiValues in the attribute are returned, concatenated with spaces." I just find it strange it does so, given the whole nature of a mv system.

As for ChatGPT's suggestion; unless I am misunderstanding what it means; ChatGPT thinks there is a 'processing code' called "MV" which would take the results of the T-conversion and somehow turn it magically into a mv! I am not aware of any such conversion code! Certainly not in d3. Perhaps it is hallucinating? Or other flavours of mv may allow that?

Lastly, yes I know if I want a specific known mv I can get that by using the vc syntax mentioned above.

I wonder if Rocket would look some extra syntax to retain backward-compatibility yet allow for a mv to be returned as a mv??