Wedge
Public area => Off-topic => The Pub => Other software => Topic started by: Sergeant on August 7th, 2011, 06:01 PM
-
Very excited about Wedge, however my forum is currently running SMF 2.0 RC3 and so I'm concerned that I won't be fully geared up for the transition to Wedge on its final release.
...so, would I be best running through the process of upgrading my forum to SMF 2.0 Final now, in preparation for a cleaner upgrade to Wedge?
-
Well, I'd upgrade to 2.0 final anyway knowing as I do that there are security related issues in RC3 that have been addressed by 2.0 final...
To be honest, though, there are no major DB changes between RC3 and final so the process should be virtually identical anyway from an import point of view; of course if the structure's been modified through mods, your mileage can and will vary.
-
Well, I'd upgrade to 2.0 final anyway knowing as I do that there are security related issues in RC3 that have been addressed by 2.0 final...
To be honest, though, there are no major DB changes between RC3 and final so the process should be virtually identical anyway from an import point of view; of course if the structure's been modified through mods, your mileage can and will vary.
Out of curiosity, what is your view on UTF8 and is it beneficial for our SMF builds to be converted or will Wedge not support it?
-
Wedge is expressly UTF-8 only, because it solves so many problems around internationalisation. AFAIK the importer will already deal with conversion to UTF-8 for you (and if it doesn't yet, it will in time)
-
Wedge is expressly UTF-8 only, because it solves so many problems around internationalisation. AFAIK the importer will already deal with conversion to UTF-8 for you (and if it doesn't yet, it will in time)
-
AFAIK the importer will already deal with conversion to UTF-8 for you (and if it doesn't yet, it will in time)
-
Exactly. Even mixed strings (containing e.g. latin and utf-8 characters) will be properly converted during the import process :eheh:
-
This shall be the case, yes. And if it isn't, I'll rewrite the friggin' importer myself to do it. :P
-
Actually, quick reply used to have issues with entity handling anyway, but I seem to recall it's since been fixed (fairly sure I ended up fixing it by proxy when adding the hybrid editor)
-
It still has the annoying saveEntities function call though.
-
That's the fix to it; the original QR box didn't have that, and it had a tendency to mess with entities in all kinds of bad ways.