[Mule3doc] mule3 User Guide translation principles and terminology

1. Public terms (it is recommended that you do not translate them. Add a glossary at the end of the translation)

Flow

Pattern

Service

Component component

Connector

Inbound Access

Outbound

Transport Transmitter

Endpoint

Router route

Filter

Transformer Converter

Enricher Booster

Splitter

Aggregator

Processor

Validator

Proxy proxy, Agent Proxy, broker proxy ==> we strongly recommend that you do not translate

Resolver Splitter

One-way unidirectional

Request-Response

Bridge

Dead letter queue dead Channel

Exception strategy exception Policy

 

2. Translation rules

1) The translation is intended for beginners of mule, so try to use a smooth and easy-to-understand expression based on your loyalty and willingness.

2) long sentences can be split into multiple short sentences.

3) The keywords must be translated.

4) for the first time when a professional term or a Chinese term is difficult to express, the original English text is specified. For example, inbound endpoint ).

 

3. Non-translated content

1)Code-related content: Code block, the code snippet referenced in the text that explains the code

2)Attribute or XML element of the Configuration: <> Specified elements or attributes in the content or description text

3)Some professional terms: Common expressions (logger/key/Vm), see content, modes in the list, etc.

4)Abbreviations: ESB, JMS, HTTP, EIP, MEP, etc.

5)Other terms or terms that are difficult to translate: Please submit it by email or in the group and add it to this list after discussion.