jaykul

I think OpenID has essentially emerged victorious in this. That post from 2005 is really outdated (as you’ll see if you try to look up any of the others he mentioned). I’d hope to see the OpenID stuff make it into the core sooner rather than later.

Regarding Jabber …. I know there’s a web/jabber-id project, but I’d have to say that I don’t think it’s a good login identifier. The key to the OpenID system is that (similar to CardSpace — they are essentially compatible) you get to choose which infromation you make available to sites that you log into using your ID. Some sites can require that you include certain pieces of information (like your email, or real name, or whatever) but you don’t implicitly give them access to anything else.

Doing the same thing with JabberIDs would require quite a bit of modification to the Jabber spec (currently your ID/vcard access is basically all or nothing) and would require web sites to implement a Jabber login themselves so the website could log into Jabber to check your ID in some way…

I fixed the javascript link to take out the language attribute, I had just copied it from the DomTT website and not tried validating. Validates XHTML 1.0->1.1 now. ??

The one thing that’s missing right now is that you have to choose upfront to either use the JS (javascript), or not … if you choose to use it, it takes the title attribute off the acronym or abbr (abbreviation) tag, which means if people have JS disabled, they won’t see a pop-up tooltip.

Personally, I think the tooltips on acronyms are a bit of an ugly crutch — I prefer the plain English way of doing things: spell out the meaning of the abbreviation the first time you use it, unless you expect your readers to already know what it means.

But as an option on the script, I’m considering flipping it around so you can choose to have the javascript itself replace the “title” attribute with the tooltip, if you want. (It’s not that way now because normal tooltips can’t have HTML, so if you wanted to do it that way, you would have to avoid HTML)

If you’re using textile … you should be using “bq. ” at the begginning of the line for blockquotes, not the

tag …

You can use xhtml while using textile, but you need to take into account that you are using textile. Which is to say: if you leave a blank line, textile is going to start a new paragraph for you, unless you’re in a <notextile> block, so to accommodate the fact that your are using textile, you need to put a leading space on the line if you’re starting a block-level xhtml tag after blank lines … or: a) use textile markup, or b) wrap the whole thing in <notextile> tags.

I use Textile 2 too. ??

Not only is it easier than coding html … removed urls and footnotes rock — I’m thinking about a LaTeX plugin ??

The bottom line, of course, is that I bought into the idea that if I store “plain text” as much as possible, I can always mark it up to be compliant with new standards…

Not sure what you mean, since I’ve got several bulleted lists on my site like:

* something about Office and PDF
* something about svchost.exe

And they’re all still working the way they should (that is, getting converted to li tags).

Textile 2.6 (based on TextPattern 4) has working == or <notextile> blocks, so you can just <track>==Artist – Title==</track> … or whatever. Also, if you use the entity = ( ampersand-hashmark, aka pound sign-61-semicolon ), Textile will leave it alone.

You can use TextControl to choose a filter per-post… that should let you use it for just the posts you needed it on …

WordPress has a concept of “filter” plugins, which is what Textile, Markdown, etc are. The idea is to store the text un-converted in the database, and convert it on the way out.

The idea is that if, for instance, you wanted to upgrade your site to XHTML 1.1 or even XHTML 2 … or whatever the next version of XHTML is after that … you would upgrade to Textile 5 (or whatever we’re up to by then) and your output would be safe, instead of having to update all your posts by hand…

Of course, the real reason is that nobody has written a good alternative markup that can convert *back* from XHTML.

The new version 2.6 release has working escapes ( == or <notextile> ), and you should be able to insert HTML without pain now.

‘kay … I’m gonna actually try to stay a little involved again, but what to I have to do to get this marked resolved?

Fixed… Finally.

https://www.huddledmasses.org/2005/10/03/textile-plugin-26-released/

Yeah, Textile has an “acronym” feature which assumes the acronyms will be listed like: AFAIK(As Far As I Know)

The solution is to use “==” to tell Textile to ignore that content:

===DATE(ETC())==

Well, I put up a workaround on my site yesterday…
I thought the workaround is a little ugly, so … today I came up with a more elegant solution (that is: a new regular expression).
Feel free to grab it from the original page:
https://www.huddledmasses.org/-wordpress-plugin-acronym-replacer/

Sure, why not. Actually, I meant to do that last night when I made the other change, but I ran out of time and forgot about it.
Speaking of Matt’s, did he release it? If so, why are so many people hitting mine? What’s better about it?

In the admin section!? Yikes. Uhm…. It sounds like you either cut-n-pasted too much, or too little …
https://huddledmasses.org/wp-content/plugins/source.php?file=image-headlines.php&justcode=true
If you copy from below the <hr> to the end, that *should* work, and without affecting the admin section at all… I guess I *should* consider offering these for download, since the plugins are supposed to be drag-n-drop … but THIS plugin requires the user to edit it (at the bottom there, to set the values, as you’ve no doubt read about on my home page already: https://huddledmasses.org-automatic-images-for-headlines/ ), so I figure cut-n-paste isn’t that big of a deal ??
Incidentally, this version has more logging in place to try to help diagnose errors (as well as the new features mentioned in the edit to the post)