+IDILIO49 Posted May 16, 2020 Share Posted May 16, 2020 It seems that cache pages are not showing everything they should.... By example https://coord.info/GC7FZWH somewhere in the cache description we can see: ...Em 1977, Cinco anos depois (1983)... But when we get the GPX for that cache the text in same place is: ...Em 1977, <<devido a uma crise interna» os irmãos Penela -herdeiros do fundador desta fábrica – decidem prosseguir com a produção em plástico, plástico e folha, usando a sigla PEPE (Penela e Penela). Cinco anos depois (1983)... The text is not even visible in the source page of the page and worst because in GPX it says this field is not even html... Why is this missing on the page? Quote Link to comment
+thebruce0 Posted May 17, 2020 Share Posted May 17, 2020 (edited) It likely has to do with the "<<". The single brace is an HTML-reserved character, and the double might be messing up the HTML-sanitizing function (testing description for html content) - in this case "<<" isn't HTML and should be escaped (as "<<") but it looks like it's treating the first brace as an html tag opening, hiding everything until it believes it's closed. Is there no ">" before "Cinco anos..."? It looks like it is a bug in the sanitization function, but I think you should be able to get around it by using the special character for the double brace, like you did with the "»". If you change "<<" to "«" I'm guessing it will all display properly. «devido a uma crise interna» Secondly, is the text you quoted in the Source view for the description, or in the composition view? If in the Source view, then you'd probably be best to get in the habit of avoiding "<" and ">" in the source text, just to be safe. Using < and &rt; in their place (again in Source view only) is a better habit. Edited May 17, 2020 by thebruce0 1 Quote Link to comment
+IceColdUK Posted May 17, 2020 Share Posted May 17, 2020 The ‘<<‘ is definitely the issue - may be worth letting the CO know, and suggesting he changes his description to use ‘«’ instead. Handling within the official App is strange too. The ‘Text’ version does show the text missing from the web page, but the ‘Web’ version truncates the page completely. Quote Link to comment
+thebruce0 Posted May 19, 2020 Share Posted May 19, 2020 Yes because the opening brace is not being escaped in HTML view, so everything afterwards is being treated an HTML tag. It's an issue with the website's sanitization, and potentially the app's sanitization - how the text decides what is and isn't intended to be reserved HTML code. In text, it would be fine. In a web/html view, unless the << is escaped, it will cause problems. Theoretically, "<<" would be allowed, but having the ability to edit the source, there a few ways to fix it (whether the CO or HQ's sanitizing algorithm) as mentioned in my first reply. But most likely the quickest and easiest (and most textually consistent) is for the CO to change the "<<" characters to "«" to match the closing brackets. Until that happens, text view may be the only option. Even so, it's a bug HQ should probably fix Quote Link to comment
+ecanderson Posted May 21, 2020 Share Posted May 21, 2020 Yes, they really should fix it, if for no other reason than the fact that << and >> are the characters uses as quote marks in some languages. See here >> https://jakubmarian.com/map-of-quotation-marks-in-european-languages/ Quote Link to comment
+thebruce0 Posted May 22, 2020 Share Posted May 22, 2020 In any case, the existence of an opening bracket is causing a bug in the display of the content. Whatever's done, there should at least be a patch to ensure "<<" doesn't break a description (website or gpx or 1st/3rd part app). Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.