English–Chinese Window Project Terminology: A Controlled Method, Not Just a Word List

1. Build concept records before translating labels

Assign a concept ID independent of language. Record definition, scope note, broader/narrower/related concepts, part-of relationship, diagram or photograph, counterexample, applicable product/system, source, approved English and Chinese terms, abbreviations, forbidden synonyms, reviewer, status, revision and effectivity. A bilingual spreadsheet with only two term columns cannot expose conceptual disagreement.

Separate generic concepts from manufacturer or project-specific named items. Frame, sash/leaf, lite, glazing bead, mullion, transom, jamb, sill, meeting stile and threshold need diagrammed relationships for the exact system. Marketing series names and supplier part descriptions should be stored as labels linked to concepts, not treated as universal definitions.

Mark every example below as project-pending until approved. A candidate such as frame — [项目待批准中文术语] is a query placeholder, not a translation recommendation. Never publish unknown Chinese text as a standard to make the termbase look complete.

2. Lock viewpoint and handing before naming left or right

Create a viewpoint diagram showing interior/exterior, observer position, direction of view, hinge/pivot side, handle/lock side, opening direction and arrow/symbol legend. Link every handing term to this diagram and exact opening type. 'Left' alone is prohibited until the convention is approved.

Distinguish product handing, hardware handing, active/inactive leaf, leading/trailing panel and installation orientation. A door hardware supplier's left-hand convention may not match an architectural elevation convention; sliding panels can overlap without hinges; tilt-and-turn operation adds handle positions and movement states. Store system-specific definitions rather than forcing one binary rule.

Test the term with paired mirrored sketches and a physical/sample orientation. Ask bilingual reviewers and site users to identify the same unit independently. Record disagreement and revise the diagram/term before labels, schedules or orders are released.

3. Define opening operation with diagrams and state sequences

For each operation, show closed state, initiating action, movement path and open state: fixed, casement, awning/top-hung, hopper/bottom-hung, tilt-and-turn, pivot, sliding, lift-slide, folding or project-specific type. These labels vary across markets; no list entry here establishes the approved bilingual term.

Separate kinematics from marketing and hardware. 'Tilt' can describe sash movement, a handle position or supplier family. 'Sliding door' does not define panel count, track, active panel, pocketing, stacking or synchronisation. Attach operation term to the exact schematic, section/elevation and configuration fields.

Record prohibited ambiguous phrases and approved sentence patterns for schedules: operation term plus viewpoint/handing, panel arrangement, inward/outward movement and restrictions only where verified. Validate that drawings, labels, BIM/CAD properties, hardware schedule and physical sample use the same concept ID.

4. Control frame, sash and hardware-interface terminology together

Build a part-of tree from window/door unit to frame, operable/fixed leaf or sash, glass/infill, glazing retention, seals, drainage and hardware assemblies. Diagram head, sill, jamb, mullion, transom, stile, rail and meeting interfaces for the exact product. Avoid defining parts solely by translated nouns that may swap horizontal and vertical members.

For hardware, distinguish component identity from interface and function: hinge/pivot, stay, roller, track, lock case, gearbox, keep/strike, handle, spindle, cylinder, restrictor and fasteners only as applicable. Record mating components, handing, mounting datum, operation concept and supplier part terminology. A term match does not prove compatibility.

Link exploded drawing balloons and manufacturer part numbers to the termbase. Store deprecated and forbidden synonyms with reason—wrong scope, different viewpoint, market-specific meaning or confused part. Search should find old terms while output templates allow only approved terms.

5. Tie drawing symbols, abbreviations and data fields to concepts

Create a legend register for opening arcs, sliding arrows, tilt symbols, fixed-lite marks, section/detail callouts, centre lines, hidden lines, revision clouds and project-specific icons. Each symbol needs graphic sample, concept ID, meaning, viewpoint, applicable drawing type, source and bilingual label. Do not infer a symbol from visual resemblance.

Control abbreviations, case, punctuation and field values across drawings, schedules, BIM/CAD, ERP/BOM, labels and inspection forms. One approved concept can have a display label and constrained machine value, but mappings must be explicit. Avoid translating machine codes casually.

Test exported PDFs and printed/site views: font/glyph rendering, arrow orientation after mirroring, colour-independent interpretation, scale and legibility. A bilingual legend is incomplete if field users cannot connect it to the physical opening.

6. Approve, version and distribute terminology through one change route

Assign source owner, bilingual technical translator, manufacturer/hardware reviewer, designer, legal reviewer for contract-defined terms, document controller and final project approver. Define statuses such as candidate, queried, technically reviewed, legally reviewed, approved, deprecated and withdrawn; meanings are project-specific.

A term request records context sentence, screenshot/drawing, physical reference, requester, ambiguity, candidate concepts and urgency. Review concept first, then translation. Issue a revision showing additions, changed definitions, preferred and forbidden terms, affected documents/data and effective date. Do not overwrite prior terms used in signed records.

Publish controlled termbase exports and diagram sheets to translators, designers, factories, inspectors and site teams. Integrate QA into authoring templates and translation memory, but allow documented queries rather than autocorrecting uncertain language. Sweep points of use after change.

7. Use factory and site feedback without letting local slang become the standard

Collect misunderstood labels, wrong allocations, RFI language, inspection disputes, voice-message paraphrases and search failures with opening mark, document, image and context. Record what users thought the term meant and operational effect. Treat feedback as evidence for review, not immediate approval of popular wording.

Run periodic high-information tests: mirrored handing, mixed frame/sash parts, similar hardware interfaces, uncommon operation, multilingual drawing symbol and a deprecated synonym. Ask office, factory and site users to identify the same concept and physical item. Analyse disagreement by concept, diagram, translation, training or data issue.

Update only through governance. Provide a temporary clarification with authority and expiry where urgent, then incorporate approved definition, diagram, translation and affected documents. Close with evidence that the physical labels, schedule, drawing, BOM and site instruction now align.

8. Measure terminology control by operational outcomes, not glossary size

Track query volume by concept, repeated ambiguity, wrong-part or wrong-mark events involving language, RFI rework, drawing-note corrections, deprecated-term recurrence, search failure and time to approved resolution. Counts require context: more queries can mean healthier reporting rather than poorer translation. Never invent a zero-error claim.

Sample active outputs against the termbase: schedules, drawings, BOM, labels, inspection forms, RFIs, manuals and site instructions. Compare concept ID, approved term, diagram/viewpoint, effectivity and version. A document can use the preferred word yet apply it to the wrong component, so review physical or graphical context.

Use trends to prioritise better diagrams, definitions, training, system validation or authoring controls. Preserve local feedback and rejected alternatives. Report improvements only from reproduced evidence and keep terminology performance separate from product quality or staff competence judgments.

FAQ

Continue the project review

Connect this guide with the proposed window and door systems, then review how Cavorlen approaches manufacturing and quality control. When your schedule is ready, send it through the project review form.

Related buyer guides

• Window Handing Explained: Interior View, Exterior View and Opening Symbols
• Bilingual Window Contracts and Drawings: Translation and Precedence Control
• Designing Window and Package Labels for Site Installation