使用 Homebrew 安装 nfd2nfc

项目链接

• 主页

命令和别名

• nfd2nfc
• nfd2nfc-watcher

项目历史

The project documents the root problem plainly: macOS stores filenames in decomposed NFD form, while Windows and Linux commonly use NFC. nfd2nfc wraps that conversion in an interactive TUI, scriptable CLI, and background watcher service. The README says it moved from the maintainer's personal tap to homebrew-core starting with v2.0.7.

采用历史

Adoption is small but precise: it serves users who regularly move filenames with Hangul, accented Latin characters, Japanese kana, or other composed characters across platforms. The Homebrew API generated on 2026-07-01 reported 144 installs-on-request in the preceding 365 days, plus 7 HEAD installs.

使用方式

The usual package-nerd path is `brew install nfd2nfc`, run `nfd2nfc` for the TUI, register watch paths, and let `nfd2nfc-watcher` convert new or modified filenames. For scripting, the README documents commands such as `nfd2nfc status --json`, `nfd2nfc convert <path> --mode recursive --target nfc --dry-run --json`, and watcher start/stop/restart commands.

Because it is a macOS watcher that renames files, permissions matter: upstream documents Full Disk Access for the watcher binary and notes that application-level NFD conversion by browsers, email, cloud storage, messaging apps, and archive tools remains outside nfd2nfc's scope.

为什么软件包爱好者会关心

This is a classic small macOS packaging win: a narrow filesystem annoyance, a Homebrew formula, a LaunchAgent-backed watcher, JSON-friendly CLI output, and no cross-platform ambition beyond fixing the local source of bad filenames.

时间线

• v2.0.7: README migration notes say the project moved from the personal tap to homebrew-core.
• 2026-07-01: Homebrew formula API generated data for nfd2nfc 2.1.0.

Related projects

• Unicode normalization
• macOS LaunchAgent
• Homebrew

来源

• https://formulae.brew.sh/api/formula/nfd2nfc.json
• https://github.com/elgar328/nfd2nfc