Activity for Alex Alabuzhev
-
Alex Alabuzhev posted a comment on ticket #215
ID3v2 frame overview Possible encodings: $00 ISO-8859-1 [ISO-8859-1]. Terminated with $00. $01 UTF-16 [UTF-16] encoded Unicode [UNICODE] with BOM. All strings in the same frame SHALL have the same byteorder. Terminated with $00 00. $02 UTF-16BE [UTF-16] encoded Unicode [UNICODE] without BOM. Terminated with $00 00. $03 UTF-8 [UTF-8] encoded Unicode [UNICODE]. Terminated with $00. I.e. ID3v2 is always either some Unicode form or pure ASCII. Without the change the library converts the strings to the...
-
i am not sure if this change is always good idea Why?
-
Thanks
-
AudioPlayer: support Unicode in ID3v2 tags
-
Last access and creation timestamps can carry some private information about time of user actions Indeed, but so does the modification timestamp, probably even more often, and people actually concerned with digital footprints would supposedly thoroughly inspect the final result before handing it to anyone anyway. if you compress same files to zip archive several times, you will have different results with changed access timestamps Isn't that already covered by -ssp? Anyway, I'm not suggesting to...
-
Hi, I noticed a change in zip archives creation, not mentioned in History.txt: Previously the "tc" parameter was switching between the NTFS timestamps (modification, creation, access, 100ns precision) and the DOS timestamp (modification only, 2s precision) and by default all NTFS timestamps were stored. In v22 quite a few things changed: - "tc" only controls the creation time - additional parameters "tm" and "ta" have been added to control modification and access times correspondingly - "tc" and...
-
Thank you for your response. The archive could be created at another powerful computer That definitely makes sense. However, there are some drawbacks too - not every unpacker supports LZMA2 and change of the compression method might render the archive "broken" for them and cause troubles for the user. Please see this topic for an example https://forum.farmanager.com/viewtopic.php?f=4&t=11264
-
(I wonder why I can freely create a ticket here but adding a comment to it requires moderaton)
-
Removing a file from a solid archive changes its compression method
-
Hi Igor, In CPP\7zip\UI\Far\Far.cpp both OpenFilePlugin and OpenPlugin are implemented in terms of MyOpenFilePlugin function. This leads to a subtle error: if opening an archive is interrupted by the user, MyOpenFilePlugin returns -2, which is a perfectly valid return code for OpenFilePlugin to stop futher processing of that file, but not for OpenPlugin, which supports only one "magic" value (-1) and treats everything else as a valid panel handle. Far then passes this panel handle to GetOpenPanelInfo,...
1 >