 sj |
||
|
||
HTML Practice thread 2 - please ignore
|
|
|
Subject: HTML test thread 2 - please ignore From: GUEST,SharonA at the library Date: 24 Oct 01 - 07:45 PM Second verse, same as the first! (i.e. I'm just practicing here; please ignore this while I practice) |
|
Subject: RE: HTML test thread 2 - please ignore From: JohnInKansas Date: 25 Oct 01 - 08:47 AM Thinking out loud - to myself. References to W3C Committee HTML 4.01 Specification Most of the documentation for html assumes that an html document is being prepared to be sent to another user. In the process of sending a document, it may reside on a server, which can forward it to one or more users; but in its server role, it is not necessary that the intermediary device be able to actually "read" the document. Instructions which the server may/must use to receive and to resend the document, and instructions that tell the receiving user how to "read" the document, must be given in a very limited set of characters. In discussions in other html threads, a number of people have assumed that characters in this same limited group are the only ones that can be used "uncoded." I have been unable to find any statement on "reserved" or "prohibited" characters in the HTML Specification. Paragraph 5.3.2 of the Specification names only the four characters <, >, &, and " as characters that authors "should" code. The implication is that a reader program might be able to distinguish their use in clear text from their use as escape/control characters, but the possibility of confusing the machine makes it advisable to code. The document can "declare" a "character set" to permit the use of additional characters in the body of the document. Unfortunately, some servers are unable to transmit a character set declaration, and some others are (apparently frequently) not set up to do so. If the end user of the document can identify, and "owns" (can use) the declared character set, then coding of most(?) additional characters - in the body of the document - should become unnecessary. With proper instructions in the document header, some - but not all - servers can do some character set translation, so that documents can be sent with different character sets to different users. According to the current html specification, only the most "modern" servers are well equipped to perform appropriate character set translations. This facility is apparently not much used, but someday may bring the "ANSIquarians" and the "EBCIDICians," the "macinthrashers" and the "mickeysofters," and all the "littleendians" and bigendians" together to make a treaty. (Until the ISOdeviants mess things up again?) Many - especially older - documents do not include character set declarations, and some - especially older - servers are not capable of transmitting an included declaration. The html specification is quite clear that there is no useful default character set. If there is no declared character set, or if that set is unavailable to the "reader" program, then each reader device is pretty much free to do whatever it can to execute the document in readable form. It appears that most "readers" do, in fact, invoke some sort of extended character set, and most of them apparently do a pretty good job of interpreting fairly large numbers of strange characters. I have noted that when I save a document as html in Word, I get different things than when I post the same document to a mudcat thread. (Usually, mudcat works better.) The revelatory flash is that a posting to a mudcat thread is NOT an html document. It is only an "edit" of an existing document. All of the document characteristics have been predefined by the mudcat magicians. Most of the web works pretty well with the most primitive of web pages, and even the most perfect of pages will be mangled differently by different readers. The question then is, "Which characters can I type and which ones do I have to code?" The corollary question is,"Does everything that works for me work for everyone?" Tests to follow. John |
|
Subject: RE: HTML test thread 2 - please ignore From: JohnInKansas Date: 25 Oct 01 - 08:50 AM Testing: Using an English-US keyboard (qwerty). Two &nbs; between each character. Coding the 4 suspect characters <, >, &, and " to keep the key count straight.
Sending now, either to see if this works, or to see how many html errors I made. Never know which. John. |
|
Subject: RE: HTML test thread 2 - please ignore From: The_one_and_only_Dai Date: 25 Oct 01 - 08:52 AM john, it's , incidentally <grin> |
|
Subject: RE: HTML test thread 2 - please ignore From: JohnInKansas Date: 25 Oct 01 - 08:55 AM OK, so I can't spel nbspbr> (and my chelspecker didn't catch it).br> Testing: Using an English-US keyboard (qwerty). Two &nbs; between each character. Coding the 4 suspect characters <, >, &, and " to keep the key count straight.
Sending now, either to see if this works, or to see how many html errors I made. Never know which. John.
|
|
Subject: RE: HTML test thread 2 - please ignore From: JohnInKansas Date: 25 Oct 01 - 09:03 AM Well, I stuttered in the first row I accidentally typed the ampersand. Thought I took it out when I put the code & in. It read both the typed character and the code. Every character on my keyboard came across as typed, with the exception of the <, > and ", which I sent only as code. What a revelation! I suppose I could try typing those three, but I think I'll stick with the Std Committe recommendation. Pretty sure the " comes across, since it does get used a lot. John |
|
Subject: RE: HTML test thread 2 - please ignore From: JohnInKansas Date: 25 Oct 01 - 09:34 AM Let's see if I can mess this up:
John |
|
Subject: RE: HTML test thread 2 - please ignore From: JohnInKansas Date: 25 Oct 01 - 09:41 AM Try some pretty on it:
John |
|
Subject: RE: HTML test thread 2 - please ignore From: MudGuard Date: 25 Oct 01 - 09:42 AM John, < and > might come thru if there is whitespace next to them, but e.g. <b> would not come thru - so your test is valid for single characters surrounded by whitespace only. It depends heavily on the context whether the 4 chars have to be encoded or not. |
|
Subject: RE: HTML test thread 2 - please ignore From: JohnInKansas Date: 25 Oct 01 - 09:43 AM Try some more pretty on it:
John |
|
Subject: RE: HTML test thread 2 - please ignore From: JohnInKansas Date: 25 Oct 01 - 09:54 AM MudGuard I'm pretty sure you're right on with that. White space would be about the only way for the rip to tell that the character isn't an escape. The Spec is pretty straightforward about recommending that those 4 be coded, and I think I'll try to follow their recommendation. Those are the only 4 "named entity" characters in the lower 159 characters - i.e. on the keyboard. Makes one think there must be a reason why they made them easy. John |
|
Subject: RE: HTML test thread 2 - please ignore From: JohnInKansas Date: 25 Oct 01 - 02:18 PM My little tests above indicate that all of the characters on my US English keyboard except <, >, &, and " can, at least in some cases, be typed into a thread post without coding. The standard keyboard characters consist of most of the possible ASCII/ANSI/ISO8859-1 characters up to decimal number 126. My O'Reilly HTML Guide indicates that decimal values from 130 thru 159 are NOT DEFINED by the HTML 4.0 Standard and should not be used. None of these characters are "named entities." Equivalent characters for most of them are defined in the HTML Standard, but at different numeric values. The obvious problem people might run into with these "forbidden" characters is that Word (and probably other wp software) likes to put "curly quotes" in for you, both double and single, and may put en and em dashes in for your hyphens. All of these "AutoCorrect" characters that Word uses - that I've found so far - are in this "forbidden" ANSIValue range. Anyone composing in Word (or other?) and noticing dropped characters would do well to turn off this AutoCorrect function. In Word, it's <Tools><AutoCorrect><AutoFormatAsYouType> and unclick the curly quotes - at least. Once you have turned this function on or off, doing a replace " with " replace all, (and replace ' with ') will put all of them to whichever mode you have set - straight or curly. As a "by the way" comment, when you use the "Insert Symbol" function in Word, the abominable thing that is stuck into your document is NOT a character. It is a "graphic" thingy with a bad disposition. Don't do that in anything you want to put into html. The less than, greater than, ampersand, and double quote are the only "named entities" in the lower 126 ANSIVals. These four are also the only ones in the keyboard range (that I know of) that have "escape" or "tag" usage which could mess up the reader if they are not coded. (The percent character can be used as an escape in a URL, but that should not be of concern. Mostly we just copy what's there.) All other characters that are given "name entities" have decimal values of 160 and above. The HTML Spec lists about 256 of them, up to decimal value 9830 - ♦. Curiously, my O'Reilly doesn't list any characters past decimal 255. The HTML 4.0 Spec lists characters from several different character sets. While inclusion of these characters in the HTML Spec gives the impression that the characters should all be available to any "conforming" document, the Spec is somewhat vague about the difference between "required," "expected," and "permitted." Character definitions come principally from ISO 8879 and ISO 10646. The HTML Spec contains a notice: Portions © International Organization of Standardizatio Permission to copy in any form is granted for use with conforming SGML systems and applications as defined in ISO 8879, provided this notice is included in all copies." Unfortunately, three tries later, I have failed to get the entire statement to print (margins), but there it is - mostly. HTML 4.0 ¶24.2 lists Latin1 characters, the bulk of the characters used in English and many Western European languages. Approximately 96 characters. HTML 4.0 ¶24.3 lists Symbol characters, principally from the Latin Extended-B set, intended for use as symbols in technical and mathematical works. About 125 characters. HTML 4.0 ¶24.4 lists Special characters. This list includes the four "Control" characters from the keyboard set, a few Latin Extended-A characters, and some "Spacing Modifier Letters." Two characters at the end of this list are noted as "proposed but not yet ISO standardized. About 30 characters. Characters that aren't on the keyboard apparently do have to be coded. Non-keyboard characters can be put into a Word doc using the Alt-Numpad method, but they don't seem to come across in html when you do that. (Most of the ASCII/ANSI values for Alt-Numpad entry are in the "prohibited" range.) So far, the indication is that all of the characters "named" in the HTML Spec should show ok in a mudcat thread when coded as decimal, hex, or name entities. John |
|
Subject: RE: HTML test thread 2 - please ignore From: JohnInKansas Date: 25 Oct 01 - 02:23 PM HTML 4.0 ∥24.2 Latin1 characters
John |
|
Subject: RE: HTML test thread 2 - please ignore From: JohnInKansas Date: 25 Oct 01 - 02:25 PM HTML 4.0 ∥24.2 Latin1 characters (part 2)
John |
|
Subject: RE: HTML test thread 2 - please ignore From: JohnInKansas Date: 25 Oct 01 - 02:26 PM HTML 4.0 ∥24.2 Latin1 characters (Part 3)
John |
|
Subject: RE: HTML test thread 2 - please ignore From: JohnInKansas Date: 25 Oct 01 - 02:29 PM HTML 4.0 ¶24.3 Symbol characters
John |
|
Subject: RE: HTML test thread 2 - please ignore From: JohnInKansas Date: 25 Oct 01 - 02:30 PM HTML 4.0 ¶24.3 Symbol characters (part 2)
John |
|
Subject: RE: HTML test thread 2 - please ignore From: JohnInKansas Date: 25 Oct 01 - 02:31 PM HTML 4.0 ¶24.3 Symbol characters (Part 3)
John |
|
Subject: RE: HTML test thread 2 - please ignore From: JohnInKansas Date: 25 Oct 01 - 02:35 PM HTML 4.0 ¶24.3 Symbol characters (Part 4)
John |
|
Subject: RE: HTML test thread 2 - please ignore From: JohnInKansas Date: 25 Oct 01 - 02:37 PM HTML 4.0 ¶24.3 Symbol characters (Part 5)
John |
|
Subject: RE: HTML test thread 2 - please ignore From: JohnInKansas Date: 25 Oct 01 - 02:39 PM HTML 4.0 ¶24.3 Symbol characters (Part 6)
John |
|
Subject: RE: HTML test thread 2 - please ignore From: JohnInKansas Date: 25 Oct 01 - 02:41 PM HTML 4.0 ¶24.3 Symbol characters (Part 7)
John |
|
Subject: RE: HTML test thread 2 - please ignore From: JohnInKansas Date: 25 Oct 01 - 02:42 PM HTML 4.0 ¶24.4 Special Characters
John |
|
Subject: RE: HTML test thread 2 - please ignore From: JohnInKansas Date: 25 Oct 01 - 02:49 PM HTML 4.0 ¶24.4 Special Characters (Part 2)
HTML 4.0 ¶24.4 Special Characters (Part 3) Proposed but not yet ISO standardized:
John |
|
Subject: RE: HTML test thread 2 - please ignore From: SharonA Date: 25 Oct 01 - 03:19 PM *sniff* And I was so proud of myself for making a blueclickeything... I need a deep, deep hole to crawl into. :^( |
|
Subject: RE: HTML test thread 2 - please ignore From: JohnInKansas Date: 25 Oct 01 - 03:49 PM Well SharonA, I'm counting about 65 "errors" in what I've got up there so far. It's gonna take me a couple of days to figure out what's going on. A couple of characters that printed when I put them in text up above don't wanna show themselves in the tables. I think it's cuz my SO walked in & started messing with the connection, but I guess I better not tell her that. Sorry, but I guess I did kinda mess up your thread. John |
|
Subject: RE: HTML test thread 2 - please ignore From: SharonA Date: 25 Oct 01 - 05:10 PM No, you didn't mess up "my" thread. It's just going to take me 65 YEARS to figure out what the heck you're doing! I mean, jeez, it took me four-and-a-half months to get around to learning the blueclickey code! :^) |
|
Subject: RE: HTML test thread 2 - please ignore From: JohnInKansas Date: 26 Oct 01 - 06:33 AM SharonA Most of what you type into a post works, as long as you put your <br> at the end of each line. If you type one of the "escape" characters, an html reader (IE, Netscape, etc) thinks you're telling it to "do something," so if all you want to do is "show" a character, you have to use code. For example, if you wanted to say "a is less than b," you would write the equation "a<b." Since the html reader might think that the <b was the beginning of a command, something like <br> perhaps, what you actually need to type is: a<b The only three characters on your typewriter that should always be "coded" are the "ampersand," "lessthan" or "left angle bracket," and the "greaterthan" or "right angle bracket." The HTML Spec notes that a fourth, the "double quote" can sometimes have an "escape" or special meaning, so some people prefer to code it as well. In normal text, the &quo; usually comes across okay, so usually it's okay to just type it, but there may be times when it needs code. All characters can be "written in code," but it would be pretty silly to type: HELP! when what you want to say is: HELP! On the other hand, if you want a copyright symbol, ©, you can type © and the © should "show" when you post it. Not all defined codes work on all documents, with all servers, for all reader programs. All I have been doing up above is "sending myself" all of the codes defined in the HTML Specification in order to see which ones work. If you find a character in the rightmost column (EntityChar) that you want to use in a post, you type what is in the next column to the left (EntityCode) where you want the character to appear. A few characters show "dummies" instead of the intended character. I'm working on them. The "vertical white rectangle" (that's how it shows on my display) is a "default" for a "missing" character. As far as I can tell, you can't put this character in your document on purpose. John |
|
Subject: RE: HTML test thread 2 - please ignore From: JohnInKansas Date: 26 Oct 01 - 06:44 AM The HTML Spec notes that a fourth, the "double quote" can sometimes have an "escape" or special meaning, so some people prefer to code it as well. In normal text, the &quo; usually comes across okay, so usually it's okay to just type it, but there may be times when it needs code. One problem with coding is "Ya gotta spel them ryte." For < you type < For > you type > For & you type & For " you type " I left of the "t" in one "quot" up above, so it should have been: The HTML Spec notes that a fourth, the "double quote" can sometimes have an "escape" or special meaning, so some people prefer to code it as well. In normal text, the " usually comes across okay, so usually it's okay to just type it, but there may be times when it needs code. If I didn't make "typos" real fast, I'd never get anything typed. John |
|
Subject: RE: HTML test thread 2 - please ignore From: MudGuard Date: 26 Oct 01 - 07:33 AM the <b was the beginning of a command, something like <br> perhaps Wrong. There is no such thing as an HTML command. HTML is not a programming language, it is a language describing the structure of a document. HTML has elements, e.g.: html, b, br ... Elements consist of tags (opening tags, e.g.: <html> and closing tags e.g.: </html>), attributes (see below) and content (the stuff between the opening and closing tag. Attributes are specified in the opening tag as a name-value-pair (in some cases the name can be ommitted, e.g. the selected value of the option element) name and value are separated by an equal sign, values should and in many cases have to be enclosed in quotes (either single or double quotes, opening and closing quote must match). Example:
Yellow background: the table element
|
|
Subject: RE: HTML test thread 2 - please ignore From: MudGuard Date: 26 Oct 01 - 07:37 AM Arrgh, last two lines are incomplete, class is also an attribute name and foobar (NOT: "foobar") is also an attribute value. |
|
Subject: RE: HTML test thread 2 - please ignore From: JohnInKansas Date: 26 Oct 01 - 08:55 AM MudGuard No argument at all with your semantics, however I was attempting to communicate with someone who probably isn't interested in "specanese." "Command" was used in the colloquial sense of something that tells something to do something - or how to do something. Sorry if it offends, but I assumed that the ones who need to worry about the "literal" meanings will be elsewhere. John |
|
Subject: RE: HTML test thread 2 - please ignore From: MudGuard Date: 26 Oct 01 - 09:05 AM No offense, I was just seeing someone who reads the standards (quite an exception, even among HTML "experts") and still uses "wrong" names for the things... |
|
Subject: RE: HTML test thread 2 - please ignore From: MMario Date: 26 Oct 01 - 09:07 AM And even within the business - I see both resumes and "help wanted" notices that speak of "programming in HTML" - though that phrase is nonsense. |
|
Subject: RE: HTML test thread 2 - please ignore From: JohnInKansas Date: 26 Oct 01 - 09:51 AM Test soft hyphen. The following line contains multiple "soft hyphens," character ­ embedded thoroughout. The theory is that the soft hyphen is invisible unless a "word" breaks at the end of a line. BlowzyNightFrumpsVex'dJackQBlowzyNightFrumpsVex'dJackQBlowzyNightFrumpsVex'dJackQBlowzyNightFrumpsVex'dJackQBlowzyNightFrumpsVex'dJackQBlowzyNightFrumpsVex'dJackQBlowzyNightFrumpsVex'dJackQBlowzyNightFrumpsVex'dJackQBlowzyNightFrumpsVex'dJackQBlowzyNightFrumpsVex'dJackQBlowzyNightFrumpsVex'dJackQBlowzyNightFrumpsVex'dJackQBlowzyNightFrumpsVex'dJackQ John |
|
Subject: RE: HTML test thread 2 - please ignore From: JohnInKansas Date: 26 Oct 01 - 09:55 AM Soft hyphen character ­ or ­ does what it is supposed to. John |
|
Subject: RE: HTML test thread 2 - please ignore From: JohnInKansas Date: 26 Oct 01 - 10:08 AM Guys, I'm still waiting for the world to get me a good, usable, Windows compatible ΤΕΧ setup, and I do get impatient sometimes when html "experts" don't recognize the SGML base for it. Sort of like when ADA came out. The first spec was very specific about it being an "interface management tool" and not a programming language. But programmers got 'holt of it. B.S (big sigh, or...) John |
|
Subject: RE: HTML test thread 2 - please ignore From: JohnInKansas Date: 26 Oct 01 - 11:40 AM In the Special Characters set, the following characters failed to display: 8194,   - en space 8195,   - em space 8201,   - thin space Test of em, en, thin spaces: Normal text: Blowzy night frumps vex'd Jack Q. With en space: Blowzy night frumps vex'd Jack Q. With em space: Blowzy night frumps vex'd Jack Q. With thin spaces: Blowzy night frumps vex'd Jack Q. John |
|
Subject: RE: HTML test thread 2 - please ignore From: SharonA Date: 26 Oct 01 - 12:05 PM Yeah, John, I had a specanese once. Cute little dog, but kinda yappy. *G* |
|
Subject: RE: HTML test thread 2 - please ignore From: JohnInKansas Date: 26 Oct 01 - 12:59 PM Woof! John |
|
Subject: RE: HTML test thread 2 - please ignore From: JohnInKansas Date: 26 Oct 01 - 01:35 PM Test of 8206 & 8207. Input string: Blowzy night frumps vex'd Jack Q. Insert 8207 ahead of frumps. Insert 8206 after frumps. Blowzy night frumps vex'd Jack. Q. John |
|
Subject: RE: HTML test thread 2 - please ignore From: JohnInKansas Date: 26 Oct 01 - 03:48 PM Checking some strange characters: 130 ‚ 131 ƒ 132 „ 133 … 134 † 135 ‡ 136 ˆ 137 ‰ 138 Š 139 ‹ 140 Œ 141 142 Ž 143 144 145 ‘ 146 ’ 147 “ 148 ” 149 • 150 – 151 — 152 ˜ 153 ™ 154 š 155 › 156 œ 157 158 ž 159 Ÿ John |
|
Subject: RE: HTML test thread 2 - please ignore From: JohnInKansas Date: 26 Oct 01 - 04:45 PM A format test
John |
|
Subject: RE: HTML test thread 2 - please ignore From: JohnInKansas Date: 26 Oct 01 - 04:50 PM And another:
John |
|
Subject: RE: HTML test thread 2 - please ignore From: JohnInKansas Date: 26 Oct 01 - 05:19 PM
John |
|
Subject: RE: HTML test thread 2 - please ignore From: Jon Freeman Date: 26 Oct 01 - 05:37 PM John, soft hyphen does not work in my Opera 4.02. It just forces one long line that I have to scroll through horizontally. I like the feature though but what version of HTML does it need? This leads me to the internet compatibility problems. I favour compatibility over features as I don't like situations whereby a user would need to upgrade browser (or possibly even hardware) to be able to use a site but the other side of the coin is things do need to continue to progress. How does one address this? Jon |
|
Subject: RE: HTML test thread 2 - please ignore From: JohnInKansas Date: 26 Oct 01 - 06:26 PM Jon A soft hyphen will only break a line at the "edge of the page," so my guess is that on an html viewer that would only happen at the same place where an unbroken line would wrap. In a "DOSSY" display, the wrap length is usually about the same size as your keyboard buffer, so it could go out to 124 characters or more. If the line doesn't break (or "wrap") on its own, a soft hyphen won't force it to. The main purpose of the soft hyphen is to tell a word where to break, if and when it needs to, and to be invisible otherwise. Usually only needed when you have a word that your "hyphenation dictionary" might not recognize. I don't really think the html version has a lot to do with it. I'm not very familiar with readers other than IE - and haven't really poked around in it much. Opera may have someplace where you can set page/display format preferences? John |
|
Subject: RE: HTML test thread 2 - please ignore From: MudGuard Date: 26 Oct 01 - 06:47 PM John, the entity names are case sensitive! ↔ displays ↔ while ⇔ does not. |
|
Subject: RE: HTML test thread 2 - please ignore From: MudGuard Date: 26 Oct 01 - 06:50 PM while ⇔ does not. You should also see the case-sensitivity in ä (ä) and Ä (Ä) |
|
Subject: RE: HTML test thread 2 - please ignore From: JohnInKansas Date: 26 Oct 01 - 07:06 PM MudGuard I thought I had checked everything so that it all matched the Spec. Since I did a lot of global replaces and such setting up my test specimens, it's possible that something got out of place. Since the first big group of test posts had each character in decimal, octal, and name code, though, I would think that I'd have to make at least two mistakes to get a bad result across a row. I'm in the process of checking out the flukes now, but I'm off to our Friday night jam so I'll be out of touch for 4 or 5 hours - depending on how long the fingers hold up. But yes! Character codes are one of the exeptions to html tags etc being non-case sensitive. John |
|
Subject: RE: HTML test thread 2 - please ignore From: JohnInKansas Date: 26 Oct 01 - 07:17 PM MudGuard again I think I saw where you got the uArr from. The post just a little way up from here was just to check out a table spacing, and I just used some junk that I had handy, but the "A" does go in the name tag for character decimal 8656 (& others through 8660). The upper case A is supposed to make them "double arrows," while the corresponding lower case gives you a single. Most of these are characters that don't work on mudcat (apparently). John |
|
Subject: RE: HTML test thread 2 - please ignore From: JohnInKansas Date: 27 Oct 01 - 01:55 AM Layout check:
|
|
Subject: RE: HTML test thread 2 - please ignore From: MudGuard Date: 27 Oct 01 - 03:49 AM Whether the characters work or not does NOT depend on mudcat or any other web server. The &xxx; character sequences get delivered as is to the browser. Therefore it depends on your browser and the font used for displaying the page the characters are in. Didn't know about the ⇔ double arrow thing (and of course did not look it up as I assumed it was a case error) Btw, in current HTML standard, which is XHTML 1.1 (I think) all element and attribute names are case sensitive (i.e. have to be written in small letters) and all attribute values have to be in quotes.
|
|
Subject: RE: HTML test thread 2 - please ignore From: JohnInKansas Date: 27 Oct 01 - 05:49 PM MudGuard: I'm still working on the concept, but it is true that a server just passes stuff to a browser. A post to a thread on mudcat, however, is an edit to a "standing document" and the document itself can affect what gets passed, in its declarations. As noted, most of "what you see" is "what you get" in the sense that each user's own browser has to interpret incoming stuff. Posts above are part of my own effort to satisfy my curiosity about what works. Theory don't matter at this point. I have a pretty good idea now of what characters and code actually work on mudcat for me. I should be able soon to re-post the ones that work for me - in a separate thread of course, since this one is beginning to bog down. Then anyone else who sees something different - or doesn't see something - will be able to tell us. The HTML 4 Specification (link at one of my first posts in this thread) is still, apparently in "review" and has not been "adopted" officially. Thus it cannot be considered "the standard" except by virtue of the observation that everyone seems to be using it. It is my understanding that XHTML is a "new critter" that few people have gotton into (mickeysoft notwithstanding). It's sort of like when C became C+ and then C++ and now C-squared. They're part of a family - but they aint the same languages. I'll have to look into XHTML soon, but for now mudcat seems to be working fine as an HTML document, and is mostly HTML 4 compliant(?). Incidentally - I'm having trouble getting back to this thread. The posts are not that numerous, but a lot of mine have been quite large - or maybe it's just interruptions while the FBI puts their new wiretap on me. It may be time to move the discussion to another thread. There are a couple of other HTML ones going. John |
|
Subject: RE: HTML test thread 2 - please ignore From: Nigel Parsons Date: 10 Feb 03 - 07:29 PM Wouldn't it be nice if these threads had a "number of hits" counter. Apart from the people posting to them I'd love to see how many people read a thread titled "Please ignore" Nigel |
|
Subject: RE: HTML test thread 2 - please ignore From: Mr Happy Date: 17 Feb 03 - 10:42 PM |
|
Subject: DON'T IGNORE--here are some good HTML titles From: Stilly River Sage Date: 18 Feb 03 - 12:58 PM John in Kansas, if I see a more recent or active HTML practice thread come along I'll post these over there also. Today I upgraded my reference library for my web design work. After deciding that I have just enough javascript information to get myself into trouble, I've picked up the latest editions of favorite books to read the instructions so I can do it correctly! I find that the "Visual Quickstart Guide" (Peachpit Press) series is very useful as a learning tool as well as a reference source. Good indexes, easy to understand examples, and in some cases, supporting web sites where you can go in and view the code in action or copy it to use yourself. Elizabeth Castro, HTML for the World Wide Web Jason Teague, DHTML and CSS for the World Wide Web Tom Negrino, Dori Smith, JavaScript for the World Wide Web (fourth edition, NOT JavaScript, etc. 3, which is still out there for sale). SRS |
|
Subject: RE: HTML test thread 2 - please ignore From: GUEST,Oldguy Date: 18 Feb 03 - 01:15 PM Hey webmaster: If you have the capability please make the IP numbers of the posters visible in the posts. I run some old fashioned bulletin boards and showing their IP number helps keep a bunch of garbage from being posted. Whatever you do don't let the tunebook go away. Old Guy |
|
Subject: RE: HTML test thread 2 - please ignore From: Stilly River Sage Date: 18 Feb 03 - 01:38 PM I think Joe Offer has the ability to search and block IP addresses when abuse occurs (we've had a couple of folks drop in lately and leave a lot of trash links on threads). But I can't see any good reason for publishing them, since they're just numbers. Just one more layer of stuff to have to work with. Why would posting numbers keep garbage out? SRS |
|
Subject: RE: HTML test thread 2 - please ignore From: Mr Happy Date: 29 Aug 03 - 11:12 AM http://www.mudcat.org/photos/images/mr_happy2.jpg. Mr Happy amusing the natives in Bishop's Castle. |
|
Subject: RE: HTML test thread 2 - please ignore From: John Routledge Date: 23 Aug 04 - 07:47 PM mudcat.org |
|
Subject: RE: HTML Practice thread 2 - please ignore From: wysiwyg Date: 16 Feb 05 - 12:46 PM
|
|
Subject: RE: HTML Practice thread 2 - please ignore From: Bill D Date: 16 Feb 05 - 01:32 PM it's a meandering asterisk! |
|
Subject: RE: HTML Practice thread 2 - please ignore From: wysiwyg Date: 16 Feb 05 - 03:27 PM Nope. The lady who sent it to me in email has it SO much prettier.... More of a chinese dragon effect. ~S~ |
|
Subject: RE: HTML Practice thread 2 - please ignore From: Mr Happy Date: 04 Apr 06 - 06:03 PM Mr Happy |
|
Subject: RE: HTML Practice thread 2 - please ignore From: Mr Happy Date: 04 Apr 06 - 06:06 PM Mr Happy |
|
Subject: RE: HTML Practice thread 2 - please ignore From: Mr Happy Date: 04 Apr 06 - 06:09 PM Mr Happy |
| Share Thread: |
