Closed joshuasosa closed 2 years ago
More examples:
–
converted to â
after migration (e.g., Rover–Aerial
became RoverâAerial
)–
converted to –
after migration (e.g., 2014–2015
became 2014–2015
)†
converted to â€
ü
converted to ü
(e.g., Steinbrügge
became Steinbrügge
)Long example:
Voigt JRC†, CW Hamilton, G Steinbrügge, Á Höskuldsson, I Jónsdottir, and T Thordarson (accepted) Linking lava morphologies to effusion rates for the 2014–2015 Holuhraun lava flow-field, Iceland, Geology
became:
Voigt JRC†, CW Hamilton, G Steinbrügge, à Höskuldsson, I Jónsdottir, and T Thordarson (accepted) Linking lava morphologies to effusion rates for the 2014–2015 Holuhraun lava flow-field, Iceland, Geology
Seems like the migration script is currently not multibyte safe.
This issue still occurs for me on current migrations.
Scratch my last comment, my last major migration was done just before the last AZQS update. I re-tested with the same data and confirm issues are resolved. Thanks!
Problem/Motivation
UAQS pages may have text that contains special characters, some of which gets imported improperly.
Describe the bug
The particular case I found is a UAQS Flexible Page with a Text area paragraph that contains a registered mark ® (e.g., Spacewatch®) results in it being migrated to an AZQS Page with a Text paragraph that replaces that registered mark with ® (e.g., Spacewatch®),
In comparison, basic pages or other custom content types that were created in Drupal 7 and migrated using Drupal 9's built-in migration tools get imported with correct text.