金融系统语言国际化设计

概览

Overview

背景

Background

对象

Objects

流程

Process

技术栈

Technology Stack

翻译标准

Translation Standards

词条规范

Terminology

背景

Background

  系统语言国际化的水平体现在细节中，正是这些看起来不影响核心功能的用户体验细节恰好能反映一个软件的成熟度、团队专业程度，也无形中降低了内部团队与客户间跨语言沟通成本、提升了品牌附加值。 

The level of internationalization in system language is reflected in the details. It is precisely these seemingly insignificant user experience details that can reflect the maturity of software, the professionalism of the team, and also indirectly reduce the cross-language communication costs between internal teams and customers, enhancing brand added value.

对象

Objects

 一切需要在视觉上暴露给客户的内容。

Anything that needs to be exposed visually to the customer.

  首先是后台管理系统，这是使用频次最高、暴露面最广的GUI，从技术设计角度被分分静态页面、动态参数如下拉项以及后台可能抛出的错误信息。

Firstly, the backend management system, which is the GUI with the highest frequency of use and the widest exposure. From a technical design perspective, it is divided into static pages, dynamic parameters such as dropdown items, and possible error messages thrown by the backend.

其次是API文档，作为系统集成环境交流的重要载体，同时也具备较好的稳定性，有国际化沉淀的价值。

Secondly, API documentation, as an important carrier for system integration communication, also has good stability and accumulates internationalization value.

第三是FSD/PRD，内部研发迭代流程无需翻译，只有当作为对客交付物时，在需求敲定后再翻译。

Thirdly, FSD/PRD, internal development iteration processes do not need translation, only when they are delivered to clients, they are translated after the requirements are finalized.

对外部暴露的错误码清单，主要是把系统内部错误封装为对外错误信息&错误码。

Error code lists exposed to the outside, mainly encapsulating internal errors of the system as external error messages and error codes.

流程

Process

核心是确保翻译有人受理、改动有人评审、启用会同评审、影响范围可控、’发布各方知晓。

The core is to ensure that there are people responsible for translation, someone to review changes, enable the same review, control the scope of influence, and ensure that all relevant parties are informed of the release.

技术栈

Technology Stack

初版翻译。主流还是人工翻译，源于翻译工具（包括人工智能工具）不擅长于专业术语的准确、简练、一致性。

Initial translation. Manual translation is still mainstream, mainly because translation tools (including artificial intelligence tools) are not proficient in accurate, concise, and consistent use of technical terms.

翻译校正。如Amount缩写为Amt.，End of day缩写为EOD等有固定逻辑且需要保持强一致性的校正项，可通过程序读取初版翻译文件来校正，如java、python都可以胜任该任务，对于非技术人员，python入门门槛较低、可以尝试。 

Translation correction. Corrections like abbreviating "Amount" as "Amt." or "End of day" as "EOD" that have a fixed logic and need to maintain strong consistency can be corrected by reading the initial translation file through programming. Both Java and Python are suitable for this task. For non-technical personnel, Python has a lower entry threshold and can be tried.

  语言切换。原语言词条编译出唯一的key，目标语言绑定该key。

Language switching. The original language term compiles a unique key, and the target language binds to this key.

翻译标准

Translation Standards

  统一、专业术语、长度、场景动作、单复数、主被动、时态等，根本目标是追求翻译的自解释。

Uniformity, professional terminology, length, scenario actions, singular/plural, active/passive voice, tense, etc. The fundamental goal is to pursue self-explanatory translations.

词条

Terminology

一个好的词条文件应该是可以方便地被维护的，要达到这一点，首先需要科学分类，便于检索，便于专业领域的人审阅；其次是摆放顺序。词条摆放摆应按照因果关系、生命周期先后顺序、使用频次、重要程度多方面考量，确定摆放先后顺序，并将关联概念放在一起；最后要避开禁用词汇，如伊斯兰业务中用收益替代利息字眼。

A good terminology file should be easy to maintain. To achieve this, scientific classification is needed for ease of retrieval and review by professionals in the field. The arrangement of terminology should follow considerations such as causality, order of the lifecycle, frequency of use, and importance. Related concepts should be grouped together. Finally, it is essential to avoid prohibited vocabulary, such as using "profit" instead of "interest" terminology in Islamic finance, etc.