User Tools

Site Tools


en:about:translation

Translation Operations Guide (Japanese / English)

This page states how we manage our bilingual wiki (Japanese and English). Editors should follow the naming rules, creation workflow, and style guide defined here.

1. Policy

  • Language namespaces: ja: (Japanese) / en: (English)
  • Keep mirrored page IDs: e.g., ja:workshop:go-242a-2 ↔ en:workshop:go-242a-2
  • Put ~~TRANSLATION~~ at the very top of each page (beginning of line, followed by a blank line)
  • Prefer media:common: for images; localize only captions
  • UI language follows the page language (translateui=ON)
  • translations:
    ja en
  • display:
    name

    (“日本語 / English” labels)

  • copytrans: ON (copy source text into a new translation)
  • checkage: ON (warn when translations are outdated)
  • show_path: ON (show creation path for missing translations)
  • redirectstart: OFF for now (consider later when stable)
  • If you use indexmenu with
    |js

    , set defer_js=0

3. Structure & Naming

  • Roots:
    ja:start

    /

    en:start
  • Sections:
    • Builds:
      ja:workshop:*

      /

      en:workshop:*
    • References:
      ja:reference:*

      /

      en:reference:*
    • How-to:
      ja:guide:*

      /

      en:guide:*
  • Media:
    • Common:
      media:common:<aircraft-key>:step01.jpg
    • Language-specific:
      ja:img:*

      /

      en:img:*

4. Creating a translation (workflow)

  1. (1) Open the source page (e.g., ja:workshop:go-242a-2)
  2. (2) In the language switcher, the opposite language shows an entry; a red “?” means “missing page”
  3. (3) Create the target page (e.g., en:workshop:go-242a-2) → with copytrans=ON, the source is duplicated into the editor
  4. (4) Keep IDs/links as-is and translate the text
  5. (5) When the source is updated, use checkage warnings to sync

5. Style (minimal set)

  • Numbers/units: half-width + SI (e.g., 10 mm, 1/50)
  • Proper nouns: give the counterpart in parentheses at first appearance (e.g., end grain(木口))
  • Punctuation: JP uses 「、。」; EN uses commas and periods
  • Headings:
    ====== Title ======

    ===== Sub =====

    ====

6. Images & Captions

  • In-page calls (common media / width 600px):
    • JP:
      {{media:common:go-242a-2:step01.jpg?600|工程1:胴体ブロックの荒取り}}
    • EN:
      {{media:common:go-242a-2:step01.jpg?600|Step 1: Rough cutting the fuselage block}}
  • Share the same image; localize captions only.

7. FAQ

  • Q. What is the red “?” before a language name?
    • *A. It indicates a missing translation page (a redlink). Clicking it opens the creation form for that language/ID.
  • Q. The switcher does not appear / markup shows as plain text.
    1. Place
      ~~TRANSLATION~~

      at line 1 (followed by a blank line)

    2. Do not put it inside nowiki/code blocks
    3. Ensure the counterpart page exists and is viewable (ACL)
    4. After changes, reload with
      &purge=true
  • Q. indexmenu tree won’t work

Set defer_js=0 (temporary requirement; subject to future improvement).

8. Quality checklist for build articles

  • Safety notes (tools/paints/PPE)
  • Rationale for materials (wood species & grain direction)
  • Common mistakes & prevention (for reproducibility)
  • Dimensions & jigs (where to read on drawings)
  • Finishing steps (abrasive grit, drying time)

9. Editor checklist

  1. [ ] Mirrored IDs (ja:/en:)
  2. [ ]
    ~~TRANSLATION~~

    at the top

  3. [ ] Use
    media:common:

    where possible

  4. [ ] Terminology consistent (see glossary)
  5. [ ] Verify output (&purge=true)

Last updated: @@@DATE@@@

en/about/translation.txt · Last modified: by admin