Use HTML on a cache page

[+rockey_f_squirrell]

So i know basic HTML, the (I will SUBSTITUTE the TAGS with '(code)' so it dont mess with my message in here).

 

I know the (p), (br), (bold), (Center), (Font size="#"), (Font color="######"). So I included the HTML on my cache page, and it works to some extent but as i type a paragraph, I have a (p) at the end to start the next paragraph. As I go to preview the page, I see that the whole page is double spaced.

 

Is there a way to fix this. I also notice when I go back to edit, each new paragraph has a new (/font) (/font) (/font). I wanted to include 'Best of' portions of logs within the page.(From Geocache GCNBA8 - if you wish to see it yourself)

 

Between each Paragraph of the Cache Description, I will have very small font, what different cachers thought, because the description looks like a killer, but almost everyone ends up loveing it. Here are a few examples I want to include between the main paragraphs...

--------------------

(Climbing the Great Pyramid)

 

Monk-E Arms - 03/14/2014

I needed a break from my week, and this definitely provided it... I have wanted to grab this one for almost as long as I've been caching

 

dnkleimbach - 03/30/2013

Not too bad but definitely a obstacle course. Snakes are out. Definitely advise late fall early spring retrieval. Easy find once at Gz The difficulty was in the hike

 

samijok - 02/17/2013

Be ready for a hike! Very pretty trip!

------------------------

What I want to do is(reduce the size of the log samples to it doesnt overtake the page, but it sort of has a similarity of what you see at fast food restaurants like on cups or burger wrappers (Fazolis and hardees and BK are good examples)

 

So How can I fix that to where it is not all double spaced, and having like (/font) 12 times at the end of my last paragraph in my edit screen.

Edited April 22, 2014 by rockey_f_squirrell

[+TriciaG]

Doing a quick "view selection source", I see code like this:

<font size="6"><font size="4"><font size="2"><font size="4"><font size="2"><font size="4"><font size="2"><font size="4">

that the beginning of the paragraphs. No wonder there are so many "close font" tags.

 

Dumb question: are you closing your "p" tags at the end of each paragraph?

 

Perhaps you could post your code here (in the "code" BB tags) and we can look at it easier.

[+Semper Questio]

Also, keep in mund that Geocaching using some kind of code scrubber (someone here will remmeber the name of it) that enforces their coding standards. This can yield some "interesting" results. That's why I try to keep things VERY simple and I use tables to do special formatting and layouts. Seems to work with far fewer headaches.

[+Chief301]

I don't know jack about coding, so I mostly copy and paste the HTML codes from a UK Geocaching site....

 

http://www.follow-the-arrow.co.uk/resources/htmlcodes.html

 

They always seem to get me to what I'm trying to do.

[Blue Square Thing]

It would certainly be worth trying to deal with the multitude of opening font size= tags. You only ever need one open at once - wysiwyg editors can usually be relied upon to screw up the way these work and that may be what's at fault here. You need to go into the html view and take all but one out for every line - and make sure it has a closing /font tag as well.

 

That's the starting point anyway - try that first and see where you get to. For the life of me I can't remember whether font size="6" is bigger or smaller than "2" - haven't used such old school tags for years, but having too many of them is likely to be the thing mucking up your line spacing I imagine,

Edited April 22, 2014 by Blue Square Thing

[+Graculus]

Use the break tag instead of p. This will give you a single line break not double. The page in my resource site (linked to above and also in my signature) explains about the P and BR tags.

<br />

Be aware that some more complex HTML doesn't work on the cache page. You'll see a list when you are editing the page of what is allowed.

 

Also note that people view caches pages on phones and GPS screens. Whilst you may have a fantastically colorful and eye watering catching page in your web browser it may not look like that on a smaller screen

 

Chris

Graculus

Volunteer UK Reviewer for geocaching.com

----------------------------------------------------------------------------

UK Geocaching Wiki

Geocaching.com Help Center

UK Geocaching Information & Resources website

[+rockey_f_squirrell]

Use the break tag instead of p. This will give you a single line break not double. The page in my resource site (linked to above and also in my signature) explains about the P and BR tags.

<br />

Be aware that some more complex HTML doesn't work on the cache page. You'll see a list when you are editing the page of what is allowed.

 

Also note that people view caches pages on phones and GPS screens. Whilst you may have a fantastically colorful and eye watering catching page in your web browser it may not look like that on a smaller screen

 

Chris

Graculus

Volunteer UK Reviewer for geocaching.com

----------------------------------------------------------------------------

UK Geocaching Wiki

Geocaching.com Help Center

UK Geocaching Information & Resources website

 

I've tried the br/ tags as well and it had no change. I will try that copy/paste from that UK site mentioned above. Thanks for all y'alls imputs

[+rockey_f_squirrell]

OK I think I got something figured out, thanks for y'alls help. I was forgetting to do a (/font) at the end of each change.

[+KC2WI]

I found that the 'html scrubber' makes some confusing and unpredictable changes to some fairly basic html code that should be good (since it was generated with Dreamweaver).

[+Lil Devil]

ROFL you're living in a Dreamworld if you think Dreamweaver creates good code.

[Blue Square Thing]

ROFL you're living in a Dreamworld if you think Dreamweaver creates good code.

^ this!

 

I teach 15 year olds how to use it and once they've changed the font three times on a line the code is then full of font tags again - just like the OP's. Newer versions will also tend to throw in CSS (sometimes inline, usually not) rather than old school font tags btw - which, I presume, will be taken out by the GS scrubber routines. This would make any code produced in DW quite unstable when brought here I would imagine.

 

Hand coding - it's the future you know :-)