====== 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)

===== 2. Recommended Translation settings =====
  * **translations**: <code>ja en</code>
  * **display**: <code>name</code> (“日本語 / 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 <code>|js</code>, set **defer_js=0**

===== 3. Structure & Naming =====
  * Roots: <code>ja:start</code> / <code>en:start</code>
  * Sections:
    * Builds: <code>ja:workshop:*</code> / <code>en:workshop:*</code>
    * References: <code>ja:reference:*</code> / <code>en:reference:*</code>
    * How-to: <code>ja:guide:*</code> / <code>en:guide:*</code>
  * Media:
    * Common: <code>media:common:&lt;aircraft-key&gt;:step01.jpg</code>
    * Language-specific: <code>ja:img:*</code> / <code>en:img:*</code>

===== 4. Creating a translation (workflow) =====
  - (1) Open the source page (e.g., ja:workshop:go-242a-2)
  - (2) In the language switcher, the opposite language shows an entry; a **red “?”** means “missing page”
  - (3) Create the target page (e.g., en:workshop:go-242a-2) → with **copytrans=ON**, the source is duplicated into the editor
  - (4) Keep IDs/links as-is and translate the text
  - (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: <code>====== Title ======</code> → <code>===== Sub =====</code> → <code>====</code>…

===== 6. Images & Captions =====
  * In-page calls (common media / width 600px):
    * JP: <code>{{media:common:go-242a-2:step01.jpg?600|工程1：胴体ブロックの荒取り}}</code>
    * EN: <code>{{media:common:go-242a-2:step01.jpg?600|Step 1: Rough cutting the fuselage block}}</code>
  * 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.**  
    - Place <code>~~TRANSLATION~~</code> at line 1 (followed by a blank line)  
    - Do not put it inside **nowiki/code blocks**  
    - Ensure the counterpart page exists and is viewable (ACL)  
    - After changes, reload with <code>&amp;purge=true</code>
  * **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 =====
  - [ ] Mirrored IDs (ja:/en:)  
  - [ ] <code>~~TRANSLATION~~</code> at the top  
  - [ ] Use <code>media:common:</code> where possible  
  - [ ] Terminology consistent (see glossary)  
  - [ ] Verify output (&purge=true)

----

Last updated: @@@DATE@@@