Please describe the problem:
When creating a zip archive, symbolic links aren't being followed, but are added as links instead (zip -y == store symbolic links as the link instead of the referenced file). I don't think that's how it should be as a symlink in an archive is practically useless. I suggest that file-roller doesn't use -y option when creating a zip archive.

Steps to reproduce:
1. Create a directory with a few symlinks in it
2. Create a zip from it using File-Roller
3. Unpack it in Windows or another machine where targets for the created symlinks don't exist


Actual results:
Symlinks are unpacked, but they don't work where there are no files they reference.

Expected results:
IMO, archives created with File-Roller should be as portable as possible, meaning, that the symlinks should be resolved before adding them to the archive.

Does this happen every time?


Other information:
I think the policy regarding symlinks should be same no matter what type of archive is chosen to create (I'm currently not sure how File-Roller treats symlinks when creating a tar.gz, for example). However, maybe it's also worth to add an option to switch that?