Editorial Standards

Editorial Standards for Kanji.Jepang.org

Use this page to see where data comes from, how meanings are chosen, what the site does not claim, and how to report corrections.

Data sourcingMeaning fallbackCorrection policy

Last Updated

March 23, 2026

Primary Product Language

Indonesian

1. Sources and Foundation

Kanji.Jepang.org uses data from open-source projects, kanji lists, vocabulary sources, and supporting visual assets.

Each source has different strengths, gaps, and license terms. We try to keep attribution and usage limits clear whenever possible.

2. Normalization and Presentation

Many original sources are hard to read when pasted directly into study pages. We reorganize labels, ordering, and grouping so you can find what matters faster.

The goal is to make pages easier to use, not to hide uncertainty when data is incomplete.

  • Keep labels and section order consistent
  • Place kanji into stable browse routes such as JLPT, Jōyō, and radicals
  • Prefer lightweight pages with clear hierarchy
  • Review results before publishing updates

3. Indonesian-First Meaning Policy

Kanji.Jepang.org follows an Indonesian-first display policy. Indonesian meanings are primary whenever available and editorially acceptable.

When Indonesian is missing, English serves as fallback support. This prevents empty labels and avoids forced low-quality translation.

  • Priority 1: Indonesian meaning (ready and publishable)
  • Priority 2: English fallback meaning
  • Priority 3: first non-empty locale if relevant
  • Priority 4: empty if data is genuinely missing

4. Limits and Interpretation Boundaries

No dictionary can fully remove ambiguity in every context. Some entries have richer data than others, and nuance may vary by usage context.

Use this site as a practical reference aid, not as a legal, medical, or official translation authority.

  • Coverage depth can vary by entry
  • Short glosses may not capture every nuance
  • Vocabulary and sentence coverage may change as data improves
  • A large collection does not mean every page has the same level of detail

5. Corrections, Verification, and Updates

Specific correction reports are strongly preferred: include the URL, affected section, proposed fix, and supporting references when possible.

We review reports to find the source of the problem and update the page, data, or supporting reference when needed.