Skip to main content ↑ ↓
Topic: Using #[number] placeholder (Read 6617 times) previous topic - next topic

Using #[number] placeholder

Hello. I've noticed after one of the latest updates that I can no longer use "#" before my [number] [weather] placeholders. When I put the # there now, it seems to just increase the font size of everything after it. Also, it doesn't show the # at all anymore. This is all according to the preview, I've not actually posted a log like this because I didn't want the giant font.

Is this intentional? Is there a way for me to get the number sign back in front of the number of caches, without increasing the font size?

Thank you.
 

Re: Using #[number] placeholder

Reply #1 –
Geooh now allows Markdown syntax in logs. And "#" is a Markdown code for headings. But, normally you need "# H2" for example. You could try space after # or something else. The geocaching website shows renders Markdown formatting in logs so I would have thought it was always a problem.

Re: Using #[number] placeholder

Reply #2 –
Ok. Yeah, it worked fine previously. Now I can't get the # to show regardless of what I place after it, spaces or characters. I guess I'll just have to use "Find [number]" instead.

Thanks for the response.

Re: Using #[number] placeholder

Reply #3 –
Also, I seem to no longer be able to adjust the spacing between "[number] [weather]". Previously I could add spaces between them and it would work but now it doesn't matter how many spaces I add, they're right next to each other in the log. Is there another way that I should be going about adding space between these? Thanks.

Re: Using #[number] placeholder

Reply #6 –
Sorry for the delayed response. Glad you could replicate it! Thanks for the reply.

Re: Using #[number] placeholder

Reply #7 –
I've got a fix for the # and spacing... but just so you know, Geooh may be the only app to properly show intended spacing in the log display. The official app definitely doesn't do Markdown rendering in their app, and spacing. The website will show Markdown properly, but all spacing is also lost. If you open their log editor (which uses Markdown), you see the spacing is there, but web pages have a tendency to collapse multiple spaces. Geooh will handle it correctly and not collapse by converting spaces to the HTML " " character. If you really want to retain spaces in all apps and the website, don't use spaces, but the   character instead. Groundspeak developers should change log displays on the web and their app, but alas I don't think that will happen.

Re: Using #[number] placeholder

Reply #8 –
Great news on the fix for #.

I went back and look at some older logs online and you are correct. The spacing was NOT carrying over to the logs outside of the app like I had assumed. Nothing I can't live without. 

Thanks again for your time, and responses.