Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Bad hint format #261

Closed
GoogleCodeExporter opened this Issue Jul 19, 2015 · 3 comments

Comments

Projects
None yet
1 participant
The cache_desc.hint field is encoded as

  nl2br(htmlspecialchars($hint, ENT_COMPAT, 'UTF-8'))

in both OCDE and OCPL databases. OKAPI outputs the hints in this encoded 
format, while the docs say it's plaintext. In GPX it should also be plaintext.

I think there is no clean way to solve this mess for the existing 
geocaches.hint field. There can be existing clients which expect plaintext, and 
clients which (implicitly) rely on the HTML encoding.

Also, I think that an HTML hint field is bogus, because (a) OC users can enter 
only plain text, and (b) most or all tools out there will ROT13-encode HTML 
tags and encoded entities. GSAK *does* that, it shows &yg; for < when I 
import an OC hint containing "<" :-S

I am not sure what to do best with the geocaches.hint field, but anyway I 
propose to add a new hint2 field which IS plain text, and which is used for GPX.

Original issue reported on code.google.com by following09 on 9 Jun 2013 at 12:10

This issue was updated by revision r815.

Original comment by following09 on 9 Jun 2013 at 11:21

I thought it was plaintext. I agree!

Original comment by rygielski on 12 Jun 2013 at 10:39

This issue was closed by revision r817.

Original comment by following09 on 12 Jun 2013 at 2:38

  • Changed state: Fixed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment