翻译公司资讯

世联翻译公司完成开发规范英文翻译

发布时间：2018-10-12 09:10　　点击：

世联翻译公司完成开发规范英文翻译

Specification for Interface Development of FedEx Domestic Service

1 About this Manual

1.1 Resource

http://www.w3.org/XML/

1.2 Support

Please contact 599943@fedex.com

2 Article tracking

2.1 Introduction of article tracking service

You can acquire the real-time article tracking information through FedEx domestic time-limited article tracking service

2.2 Article tracking according to Transport tracking number

2.2.1 Description

You can track the package under time-limited service through Transport tracking number.

2.2.2 Request format

Adopt GET way for applying in specific samples.

2.2.3 Response format

Three Response Formats are provided as follows for details.

2.2.3.1 Detailed information for single article

Samples Sample ：

<?xml version="1.0" encoding="UTF-8"?>

<fedex-express>

<destination>Shenzhen</destination>

<sentby>Yan Hongxia</sentby>

<deliveredto>Liao Zhenghong</deliveredto>

<signedforby>Yang Changyuan</signedforby>

<service>Preferentially delivered </service>

<status>Arrival at FexEx working site</status>

<scan>Arrival at FexEx working site</scan>

<location>Shanghai</location>

Specification for Interface Development of FedEx Domestic Service

Page 3 Printed 12/21/2012

</activity>

<scan>Delivered </scan>

<location>Shenzhen</location>

</activity>

<scan>Articles being loaded in delivering process </scan>

<location>Shenzhen</location>

</activity>

<scan>At the local FedEx delivery office </scan>

<location>Shenzhen</location>

</activity>

<scan>Article received </scan>

<location>Shanghai</location>

</activity>

</activities>

</detail>

</tracking>

</fedex-express>

Field meaning ：

Field name Meaning Type

tn Transport tracking number String

ptn If Transport tracking number is null, it means the article is one-order-for-one-piece type. String

destination Destination String

shipdate Posting date & time String

sentby Sender String

deliveredto Recipient String

signedforby Receiver by signature String

servicetype Service type String

deliverydate Article-receiving date String

status Updated status ofthe article String

datetime Date & time of the article posting service String

scancode Contents of the article posting service String

location Places of the article posting service String

details Detailed information of the article posting service String

2.2.3.2 Summary of variant articles

Sample ：

<?xml version="1.0" encoding="UTF-8"?>

<fedex-express>

<ts>

<status>Arrival at FexEx working site</status>

<destination>Shenzhen</destination>

<service>Preferentially delivered</service>

</ts>

<ts>

<status>Arrival at FexEx working site</status>

<destination>Shenzhen</destination>

<service>Preferentially delivered</service>

</ts>

</single>

<mps>

<ts>

<status>Exception cases of delivery </status>

<destination>Changsha</destination>

<service>Preferentially delivered</service>

</ts>

</mps>

</missing>

</invalid>

</summary>

</tracking>

</fedex-express>

Field meaning ：

Field name Meaning Type

tn Transport tracking number String

status Updated status ofthe article String

datetime Updated time status of the article String

destination Destination String

service Service String

2.2.3.3 Summary of one-order-for-variant-articles

Sample ：

<?xml version="1.0" encoding="UTF-8"?>

<fedex-express>

<mps>

<status>Exception cases of delivery </status>

<destination>Changsha</destination>

<service>Preferentially delivered</service>

</ts>

<status>Exception cases of delivery </status>

<destination>Changsha</destination>

<service>Preferentially delivered</service>

</ts>

</mps>

</tracking>

</fedex-express>

Field meaning ：

Field name Meaning Type

tn Transport tracking number String

status Updated status ofthe article String

datetime Updated time status of the article String

destination Destination String

service Service String

2.2.4 Inquiring single order

2.2.4.1 Request method

This inquiry supports Chinese and English version. Chinese is the defaulted version.

GET http://example.example.ex/service/track/xxxxxxxxxxxx

English website is

GET http://example.example.ex/service/track.en/xxxxxxxxxxxx

2.2.4.2 Reply

If the article is one-order-for-variant-pieces, the returned contents are summarized information, referring to 2.2.3.3. If someone wants to inquire some specific article’s detailed information under the order, request shall be sent again as per the following request method.

GET http://example.example.ex/service/track/xxxxxxxxxxxx/XXXXXXXXXXXX

The obtained replied contents refer to 2.2.3.1

If the article is one-order-for-one-piece, the returned contents refer to 2.2.3.1

If the article cannot be inquired normally, the returned contents refer to 2.2.3.2

2.2.5 Inquiring variant orders

2.2.5.1 Request method

GET http://example.example.ex/service/track/xxxxxxxxxxxx,xxxxxxxxxxxx

Transport tracking number is separated by “，”.

2.2.5.2 Response

The returned contents are summarized information, referring to 2.2.3.2. If someone wants to inquire some specific article’s detailed information under the order, request shall be sent again as per the following request method.

GET http://example.example.ex/service/track/xxxxxxxxxxxx,xxxxxxxxxxxx/XXXXXXXXXX

If the article is one-order-for-one-piece, the returned contents refer to 2.2.3.1.

GET

http://example.example.ex/service/track/xxxxxxxxxxxx,xxxxxxxxxxxx/XXXXXXXXXXXX/xxxxxxxxxxxx

The obtained replied contents refer to 2.2.3.1

2.3 Adopt articles tracking request interface and response according to Transport tracking number

2.3.1 Description

You may track the packages under domestic time-limited service according to Transport tracking number.

2.3.2 Request format

Adopt GET way for applying, referring to Sample specifically.

2.3.3 Response format

Two Response formats are provided as follows for details.

2.3.3.1 Detailed information for single article

Sample ：

<?xml version="1.0" encoding="UTF-8"?>

<fedex-express>

<destination>Shenzhen</destination>

<sentby>Yang Hongxia</sentby>

<deliveredto>Liao Zhenghong</deliveredto>

<signedforby>Yang Changyuan</signedforby>

<service>Preferentially delivered</service>

<status>Arrival at FexEx working site</status>

<scan>Arrival at FexEx working site</scan>

<location>Shanghai</location>

</activity>

<scan>Delivered </scan>

<location>Shenzhen</location>

</activity>

<scan>Articles being loaded in delivering process </scan>

<location>Shenzhen</location>

</activity>

<scan>At the local FedEx delivery office </scan>

<location>Shenzhen</location>

</activity>

<scan>Article received </scan>

<location>Shanghai</location>

Field meaning ：

Field name Meaning Type

order Order tracking number String

tn Transport tracking number String

ptn If Transport tracking number is null, it means the article is one-order-for-one-piece type. String

destination Destination String

shipdate Posting date & time String

sentby Sender String

deliveredto Recipient String

signedforby Receiver by signature String

servicetype Service type String

deliverydate Article-receiving date String

status Updated status ofthe article String

datetime Date & time of the article posting service String

scancode Contents of the article posting service String

location Places of the article posting service String

details Detailed information of the article posting service String

2.3.3.2 Summary of one-order-for-variant-articles

Sample ：

<?xml version="1.0" encoding="UTF-8"?>

<fedex-express order=”0953770932427”>

<mps>

<status>Exception cases of delivery </status>

<destination>Changsha</destination>

</activity>

</activities>

</detail>

</tracking>

</fedex-express>

<service>Preferentially delivered</service>

</ts>

<status>Exception cases of delivery </status>

<destination>Changsha</destination>

<service>Preferentially delivered</service>

</ts>

</mps>

</tracking>

</fedex-express>

Field meaning ：

Field name Meaning Type

order Order tracking number String

tn Transport tracking number String

status Updated status ofthe article String

datetime Updated time status of the article String

destination Destination String

service Service String

2.3.4 Inquiring order

2.3.4.1 Request method

This inquiry supports Chinese and English version. Chinese is the defaulted version.

GET http://example.example.ex/service/mctrack/xxxx/xxxxxxxxxxxx

English website is

GET http://example.example.ex/service/mctrack.en/xxxx/xxxxxxxxxxxx

2.3.4.2 Response

If the article is one-order-for-variant-pieces, the returned contents are summarized information, referring to 2.2.3.2. If someone wants to inquire some specific article’s detailed information under the order, request shall be sent again as per the following request method.

GET http://example.example.ex/service/mctrack/xxxx/xxxxxxxxxxxx/XXXXXXXXXXXX

The obtained replied contents refer to 2.3.3.1

If the article is one-order-for-one-piece, the returned contents refer to 2.3.3.1.

2.4 Access address

In view of different access address for different customers, please contact the sales department for specific address. Thanks.

3 SERVICE CHECKING

3.1 Introduction of Service Checking service v1.2

You inquire the information like the existing service, delivery time limit and deadline of getting articles by telephone between two post codes by providing a pair of post codes (Post code of commencement place and destination).

3.2 Response format

Adopt POST method for request /ecs/service/

3.2.1 Request for head format

<?xml version="1.0" encoding="utf-8"?>

<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"

elementFormDefault="qualified">

<xs:element name="RequestDocument" type="RequestDocumentType" />

<xs:complexType name="RequestDocumentType">

<xs:sequence>

<xs:element name="head" type="RequestDocumentHeadType"

minOccurs="1" maxOccurs="1" />

<xs:element name="body" type="xs:anyType" minOccurs="1"

maxOccurs="1" />

</xs:sequence>

</xs:complexType>

<xs:complexType name="RequestDocumentHeadType">

<xs:sequence>

<xs:element name="serialId" minOccurs="0" maxOccurs="1"

nillable="true"> <!-- serial id to match with the message request/response

pair -->

<xs:simpleType>

<xs:restriction base="xs:string">

<xs:pattern

value="[a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}" />

</xs:restriction>

</xs:simpleType>

</xs:element>

<xs:element name="serviceId" type="xs:string" minOccurs="1"

maxOccurs="1" />

<xs:element name="requesterId" type="xs:string" minOccurs="1"

maxOccurs="1" />

</xs:sequence>

<xs:attribute name="version" type="xs:string" default="1.0" />

</xs:complexType>

</xs:schema>

3.2.2 Request for body format

That is, the internal body format of RequestDocument

<?xml version="1.0" encoding="utf-8"?>

<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"

targetNamespace="http://cndxp.apac.fedex.com/ecs/remote/schema"

xmlns="http://cndxp.apac.fedex.com/ecs/remote/schema"

elementFormDefault="qualified">

<xs:complexType name="LogisticServicePublicRequestType">

<xs:sequence>

<xs:element name="senderPostalCode" type="xs:string"

minOccurs="1" maxOccurs="1" />

<xs:element name="recipientPostalCode" type="xs:string"

minOccurs="1" maxOccurs="1" />

<xs:element name="pickupDate" type="xs:string"

minOccurs="1" maxOccurs="1" />

</xs:sequence>

<xs:attribute name="version" type="xs:string" default="1.0" />

</xs:complexType>

</xs:schema>

Specifically, refer to Sample

3.2.3 Request Sample ：

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<head version="1.0"> Request message version number, 1.0 for default.

<serialId>1e690757-87e1-4b0a-84fa-2352f724ddd6</serialId> Message pair number ，uuid format

<serviceId>SERVICE_0002</serviceId> Service code, necessarily filled in

<requesterId>CUSTOMER_ID</requesterId> Request party code ，necessarily filled in, capital and small letter sensitive

</head>

<body xsi:type="LogisticCodServicePublicRequestType" version="1.0"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<senderPostalCode>200042</senderPostalCode> Commencement place code ，necessarily filled in

<recipientPostalCode>100017</recipientPostalCode> Destination post code，necessarily filled in

<pickupDate>2013-01-05</pickupDate> Date of getting articles ，necessarily filled in

</body>

</RequestDocument>

3.2.4 Field meaning ：

Field name Meaning Type

serialId Message pair number UUID

serviceId Service code String

requesterId Request party code String

senderPostalCode Commencement place code String

recipientPostalCode Destination post code String

pickupDate Date of getting articles String

3.3 Response format

Two response formats are provided, normal response format and exception response format.

3.3.1 Response head format

<?xml version="1.0" encoding="utf-8"?>

<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"

elementFormDefault="qualified">

<xs:element name="ResponseDocument" type="ResponseDocumentType" />

<xs:complexType name="ResponseDocumentType">

<xs:sequence>

<xs:element name="head" type="ResponseDocumentHeadType"

minOccurs="1" maxOccurs="1" />

<xs:element name="body" type="xs:anyType" minOccurs="1"

maxOccurs="1" nillable="true" />

</xs:sequence>

</xs:complexType>

<xs:complexType name="ResponseDocumentHeadType">

<xs:sequence>

<xs:element name="serialId" minOccurs="0" maxOccurs="1"

nillable="true"> <!-- serial id to match with the message request/response

pair -->

<xs:simpleType>

<xs:restriction base="xs:string">

<xs:pattern

value="[a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}" />

</xs:restriction>

</xs:simpleType>

</xs:element>

<xs:element name="serviceId" type="xs:string" minOccurs="1"

maxOccurs="1" />

<xs:element name="successFlag" type="xs:boolean"

minOccurs="1" maxOccurs="1" />

<xs:element name="errorCode" type="xs:string" minOccurs="0"

maxOccurs="1" nillable="true" /> <!-- predefined error code if the

successFlag is false -->

<xs:element name="errorMessage" type="xs:string"

minOccurs="0" maxOccurs="1" nillable="true" /> <!-- the detail error

message of the error code -->

</xs:sequence>

<xs:attribute name="version" type="xs:string" default="1.0" />

</xs:complexType>

</xs:schema>

3.3.2 Response body format

That is, the internal body format of ResponseDocument.

<?xml version="1.0" encoding="utf-8"?>

<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"

targetNamespace="http://cndxp.apac.fedex.com/ecs/remote/schema"

xmlns="http://cndxp.apac.fedex.com/ecs/remote/schema"

elementFormDefault="qualified">

<xs:complexType name="LogisticServicePublicResponseType">

<xs:sequence>

<xs:element name="logisticService" type="LogisticServicePublicType"

minOccurs="0" maxOccurs="unbounded" nillable="true" />

</xs:sequence>

<xs:attribute name="version" type="xs:string" default="1.0" />

</xs:complexType>

<xs:complexType name="LogisticServicePublicType">

<xs:sequence>

<xs:element name="serviceCode" type="xs:string" minOccurs="1"

maxOccurs="1" />

<xs:element name="cutOffTime" type="xs:string" minOccurs="1"

maxOccurs="1" />

<xs:element name="isCod" type=”xs:int"

minOccurs="1" maxOccurs="1" />

<xs:element name="transitDays" type=”xs:int"

minOccurs="1" maxOccurs="1" />

<xs:element name="transitDate" type="xs:string"

minOccurs=”1” maxOccurs=”1”/>

</xs:sequence>

</xs:complexType>

</xs:schema>

For details, refer to the following Sample

3.3.3 Normal response sample ：

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<head version="1.0"> Response message head version number, default value is 1.0.

<serialId>1e690757-87e1-4b0a-84fa-2352f724ddd6</serialId> Number of information pairs, UUID format (Information number must be identical with the request message for treating).

<serviceId>SERVICE_0002</serviceId> Service code

<successFlag>true</successFlag> Whether service responds normally or not; if true, get response content from body.

</head>

<body xsi:type="sch:LogisticServicePublicResponseType" version="1.0"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">Response message body version number, default value is 1.0.

<serviceCode>PDS</serviceCode> Service code

<cutOffTime>17:30:00</cutOffTime> Deadline for getting articles

<isCod>1</isCod> with COD business

<transitDays>1</transitDays> Delivery days

<transitDate>2013-01-03 18:00:00</transitDate> Expected delivered date and time

</logisticService>

<serviceCode>99TS</serviceCode> Service code

<cutOffTime>17:30:00</cutOffTime> Deadline for getting articles

<isCod>1</ isCod> with COD business

<transitDays>3</transitDays> Delivery days

<transitDate>2013-01-05 18:00:00</transitDate> Expected delivered date and time

</logisticService>

</body>

</ResponseDocument>

3.3.4 Exception reply Sample （Post code of commencement place is not filled in the request）：

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<serviceId>SERVICE_0002</serviceId>

<successFlag>false</successFlag> Whether service responds normally or not; if false, get exception code from errorCode and get exception message from errorMessage.

<errorCode>BUS_ERR_000004</errorCode> Exception code, BUS prefix indicates business exception and SYS prefix indicates system exception

<errorMessage>Not found sender postal code!</errorMessage> Exception message

</head>

</ResponseDocument>

3.3.5 Exception reply Sample （Post code of destination place is not filled in the request ）：

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<serviceId>SERVICE_0002</serviceId>

<successFlag>false</successFlag>

<errorMessage>Not found recipient postal code!</errorMessage>

</head>

</ResponseDocument>

3.3.6 Field meaning ：

Field name Meaning Type

serialId Message pair number UUID

serviceId Service code String

successFlag Boolean

Whether service responds normally or not; if false, get exception code from errorCode and get exception message from errorMessage.

serviceCode Service code String

cutOffTime Up to the time of getting articles String

isCod COD business：1=existing，0=null Int

transitDays Delivery date Int

TransitDate Expected delivery date:YYYY-MM-DD hh24:mi:ss String

errorCode Exception code(BUS prefix indicates business exception; SYS prefix indicates system exception) String

errorMessage Exception message String

3.4 Exception code

3.4.1Business exception code：

Exception code Meaning

BUS_ERR_000001 NOT_FOUND_REQUEST_SERVICE

BUS_ERR_000002 NOT_FOUND_REQUEST_BODY

BUS_ERR_000003 MISMATCH_REQUEST_BODY_TYPE

BUS_ERR_000004 NOT_FOUND_SENDER_POSTAL

BUS_ERR_000005 NOT_FOUND_RECIPIENT_POSTAL

BUS_ERR_000006 RAISED_BY_INERNAL_SERVICE_QUERY_LOGISTIC_SERVICE

BUS_ERR_000007 ILLEGAL_INTERNAL_SERVICE_REQUEST_FORMAT

BUS_ERR_000008 ILLEGAL_INTERNAL_SERVICE_RESPONSE_FORMAT

BUS_ERR_000009 FAIL_CONVERT_INTERNAL_SERVICE_RESPONSE_TO_XML

BUS_ERR_0000010 NOT_FOUND_PICKUP_DATE

BUS_ERR_0000011 NOT_FOUND_SERVICE_SUPPORT_MESSAGE

BUS_ERR_0000012 NOT_FOUND_MSG_FROM_POSTAL_SERVICE

BUS_ERR_0000013 ERR_FORMAT_PICKUP_DATE

3.4.2 System exception code：

Exception code Meaning

SYS_ERR_0000 CAUSED_BY_SYSTEM_OF_SERVICE_QUERY_LOGISTIC_SERVICE

SYS_ERR_0000 CAUSED_BY_SYSTEM_OF_INERNAL_SERVICE_QUERY_LOGISTIC_S

02 ERVICE

3.5 Service address

Please contact the sales personnel

Version Date Description of Change By

V 1.0 March 16, 2009 First Draft Li-xi Yao

V 1.1 August16, 2009 Adding tracking by order Li-xi Yao

V 1.2 Sep 26, 2009 Example update Xing-Kun Tang

V 1.3 Sep 22, 2011 Append Service Checking Ian Bao

V 1.3.1 Oct 11, 2011 CUSTOMER_ID Ian Bao

V 1.3.2 Dec 29, 2011 Change Key Contact & Doc Management Han-Yue Li

V 1.3.3 Dec 21, 2012 PDS Han-Yue Li

Unitrans世联翻译公司在您身边,离您近的翻译公司,心贴心的专业服务,专业的全球语言翻译与信息解决方案供应商,专业翻译机构品牌。无论在本地,国内还是海外,我们的专业、星级体贴服务，为您的事业加速！世联翻译公司在北京、上海、深圳等国际交往城市设有翻译基地，业务覆盖全国城市。每天有近百万字节的信息和贸易通过世联走向全球！积累了大量政商用户数据，翻译人才库数据，多语种语料库大数据。世联品牌和服务品质已得到政务防务和国际组织、跨国公司和大中型企业等近万用户的认可。专业翻译公司,北京翻译公司,上海翻译公司,英文翻译,日文翻译,韩语翻译,翻译公司排行榜,翻译公司收费价格表,翻译公司收费标准,翻译公司北京,翻译公司上海。

上一篇：世联翻译公司完成安装使用说明中文翻译
下一篇：世联翻译公司完成汽车介绍中文英文翻译

收藏打印

“贵司提交的稿件专业词汇用词准确，语言表达流畅，排版规范，且服务态度好。在贵司的帮助下，我司的编制周期得以缩短，稿件语言的表达质量得到很大提升”

华东建筑设计研究总院
“我单位是一家总部位于丹麦的高科技企业，和世联翻译第一次接触，心中仍有着一定的犹豫，贵司专业的译员与高水准的服务，得到了国外合作伙伴的认可！”

世万保制动器（上海）有限公司
“我公司是一家荷兰驻华分公司，主要致力于行为学研究软件、仪器和集成系统的开发和销售工作，所需翻译的英文说明书专业性强，翻译难度较大，贵司总能提供优质的服务。”

诺达思（北京）信息技术有限责任公司
“为我司在东南亚地区的业务开拓提供小语种翻译服务中，翻译稿件格式美观整洁，能最大程度的还原原文的样式，同时翻译质量和速度也得到我司的肯定和好评！”

上海大众
“在此之前，我们公司和其他翻译公司有过合作，但是翻译质量实在不敢恭维，所以当我认识刘颖洁以后，对她的专业性和贵公司翻译的质量非常满意，随即签署了长期合作合同。”

银泰资源股份有限公司
“我行自2017年与世联翻译合作，合作过程中十分愉快。特别感谢Jasmine Liu, 态度热情亲切，有耐心，对我行提出的要求落实到位，体现了非常高的专业性。”

南洋商业银行
“与我公司对接的世联翻译客服经理，可以及时对我们的要求进行反馈，也会尽量满足我们临时紧急的文件翻译要求。热情周到的服务给我们留下深刻印象！”

黑龙江飞鹤乳业有限公司
“翻译金融行业文件各式各样版式复杂，试译多家翻译公司，后经过比价、比服务、比质量等流程下来，最终敲定了世联翻译。非常感谢你们提供的优质服务。”

国金证券股份有限公司
“我司所需翻译的资料专业性强，涉及面广，翻译难度大，贵司总能提供优质的服务。在一次业主单位对完工资料质量的抽查中，我司因为俄文翻译质量过关而受到了好评。”

中辰汇通科技有限责任公司
“我司在2014年与贵公司建立合作关系，贵公司的翻译服务质量高、速度快、态度好，赢得了我司各部门的一致好评。贵司经理工作认真踏实，特此致以诚挚的感谢！”

新华联国际置地（马来西亚）有限公司
“我们需要的翻译人员，不论是笔译还是口译，都需要具有很强的专业性，贵公司的德文翻译稿件和现场的同声传译都得到了我公司和合作伙伴的充分肯定。”

西马远东医疗投资管理有限公司
“在这5年中，世联翻译公司人员对工作的认真、负责、热情、周到深深的打动了我。不仅译件质量好，交稿时间及时，还能在我司资金周转紧张时给予体谅。”

华润万东医疗装备股份有限公司
“我公司与世联翻译一直保持着长期合作关系，这家公司报价合理，质量可靠，效率又高。他们翻译的译文发到国外公司，对方也很认可。”

北京世博达科技发展有限公司
“贵公司翻译的译文质量很高，语言表达流畅、排版格式规范、专业术语翻译到位、翻译的速度非常快、后期服务热情。我司翻译了大量的专业文件，经过长久合作，名副其实，值得信赖。”

北京塞特雷特科技有限公司
“针对我们农业科研论文写作要求，尽量寻找专业对口的专家为我提供翻译服务，最后又按照学术期刊的要求，提供润色原稿和相关的证明文件。非常感谢世联翻译公司！”

中国农科院
“世联的客服经理态度热情亲切，对我们提出的要求都落实到位，回答我们的问题也非常有耐心。译员十分专业，工作尽职尽责，获得与其共事的公司总部同事们的一致高度认可。”

格莱姆公司
“我公司与马来西亚政府有相关业务往来，急需翻译项目报备材料。在经过对各个翻译公司的服务水平和质量的权衡下，我们选择了世联翻译公司。翻译很成功，公司领导非常满意。”

北京韬盛科技发展有限公司
“客服经理能一贯热情负责的完成每一次翻译工作的组织及沟通。为客户与译员之间搭起顺畅的沟通桥梁。能协助我方建立专业词库，并向译员准确传达落实，准确及高效的完成统一风格。”

HEURTEY PETROCHEM法国赫锑石化
“贵公司与我社对翻译项目进行了几次详细的会谈，期间公司负责人和廖小姐还亲自来我社拜访，对待工作热情，专业度高，我们双方达成了很好的共识。对贵公司的服务给予好评！”

东华大学出版社
“非常感谢世联翻译！我们对此次缅甸语访谈翻译项目非常满意，世联在充分了解我司项目的翻译意图情况下，即高效又保质地完成了译文。”

上海奥美广告有限公司
“在合作过程中，世联翻译保质、保量、及时的完成我们交给的翻译工作。客户经理工作积极，服务热情、周到，能全面的了解客户的需求，在此表示特别的感谢。”

北京中唐电工程咨询有限公司
“我们通过图书翻译项目与你们相识乃至建立友谊，你们报价合理、服务细致、翻译质量可靠。请允许我们借此机会向你们表示衷心的感谢！”

山东教育出版社
“很满意世联的翻译质量，交稿准时，中英互译都比较好，措辞和句式结构都比较地道，译文忠实于原文。TNC是一家国际环保组织，发给我们美国总部的同事后，他们反应也不错。”

TNC大自然保护协会
“原英国首相布莱尔来访，需要非常专业的同声传译服务，因是第一次接触，心中仍有着一定的犹豫，但是贵司专业的译员与高水准的服务，给我们留下了非常深刻的印象。”

北京师范大学壹基金公益研究院
“在与世联翻译合作期间，世联秉承着“上善若水、厚德载物”的文化理念，以上乘的品质和质量，信守对客户的承诺，出色地完成了我公司交予的翻译工作。”

国科创新（北京）信息咨询中心
“由于项目要求时间相当紧凑，所以世联在保证质量的前提下，尽力按照时间完成任务。使我们在世博会俄罗斯馆日活动中准备充足，并受到一致好评。”

北京华国之窗咨询有限公司
“贵公司针对客户需要，挑选优秀的译员承接项目，翻译过程客户随时查看中途稿，并且与客户沟通术语方面的知识，能够更准确的了解到客户的需求，确保稿件高质量。”

日工建机（北京）国际进出口有限公司