neuron-explorer
Qwen3.5‑4B 전용 조향형 뉴런 탐색기, 모든 MLP 뉴런을 밀어 결과를 보관·탐색
🌐 Internationalization (i18n) for Next.js
저장소 README에서 가져옴
README 전체를 불러오는 중입니다.
README 전문 보기 ↗Internationalization for Next.js.
Internationalization (i18n) is an essential part of the user experience, therefore next-intl gives you all the parts you need to get language nuances right.
// UserProfile.tsx
import {useTranslations} from 'next-intl';
export default function UserProfile({user}) {
const t = useTranslations('UserProfile');
return (
<section>
<h1>{t('title', {firstName: user.firstName})}</h1>
<p>{t('membership', {memberSince: user.memberSince})}</p>
<p>{t('followers', {count: user.numFollowers})}</p>
</section>
);
}
// en.json
{
"UserProfile": {
"title": "{firstName}'s profile",
"membership": "Member since {memberSince, date, short}",
"followers": "{count, plural, ↵
=0 {No followers yet} ↵
=1 {One follower} ↵
other {# followers} ↵
}"
}
}
As an app grows, messages may drift and become inconsistent.
A companion tool, eloqnt/cli, catches this by analyzing your source code and messages statically:
$ eloqnt lint
messages/de.json
│
│ "UserProfile.title": "Dein Profil"
│ ─┬──────────
│ ╰─ Inconsistent ICU arguments: missing {firstName} (inconsistent-args)
│
│ "UserProfile.membership": "Member since {memberSince, date, short}"
│ ─┬──────────────────────
│ ╰─ Missing translation for de (missing-translation)
✗ 1 error
! 1 warning
→ Rule details: https://cli.eloqnt.dev/docs/lint-rules/<rule>
→ Run `eloqnt translate` to fill in 1 missing translation
It can optionally also fill in missing translations with eloqnt translate, using your source code as context.