Created attachment 668949 [details]
Unzip can handle filenames in archive only with ascii encoding. All symbols with code > 127 it replaces with '?'. Upstream promised to fix this more than 2 years ago. But new upstream version did'n come. Seems upstream is dead.
I wrote a patch which add -I and -O command line options to setup ISO and OEM encodings. It options was agreed with upstream. Also a like patch uses other linux distributions to fix encodings problem in unzip package. This patch uses libnatspec library. So you need to add this to BR.
The patch was tested in RFRemix distribution. It works fine for two years.
So. Any news? Do you agree with this patch?
I am currently waiting for upstream response. If they incorporate your patch into the future Unzip release, I will include it into Fedora.
I afraid you won't get any responce. Upstream dead.
Steven Schweda seems to be active on sourceforge.
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '18'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 18's end of life.
Thank you for reporting this issue and we are sorry that we may not be
able to fix it before Fedora 18 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior to Fedora 18's end of life.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
So will be it applyed?
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle.
Changing version to '23'.
(As we did not run this process for some time, it could affect also pre-Fedora 23 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.)
More information and reason for this action is here:
It is fixed in rawhide already. Used upstream solution of this.
Please provide link to upstream solution.
Link to fixed upstream solution:
I apologize that I don't want to search it in upstream's forum now. If used patch doesn't solve this problem, feel free to reopen it again.
If you want to try this solution in older Fedora, you can try test this package from copr:
Also you can use:
# dnf copr enable pstodulk/unzip
It's originally for testing of support of segmented archives but contains all from rawhide, so you can try it.