Open AndersBrohus opened 9 months ago
Hi, yeah i think its the zip process in migrations think, need to take a look at it.
Perhabs we could just use the guid instead of node name for this and it would work?
Hi there,
I have "funkier" situation with my site in spanish: my uSync zip data exported from v7 loads correctly on Migrations in V12; but if I just unzip-and-rezip it then the funky characters appears. No matter which software I use (windows, 7zip, winrar) nor command-line switch nor console encoding I use, this is what always happens.
The workaround that I have found was using VMware with an ubuntu install, accessed via shared folder the unzipped files and zip it in ubuntu with the typical zip command. This zip now I can load into migrations and will decompress special characters in filenames correctly.
I have the need of tweaking some folder structure and names and it is a lot easier and less error prone with a console script into the .config files rather than doing it in the backend for each of our testing stages and final production.
Hope this helps, Daniel.
Hi @KevinJump,
I do not know if this is an issue in uSync or uSyncMigrations, but if we have a uSync file named christina-jørgensen.config will be "converted" to christina-j�rgensen.config when uSync unzips the zip file.
This happens to all special characters ... :)