| 5:34 am on Feb 19, 2013 (gmt 0)|
I think you're talking about a title attribute- (img="a.jpg" title="lore ipsum") - rather than a <title> tag, right?
| 5:49 am on Feb 19, 2013 (gmt 0)|
Whew. I thought you were asking about the <title> of a page, and was all set to scream that you CAN'T have line breaks in a page title :)
|s there a way of putting a line-break into the title text? |
In theory yes. In practice ... uh ... depends on the whim of the browser. All my current browsers will interpret a physical linebreak inside the title attribute's quotation marks as a physical linebreak in the displayed title. But I'm not positive browsers are really supposed to do this.
| 8:59 am on Feb 19, 2013 (gmt 0)|
Hi there ctoz,
I use the HTML character code for a carriage return...
title="Web Master World"
It works nicely in this selection of browsers at least...
- Firefox 18.0.2
- Opera 12.14
- Safari 5.1.7
- Chrome 24.0.1312.52
| 12:10 pm on Feb 19, 2013 (gmt 0)|
I'll be darned.
<p>CR alone <span title = "line break here">like this</span>.</p>
<p>LF alone <span title = "line break here">like this</span>.</p>
<p>CRLF <span title = "line break here">like this</span>.</p>
All three come out the same on current Mac versions of Safari, FF, Chrome and Opera.
Would anyone care to speculate about why the version (LF alone) is read by MSIE 5.23 as no whitespace and then one whitespace, while the CRLF version ( ) comes through as one whitespace and then two whitespaces? CR alone --the Mac Classic line break-- is recognized as a single white space each time.
Come to think of it, the entities should work exactly the same as literal line breaks shouldn't they.
| 1:25 pm on Feb 19, 2013 (gmt 0)|
It probably traces back to the historic difference in the text file formats between UNIX/Linux/Mac and DOS/Windows, one way or the other.
| 1:57 pm on Feb 19, 2013 (gmt 0)|
Don't look for it Lucy! You may not like what you find.
| 4:25 pm on Feb 19, 2013 (gmt 0)|
Dead and buried that version, even forgotten long ago.
Actually a good thing IMHO.
| 5:13 pm on Feb 19, 2013 (gmt 0)|
MSIE 5.23?! What the?!
As of October of 2008 (4 years and 4 months ago), IE 5.5 had 0.05% market share. IE < 5.5 had already fallen off the radar, and this was the last month that stats were presented for IE 5.5 on [gs.statcounter.com...]
Dead and buried is an understatement.
| 9:24 pm on Feb 19, 2013 (gmt 0)|
IE 5.23 is a mac version, actually the last MSFT ever distributed - it's a piece of utter junk IMHO.
It's compiled for the PowerPC architecture, so you need an emulator like rosetta to run it on modern mac hardware. Rosetta itself was discontinued as well (not installed by default under snow leopard (10.6), not supported anymore on Lion (10.7) and Mountain Lion (10.8)) Rosetta was a way to facilitate the transition of the PowerPC architecture to the Intel based one for Tiger (10.4) and Leopard (10.5) - a rather painless transition to those who used rosetta (even unknowingly sometimes).
If anybody wants it: archive.org has a copy of IE 5.23. But seriously: forget about it. This IE is much, much worse than any other IE version you might ever run into. It had it's very own special set of IE bugs ("features" as MSFT only fixed security bugs or legal problems in IE.)
| 11:25 pm on Feb 19, 2013 (gmt 0)|
Fer hevvins sake, people. I don't use MSIE 5.23. In fact I was staggered to find it still works on my current Mac (10.6.8, the last version that came with Rosetta-- and that's after bidding a tearful farewell to 10.4, the last version to permit Classic). I just fire it up now and then for experimental purposes. I sometimes run Lynx for the same reason.
Some of you may be too young to remember, but for years and years-- decades even-- one of the beauties of the Mac was that you could continue running positively ancient applications. Not like That Other Platform where you basically had to upgrade all your software every time you moved to a new operating system. To this day I haven't found a diff-merge program that works as well as the one dating from 1991 that I used to use. And I've never managed to replace the whole array of font-wrangling programs I used to have.
What was the question again?
Oh, right. Line breaks inside quotation marks, as in "title" or "alt" attributes. Basically anything inside quotes is treated as literal text.