'Less than character' in hint

[+Vooruit!]

I just stumbled upon a problem while creating a new cache. I wanted to put this text inside the hint:

 

[1] 15 < answer < 45
[2] some other hint

 

This, however gave a very strange result. When previewing the cache, it came out as:

 

[1] 15 [2] some other hint

 

Furthermore, for some reason, the decrypt/encrypt switch seemed to have been flipped: I could 'decrypt' the garbled hint, giving:

 

[1] 15 [2] fbzr bgure uvag

 

Obviously, something goes wrong when parsing the hint. Until this gets fixed, I would be grateful to learn how I can have a '<' in the hint.

 

edit: I've tried using <, but this does not get parsed as one would hope.

Edited June 19, 2015 by Vooruit!

[cezanne]

 

[1] 15 < answer < 45

 

Obviously, something goes wrong when parsing the hint. Until this gets fixed, I would be grateful to learn how I can have a '<' in the hint.

 

 

Try 45 > answer > 15 as a temporary solution.

 

Or use something like between.

[+Vooruit!]

I don't like it at all, but I guess it'll have to do for now. Thanks for thinking along!

[+dprovan]

You could write it out: "fifteen is less that the answer which is less that forty-five". In addition to getting around the problem, it also makes the hint unclear when it's in rot-13. After all, almost everyone would guess what "15 < nafjre < 45" meant. (Not that hints are really ever kept in rot-13, but it's the principle of the thing...)

[+Vooruit!]

Haven't thought of that, but it makes sense.

[+ecanderson]

At a guess, I'd say the less than character is being interpreted as the opening of an HTML tag.

[+Vooruit!]

My guess as well. Probably some kind of too-well-performing anti-XSS measure.