docs: Added README."en".md translation via https://github.com/dephrai…

…im/translate-readme

README.en.md

@@ -4,7 +4,7 @@
 -   [English](README.en.md)
 
 Picture resources and so on come from the Internet.
-This code warehouse is for learning only, if it is used by others for commercial purposes, it has nothing to do with me! Please obey the license!
+This code warehouse is only for learning, if it is used by others for commercial purposes, it has nothing to do with me! Please obey the license!
 
 ## Qt-App
 
@@ -43,8 +43,9 @@ Crash Reporter;
 ## Questions and Notes
 
 1.  MacOS, the bundle generated by cmake is not generated under the .app/Contents/ folder`PkgInfo`document;
-    1.  [app/CMakeLists](/apps/app/CMakeLists.txt), using this CMakeLists.txt can generate bundles on MacOS, and can also display icons normally, but there is no PkgInfo file;
+    1.  [app/CMakeLists](/apps/app/CMakeLists.txt), using this CMakeLists.txt can generate a bundle on MacOS, and can also display icons normally, but there is no PkgInfo file;
     2.  How should cmake generate PkgInfo files?
+        1.  WireShark uses`set_source_files_properties(${CMAKE_CURRENT_SOURCE_DIR}/PkgInfo PROPERTIES MACOSX_PACKAGE_LOCATION .)`In a similar way, copy it to the bundle;
     3.  qmake will generate PkgInfo file by default, only need to specify`TARGET=app`or`CONFIG+=bundle`can;
 2.  Under the Unix system, it is necessary to use the static library as much as possible to avoid the dependency problem of the dynamic library;
     1.  Several modules in this project are dynamic libraries, because they are plugins, they need to be loaded dynamically;