In RTL languages the order of previous context and next context should be reversed.
I agree that it makes reading RTL text more comprehensible. But you can drag the headings to get Next Context | Result | Previous Context,
Agreed! [Y]
Which is what I did for the 2nd screen shot. But that takes 1 additional piece of system knowledge and 2 additional actions to achieve a very basic function.
Design oversight rather than a bug, per se.
Column settings are stored per column set, which arises from the results and not per query, which is not currently analyzed in this way. But we definitely could come up with a better default order for column sets that exclusively have RTL content in these three surface text columns. I added an "idea" case for this.
