Initial toolkit: scripts, references, skills, and term database
This commit is contained in:
iacore
@@ -0,0 +1,127 @@
|
||||
# Termbase Rebuild (from absorbed termbase-management)
|
||||
|
||||
How to rebuild the terms DuckDB from source spreadsheets. This is the full pipeline from the now-archived `termbase-management` skill.
|
||||
|
||||
## Prerequisites
|
||||
|
||||
```bash
|
||||
pip install openpyxl odfpy pyyaml duckdb
|
||||
```
|
||||
|
||||
## Step 1: Inspect spreadsheet structure
|
||||
|
||||
```python
|
||||
from openpyxl import load_workbook
|
||||
wb = load_workbook(path, read_only=True, data_only=True)
|
||||
for sn in wb.sheetnames:
|
||||
ws = wb[sn]
|
||||
rows = [list(r) for r in ws.iter_rows(min_row=1, max_row=6, values_only=True)]
|
||||
print(f"[{sn}] {sum(1 for _ in ws.iter_rows())} rows, cols: {len(rows[0]) if rows else 0}")
|
||||
for r in rows[:5]: print(f" {r}")
|
||||
```
|
||||
|
||||
For ODS files, use odfpy:
|
||||
```python
|
||||
from odf.opendocument import load as odf_load
|
||||
from odf.table import Table, TableRow, TableCell
|
||||
from odf.text import P
|
||||
|
||||
doc = odf_load(path)
|
||||
for table in doc.getElementsByType(Table):
|
||||
for row in table.getElementsByType(TableRow):
|
||||
cells = row.getElementsByType(TableCell)
|
||||
vals = []
|
||||
for cell in cells:
|
||||
text = ''
|
||||
for p in cell.getElementsByType(P):
|
||||
for node in p.childNodes:
|
||||
if node.nodeType == node.TEXT_NODE:
|
||||
text += node.data
|
||||
vals.append(text.strip() if text else None)
|
||||
```
|
||||
|
||||
## Step 2: Convert to CSV + YAML
|
||||
|
||||
### Cleaning
|
||||
- Strip trailing None/empty values from each row: `while row and not row[-1]: row.pop()`
|
||||
- Skip entirely empty rows
|
||||
- Pad all rows to the max column count
|
||||
|
||||
### Duplicate header handling
|
||||
Some sheets have duplicate column names (e.g., two `英文` columns in paired layout). Deduplicate with suffixes:
|
||||
```python
|
||||
from collections import Counter
|
||||
def dedup_headers(headers):
|
||||
seen = Counter()
|
||||
result = []
|
||||
for h in headers:
|
||||
s = str(h) if h else ''
|
||||
if s in seen:
|
||||
seen[s] += 1
|
||||
result.append(f"{s}_{seen[s]}")
|
||||
else:
|
||||
seen[s] = 1
|
||||
result.append(s)
|
||||
return result
|
||||
```
|
||||
|
||||
### Output formats
|
||||
- **CSV**: `csv.writer` — column-major, preserves all raw data
|
||||
- **YAML**: `yaml.dump(data, allow_unicode=True, default_flow_style=False, sort_keys=False, width=200)` — list of dicts
|
||||
|
||||
## Step 3: Load into DuckDB
|
||||
|
||||
```python
|
||||
import duckdb
|
||||
con = duckdb.connect('termlib.duckdb')
|
||||
|
||||
# Simple CSVs work with auto-detect:
|
||||
con.execute("""
|
||||
CREATE TABLE table_name AS
|
||||
SELECT * FROM read_csv_auto('file.csv', header=true, all_varchar=true)
|
||||
""")
|
||||
```
|
||||
|
||||
### Pitfall: Multiline CSV fields
|
||||
CSV files with embedded newlines (common in glossary example-sentence columns) break DuckDB's auto-sniffer. Fall back to Python csv.reader:
|
||||
|
||||
```python
|
||||
import csv
|
||||
with open(path, 'r', encoding='utf-8') as f:
|
||||
rows = list(csv.reader(f))
|
||||
|
||||
headers = rows[0]
|
||||
data = rows[1:]
|
||||
|
||||
col_defs = ', '.join(f'"{h}" VARCHAR' for h in cleaned_headers)
|
||||
con.execute(f'CREATE TABLE "{table}" ({col_defs})')
|
||||
|
||||
batch_size = 500
|
||||
for i in range(0, len(data), batch_size):
|
||||
batch = data[i:i+batch_size]
|
||||
placeholders = ', '.join(['(' + ', '.join(['?' for _ in headers]) + ')' for _ in batch])
|
||||
flat = [v for row in batch for v in row]
|
||||
con.execute(f'INSERT INTO "{table}" VALUES {placeholders}', flat)
|
||||
```
|
||||
|
||||
### Pitfall: DuckDB CLI opens in-memory by default
|
||||
Running plain `duckdb` gives an empty database. Always pass the file path:
|
||||
```
|
||||
duckdb path/to/termlib.duckdb
|
||||
```
|
||||
|
||||
## Step 4: Create unified views
|
||||
|
||||
See `references/unified-view.sql` for the pattern. Key patterns:
|
||||
- `UNION ALL` across all source tables
|
||||
- Normalize column names to `zh`, `en`, `loc` (出处), `source`
|
||||
- For paired-column sheets (e.g., `中文/英文` + `补充内容/英文_1`), emit two UNION branches
|
||||
- Filter out rows where zh or en is NULL/empty
|
||||
|
||||
## Pitfalls
|
||||
|
||||
- **ODS reading**: Must traverse `odf.text.P` child elements, not direct text nodes
|
||||
- **Duplicate headers**: JSON/YAML dict silently overwrites duplicate keys — always deduplicate
|
||||
- **Multiline CSV + DuckDB**: `read_csv_auto` fails on CSVs with quoted newlines — use Python csv.reader
|
||||
- **DuckDB path**: Always explicit file path; `duckdb` alone is in-memory
|
||||
- **`execute_code` sandbox**: Does NOT share pip-installed packages — use `terminal` for Python scripts
|
||||
@@ -0,0 +1,58 @@
|
||||
# Translation Alignment Workflow
|
||||
|
||||
How to align translated djot files against the MPI terms database.
|
||||
|
||||
## When
|
||||
|
||||
After producing a first-pass translation, or when the user asks to check terminology. Any time a `.dj` file contains glossary-style `{% "..." %}` blocks with Chinese→English term pairs.
|
||||
|
||||
## Steps
|
||||
|
||||
1. Read the full translated file. Extract all Chinese terms from `{% "TERM" (pinyin) = ENGLISH ... %}` blocks.
|
||||
|
||||
2. Start the search server: `python3 $MPI_PROJECT_ROOT/terms-search/server.py &` (port 8910). It may already be running — check with `curl -s http://localhost:8910/`.
|
||||
|
||||
3. Batch-search each term via the HTTP API:
|
||||
```
|
||||
curl -s "http://localhost:8910/search?q=TERM&limit=5"
|
||||
```
|
||||
Prefer `src=DoT定稿` filter for authoritative hits, but also check without filter to catch 内部特色词 and 佛教术语 entries.
|
||||
|
||||
4. For each term, compare the database `en` against the file's translation. A mismatch exists when the core term translation differs (ignore explanatory commentary in glossary blocks).
|
||||
|
||||
5. Priority order for which source to trust:
|
||||
- DoT定稿 (highest authority — final translation decisions)
|
||||
- 内部特色词 (MPI internal terminology)
|
||||
- 佛教术语 (general Buddhist terms)
|
||||
- 经论名 (sutra/shastra titles)
|
||||
|
||||
6. Apply fixes with `patch` tool. Fix BOTH the glossary comment AND all body-text occurrences. Use `replace_all=true` for terms that appear identically in multiple places.
|
||||
|
||||
7. After fixing, grep for remaining old forms to verify nothing was missed.
|
||||
|
||||
## Pitfalls
|
||||
|
||||
- Glossary blocks often include commentary after the term (pinyin, explanations). Compare only the core term translation, not the full comment.
|
||||
- Some terms appear in body text without glossary blocks — scan the body for domain terms too.
|
||||
- The search.py CLI does NOT support `src:` or `loc:` filter syntax directly; use the HTTP API or direct DuckDB queries instead.
|
||||
- Replace-all can create double articles ("the The Eight Steps...") when body text already has the article before the term. Check each replacement site.
|
||||
- Escaped quotes in patch old_string/new_string cause false "Escape-drift" errors. Use unescaped `"` characters from the actual file content.
|
||||
- Terms may have different translations in different contexts (e.g., standalone 心灯 = "lamp of awakening" vs compound 点亮心灯 = "illuminate one's heart"). Use the standalone form for glossary entries.
|
||||
- Sutra quote conventions (e.g., Diamond Sutra "lives" not "bodies" for 身体布施) are not always in the database. Apply standard English Buddhist idiom.
|
||||
|
||||
## Example
|
||||
|
||||
Searching 三无漏学:
|
||||
```
|
||||
curl -s "http://localhost:8910/search?q=三无漏学&limit=5"
|
||||
→ DoT定稿: "three uncontaminated forms of training"
|
||||
→ Current file: "the three undefiled studies"
|
||||
→ MISMATCH → fix
|
||||
```
|
||||
|
||||
## Report
|
||||
|
||||
After alignment, the user may ask for a report. Save it as `alignment-report.dj` in the project directory with:
|
||||
- Summary line (source breakdown)
|
||||
- Per-term before/after table with source annotation
|
||||
- "Not Changed" section listing terms checked and found acceptable
|
||||
Reference in New Issue
Block a user