Andee lives on your phone or Mac and uses any app like you do—no integrations, no root, any model; memory and passwords never leave your device | Andee 住进你的手机或 Mac,像你一样操作任何 App——无需集成、无需 Root、支持任意模型,记忆和密码绝不离开设备。
fix(release): Chinese packages can't carry Han characters in asset names
booboosui169d627c45ec
diff --git a/docs/releases/v0.6.1.md b/docs/releases/v0.6.1.mdindex 2d78089..53acba1 100644--- a/docs/releases/v0.6.1.md+++ b/docs/releases/v0.6.1.md@@ -87,38 +87,31 @@ fixed, along with the two reasons it could happen.| File | Take it if ||---|---|-| `andee-0.6.1-arm64-v8a-en.apk` | anything bought in the last several years — **almost everyone** |-| `andee-0.6.1-armeabi-v7a-en.apk` | an older 32-bit device |-| `andee-0.6.1-x86_64-en.apk` | an emulator |+| `andee-0.6.1-en-arm64-v8a.apk` | anything bought in the last several years — **almost everyone** |+| `andee-0.6.1-en-armeabi-v7a.apk` | an older 32-bit device |+| `andee-0.6.1-en-x86_64.apk` | an emulator |**macOS** (macOS 14 or later). Not a universal binary — take the one matching your Mac:| File | Take it if ||---|---|-| `andee-0.6.1-arm64-en.dmg` | an Apple silicon Mac (M1 and later) — **most Macs** |-| `andee-0.6.1-x64-en.dmg` | an Intel Mac |+| `andee-0.6.1-en-arm64.dmg` | an Apple silicon Mac (M1 and later) — **most Macs** |+| `andee-0.6.1-en-x64.dmg` | an Intel Mac |### Chinese packages-The Chinese packages are named in Chinese, so a Chinese reader can tell them apart in a download list-without knowing which server serves which language. Their file names are therefore reproduced verbatim-below — the only place in this document with non-English text, and the reason the project's-"no Han characters in English docs" check is waived for this section: a download table that cannot name-the file is not a download table.+The Chinese packages are the `-zh-` files in the list above. On the Release page each one displays a+Chinese label beside it — **Andee 0.6.1 中文版 · arm64-v8a**, and so on — so the two sets are easy to+tell apart.-<!-- zh-filenames-are-load-bearing: these are literal download names, not prose. -->+The **file names** are ASCII (`-en-` / `-zh-`) because GitHub deletes Han characters from release asset+names; a package whose name carried the Chinese wording would arrive with it removed and two separators+left touching. So the Chinese wording lives in the label instead, which survives — and the downloaded+file name stays ASCII, which also means it survives every filesystem it is copied onto.-| File | Take it if |-|---|---|-| `安迪-0.6.1-arm64-v8a-中文版.apk` | most Android devices |-| `安迪-0.6.1-armeabi-v7a-中文版.apk` | an older 32-bit device |-| `安迪-0.6.1-x86_64-中文版.apk` | an emulator |-| `安迪-0.6.1-arm64-中文版.dmg` | an Apple silicon Mac (M1 and later) |-| `安迪-0.6.1-x64-中文版.dmg` | an Intel Mac |--The pairing is identical to the English set above: three Android APKs by CPU, two macOS dmgs by chip.-The Chinese set points at `baas.kuafuai.net`; the English set at `myapp.codeflying.app`. That is the-only difference, and it is already baked in — you do not choose it.+The pairing is identical to the English set: three Android APKs by CPU, two macOS dmgs by chip. The+Chinese set points at `baas.kuafuai.net`; the English set at `myapp.codeflying.app`. That difference is+already baked in — you do not choose it.### Opening the Mac app