From 05346bda87a980dea294812e94f07449f9011e46 Mon Sep 17 00:00:00 2001 From: bitcookies Date: Wed, 5 Jun 2024 11:10:49 +0800 Subject: [PATCH] =?UTF-8?q?=F0=9F=93=98=20Simpler=20Coding=20Instructions?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- README.md | 87 +- README.zh-CN.md | 90 +- assets/ascii-characters-dark.svg | 8 + assets/ascii-characters-light.svg | 7 + assets/windows-1252-characters-dark.svg | 1083 ++++++++++++++++++++++ assets/windows-1252-characters-light.svg | 1083 ++++++++++++++++++++++ 6 files changed, 2269 insertions(+), 89 deletions(-) create mode 100644 assets/ascii-characters-dark.svg create mode 100644 assets/ascii-characters-light.svg create mode 100644 assets/windows-1252-characters-dark.svg create mode 100644 assets/windows-1252-characters-light.svg diff --git a/README.md b/README.md index d1ba25cc..a77c5c29 100644 --- a/README.md +++ b/README.md @@ -39,27 +39,26 @@ See [here](README.HOW_DOES_IT_WORK.md). ## 3. How to use? -There are several ways to use it: +There are several ways to use it. -- [Use Github Actions](#6-Use-Github-Actions) -- [Use Github Actions with secrets](#7-Use-Github-Actions-with-secrets) -- [Build in Visual Studio](#8-Build-in-Visual-Studio) +- [Use Github Actions](#4-Use-Github-Actions) +- [Use Github Actions with secrets](#5-Use-Github-Actions-with-secrets) +- [Build in Visual Studio](#6-Build-in-Visual-Studio) -## 4. Encoding +### 3.1 Encoding -WinRAR Keygen supports `ASCII`, `ANSI` and `UTF-8` encoding types, the following is a brief description of the three encoding types. +WinRAR Keygen supports `ASCII`, `ANSI` and `UTF-8` encoding types, the corresponding supported characters are listed in the table below. -> [!WARNING] -> It is recommended that you do not generate licenses with non-ASCII characters in ANSI encoding for the time being, as there is a problem with garbled PowerShell console characters for Chinese, Japanese, and Korean on Windows Server 2022, [which is being fixed by Microsoft](https://learn.microsoft.com/en-us/troubleshoot/windows-server/system-management-components/powershell-console-characters-garbled-for-cjk-languages). -> +> [!NOTE] +> The default is `utf8`, but you can specify the encoding as `ascii` or `ansi`. -| Encoding | Instruction | Supported Characters | +| Encoding | Supported Characters | Character Examples | | -------------------------------------------- | ------------------------------------------------------------ | ------------------------------------------------------------ | -| [ASCII](https://en.wikipedia.org/wiki/ASCII) | Single byte encoding only using the bottom 7 bits. (Unicode code points 0-127.) No accents etc. | Only full ASCII characters are supported. | -| ANSI | There's no one fixed ANSI encoding - there are lots of them. Usually when people say "ANSI" they mean "the default locale/codepage for my system" which is obtained via [Encoding.Default](http://msdn.microsoft.com/en-us/library/system.text.encoding.default.aspx), and is often [Windows-1252](http://en.wikipedia.org/wiki/Windows-1252) but can be other locales. | Only full ASCII characters and the language of your operating system are supported. | -| [UTF-8](https://en.wikipedia.org/wiki/UTF-8) | Variable length encoding, 1-4 bytes per code point. ASCII values are encoded as ASCII using 1 byte. | Support full UTF8 encoded characters. | +| [ASCII](https://en.wikipedia.org/wiki/ASCII) | Only full ASCII characters are supported. | | +| ANSI | There is no one fixed ANSI code, usually [Windows-1252](https://en.wikipedia.org/wiki/Windows-1252), but other local codes are also possible. | | +| [UTF-8](https://en.wikipedia.org/wiki/UTF-8) | Support full UTF8 encoded characters. | ASCII characters, English, 简体中文, 繁體中文, Deutsch, Français, 日本語, 한국어, et al. | -## 5. License type +### 3.2 License type There are two types of WinRAR licenses, `rarreg.key` and `rarkey.rar`, which differ only in their import. @@ -76,16 +75,16 @@ C:\Users\yourname\AppData\Roaming\WinRAR\rarreg.key You can also compress `rarreg.key` into `rarkey.rar` and double-click it to run it, and the license import will take place automatically. -## 6. Use Github Actions +## 4. Use Github Actions
Click to expand The new workflow can easily help you generate a license, you just need to follow these steps. -> Your `Username` and `License Name` will appear in the actions log, if you don't want to give out this information, see [7. Using Github Actions with secrets](#7-Use-Github-Actions-with-secrets). +> Your `Username` and `License Name` will appear in the actions log, if you don't want to give out this information, see [5. Using Github Actions with secrets](#5-Use-Github-Actions-with-secrets). -### 6.1 Fork +### 4.1 Fork **Fork** this repo. @@ -93,7 +92,7 @@ The new workflow can easily help you generate a license, you just need to follow ![Fork](assets/fork-dark.png#gh-dark-mode-only) -### 6.2 Allow fork repo to run workflows +### 4.2 Allow fork repo to run workflows Go back to the repo you just forked and click **Actions** to allow Workflows to run in your forked repo. @@ -101,11 +100,11 @@ Go back to the repo you just forked and click **Actions** to allow Workflows to ![Workflow](assets/enable-workflows-dark.png#gh-dark-mode-only) -### 6.3 Run workflow +### 4.3 Run workflow After allowing the workflow, go to **Actions > WinRAR Keygen > Run workflow** and fill in the information to start generating. -> For the difference of license encoding, please refer to [4. Encoding](#4-Encoding). +> For the difference of license encoding, please refer to [3.1 Encoding](#31-Encoding). ![Secrets](assets/run-ketgen-light.png#gh-light-mode-only) @@ -121,18 +120,18 @@ After running successfully, open the corresponding task and select **rarreg_file Extract rarreg_file.zip to get `rarreg.key` and drag to import into WinRAR. You can also compress `rarreg.key` into `rarkey.rar`, then double-click it to run it, and the license import will be done automatically. -If you get an invalid key, please check [the specific solution](#9-invalid-key). +If you get an invalid key, please check [the specific solution](#7-invalid-key).
-## 7. Use Github Actions with secrets +## 5. Use Github Actions with secrets
Click to expand Using [secrets](https://docs.github.com/en/actions/security-guides/encrypted-secrets) can help you hide license information. -### 7.1 Fork +### 5.1 Fork **Fork** this repo. @@ -140,7 +139,7 @@ Using [secrets](https://docs.github.com/en/actions/security-guides/encrypted-sec ![Fork](assets/fork-dark.png#gh-dark-mode-only) -### 7.2 Allow fork repo to run Workflows +### 5.2 Allow fork repo to run workflows Go back to the repo you just forked and click **Actions** to allow Workflows to run in your forked repo. @@ -148,7 +147,7 @@ Go back to the repo you just forked and click **Actions** to allow Workflows to ![Workflow](assets/enable-workflows-dark.png#gh-dark-mode-only) -### 7.3 Create secrets +### 5.3 Create secrets After allowing the workflow, go to **Settings > Secrets and variables > Actions > New repository secret** to create a secret. @@ -156,7 +155,7 @@ After allowing the workflow, go to **Settings > Secrets and variables > Actions ![Secrets](assets/secrets-dark.png#gh-dark-mode-only) -Create three Secrets with the names `TEXT1`, `TEXT2` and `PWD` and fill in the relevant values. +Create three secrets with the names `TEXT1`, `TEXT2` and `PWD` and fill in the relevant values. > The value filled in should be consistent with the type of code you have chosen. @@ -176,11 +175,11 @@ Once created, you will see it. ![Secrets Repo](assets/secrets-repo-dark.png#gh-dark-mode-only) -### 7.4 Run workflow +### 5.4 Run workflow Go to **Actions** and select **WinRAR Keygen with secrets** to run workflow manually. -For the difference of license encoding, please refer to [4. Encoding](#4-Encoding). +For the difference of license encoding, please refer to [3.1 Encoding](#31-Encoding). ![Run](assets/run-workflow-light.png#gh-light-mode-only) @@ -194,13 +193,13 @@ After running successfully, open the corresponding task and select **rarreg_file ![Download](assets/file-download-dark.png#gh-dark-mode-only) -Extract rarreg_file.zip to get `rarreg.7z`, unzip it with the password to get `rarreg.key`, then drag and drop to import into WinRAR. You can also compress `rarreg.key` into `rarkey.rar`, then double-click it to run it, and the license import will be done automatically. +Extract `rarreg_file.zip` to get `rarreg.7z`, unzip it with the password to get `rarreg.key`, then drag and drop to import into WinRAR. You can also compress `rarreg.key` into `rarkey.rar`, then double-click it to run it, and the license import will be done automatically. -If you get an invalid key, please check [the specific solution](#9-invalid-key). +If you get an invalid key, please check [the specific solution](#7-invalid-key).
-## 8. Build in Visual Studio +## 6. Build in Visual Studio
Click to expand @@ -209,7 +208,7 @@ I recommend using the Github Actions, but you can still do your own compilation. If you don't want to compile it yourself, you can also go to the [release](https://github.com/bitcookies/winrar-keygen/releases/) page to get `winrar-keygen.exe`. -### 8.1 Prerequisites +### 6.1 Prerequisites 1. Please make sure that you have **Visual Studio 2022**. Because this is a VS2022 project. If you are still using Visual Studio 2019, you can find projects for VS2019 in the [vs2019](https://github.com/bitcookies/winrar-keygen/tree/vs2019) branch, but this branch will no longer be maintained. @@ -234,7 +233,7 @@ If you don't want to compile it yourself, you can also go to the [release](https ``` -### 8.2 Build +### 6.2 Build 1. Open this project in __Visual Studio__. @@ -244,7 +243,7 @@ If you don't want to compile it yourself, you can also go to the [release](https You will see executable files in `bin/` directory. -### 8.3 How to use? +### 6.3 How to use? Execute the following code in the terminal and configure two parameters to generate `rarreg.key`. @@ -282,7 +281,7 @@ dd4ab952600ba16a99236d910bfa995d5f60651ec451f462511507 Save the generated information in **ANSI encoding** as `rarreg.key`. -### 8.4 Multi-language support +### 6.4 Multi-language support Execute the following code in the terminal and configure two paramet @@ -304,7 +303,7 @@ winrar-keygen.exe "日本語" "license" | Out-File -Encoding ansi rarreg.key winrar-keygen.exe "한국어" "license" | Out-File -Encoding ansi rarreg.key ``` -When generating utf-8 licenses, you may need to check Use ***[Beta:Use Unicode UTF-8 for global language support](https://stackoverflow.com/a/57134096/10242225)*** in **Control Panel > Clock and Regions > Regions > Administration > Change System Region Settings** in order to process the data correctly. However, it is not recommended that you do this, which may cause many software to not work properly, and it is recommended to [Use Github Actions](#6-Use-Github-Actions). +When generating utf-8 licenses, you may need to check Use ***[Beta:Use Unicode UTF-8 for global language support](https://stackoverflow.com/a/57134096/10242225)*** in **Control Panel > Clock and Regions > Regions > Administration > Change System Region Settings** in order to process the data correctly. However, it is not recommended that you do this, which may cause many software to not work properly, and it is recommended to [use Github Actions](#4-Use-Github-Actions). Generate multi-language licenses with UTF-8 encoding. @@ -326,13 +325,13 @@ winrar-keygen.exe "utf8:한국어" "license" | Out-File -Encoding utf8 rarreg.ke
-## 9. Invalid key +## 7. Invalid key Why is my `rarreg.key` invalid? -### 9.1 Character encoding +### 7.1 Character encoding -`TEXT1` and `TEXT2` are required to fulfill [corresponding coding requirements](#4 - coding description). +`TEXT1` and `TEXT2` are required to fulfill [corresponding coding requirements](#31-Encoding). ```console winrar-keygen.exe @@ -340,7 +339,7 @@ winrar-keygen.exe You can refer to: [Generation of "rarreg.key"](https://github.com/bitcookies/winrar-keygen/blob/master/README.HOW_DOES_IT_WORK.md#7-generation-of-rarregkey) -### 9.2 Text encoding +### 7.2 Text encoding If you use the following command: @@ -360,20 +359,20 @@ winrar-keygen.exe "Github" "Github.com" | Out-File -Encoding ansi rarreg.key winrar-keygen.exe "utf8:Github" "Github.com" | Out-File -Encoding utf8 rarreg.key ``` -## 10. Contributing +## 8. Contributing -### 10.1 Suggestion +### 8.1 Suggestion If you encounter some problems, you can report on the [Issues](https://github.com/bitcookies/winrar-keygen/issues) page. There will be many enthusiastic developers or Github users to help you. This project welcomes contributions and suggestions. You can make suggestions in [Issues](https://github.com/bitcookies/winrar-keygen/issues), or submit a pull request 😄 -### 10.2 Thanks +### 8.2 Thanks Thank you very much to some enthusiastic developers for helping answer some questions in [Issues](https://github.com/bitcookies/winrar-keygen/issues). 🏆 Special Thanks [@Sonic-The-Hedgehog-LNK1123](https://github.com/Sonic-The-Hedgehog-LNK1123) -## 11. License +## 9. License The code is available under the [MIT license](https://github.com/bitcookies/winrar-keygen/blob/master/LICENSE) diff --git a/README.zh-CN.md b/README.zh-CN.md index a25a2947..f4b919b0 100644 --- a/README.zh-CN.md +++ b/README.zh-CN.md @@ -41,24 +41,24 @@ WinRAR 不是免费软件。如果你想使用它，你应当向 [__RARLAB__](ht 有多种方法可供选择： -+ [使用 Github Actions](#6-使用-Github-Actions) -+ [使用 Github Actions with secrets](#7-使用-Github-Actions-with-secrets) -+ [通过 Visual Studio 编译使用](#8-通过-Visual-Studio-编译使用) ++ [使用 Github Actions](#4-使用-Github-Actions) ++ [使用 Github Actions with secrets](#5-使用-Github-Actions-with-secrets) ++ [通过 Visual Studio 编译使用](#6-通过-Visual-Studio-编译使用) -## 4. 编码说明 +### 3.1 编码说明 -WinRAR Keygen 支持 `ASCII`、`ANSI` 和 `UTF-8` 三种编码类型，以下是三种编码的简单说明： +WinRAR Keygen 支持 `ASCII`、`ANSI` 和 `UTF-8` 三种编码类型，对应支持的字符如下表： -> [!WARNING] -> 建议暂时不要用 ANSI 编码方式生成非 ASCII 字符的 license，因为在 Windows Server 2022 上中文、日语和韩语的 PowerShell 控制台字符会出现乱码问题，[该问题微软正在修复](https://learn.microsoft.com/en-us/troubleshoot/windows-server/system-management-components/powershell-console-characters-garbled-for-cjk-languages)。 +> [!NOTE] +> 默认使用 `utf8`，但是你也可以指定编码为 `ascii` 或 `ansi`。 -| 编码 | 说明 | 支持的字符 | -| -------------------------------------------- | ------------------------------------------------------------ | ----------------------------------------------------- | -| [ASCII](https://en.wikipedia.org/wiki/ASCII) | 单字节编码，只使用最下面的 7 位，没有重音符号等 | 仅支持 ASCII 字符 | -| ANSI | 没有一种固定的 ANSI 编码。通常说的 ANSI 是指 “系统默认的本地/代码页”，它通过 [Encoding.Default](http://msdn.microsoft.com/en-us/library/system.text.encoding.default.aspx) 获得，通常是 [Windows-1252](http://en.wikipedia.org/wiki/Windows-1252)，但也可以是其他本地 | 仅支持 ASCII 字符和您操作系统所设国家或地区的语言编码 | -| [UTF8](https://en.wikipedia.org/wiki/UTF-8) | 可变长度编码，每个码位 1-4 个字节（ASCII 值用 1 个字节编码为 ASCII） | 支持 UTF-8 编码字符 | +| 编码 | 支持的字符 | 字符示例 | +| -------------------------------------------- | ------------------------------------------------------------ | ------------------------------------------------------------ | +| [ASCII](https://en.wikipedia.org/wiki/ASCII) | 仅支持 ASCII 编码字符 | | +| ANSI | 没有一种固定的 ANSI 编码，通常是 [Windows-1252](http://en.wikipedia.org/wiki/Windows-1252)，但也可以是其他本地 | | +| [UTF8](https://en.wikipedia.org/wiki/UTF-8) | 支持 UTF-8 编码字符 | ASCII characters, English, 简体中文, 繁體中文, Deutsch, Français, 日本語, 한국어, et al. | -## 5. License 类型 +### 3.2 License 类型 WinRAR license 有 `rarreg.key` 和 `rarkey.rar` 两种类型，它们仅在导入上有区别： @@ -67,7 +67,7 @@ WinRAR license 有 `rarreg.key` 和 `rarkey.rar` 两种类型，它们仅在导 | | | | 拖动导入或放于指定位置 | 双击运行自动导入 | -如果你无法执行拖动操作，你可以尝试把 `rarreg.key` 放置与以下目录中： +如果你无法执行拖动操作，你可以尝试把 `rarreg.key` 放置于以下目录中： ```shell C:\Users\yourname\AppData\Roaming\WinRAR\rarreg.key @@ -75,16 +75,16 @@ C:\Users\yourname\AppData\Roaming\WinRAR\rarreg.key 你也可以将 `rarreg.key` 压缩成 `rarkey.rar` 然后双击运行，授权导入将会自动进行。 -## 6. 使用 Github Actions +## 4. 使用 Github Actions
点击展开 新的 workflow 能很方便的帮助你生成 license，你只需跟随以下步骤即可： -> 你的 `Username` 和 `License Name` 会出现在 actions 日志中，如果你不想泄露这些信息，请参考 [7. 使用 Github Actions with secrets](#7-使用-Github-Actions-with-secrets)。 +> 你的 `Username` 和 `License Name` 会出现在 actions 的日志中，如果你不想泄露这些信息，请参考 [5. 使用 Github Actions with secrets](#5-使用-Github-Actions-with-secrets)。 -### 6.1 Fork +### 4.1 Fork 点击该项目右上角的 **Fork** 按钮，fork 一份代码到你的 Github： @@ -92,7 +92,7 @@ C:\Users\yourname\AppData\Roaming\WinRAR\rarreg.key ![Fork](assets/fork-dark.png#gh-dark-mode-only) -### 6.2 允许 Fork 仓库运行 Workflows +### 4.2 允许 fork 仓库运行 workflows 返回到你刚刚 fork 完成的 repo，然后点击 **Actions** 去允许 workflows 在你的 fork repo 中运行： @@ -100,11 +100,11 @@ C:\Users\yourname\AppData\Roaming\WinRAR\rarreg.key ![Workflow](assets/enable-workflows-dark.png#gh-dark-mode-only) -### 6.3 运行 workflow +### 4.3 运行 workflow 允许 workflow 后，选择 **WinRAR Keygen > Run workflow** 并填入信息就可以开始生成了： -> License 编码的区别请参考 [4. 编码说明](#4-编码说明)。 +> License 编码的区别请参考 [3.1 编码说明](#31-编码说明)。 ![Secrets](assets/run-ketgen-light.png#gh-light-mode-only) @@ -120,18 +120,18 @@ C:\Users\yourname\AppData\Roaming\WinRAR\rarreg.key 将 `rarreg_file.zip` 解压缩后会得到 `rarreg.key`，然后拖动导入 WinRAR 即可。你也可以将 `rarreg.key` 压缩成 `rarkey.rar`，然后双击运行，授权导入将会自动进行。 -如果你得到的是 key 是无效的，请查看 [解决方法](#9-无效的-Key)。 +如果你得到的是 key 是无效的，请查看[解决方法](#7-无效的-Key)。
-## 7. 使用 Github Actions with secrets +## 5. 使用 Github Actions with secrets
点击展开 使用 [secrets](https://docs.github.com/en/actions/security-guides/encrypted-secrets) 可以帮助你隐藏 license 信息。 -### 7.1 Fork +### 5.1 Fork 点击该项目右上角的 **Fork** 按钮，fork 一份代码到你的 Github： @@ -139,7 +139,7 @@ C:\Users\yourname\AppData\Roaming\WinRAR\rarreg.key ![Fork](assets/fork-dark.png#gh-dark-mode-only) -### 7.2 允许 Fork 仓库运行 Workflows +### 5.2 允许 fork 仓库运行 workflows 返回到你刚刚 fork 完成的 repo，然后点击 **Actions** 去允许 workflows 在你的 fork repo 中运行： @@ -147,15 +147,15 @@ C:\Users\yourname\AppData\Roaming\WinRAR\rarreg.key ![Workflow](assets/enable-workflows-dark.png#gh-dark-mode-only) -### 7.3 创建 Secrets +### 5.3 创建 secrets -允许 workflows 后，进入 **Settings > Secrets and variables > Actions > New repository secret** 来创建 Secrets： +允许 workflows 后，进入 **Settings > Secrets and variables > Actions > New repository secret** 来创建 secrets： ![Secrets](assets/secrets-light.png#gh-light-mode-only) ![Secrets](assets/secrets-dark.png#gh-dark-mode-only) -创建三个 Secrets，名称为 `TEXT1` 、 `TEXT2` 和 `PWD`，并填入相关值： +创建三个 secrets，名称为 `TEXT1` 、 `TEXT2` 和 `PWD`，并填入相关值： > 填入的值应与你选择的编码类型保持一致。 @@ -175,11 +175,11 @@ C:\Users\yourname\AppData\Roaming\WinRAR\rarreg.key ![Secrets Repo](assets/secrets-repo-dark.png#gh-dark-mode-only) -### 7.4 运行 workflow +### 5.4 运行 workflow 进入 **Actions** 选择 **WinRAR Keygen with secrets > Run workflow** 并填入信息： -> License 编码的区别请参考 [4. 编码说明](#4-编码说明)。 +> License 编码的区别请参考 [3.1 编码说明](#31-编码说明)。 ![Run](assets/run-workflow-light.png#gh-light-mode-only) @@ -195,11 +195,11 @@ C:\Users\yourname\AppData\Roaming\WinRAR\rarreg.key 将 `rarreg_file.zip` 解压缩后会得到 `rarreg.7z`，使用你设置的密码进行解压缩获得 `rarreg.key`，然后拖动导入 WinRAR 即可。你也可以将 `rarreg.key` 压缩成 `rarkey.rar`，然后双击运行，授权导入将会自动进行。 -如果你得到的是 key 是无效的，请查看 [解决方法](#9-无效的-Key)。 +如果你得到的是 key 是无效的，请查看[解决方法](#7-无效的-Key)。
-## 8. 通过 Visual Studio 编译使用 +## 6. 通过 Visual Studio 编译使用
点击展开 @@ -208,7 +208,7 @@ C:\Users\yourname\AppData\Roaming\WinRAR\rarreg.key 如果你不想自行编译，也可以到 [Release](https://github.com/bitcookies/winrar-keygen/releases/) 页面获取对应版本的 `winrar-keygen.exe`。 -### 8.1 前提条件 +### 6.1 前提条件 1. 请确保你有 **Visual Studio 2022**，因为这是一个 VS2022 项目。如果你仍在使用 Visual Studio 2019，可以在 [vs2019](https://github.com/bitcookies/winrar-keygen/tree/vs2019) 分支中找到适合 VS2019 的项目，但是此分支将不再维护。 @@ -231,7 +231,7 @@ C:\Users\yourname\AppData\Roaming\WinRAR\rarreg.key $ vcpkg integrate install ``` -### 8.2 编译 +### 6.2 编译 1. 在 __Visual Studio__ 中打开这个项目； 2. 选择 `Release` 配置； @@ -239,7 +239,7 @@ C:\Users\yourname\AppData\Roaming\WinRAR\rarreg.key 你将在 `bin/` 目录下看到生成的文件。 -### 8.3 如何使用？ +### 6.3 如何使用？ 直接在终端执行以下代码，配置两个参数即可生成 `rarreg.key`。 @@ -277,7 +277,7 @@ dd4ab952600ba16a99236d910bfa995d5f60651ec451f462511507 将生成的信息以 **ANSI 编码** 的文本格式保存为 `rarreg.key`。 -### 8.4 多语言的支持 +### 6.4 多语言的支持 使用 ANSI 编码时，你只能使用你操作系统所在国家或地区的字符。ANSI 编码从 Powershell 7.4 以后开始支持，你还需要[升级你的 Powershell](https://learn.microsoft.com/en-us/powershell/scripting/install/installing-powershell-on-windows?view=powershell-7.4)。 @@ -297,7 +297,7 @@ winrar-keygen.exe "日本語" "license" | Out-File -Encoding ansi rarreg.key winrar-keygen.exe "한국어" "license" | Out-File -Encoding ansi rarreg.key ``` -使用 UTF-8 编码生成多语言的 license 时，你可能需要在 “控制面板 > 时钟和区域 > 区域 > 管理 > 更改系统区域设置 ” 中勾选使用 “[Beta版:使用Unicode UTF-8提供全球语言支持](https://stackoverflow.com/a/57134096/10242225)” 才能正确的处理数据。但是不建议你这么操作，这可能会导致很多软件无法正常运行，建议[使用 Github Actions](#6-使用-Github-Actions)。 +使用 UTF-8 编码生成多语言的 license 时，你可能需要在 “控制面板 > 时钟和区域 > 区域 > 管理 > 更改系统区域设置” 中勾选使用 “[Beta版:使用Unicode UTF-8提供全球语言支持](https://stackoverflow.com/a/57134096/10242225)” 才能正确的处理数据。但是不建议你这么操作，这可能会导致很多软件无法正常运行，建议[使用 Github Actions](#4-使用-Github-Actions)。 用 UTF-8 编码生成多语言的 license： @@ -319,13 +319,13 @@ winrar-keygen.exe "utf8:한국어" "license" | Out-File -Encoding utf8 rarreg.ke
-## 9. 无效的 Key +## 7. 无效的 Key 为什么我生成的 `rarreg.key` 是无效的？ -### 9.1 字符编码不正确 +### 7.1 字符编码不正确 -参数 `TEXT1` 和 `TEXT2` 需要满足[对应的编码要求](#4-编码说明)： +参数 `TEXT1` 和 `TEXT2` 需要满足[对应的编码要求](#31-编码说明)： ```console winrar-keygen.exe @@ -333,7 +333,7 @@ winrar-keygen.exe 具体可参考原理文档：[授权文件"rarreg.key"的生成](https://github.com/bitcookies/winrar-keygen/blob/master/README.HOW_DOES_IT_WORK.zh-CN.md#7-%E6%8E%88%E6%9D%83%E6%96%87%E4%BB%B6rarregkey%E7%9A%84%E7%94%9F%E6%88%90) -### 9.2 文本储存编码不正确 +### 7.2 文本储存编码不正确 如果你使用了如下命令： @@ -353,7 +353,7 @@ winrar-keygen.exe "Github" "Github.com" | Out-File -Encoding ansi rarreg.key winrar-keygen.exe "utf8:Github" "Github.com" | Out-File -Encoding utf8 rarreg.key ``` -### 9.3 关于简体中文版 +### 7.3 关于简体中文版 在 [__RARLAB__](https://www.rarlab.com/) 下载的简体中文版 WinRAR 将会自带广告组件，即使使用了 `rarreg.key` 授权，广告组件依旧会出现。这是由于简体中文代理商的一些意见，RARLAB 已将简体中文安装包的公开链接更换成了带有广告的简体中文安装包。 @@ -378,20 +378,20 @@ https://www.rarlab.com/rar/winrar-x64-611sc.exe 请注意区分上述连接地址，更多方法可以查看 [Issues #14](https://github.com/bitcookies/winrar-keygen/issues/14) 和 [Issues #19](https://github.com/bitcookies/winrar-keygen/issues/19)。 -## 10. 贡献 +## 8. 贡献 -### 10.1 反馈和建议 +### 8.1 反馈和建议 如果您遇到了一些问题，可在 [Issues](https://github.com/bitcookies/winrar-keygen/issues) 页面反馈，会有很多热心的开发者及 Github 用户帮助你。 该项目欢迎贡献和建议，您可以在 [Issues](https://github.com/bitcookies/winrar-keygen/issues) 提出建议，或者进行提交拉取请求 😄 -### 10.2 感谢 +### 8.2 感谢 非常感谢一些热心的开发者，在 [Issues](https://github.com/bitcookies/winrar-keygen/issues) 帮助解答一些问题。 🏆 特别感谢 [@Sonic-The-Hedgehog-LNK1123](https://github.com/Sonic-The-Hedgehog-LNK1123) -## 11. 许可 +## 9. 许可 使用 [MIT License](https://github.com/bitcookies/winrar-keygen/blob/master/LICENSE) diff --git a/assets/ascii-characters-dark.svg b/assets/ascii-characters-dark.svg new file mode 100644 index 00000000..4ddc2f7e --- /dev/null +++ b/assets/ascii-characters-dark.svg @@ -0,0 +1,8 @@ + + + !"#$%&'()*+,-./012 + 3456789:;<=>?@ABCDE + FGHIJKLMNOPQRSTUVWX + YZ[\]^_`abcdefghijk + lmnopqrstuvwxyz{|}~ + diff --git a/assets/ascii-characters-light.svg b/assets/ascii-characters-light.svg new file mode 100644 index 00000000..6da2afd9 --- /dev/null +++ b/assets/ascii-characters-light.svg @@ -0,0 +1,7 @@ + + !"#$%&'()*+,-./012 + 3456789:;<=>?@ABCDE + FGHIJKLMNOPQRSTUVWX + YZ[\]^_`abcdefghijk + lmnopqrstuvwxyz{|}~ + diff --git a/assets/windows-1252-characters-dark.svg b/assets/windows-1252-characters-dark.svg new file mode 100644 index 00000000..b6b5a972 --- /dev/null +++ b/assets/windows-1252-characters-dark.svg @@ -0,0 +1,1083 @@ + + + + + + + + + + image/svg+xml + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/assets/windows-1252-characters-light.svg b/assets/windows-1252-characters-light.svg new file mode 100644 index 00000000..2db7c198 --- /dev/null +++ b/assets/windows-1252-characters-light.svg @@ -0,0 +1,1083 @@ + + + + + + + + + + image/svg+xml + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +