Geocaching Logs switching from HTML to Markdown

c.s.g. shared this question 1 year ago
Answered

Hello,


as you can read here: http://forums.groundspeak.com/GC/index.php?showtopic=336750 Groundspeak will no longer support HTML or BB-Code in Logs after February 1, 2016.


Will this cause problems in Locus?

Will Locus be able to handle the "old logs" correctly?

Will Locus be able to handle the "new logs" correctly?


c.s.g.

Comments (22)

photo
1

Hello c.s.g,


hehe I was also reading this post. And I think there won't be any serious problem, no crashes or something like this. In works case, logs won't look for a while as good as now. Anyway I'll fix it till next version in such case.


Just let me know if you find any problem in display of logs. Thanks!

photo
1

Hello Menion,

thanks for the info.

I think the best way to handle this in Locus is not to remove support for html and ubb in geocaching logs but to add support for Markdown in logs if necessary.

c.s.g.

photo
1

Yep, this is exactly what I plan to do. Maybe during February, new logs will look weirdly as Locus will not support markdowns correctly, but I'm sure, I'll fix it / improve it, during next few weeks worst.

photo
1

While you're working on that, could you please (among the other things necessary) make sure paragraph breaks display properly?


I write long longs, and break them into paragraphs (with double newline), but the current Locus simply merges it all into one big paragraph. This applies to anybody's logs, not just the ones I might write using Locus.


A fix for that would be great, thanks.

photo
1

Hi guys,


because I will need to publish one more Locus version in the end of this week, I would like to be sure, it will work fine with logs. So if you will notice any


- existing hints in public log

- problem with line breaks (as Viajero wrote)


send me link to this cache so I may test it. Thanks

photo
1

As of today's 3.15.1, nothing has changed - right? BBCode still creates smileys, italics, etc., asterisks singly or doubly don't create italics or bold, and paragraphs still merge. So I assume you're talking about the next version. I'll keep an eye open.


Thanks for jumping on this latest surprise from Groundspeak.

photo
1

Yes it is correct, in Locus has change nothing. I was not talking about changes in Locus that are already done ... I was talking about "what should I change to next version that currently (after expected changes on Groundspeak side) not work as expected".


So if You in next days notice anything around logs in Locus, that should be improved, let me know. And Viajero, send me please link to any cache that has logs that are currently not displayed correctly (if you want to fix this).

photo
1

Ah, got it. Well, the whole idea of Markdown is that it doesn't look too bad if there's no special handling for it. So special handling is optional, but I guess that's the subject of this thread.

Here's a typical log with newlines (compressed by Locus), and single- and double asterisks in anticipation of italic- and bold rendering (shown as-is by Locus):

https://www.geocaching.com/seek/log.aspx?LUID=e2b037d2-b9ec-4dbe-8db6-19843f6163a4

Note that it's still unclear exactly how Groundspeak will implement their flavor of Markdown, and it sounds like they're making tweaks. The current discussion thread over there has some pointed questions (near the bottom) about whether they'll support the API partners, eg by providing a get-rendered-text call or similar. BTW, I think the scheduled implementation date was TODAY, but it wouldn't surprise me if they're still scrambling to resolve a bunch of issues people have brought up...

http://forums.groundspeak.com/GC/index.php?showtopic=336753&st=0

It may be wise to wait a while until things settle down...

photo
1

Perfect, thanks. Agree .. let's wait a little bit.


Anyway seems that disabled support for html code is already online: https://www.geocaching.com/seek/log.aspx?LUID=473fdb95-9811-4d72-b6ef-55818ba2a4d1


Well, at least Locus will, quite logically, display these logs correctly. Btw. incorrect break-lines should be fixed in next version.

photo
1

Thank you, especially for that last part. :)

photo
1

Hi guys,

here an example of new appearence of logs with html tags

on left side in cachelisting on PC, on right side inside locus

yellow marked from me

ba3600c3f9a5c0d39181cdfb31c38d9a

for me on PC it looks terrible!

inside locus basic colors are displayed well, spezial colors and fonts are not displayed.

photo
1

Give me please link to this log for testing, thanks

photo
1

http://coord.info/GC69BBF

last log for now

photo
1

Oki thanks. I've fixed at least "i" and "linegreen" values. Rest is incorrect - usually missing closing bracers (like in case of "font") or incorrect close bracers (like in case of size).

photo
1

http://coord.info/GC6A29K

"gold" and "orange" with correct tags (i think) are not displayed

and "green tags" between "blue tags" this i think is incorrect html??

2977b4b445bca6c0e13e5d57ededc192

photo
1

Hello balloni55, "Log with c:geo"? :)

Anyway I think it is not possible to change this text to HTML correctly. Source text is:


  1. [blue]Danke an [green]balloni55[/green] und Grüße von Team [/blue][red]Eg[/red][orange]an[/orange][gold]72[/orange][yellow]31[/yellow]

[gold] is without end tag, second [orange] without start tag, many tags are inside other tags ...

Locus convert it to:


    <font color="blue"><b>Danke an <font color="green">balloni55</font> und Grüße von Team </font><font color="red">Eg</font><font color="orange">an</font>[gold]72[/orange]<font color="yellow">31</font></b>

and result ... you see it on a screenshot. And I think it can't be done better.

photo
1

ok, understand thanks

photo
photo
1

Hi menion,

on PC green displayed inside locus black, with ### and case sensitivee237d83c7b3bb4772b26cdd07faee718

http://coord.info/GC6BWM5

photo
1

Thanks balloni. It won't be perfect (because text in logs is not visible in full featured web browser, so not all features are possible), but at least green and little bit bigger :).

photo
photo
1

Here's a minor issue where bold and italics seem to collide. (I don't think it's important enough for a separate bug report.)

I have a log on http://coord.info/GC1YR6T (the only 2014 log) that starts off with a one-line paragraph containing bold and italic:


  1. **!!!!! W00T !!!!!** / *!!!!! GASP !!!!!*

(bold / italic)

It renders as


  1. *!!!!! W00T !!!!! / !!!!! GASP !!!!!*

(italic / regular)

But now this is strange: it renders incorrectly like this on my tablet, but renders correctly on the phone. (?!?!?) They're a Nexus 5 and Nexus 7 both running the same Locus Pro version 3.17.2 and same Android 6.0.whatever. On both I just went Download Logs to confirm, yes, this rendering glitch happens only on the tablet. Even with the phone in landscape mode and the tablet in portrait, to make the widths more similar. I can't figure out what else might be different...

photo
1

Thank you for a report, weird indeed.


I think this is solvable. Currently I firstly handled italic text and then bold. If I switch it, it should then work correctly. So in next version ... ;)

photo
1

I'm noticing it more consistently now; there's a local cacher who signs off his logs in bold.


On the phone: TFTC

On the tablet: *TFTC*


So - for my hardware at least - it's consistent. But weird. :)

photo