I had the same issue and just solved it through others's help. Opening it directly with gedit
,
LibreOffice
or other editors and trying to save it in another encoding didn't help. The reason is they are usually encoded in Windows-1253 set, while many Linux programs automatically detect this codeset as "Western".
One easy way to go about it, is to tell every program you use that it's not a "Western" codeset. For Gedit, you can do that by opening gedit alone, go to "Open file"
, chose your file and at the bottom of the window the correct "Character Encoding"
, which should write "Automatically detected" at this point and must be changed to a Greek codeset for getting a readable text. Gedit then opens the file in the correct codeset.
For VLC, since we are discussing about subtitles, the only thing to do is change the default subtitle encoding to "Windows-1253", you can find it in "Preferences"/"Subtitles"
. Greek letters appear normally then, even if you can't read the .srt properly in another editor.
The other, and safest, way to open readable greek characters in txt files that were written in windows machines is to first convert them to UTF-8, which will give you a permanent solution for the specific file. The way to do that is through console with iconv
tool :
iconv -f Windows-1253 -t UTF-8 input.txt > output.txt
Obviously, you either execute it from the folder the .txt file is located, or from anywhere else, but giving the whole path for input.txt and output.txt in that case. In rare cases, the original file encoding could be ISO-8859-7, which is another greek encoding, if Windows-1253 doesn't work you could try that too, replacing it as "from" encoding, i.e.
iconv -f ISO-8859-7 -t UTF-8 input.txt > output.txt
The first issue on installing unzip
is because of insufficient permissions. Chances are that you might have tried to install unzip
with
apt-get install unzip
. This is not enough.
You need to install unzip
by:
sudo apt-get install unzip
Chances are that unzip
already exists in your system.
It would be the most common scenario. You can verify the install by the command
which unzip
For your second issue, you are seeing a .zip.part
extension because the the zip
file was not completely downloaded. You can either try to download it again from the same source or choose a different source.
Best Answer
You're missing a parameter (notice the f):
if
-f <filename>
is not specified, tar will default to expanding whatever it receives in standard input. So the "hang" you're seeing is just tar waiting for data.If you feel inclined to play a bit, try redirecting your tar.bz2 file into tar's standard input:
this should also work, but it's more traditional to specify the file with -f.
Note that -f has to be at the very end because the filename is an argument to the -f option. If you do
tar -vfjv filename
it won't work, as the filename would be passed as an argument for -v, which makes no sense.