What text encoding is used in “Zip archive data, at least v?[0x314] to extract”?





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







2















I tried multiple search terms on the usual suspect search engines as well as on stack overflow and superuser, but can't find anything on this. Normally a Zip archive magic pattern is "at least v1.0" or "at least v2.0".



The closest I can come is "COMBINING REVERSED COMMA ABOVE" or "Greek dasia, rough breathing mark" which appears to me as a curly single open quote, but it makes no sense in the context, so I doubt it's right.



No issues with the zip archive, just a curiosity.



If it helps the string was generated by file v5.33 on macOS 10.14 with bash 4.4.5.



Thanks.










share|improve this question































    2















    I tried multiple search terms on the usual suspect search engines as well as on stack overflow and superuser, but can't find anything on this. Normally a Zip archive magic pattern is "at least v1.0" or "at least v2.0".



    The closest I can come is "COMBINING REVERSED COMMA ABOVE" or "Greek dasia, rough breathing mark" which appears to me as a curly single open quote, but it makes no sense in the context, so I doubt it's right.



    No issues with the zip archive, just a curiosity.



    If it helps the string was generated by file v5.33 on macOS 10.14 with bash 4.4.5.



    Thanks.










    share|improve this question



























      2












      2








      2








      I tried multiple search terms on the usual suspect search engines as well as on stack overflow and superuser, but can't find anything on this. Normally a Zip archive magic pattern is "at least v1.0" or "at least v2.0".



      The closest I can come is "COMBINING REVERSED COMMA ABOVE" or "Greek dasia, rough breathing mark" which appears to me as a curly single open quote, but it makes no sense in the context, so I doubt it's right.



      No issues with the zip archive, just a curiosity.



      If it helps the string was generated by file v5.33 on macOS 10.14 with bash 4.4.5.



      Thanks.










      share|improve this question
















      I tried multiple search terms on the usual suspect search engines as well as on stack overflow and superuser, but can't find anything on this. Normally a Zip archive magic pattern is "at least v1.0" or "at least v2.0".



      The closest I can come is "COMBINING REVERSED COMMA ABOVE" or "Greek dasia, rough breathing mark" which appears to me as a curly single open quote, but it makes no sense in the context, so I doubt it's right.



      No issues with the zip archive, just a curiosity.



      If it helps the string was generated by file v5.33 on macOS 10.14 with bash 4.4.5.



      Thanks.







      bash zip encoding character-encoding






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Feb 10 at 12:37







      Mike M

















      asked Feb 10 at 12:23









      Mike MMike M

      133




      133






















          1 Answer
          1






          active

          oldest

          votes


















          2














          It simply means that the file command doesn't have definitions that understand what version zip file you have.



          The zip definition for file has a section



          # Zip known versions
          0 name zipversion
          >0 leshort 0x09 v0.9
          >0 leshort 0x0a v1.0
          >0 leshort 0x0b v1.1
          >0 leshort 0x14 v2.0
          >0 leshort 0x15 v2.1
          >0 leshort 0x19 v2.5
          >0 leshort 0x1b v2.7
          >0 leshort 0x2d v4.5
          >0 leshort 0x2e v4.6
          >0 leshort 0x32 v5.0
          >0 leshort 0x33 v5.1
          >0 leshort 0x34 v5.2
          >0 leshort 0x3d v6.1
          >0 leshort 0x3e v6.2
          >0 leshort 0x3f v6.3
          >0 default x
          >>0 leshort x v?[%#x]


          And it basically means that file fell out the end of that definition list and is just telling you the zip version number needed to extract it.



          It looks like that list may need updating. There have been a few changes since 6.3. It is possible that the magic bytes listed are for 6.3.5 but I don't know for sure.






          share|improve this answer
























          • Ah, I was looking at it entirely wrong. Thank you!

            – Mike M
            Feb 10 at 16:33












          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "3"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1404133%2fwhat-text-encoding-is-used-in-zip-archive-data-at-least-v0x314-to-extract%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          2














          It simply means that the file command doesn't have definitions that understand what version zip file you have.



          The zip definition for file has a section



          # Zip known versions
          0 name zipversion
          >0 leshort 0x09 v0.9
          >0 leshort 0x0a v1.0
          >0 leshort 0x0b v1.1
          >0 leshort 0x14 v2.0
          >0 leshort 0x15 v2.1
          >0 leshort 0x19 v2.5
          >0 leshort 0x1b v2.7
          >0 leshort 0x2d v4.5
          >0 leshort 0x2e v4.6
          >0 leshort 0x32 v5.0
          >0 leshort 0x33 v5.1
          >0 leshort 0x34 v5.2
          >0 leshort 0x3d v6.1
          >0 leshort 0x3e v6.2
          >0 leshort 0x3f v6.3
          >0 default x
          >>0 leshort x v?[%#x]


          And it basically means that file fell out the end of that definition list and is just telling you the zip version number needed to extract it.



          It looks like that list may need updating. There have been a few changes since 6.3. It is possible that the magic bytes listed are for 6.3.5 but I don't know for sure.






          share|improve this answer
























          • Ah, I was looking at it entirely wrong. Thank you!

            – Mike M
            Feb 10 at 16:33
















          2














          It simply means that the file command doesn't have definitions that understand what version zip file you have.



          The zip definition for file has a section



          # Zip known versions
          0 name zipversion
          >0 leshort 0x09 v0.9
          >0 leshort 0x0a v1.0
          >0 leshort 0x0b v1.1
          >0 leshort 0x14 v2.0
          >0 leshort 0x15 v2.1
          >0 leshort 0x19 v2.5
          >0 leshort 0x1b v2.7
          >0 leshort 0x2d v4.5
          >0 leshort 0x2e v4.6
          >0 leshort 0x32 v5.0
          >0 leshort 0x33 v5.1
          >0 leshort 0x34 v5.2
          >0 leshort 0x3d v6.1
          >0 leshort 0x3e v6.2
          >0 leshort 0x3f v6.3
          >0 default x
          >>0 leshort x v?[%#x]


          And it basically means that file fell out the end of that definition list and is just telling you the zip version number needed to extract it.



          It looks like that list may need updating. There have been a few changes since 6.3. It is possible that the magic bytes listed are for 6.3.5 but I don't know for sure.






          share|improve this answer
























          • Ah, I was looking at it entirely wrong. Thank you!

            – Mike M
            Feb 10 at 16:33














          2












          2








          2







          It simply means that the file command doesn't have definitions that understand what version zip file you have.



          The zip definition for file has a section



          # Zip known versions
          0 name zipversion
          >0 leshort 0x09 v0.9
          >0 leshort 0x0a v1.0
          >0 leshort 0x0b v1.1
          >0 leshort 0x14 v2.0
          >0 leshort 0x15 v2.1
          >0 leshort 0x19 v2.5
          >0 leshort 0x1b v2.7
          >0 leshort 0x2d v4.5
          >0 leshort 0x2e v4.6
          >0 leshort 0x32 v5.0
          >0 leshort 0x33 v5.1
          >0 leshort 0x34 v5.2
          >0 leshort 0x3d v6.1
          >0 leshort 0x3e v6.2
          >0 leshort 0x3f v6.3
          >0 default x
          >>0 leshort x v?[%#x]


          And it basically means that file fell out the end of that definition list and is just telling you the zip version number needed to extract it.



          It looks like that list may need updating. There have been a few changes since 6.3. It is possible that the magic bytes listed are for 6.3.5 but I don't know for sure.






          share|improve this answer













          It simply means that the file command doesn't have definitions that understand what version zip file you have.



          The zip definition for file has a section



          # Zip known versions
          0 name zipversion
          >0 leshort 0x09 v0.9
          >0 leshort 0x0a v1.0
          >0 leshort 0x0b v1.1
          >0 leshort 0x14 v2.0
          >0 leshort 0x15 v2.1
          >0 leshort 0x19 v2.5
          >0 leshort 0x1b v2.7
          >0 leshort 0x2d v4.5
          >0 leshort 0x2e v4.6
          >0 leshort 0x32 v5.0
          >0 leshort 0x33 v5.1
          >0 leshort 0x34 v5.2
          >0 leshort 0x3d v6.1
          >0 leshort 0x3e v6.2
          >0 leshort 0x3f v6.3
          >0 default x
          >>0 leshort x v?[%#x]


          And it basically means that file fell out the end of that definition list and is just telling you the zip version number needed to extract it.



          It looks like that list may need updating. There have been a few changes since 6.3. It is possible that the magic bytes listed are for 6.3.5 but I don't know for sure.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Feb 10 at 12:40









          MokubaiMokubai

          58.2k16139157




          58.2k16139157













          • Ah, I was looking at it entirely wrong. Thank you!

            – Mike M
            Feb 10 at 16:33



















          • Ah, I was looking at it entirely wrong. Thank you!

            – Mike M
            Feb 10 at 16:33

















          Ah, I was looking at it entirely wrong. Thank you!

          – Mike M
          Feb 10 at 16:33





          Ah, I was looking at it entirely wrong. Thank you!

          – Mike M
          Feb 10 at 16:33


















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Super User!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1404133%2fwhat-text-encoding-is-used-in-zip-archive-data-at-least-v0x314-to-extract%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Terni

          A new problem with tex4ht and tikz

          Sun Ra