Search Results

Hi Dennis,

I think we are done with this odd encoding issue for now.

We need to stick with the plan of comparing old to new, with links for each; but we are moving off that target so let's call...

I just edited the old title.... using the double quotes on my key board.

8352

This is more-than-likely not about 7 / 8 bit ASCII, it is more-than-likely about UTF-8 and UTF-16.


See also: ...

If so, then what is wrong with the second quote mark (Unicode value) in the old site???

Those quote marks are in an encoding not processed by the PHP / HTML as proper "UTF-8" in this legacy...

Old site title is broken.... due to encoding issue:

8350

New site, title is looking good:

8351

If we edit the title on the old site and replace the mojibake with regular double quotes,...

OBTW, if I add this to the showthread PHP script:

$thread['title'] = utf8_encode($thread['title']);

(which I just did for fun to the old forum).

The issue is the same.

I think it is an...

Here ya go.....

8348

This is an encoding issue with an old post in the PHP vB3 app.

The encoding of the title DB field from years ago is not specified because the designers of vB 15+ years...

Let me check the original DB and post back..

Hold on.

Yes, the thread title in the migrated post is different because there is no migration script running against titles.

That's not a big deal, it's a total outlier.

We are not processing "thread...

What are you talking about?

The migrated versus is the same as the original version.

That is exactly how it should be.

This has nothing at all to do with migration, discourse or translating...

Here is one, but the issue is in the original DB.


Retry Logic But In Cron - UNIX for Beginners Questions & Answers - UNIX.COM Community...

While I am doing another test run, let me try to explain this better.

Our DB is nearly 15 years old.

People have copy-and-paste any kinds of encoding into the database. That stuff may have...

Here is the simple version.

I we have a post full of ORIGINAL v. MIGRATE threads, it is easy for me to compare, come up with code, test and retest.

Without the links, or links scattered all...

No. It's not that simple. It it was that simple, there would be no issue now. (The migration script already does encoding mapping from day 1. The DB is already UNICODE... the Ruby script...

This is all good... but I want to focus bottom up... only on the specific chars causing a problem in our DB.

That is what I am doing now ... finding the exact offending char and then finding the...

This Ruby code did not match... however running the search and replace mysql query directly against the DB seems to work (step by step).

8343

Testing now on staging server.... if it looks OK,...

This spam page (on new site) was full of those "odd diamond things"...

8340

https://community.unix.com/t/infraction-for-solosx-spammed-advertisements/271573

... but I got rid of them on old...

Like this:

8337

FYI existing old mysql dB

mysql> SELECT count(postid) from post where pagetext like '%“%';
+---------------+
| count(postid) |
+---------------+
| 66 |
+---------------+
1 row...

After this test, I may give this ruby gem a try as well:

File: README - Documentation for mojibake (1.1.2) (https://www.rubydoc.info/gems/mojibake/1.1.2)



See also: GitHub -...

Here some clues about this:

mysql - Trouble with UTF-8 characters; what I see is not what I stored - Stack Overflow...

There is a minor issue lingering which we currently have no working solution.

For example, see this pagetext in the original (old) forum mysql DB (continued thats to hicksd8 for finding these and...