Hi:
I have been looking for a new icon set for my USB and decided to download some .png(s) for Linux. Problem is I'm a Windows user and when extracting the folder almost half of the .png(s)/.svg(s)had 0 B as the file size and were empty. Every Gnome icon set I downloaded looked that way and I am sure it's not the extraction process as I tried it with 7-zip and Pea Zip and got the same results. How do I interact with the Linux folder to access all of the files.
- dark yux
PS: I'm doing all of this on a public computer so please make this as minimally invasive as possible.
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
It is likely that those are images that haven't been designed yet.
cowsay Moo
cowthink 'Dude, why are you staring at me.'
I second that. Or, they may be symbolic links.
I found that linux things like pictures and documents end up MUCH smaller than in windows. Windows seems to add a #*&$^ load of junk to files even a basic TXT file. i had a 900 byte txt file in linux and as soon as i edited it in windows (only added a leter) it jumped to 200kbytes. i dont know a solution to your problem.
Doesn't sound real. Unless by "edition" you mean adding 199 KB.
Files don't grow by themselves. And Windows doesn't add anything either.
"Those people who think they know everything are a great annoyance to those of us who do." Asimov
Linux folders and files should work out of the box on any PC if the partition is recognized. So as you are downloading, and you are getting stuff with 0bytes, or you have a virus, or it is blocking downloads from there. Use a web proxy to rule out the second and scan with clam win portable to rule out the first.
Blue is everything.
Try this: http://www.chrysocome.net/explore2fs
Explore2fs
Explore2fs is a GUI explorer tool for accessing ext2 and ext3 filesystems. It runs under all versions of Windows and can read almost any ext2 and ext3 filesystem.
Supported versions of Windows:
Windows 95
Windows 98
Windows 98SE
Windows ME
Windows NT 4.0
Windows 2000
Windows XP
Windows XP SP2
Windows Server 2003
Features:
Reads ext2
Reads ext3
Drag & Drop
1.44Meg Floppy Disk Support
LS120 Floppy Disk Support
ZIP & Jazz Disk Support
USB & CF Disk Support
CDROM Support
Supports Windows 98 extended partition scheme
Export files as binary
Export files as text
Export directory
View/Execute file
Large disk support
Large file support
LVM2
ReiserFS Detection
Unicode UTF8 support
Preserve time stamps on export
He said that the icon themes he is downloading have most of the icons with 0 bytes size, and he is doing that on a Windows machine, and dowloading stuff to the Windows Machine, so he is not accessing any ext2/3 filesystem, he isn't accessing another partition. So that is useless to him. He is having difficulties with seeing some icons.
But I now think Patric is right. Linux symlinks (fancy shortcuts that work on the filesystem) do not work on Windows. To reduce size, more than half of the Linux icons are made symilnks to other icons as there is no need to repeat them. So don't worry. folder.png and gtk-folder.png don't need to be different, so one is just a symlink of another. If you find an icon with 0bytes size just ignore him. On Linux you would see that it actually is a symlink, but Windows isn't as smart as it should.
Good luck!
Blue is everything.
NTFS has symlinks too, they just work differently than on ext2/3.
I never said NTFS had no symlinks, I only said symlinks made on Linux don't work on Windows.
(Also, I know Bruce is talking of the filesystem symlinks, that are some sort of shortcuts; but, other people: don't confuse symlinks with shortcuts. Shortcuts are files that say to open another file. Symlinks are redirections to files on other places, it is the best I can explain.)
Blue is everything.
I only brought it up because of the way you said it, "Windows isn't as smart as it should [be].", which suggests it can't handle Linux' symlinks because it has no concept of a symlink--which obviously isn't true. You can't expect NTFS to understand another filesystem's symlinks, since such a thing is handled at the filesystem level.
True, what you said is true.
But,
, Windows only has relative symlynks since the NTFS version that came up with Vista, before that, all NTFS symlinks were static (look it up on Wikipedia). And Windows versions that used FAT couldn't make symlinks because it doesn't has support for any 
. Linux has relative symlinks since I remember 
Blue is everything.
...this and see what I'm talking about.
http://www.silvestre.com.ar/?p=115
self.path = path if self.path == None else self.path
...but let me guess, some of the images you can't see are, for example:
But you can see:
You know why? If you had a Linux OS with an ext3 filesystem, the first ones would be symlinks, aka system shortcuts to the first ones. The biggest difference between the symlinks and the most common Windows shortcuts is that symlinks are dependent on the OS and file system, while Windows shortcuts are files that say "go to there".
So, the first files are just linking to the second ones, and will look corrupt on Windows, but they are actually useless to you. Just ignore them and delete those. They are used in icon themes to avoid repeating images uselessly while being able to provide icons to all different desktop environments.
Hope to have helped (if I am wrong I will provide more feedback when I understand what is making me unable to boot my Windows VM).
Blue is everything.
Thanks.
Edit: You might be right.
self.path = path if self.path == None else self.path