LEYUN · SITE SPEC & COMPONENT LIBRARY独立站技术规范手册

Multilingual Terminology Table for Independent Sites (Machinery / Hardware / Chemicals / Auto Parts)

Section:MULTILINGUAL COPY SPEC · Reviewed:2026-11-20 · Template asset

Key takeawayThis section defines the structure template, field dictionary, integration points and compliance boundaries for 「Multilingual Terminology Table for Independent Sites (Machinery / Hardware / Chemicals / Auto Parts)」 in MULTILINGUAL COPY SPEC. Templates are for reference only; verify local regulations and platform rules before launch.

Industries and use cases

  • Sites with four or five language versions of one product line
  • Sites where parameters are batch-generated from templates and terminology drifts
  • Teams that must keep parameters and wording consistent across language versions
  • Teams with high outsourcing costs that want fewer proofreading rounds
Template / code snippethtml
<!-- 术语表数据结构:一次维护,全站生效 -->
<!-- 建站引擎中的表结构示意 -->
<table class="term-table">
  <caption>${industry} 术语对照表(中文 / English / Deutsch / Français / Español)</caption>
  <thead>
    <tr><th scope="col">中文</th><th scope="col">English</th>
      <th scope="col">Deutsch</th><th scope="col">Français</th>
      <th scope="col">Español</th></tr>
  </thead>
  <tbody>
    <tr>
      <th scope="row">额定压力</th>
      <td>Rated pressure</td>
      <td>Nenndruck</td>
      <td>Pression nominale</td>
      <td>Presión nominal</td>
    </tr>
    <tr>
      <th scope="row">工作行程</th>
      <td>Working stroke</td>
      <td>Arbeitshub</td>
      <td>Course de travail</td>
      <td>Carrera de trabajo</td>
    </tr>
    <tr>
      <th scope="row">公差</th>
      <td>Tolerance</td>
      <td>Toleranz</td>
      <td>Tolérance</td>
      <td>Tolerancia</td>
    </tr>
    <tr>
      <th scope="row">密封件</th>
      <td>Seal / Gasket</td>
      <td>Dichtung</td>
      <td>Joint</td>
      <td>Sello / Junta</td>
    </tr>
  </tbody>
</table>

<!-- 使用方式:产品参数表的字段名从术语表取值,
     四个语言版本共用同一套键 → 数值与用词都不会漂移 -->
Fields and parameters
Field / parameterTypeDescription and values
Term entryTextChinese serves as the internal key and is not displayed externally
EnglishTextIndustry-standard wording, not literal translation
GermanTextPrefer existing terms from German industrial standards
FrenchTextTechnical terms mostly keep English loanwords or industry conventions
SpanishTextDistinguish Spain from Latin American usage
Applicable industryTextThe same term means different things in different industries
Prohibited renderingsListLiteral, ambiguous or non-compliant translations

SEO and structured-data notes

SEO and structured-data checkpoints
Use Chinese as the glossary keyManage internally with one Chinese key and output per language, so four word lists never drift apart
Prefer established industry termsGerman-speaking regions should adopt DIN vocabulary and French regions industry conventions; this matters more than "translating correctly"
Choose a preferred term among candidates"Seal" exists as seal and gasket in English; fix one per product type
Record prohibited renderingsLog past mistakes so the same error does not recur
Link the glossary to spec tablesTaking field names from the glossary is the key to cross-language consistency
Split the table by industryHardware terms differ between machinery and chemicals; mixing them contaminates both

Compliance risk notes

  • The glossary must not contain exaggerated vocabulary
  • Claim-type words face different legal limits per language; verify against the target market
  • One product must use the same preferred translation in every language version

Do not reuse this template verbatim in regulated contexts; verify local regulations and platform rules before going live.

Modification example

<!-- Modification example: link the glossary to the spec tables -->
<!-- Original: field names are re-translated in every language version -->
<!-- zh version -->
<table><tr><th>Rated pressure</th><td>21 MPa</td></tr></table>
<!-- de version -->
<table><tr><th>Nenndruck</th><td>21 MPa</td></tr></table>

<!-- Modified: values stored once; field names pulled from the glossary per language -->
<!-- Single source of truth: values separated from keys -->
const SPEC = { rated_pressure: { value: 21, unit: 'MPa' } };

<!-- Field names resolved by language at render time -->
function renderSpec(lang) {
  const t = TERMS[lang];           // glossary
  const row = SPEC.rated_pressure;  // parameter value
  return '<tr><th scope="row">' + t.rated_pressure + '</th>' +
         '<td>' + row.value + '</td><td>' + row.unit + '</td></tr>';
}

<!-- Key improvement: glossary and values are fully separated —
     changing terms touches only TERMS, changing values touches only SPEC,
     and numeric drift across four language versions becomes impossible. -->

FAQ

How is one term maintained across four languages?
Use Chinese as the single key; each language version stores one value. Changing the term edits one place and takes effect on all four pages at once.
How many entries should the glossary have?
It depends on the parameter dimensions. Common industrial products land between 40 and 80 entries, covering the high-frequency parameters.
Where do we verify German terms?
Check the relevant DIN standards and German industry associations first, rather than translating literally.
Should the glossary be published on the site?
Not in full. It is an internal asset; publishing it lets competitors reuse it directly.
Version notes2026-11-20: first release, compiled from official Google documentation and public technical sources; updated as engine rules change. Engine behaviour details follow the latest official Google documentation.

Note: this page is a summary of publicly documented search-engine rules and is for self-check reference only. Engine behaviour is subject to the latest official Google documentation; verify against your own Search Console data.