$result = get_string_from_file('thischarset',$CFG->dirroot.'/lang/'.$lang.'/moodle.php', "\$resultstring"))
Do I need to create "stubs" in dirroot/lang/ for the custom lang packs? Weren't lang packs moved to dataroot/lang/?
I'm trying to do a UTF-8 migration with 1.6.4 as 1.7.1+ gives "unknown context" error and I don't want to hassle with 1.7 any more for today
I am not sure what the exact problem is but you could try this:
change your default language to english and upload default language packs to dirroot/lang folder (copy your custom packs first somewhere). After utf-8 migration you should have utf-8 language packs created by moodle in your dataroot/lang folder. Open your custom language pack files with notepad and save files as utf-8 format + copy your modifications to dataroot/lang files...
I was just curious about the reason why utfdbmigrate.php peeks at the dirroot for the languages, as they have been moved to dataroot.
I looked at the database tables in SQLYog and all the tables are indeed marked as unicode_general_ci.
Since I am only using English I guess this all I need to do besides mark the process as completed manually and get on with my life.
But the question remains to Samuli (or anyone else who knows) ... how do I manually the mark the process as completed? Which table/field is that?
Also... Do I need to inconv any specific files or directories before I can feel safe?
section "The plan", point 2
There wil be a field unicodedb created, value 1, after the migration in mdl_config. I checked my 1.8 and it is there, I checked an unmigrated 1.6 and it has a unicodedb-field with an empty value in table mdl_config, field 1.
For English only sites, there is as far as I remember no iconv needed, but backup, backup, backup and test, test test!