• 0

SSH: Unzip and keep files in UTF-8


Question

I have a 1.6GB file that I transferred from HostGator to MediaTemple through wget since it was too large for FTP's speed.

 

Does anyone know the command that will unzip this file and make sure all the files keep their original characters in the file name? I would have thought it was "-U", I'm not sure. 

Link to comment
https://www.neowin.net/forum/topic/1193965-ssh-unzip-and-keep-files-in-utf-8/
Share on other sites

6 answers to this question

Recommended Posts

  • 0

I'm assuming zip is your format based off of what you said:

 

  Quote
-U (obsolete; to be removed in a future release) leave filenames uppercase if created under MS-DOS, VMS, etc. See -L above.

-L convert to lowercase any filename originating on an uppercase-only operating system or file system. (This was unzip's default behavior in releases prior to 5.11; the new default behavior is identical to the old behavior with the -U option, which is now obsolete and will be removed in a future release.) Depending on the archiver, files archived under single-case file systems (VMS, old MS-DOS FAT, etc.) may be stored as all-uppercase names; this can be ugly or inconvenient when extracting to a case-preserving file system such as OS/2 HPFS or a case-sensitive one such as under Unix. By default unzip lists and extracts such filenames exactly as they're stored (excepting truncation, conversion of unsupported characters, etc.); this option causes the names of all files from certain systems to be converted to lowercase. The -LL option forces conversion of every filename to lowercase, regardless of the originating file system.

 

   

EDIT: ugh, this wasn't suppose to be a double post, but I accidentally clicked quote and not edit and made it a separate post :-(

  • 0

I've tried before on another server and it doing a plain unzip on a zip file caused some files to have foreign characters, so I'm guessing -U works, I'm still not sure though. The problem isn't the letters, but the special characters, I wasn't sure if it was because of the Terminal encoding.

  • 0
  On 23/12/2013 at 19:17, Mr.XXIV said:

I've tried before on another server and it doing a plain unzip on a zip file caused some files to have foreign characters, so I'm guessing -U works, I'm still not sure though. The problem isn't the letters, but the special characters, I wasn't sure if it was because of the Terminal encoding.

 

-U is for leaving filenames as upper case if they were created on filesystems that only had uppercase characters. It won't have an affect for special characters. Also, the terminal encoding isn't going to change how the filenames of the archive are created or or extracted. A filename only dependent on the filesystem the file was created on.

 

When you unzip, by default unzip is going to make an attempt to keep the characters as they were on the original filesystem. If characters aren't supported it will do a conversation though. Your best bet is to make sure to not have filenames that aren't compatible between your src and dest filesystems.

  • 0
  On 23/12/2013 at 19:31, snaphat (Myles Landwehr) said:

-U is for leaving filenames as upper case if they were created on filesystems that only had uppercase characters. It won't have an affect for special characters. Also, the terminal encoding isn't going to change how the filenames of the archive are created or or extracted. A filename only dependent on the filesystem the file was created on.

 

When you unzip, by default unzip is going to make an attempt to keep the characters as they were on the original filesystem. If characters aren't supported it will do a conversation though. Your best bet is to make sure to not have filenames that aren't compatible between your src and dest filesystems.

 

It's from CentOS to Ubuntu and the zip is entirely based on WordPress and usually the characters are affected in the uploads folder, so I'm not sure what to guarantee. But the site looks fine right now.

  • 0
  On 23/12/2013 at 19:47, Mr.XXIV said:

It's from CentOS to Ubuntu and the zip is entirely based on WordPress and usually the characters are affected in the uploads folder, so I'm not sure what to guarantee. But the site looks fine right now.

 

I'd imagine both CentOS and Ubuntu would be using variants of ext for a filesystem so I wouldn't think there'd be compatibility issues.

 

Hmm, this sounds like it might just simply be a display only issue then between the systems (the filenames are the same between systems, but the display isn't in terminal). Check that the locales are the same. It'd be in the rc.conf file under LOCALE="...". That could change up the display of utf8 characters.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.