Forums

Do you want me to take a look at this/come up with a patch based on the current markup, or wait until you finish the admin markup?

select id from prefixtopics where moved_to is not null and last_posted < UNIX_TIMESTAMP() - 604800

where prefix is your database prefix.

That should get a list of the topic IDs. Then, you just have to change it into a delete using the same where clause.

And it is not dangerous, unless you mix up "is not null" and "is null" in which case you'll delete actual topics.

Add an extra linebreak between the text and the picture, no backslashes required.

The wrapper function is the easy part. The hard part is identifying every numeric quantity that is output that you might want to add commas/decimals to.

Deadlines are always difficult. People always ask for them, since just having releases randomly pop up can be difficult. Developers always find them difficult to follow, since there always seems to be more stuff to do, distractions that get in the way, etc.
I don't think the solution is to abandon deadlines. Without deadlines, we might as well be in an endless loop of adding new features and testing them. That was part of the reason we put a deadline in for this release: so we would have a feature freeze at a given point and from then on work on polishing the code, fixing bugs, etc. What we need to do, however, is to be more accountable for our deadlines. We need to be more proactive in making sure we meet them.

That being said, I found out I won't be here in 3 hours, when I was supposed to "release" the beta. That, coupled with the fact that people have been asking me not to release until we have the markup, which is one of the most important changes in the beta, means I'm simply going to be providing a link to download the current revision without releasing it as the beta. Once we have the markup in place, we'll release the beta for real.

You can download the current revision using this link

Exactly. Those are the sites that don't need the typography changes. The sites where you have mixed content is where it's most useful.

This is something I can support. I already did something similar for localized rewrite schemes. You just specify an extra language file (eg: lang/English/typography.php) and put your stuff in $lang_typography.

Except they're not the same. Trying to automatically change the typography of arbitrary data is something like using a BabelFish type service to automatically translate the contents of posts.

BBCode involves transforming groups of characters that are not used together normally. There is a finite list of BBCode, defined by the software, used there. Automatic censoring is a good example of why this will not work: nobody has a "perfect" censor, every censor is either too strict (censoring the word firetruck?) or too weak (add a space in between the letters and you bypass it).

In the case of typography, you have to list every single alternative case of typography used and make it all reflect the typography of the language you're using (in the case of quotation marks, for example). You also have to know the language that the poster was using within the post. And no matter what, there will always be ambiguous cases. For example:
10 500
Given that I'm from the US, you would assume that I was posting two separate numbers. However, if I were French, that would be like posting 10,500.

Not easily, no.

It is a little late to do this for beta3, but we could potentially do it for the next release.

It's a hassle to set up and provides no noticeable benefits I can see, since an unfinished extension is an unfinished extension.

...why?

I think a mailing list is a bit excessive (and difficult to run/administer) and the forum happens to serve quite well in all the capacities you're describing. It might be better to look at how we can improve this forum for those who would want some of the capabilities of a mailing list that it does not provide (eg: subscribe to an entire forum, get a daily/weekly/monthly digest, etc)