ferren

A working table which maintains a semblance of formatting as window width is changed from 50% to 100% of the usual landscape monitor is at http://www.electromontis.net/evoligion/_C/C11.shtml#T11.1 The code fragment that makes this work is ... <col width="110px"/> <col width="150px"/> <col /> <!-- This column absorbs width change --> <col width="40px"/> <thead> <tr><th>Instinct</th> <th>Synonyms</th> <th>Utility</th> <th>Chap</th></tr> </thead> <tbody> <tr class="red"> <td><b>Instinct-I</b></td> <td>Alpha-male egoism, <i>machismo</i></td> <td>Self propagating.</td> <td>11</td></tr> ... The validator says <col width=...> is obsolete and airily adds, 'use CSS', without further suggestions. I can't find anything in CSS that does this without style statements in each table box, which seems exceedingly inelegant. What am I missing?

TextWrangler (+ Firefox for display) and a wide screen, for Macs. Geany (") for Ubuntu, but it lacks TextWrangler's convenient multi-file search/replace . Free.

>Remember that IDs cannot begin with a numeric character. Oops. I have ~1200 id tags that are entirely numeric, and they have been working smoothly for several years. If I don't change them, is this likely to get me in trouble in the future? Or is this a rule that browsers are content to ignore, like using width="33%" for sizing images--illegal but the only way to produce the desired effect as window width changes.

Jumping to next/prev page is commonplace. I didn't have much luck asking about jumping to next/prev id tags, but how about jumping to next/prev header? Currently, I write: <h3 id="13"> <a class="up" href="#TOP">∧ </a> <a class="up" href="#12">↑</a> <a class="up" href="#14">↓</a> Title of section</h3> where I have to specify the next and previous id numbers. For ease of maintenance, I'd like to be able to write something like <h3 id="13"> <a class="up" href="#TOP">∧ </a> <a class="up" href="#prev.hdr">↑</a> <a class="up" href="#next.hdr">↓</a> Title of section</h3> making global changes simpler. I don't see a way to do this, but surely I am not the first person who wanted a way to increment an id automatically? 'current id ± 1' is the desired arithmetic, or 'last header' and 'next header'.

@Dave, I hoped the example code would show the usage. Buttons for 'next' and 'prev' are common in paged material; no pages in my html, but I want to jump to adjacent sections. <a href="#id+1">&vrtri;</a> would be ideal. Am I really the only person in 20 years who wants to increment an id number? It seems like such an obvious tool that I hoped someone had figured it out for me. PHP and JavaScript are terra incognita, and a long way from the subject I'm writing about. I am an author, and only reluctantly a programmer.

I have 1500 places where <nextid> would be useful. what is the recommended work-around? As is, I have to keep track of numbers. A generic 'next' and 'prev' would be ineffably convenient! Example: <h2 class="cen" id="01"><a class="triangles" href="#00">&vltri; </a> <a href="#TOP"> BRAIN ANATOMY </a> &nbs<a class="triangles" href="#02"> &vrtri;</a></h2> <p> ,,,</p> <h3 id="02"><a class="triangles" href="#01">&vltri; </a> <a href="#TOP"> 3 Layers of the Brain </a> <a class="triangles" href="#03"> &vrtri; <p> ,,,</p>

davej, I have ~3750 corrections to make and check. This goes a lot faster if I don't have to check them by uploading 100k files each time. I want to be able to see the result immediately. Following dsonesuk's clue, I think this means installing LAMP (Linux, Apache, MariaSQL, PHP) on my computer. I was hoping there might be an easier approach. (Got the L, sort of, but it and its computer are new and not entirely tamed.) On the other hand, in November I'll be at home with a couple of Macs with Apache and familiar OS X built in. Might this be a better starting point?

Yes--but if I am making a global change I would like to be able to work on a new set of 25 chapter off line, get them all working, and THEN upload them. Why can't I get at SSI files on my own computer? Example: my intrachapter navigation arrows--may be 25 sets in a chapter, worked on large screens but are too close together for small screens and finger tips. This leaves me with 1200 fiddly changes to make (can't use grep here). I'd prefer to swap in 25 working chapters after they have all been tested off line.

http://evoligion.wordpress.com works reasonably well with SSI files for features common to several pages. I want to edit it off line, at home, on my own machine. The problem is that I haven't found a way to call the SSI files. I get conflicting advice from the web. 'Can't be done!'; gobbledegook code in strange languages, assuming that I am the mythical system administrator to whom one is so often referred; wild guesses. This seems like a universally useful process which should be implemented in a trivial manner, as simple as whistling for any other URL. What am I missing?

Styling the link to indicate its state (link, hover, active, visited) is sometimes useful. However, 'visited' appears to be remembered. Is there a way to reset it to 'unvisited'? Reloading the file and browser does not do this, but I feel a need for 'visited today' vs 'visited last month', and haven't found a way to indicate this.

in a table: the pop-up box has no problem hiding adjacent boxes where it overlaps a bit, but it still tries to stay inside its <td> box. I shall work on the <img> problem first.

That'll keep me busy for a while! Thanks for the hand-holding! I just noticed related behavior

No problem here, but I could some advice. With 2500 footnotes, and a similar number of links, some glossary references, and a felt need to jump to the next figure or table, I devised my own system for navigating a 25-chapter html book. The question is, will others find my system easy and understandable. http://www.electromontis.net/evoligion/_A/Quirks.shtml explains the approach and lets one practice. Footnotes haven't received much attention from W3C, so one has to improvize. Suggestions appreciated.

</head> is now in place; Nu missed that one. Thanks for the suggestions: absolute puts the box somewhere the reader (who is presumably looking at the cursor) isn't looking: not good. overflow:hidden; stays within the width of the caption and makes a cramped box if the image is wide, as it sometimes is. References often don't fold gracefully, and do better in long boxes. overflow:hidden AND float:left; sometimes breaks the caption at the anchor and puts the remainder below the image. Not good. float:left; puts a wide box below the image, or for the rare image at 100% with caption beneath, just below the anchor (where it should be). This appears to be as close to the desired original behavior as we can get these days. All things considered, I liked the old behavior better: overlap the image, text in box runs over image. Alas. (Who thought what needed fixing?) Tutorials still tell me that the box model permits boxes to overlap. Why, if its enclosing box overlaps the image, can't the text of the <span> be persuaded overlap it? ... Suppose I wanted to position the pop-up relative to the cursor, obscuring whatever lay below, in the manner of a tool tip? Do we have any control over tool tips? I will look into this further. I found a suggestion using <abbr> which might work--except that none of my browsers know about it: <p>The <abbr title="World Health Organization">WHO</abbr> was founded in 1948.</p> TOR kept getting resets. Safari , iCab, Opera, Omniweb, Aviator, Vivaldi, Chrome and Chromium ignore it. Firefox at least underdotted WHO, but I presume that the expected hovering behavior is to display the unabbreviated title. I might make this work, if browsers cooperated .... (In any case, I'm already using underdots to go the glossary for neologism and jargon.)

Afterthought. Same code works at http://www.electromontis.net/evoligion/_C/Test11.html Added in edit: In its first working incarnation, the pop-up box did not displace the z=0 text as it now does. It simply hid it, which is acceptable. This suggests a major change in the behavior of the z-stacking algorithm, not entirely smoothed out yet. It might have been more useful if I had mentioned all this when behavior first changed, because it really looks like an HTML edit that did more than necessary. But--as always--I assumed it was something I had done, and in any case, I was focussed on writing rather than programming.