• Everytime I use the £ sign it displays like this: £

    Anyway of fixing this? Is it a bug?

    Thanks in advance

Viewing 6 replies - 1 through 6 (of 6 total)
  • Write it like this: £ and I have no doubt that will not display right….

    £
    or
    & p o u n d ; without the spaces.

    Thread Starter jinsan

    (@jinsan)

    thank you very much podz although tis a bit of along winded way, I’ll read up on those quick tag thingy me jigs.

    Cheers very much

    Rather than type html entities all the time, t’s probably easier to switch your encoding from UTF-8 to ISO-8859-1, which handles pound signs no problem.

    Thread Starter jinsan

    (@jinsan)

    what’s the difference between UTF-8 and ISOxxx. UTF-8 iss et by WP so I assumed this would be the best thing to leave it as is, will it affect anything else on my site if it was to change Or would affect validation?

    If you have already posted using one encoding, e.g. UTF-8 and you change the default encoding to something else – the new posts after that will be OK, but the old ones will show a lot of strange characters…

    Necessity creates the invention (invitation?) to jump in? …

    Especially due to mySQL default encoding being ISO-something from what I understand, restores from such SQL backup-dumps can create just this scenario – ISO-xxx data mixed with other UTF stuff on the same blog.

    Maybe we should explore workarounds? (I have an ulteria motive if you didn’t guess – don’t want to bore anyone with the details just now though).

    If necessary, what would happen if one put the settings on UTF, did a backup, then went back, put the settings on ISO-xxx, did another backup, cut and pasted the backups (in a text editor) to match the original encoding of each segment, then uploaded one or the other back to the blog? I imagine this would work, if….

    that mySQL encoding default was also dealt with. If one somehow finds the settings to change the encoding during the backup (is encoding messed with by mySQL on a restore too?) this should all be enough for a perfect consistent encoding emerging from a patchwork yes?

    I had hoped that opening any backup -even of disparately encoded posts, into Notepad+++ or the other that Podz recommends, selecting all, and changing the encoding, should also do the trick, but this wasn’t my experience. Do anyone know of cute little hat trick for this – it’s certainly much easier?

    thanks.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘How to remove  from £’ is closed to new replies.