The White Spaces trauma continues…
-
singularcontiguity – makes perfect sense.
(hehe – Latex – that’s when I fall off the discussion :-) -
That a browser makes a few white lines go up in smoke, I cannot comprehend. That would mean that all unused spaces on a weblog would be made undone by a browser?? I see differences between IE and Mozilla pages, but not THAT drastic differences.
Then why does a browser not gobble up the white spaces between hyphen and words?? Well, because it obeys the prompts from the spacebar… And my spacebar simply wishes to make 3 or 30 or 300 white spaces – read: unused page space – underneath these words, for a new paragraph. So somehow the carriage-return muscle screws it up. Or browsers are phobic to wide open spaces…Thinking about it as “browsers are phobic to wide open spaces” is, to some extent, a good way to think about it. If you put 1, 10, or 100 spaces in a row, the browser treats it identically: it sees it as “hey, look, the previous word ended, and now there’s a new one”. However, browsers don’t really object to wide open spaces as such – you just need to learn how to tell them, in a way that they understand, that you really want that space there. That’s what the style attributes do…
Does that make more sense?
-
@ singularcontiguity. thanks when i get passed this flu <‘cough> i will check out the book
“Kopka & Daly’s A Guide To LaTeX”. <‘/cough>I was not aware that we could use XML strings “$” ! in the html editor. I am assuming this is only in a few special cases such as LaTex.
-
In this case, it’s not actually an XML string; the $latex syntax is special. The reason they picked “$” as a delimiter is because that’s used in LaTeX around an inline math environment, which is what’s available to us here. :-)
-
One of the best ways in my opinion of tackling the issue of white space is to substitute punctuation for tab spaces. It allows for the work to spread itself out on its own; while at the same time providing a nice way of playing on words and sentences.
-
=Does that make more sense?=
…This browser’s trying to bullshid me?
Ok. And now for the command that makes browsers sit down and roll over and lay dead in total submission…
-
I haven’t played much with Andreas04, so this may take a couple of passes to get you to exactly where you want to be. First pass: try the following. For the last image, where you have
<img class="alignnone size-full wp-image-694" src="http://planetbarebottom.files.wordpress.com/2008/06/10015292.jpg?w=367&h=430" alt="" width="367" height="430" />in the HTML, add a style attribute to it so that it looks like this:
<img class="alignnone size-full wp-image-694" src="http://planetbarebottom.files.wordpress.com/2008/06/10015292.jpg?w=367&h=430" alt="" width="367" height="430" style="margin-top:35px;"/>that should put a 35-pixel space above the last picture. Does that work?
-
Yes, it does! But only after I changed some components of the tag. I deleted the ‘alignnone size-full’ part, and also the width and height values. Not sure yet which one does the trick, I’ll work it out later.
I also removed your hyphen ; after ‘px’, I think this is necessary. But the margin-top addition enables one pushing around the image as much and as little as one wants.Hey, great!
I think a lot can be achieved in the text editors’ HTML. It’s just a matter of finding out the right codes.
- The topic ‘The White Spaces trauma continues…’ is closed to new replies.