Quote:
Originally Posted by
hicksd8
Need to remap ASCII characters to Unicode?
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 already does encoding mapping. it is not so simple as a "general remap" or it would be done already.)
Let's stick with the plan. Find links with problems. I know how to fix these if everyone will follow my original plan and provide specific links with specific issues (original v. migrated posts).
What I need are EXACT examples of the real problem in OUR DB (not theory). Thanks. The links I posted were directly related to the EXACT char problem I am working today (right now). I used that code as a basis to address directly problems you guys found.
We want to work this bottoms up. Bottoms up means to find the exact issues (not theory) and fix the exact coding issue for each encoding issue.
Please. I'm busy and need to get this done the way I know will work. The only way to get this done correctly and surely is bottoms up. Not top down theory and speculation.
Thanks.
What I need from testers, in this thread is ORIGINAL versus MIGRATED posts examples. I can take care of the rest (finding the encoding in the DB, finding the correct transform, writing the code, running it, testing it in the DB, etc). Please keep on track looking for issues. That is the best way to help get this done.
Everything we have identified so far, I already have a solution for, and tested it and it works.
What I need are more examples of any error, anomaly or other data migration integrity issue, in two links (the original post and the migrated post).