1.2-epsilon-RC1 not showing extended chars

  • Hi all, just wanted to drop my 2 cents:
    Here’s what I did:
    1.- mysqldump my db to file
    2.- create new user and db
    3.- mysql -u new_user -p new_pw new-wp_db <dumped_file.sql
    4.- untar 1.2-epsilon-RC1 source into new dir
    5.- mysql -u new_user -p new_pw new-wp_db
    mysql > update wp_options set option_value=”https://www.lingo.com.mx/~ruben/wp1.2&#8243; where option_id=1;
    6.- point browser to upgrade.php, ran fine
    7.- extended chars (?- ?? ??) do not show; but everything else looks ok
    I have both versions (1.0 and 1.2) running, if you want to check:
    https://www.lingo.com.mx/~ruben/index.php
    https://www.lingo.com.mx/~ruben/wp1.2/index.php
    Maybe upgrade.php could ask if the user would like to choose a different location for the new wp installation, and do the update I did?
    best
    Rub??n

Viewing 7 replies - 1 through 7 (of 7 total)

  • Hi, Rub??n.
    First at all you must change your charset encoding v?-a Options->Reading->Encoding from “UTF-8” (default) to “iso-8859-1″… That’s all… ??
    Greets!

    An alternate solution is to open the .sql dump with a good text editor, and save it as utf8, then import it back into mysql.
    Then you can just keep using UTF8 in WP 1.2.

    does this also apply to seeing backslashes before the apostrophe? like if i type “your’s”, it comes across as “your\’s”. and this ONLY happens in my comments, not in the entry body itself. what could that be?
    here’s an example.

    Same question as waterlily.
    – Lars

    Thread Starter umquat

    (@umquat)

    ala_747, michel_v: UTF-8 is better, so I needed to convert the mysql dump to UTF-8. In Linux there’s a nifty utility called iconv.
    This is what I did:

    iconv -f iso-8859-1 -t utf-8 ../blogdump_wp_1.0.sql >blogdump_wp_1.0-UTF8.sql

    Then I could feed it it Mysql, worked like a charm.
    I think the moving to UTF-8 is a very solid decision, but the upgrade script really should take care of that. I would suggest the following steps:

    1. Dump the DB to a file
    2. If in Linux, use the systems iconv to convert encodings
    3. for Windows users, provide the instructions to download and execute iconv.exe (maybe from https://www.zlatkovic.com/pub/libxml/iconv-1.9.1.win32.zip) Maybe bundle it if licensing permits
    4. create another database, preferably with another user and passwd
    5. feed the newly converted file to mysql, using the new database and user
    6. Run the current upgrade (modify structure, etc.)
    7. Ask if the source code will use the current location, or another one

    Hope it helps
    Cheers
    Rub??n

    Thread Starter umquat

    (@umquat)

    woops, double post, I thought edit did exactly that ?? Please delete the ugly post ??

    Does any of this have any relationship to why all my posts imported from MT that had html in them got
    UN-html-ed and displayed with tags and all—- like tables and images insterad of rendering them, as they did when they showed in the MT blog?
    What’s my best “fix” for this? I still have the import.txt file that I used to import into WP.
    I like how WP translated all the “More” tags (the “Read On” feature of MT)
    I also like a whole bunch that it’s PHP instead of Perl (which gives me a fighting chance of being able to configure things, since PHP is easy enough to learn, and I’m also helped by Dreamweaver MX 2004, which also supports PHP.
    Dale

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘1.2-epsilon-RC1 not showing extended chars’ is closed to new replies.