OMG that is freaking awesome/crappy! I hacked 246 to take 15 characters, but never did I imagine it would take 15*4 (or 15*5?) characters to get my "15 visible" characters.

shortname should carry the same limit as longname and let the users figure out why shortname should be short. And both should be really freaking long!

EdB wrote:

OMG that is freaking awesome/crappy! I hacked 246 to take 15 characters, but never did I imagine it would take 15*4 (or 15*5?) characters to get my "15 visible" characters.

shortname should carry the same limit as longname and let the users figure out why shortname should be short. And both should be really freaking long!

I was going to edit it and just push for a total switch to Unicode, specifically UTF-8, as the default encoding of b2evolution when I saw your reply.

心道 = 2 Characters, does it qualify for the short name field?
Yes, only if b2evo is converted to UTF-8, especially the DB connection and tables. Currently, those 2 Characters gets destroyed unless the end-user knows what to do, but most do not know (or is afraid). The option left then is to type in it's character reference value. Again, it qualifies as "short", it has only 2 characters.

And I highly doubt some "pure-English" speaker will put in the short name field something this long: "World Wide Web Consortium Unofficial Blog". Because once s/he does that, s/he'll see the reason why the field is called "short name".

Anyway, I believe the time for b2evolution to switch to UTF-8 is now. OR at least provide an option during installation (for new blogs) and during upgrade (for existing blogs) to switch to UTF-8.

(Since we're talking about the installation script, might as well add a new field to change the table prefix during installation as well.)

b2evo does utf8 NOW. You just have to use an UTF-8 locale.