Downloaded file, unzipped, loaded in modules. A difficult ftp, as the ftp would not read some of the files in the flag folder. I downloaded and unzipped the file again, but the same issue persisted.

Closer look at flag files revealed what looks like ASCI code in file names, apparently corrupting the files, making them unreadable to the ftp.

I transferred the files individually, but half of the flags still would not ftp to server, with the ftp reporting error that "files not found."

I then removed the corrupt characters from the flag's file names, apparently restoring the original file names, and they then transferred easily through the ftp, and all work properly, except one, which may be a different issue. Or not.

Thanks for your work on this fine module, and I hope this helps anyone else who has encountered this issue.

Comments

blinkingtwelve’s picture

blinkingtwelve commented
Title: Google Translate Links Flag Problem » Unicode characters and corrupt filenames
Category: task » support
Status: Active » Closed (works as designed)
Issue tags: +unicode, +corrupt characters

Those are not corrupt characters. Rather, your PC doesn't know how to handle them. The filenames are in unicode so that we can have Cyrillic characters eg in the popup descriptions.
You need unicode support all the way. If you unpack on a PC, you need it in your unpacking progam and your PC's filesystem. You need it in the FTP client. You need it in the FTP server. You need it in the server filesystem and in the encoding of your HTML output.
If you have a shell account on your webhost, you might try to download the .tar.gz to there and unpack the tarball from within your shell account.