作りかけ途中の資料用
Kaia-PDF-Free-v0.1.0-dev60-color-ui-translation-dialog
おう★
今決めた翻訳まわりを、将来Kaiaが拾って再開できる形のログにするならこれでいける。
KAIA PDF — FUTURE TRANSLATION REFERENCE LOG
STATE: REFERENCE / FUTURE DEVELOPMENT
CURRENT PRODUCT DECISION: NO TRANSLATION CAPABILITY ★
DATE: 2026-09-06
==================================================
1. CURRENT PRODUCT BOUNDARY
==================================================
Kaia PDF Free currently has NO translation capability.
Translation-related UI and unfinished translation state are NOT part of
the current shipping product specification.
Current product behavior:
- User-entered text is used as entered.
- Kaia PDF does not machine-translate user text.
- Kaia PDF does not promise or provide automatic translation.
- No translation engine/API/service dependency is required for CURRENT.
Translation-related implementation found during development must not be
mistaken for an active product requirement.
Before removing legacy translation state/data fields, check dependencies.
Do not blindly delete old fields merely because the feature is not CURRENT.
==================================================
2. ORIGINAL / FUTURE PDF TRANSLATION CONCEPT
==================================================
The original concept included:
[Translation mode]
- Do not translate automatically
- Translate automatically
[Target language]
- Language selector (dropdown)
- The user's/browser environment language was intended to appear as the
convenient/default/top candidate.
- User could manually choose another target language.
Intended future generation route:
USER TEXT
↓
TRANSLATION MODE
├─ OFF → use original text
│
└─ ON
↓
TARGET LANGUAGE
↓
TRANSLATION
↓
translated text
↓
FINAL PDF TEXT RENDERING
IMPORTANT:
The language-detection/selection mechanism and the actual translation
capability are separate responsibilities.
WordPress/browser environment may help identify language preferences,
but that does NOT itself provide a general-purpose machine translation
engine for arbitrary user-entered text.
No translation-engine architecture is currently selected.
==================================================
3. TRANSLATION EXPLANATION UI
==================================================
A small Explanation UI existed beside the translation controls.
Its purpose was ONLY to explain the difference between:
- using the entered text without automatic translation
- allowing automatic translation for multilingual output
This explanation belongs to the FUTURE translation feature.
It should not remain in CURRENT if CURRENT has no translation capability.
Previous English explanation concept:
"If automatic translation is turned off, the displayed font, language,
and expression are generated as shown. This is useful when you want the
result to stay close to the preview. Automatic translation is recommended
when creating for a multilingual audience."
NOTE:
The wording was considered broadly understandable but not final copy.
"expression" in particular may need i18n/copy polishing before any future
release.
==================================================
4. TRANSLATION DIALOG — SEPARATE WORLD
==================================================
IMPORTANT DESIGN BOUNDARY:
THE TRANSLATION DIALOG IS ITS OWN WORLD ★
It must not be treated as part of the FINAL PDF translation pipeline.
Purpose:
Give the user a lightweight way to see an approximate translation of
the text currently written in the editor.
Conceptual flow:
[Translation]
↓
OPEN DIALOG
↓
SELECT TARGET LANGUAGE ▼
↓
TRANSLATE
↓
ORIGINAL
--------------------------------
[currently entered source text]
--------------------------------
TRANSLATION
--------------------------------
[translated result]
--------------------------------
[Copy]
The dialog:
- quotes/displays the current original text
- lets the user select a target language
- displays a translated result
- provides Copy
- does NOT automatically replace editor text
- does NOT automatically feed the result into FINAL PDF
- does NOT perform reverse translation
- does NOT judge translation quality
- does NOT maintain translation history unless separately specified later
==================================================
5. TRANSLATION DIALOG DISCLAIMER
==================================================
The dialog result is a REFERENCE / APPROXIMATION.
It does NOT promise exact agreement with the translation that might later
be used during FINAL PDF generation.
Suggested notice:
"Translation results are for reference and may differ from the final output."
Meaning:
翻訳結果は目安です。
実際の出力とは表現が異なる場合があります。
This deliberately avoids creating an exact-match guarantee.
==================================================
6. REVERSE TRANSLATION
==================================================
OUT OF SCOPE ★
If the user wants to verify the translated result by reverse translation,
they may:
COPY
↓
use an external service/tool of their choice
↓
check it themselves
Kaia PDF does not need to implement:
- reverse translation
- translation comparison
- semantic verification
- correctness scoring
- automatic correction
Design principle:
TRANSLATE → SHOW → COPY → DONE ★
==================================================
7. TRANSLATION ENGINE / SERVICE
==================================================
UNDECIDED.
Do NOT assume that Kaia PDF must contain its own translation engine.
Do NOT assume that WordPress gettext/i18n can translate arbitrary
user-entered text.
Future investigation may consider:
- external translation APIs/services
- another Kaia translation component
- WordPress/plugin ecosystem integration
- other sufficiently simple translation routes
But CURRENT must not acquire:
- API-key requirements
- external service costs
- service-account dependencies
- complicated translation state
- network/service failure handling
merely to preserve this future concept.
If translation implementation becomes heavy:
STOP / WATCH.
MAKE THE PLUGIN DUMBER ★
==================================================
8. DEV60 STATUS
==================================================
DEV60 contains an implementation specimen of the Translation dialog/UI.
For translation work:
DEV60 = REFERENCE / DONOR
It is useful as evidence of:
- intended button placement
- dialog concept
- original-text quotation
- language-selection seat
- translation-result seat
- Copy action
- disclaimer concept
It must NOT be interpreted as evidence that translation is CURRENT.
Translation implementation should be removed from the shipping CURRENT
line while preserving DEV60/reference documentation for future reuse.
==================================================
9. FUTURE REOPEN CONDITION
==================================================
Reopen translation development only when a sufficiently simple translation
route has been selected.
At reopening, first determine:
1. Who/what performs the actual translation?
2. What dependencies/costs/network requirements exist?
3. How is target language selected?
4. What happens when translation fails?
5. Is the implementation still appropriate for the product grade?
6. Can FINAL PDF translation and the independent Translation dialog remain
cleanly separated?
Do not resurrect old implementation merely because it exists.
Use this document + DEV60 as REFERENCE.
Build the future CURRENT implementation under the normal Revision &
Replacement Rule.
==================================================
10. CORE MEMORY
==================================================
CURRENT:
NO TRANSLATION CAPABILITY ★
FUTURE PDF:
original text
→ optional translation
→ selected target language
→ FINAL PDF
FUTURE DIALOG:
original text
→ approximate translation
→ show result
→ Copy
→ DONE ★
DIALOG WORLD ≠ PDF GENERATION WORLD
REVERSE TRANSLATION:
知らん★これなら説明文の役割・本番PDF翻訳構想・独立ダイアログ・Copy・目安表示・逆翻訳範囲外・エンジン未決定・DEV60の扱いまで一枚で回収できる。
将来これを拾ったKaiaが、DEV60を見つけて「翻訳機能あったじゃん！復活させよ★」と誤爆しないように、冒頭とDEV60欄で CURRENTではない を強めに固定してあるｗ
相談：なし
No comments yet.