翻譯公司資訊

世聯(lián)翻譯公司完成開(kāi)發(fā)規范英文翻譯

發(fā)布時(shí)間：2018-10-12 09:10　　點(diǎn)擊：

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世聯(lián)翻譯公司在您身邊,離您近的翻譯公司,心貼心的專(zhuān)業(yè)服務(wù),專(zhuān)業(yè)的全球語(yǔ)言翻譯與信息解決方案供應商,專(zhuān)業(yè)翻譯機構品牌。無(wú)論在本地,國內還是海外,我們的專(zhuān)業(yè)、星級體貼服務(wù)，為您的事業(yè)加速！世聯(lián)翻譯公司在北京、上海、深圳等國際交往城市設有翻譯基地，業(yè)務(wù)覆蓋全國城市。每天有近百萬(wàn)字節的信息和貿易通過(guò)世聯(lián)走向全球！積累了大量政商用戶(hù)數據，翻譯人才庫數據，多語(yǔ)種語(yǔ)料庫大數據。世聯(lián)品牌和服務(wù)品質(zhì)已得到政務(wù)防務(wù)和國際組織、跨國公司和大中型企業(yè)等近萬(wàn)用戶(hù)的認可。專(zhuān)業(yè)翻譯公司,北京翻譯公司,上海翻譯公司,英文翻譯,日文翻譯,韓語(yǔ)翻譯,翻譯公司排行榜,翻譯公司收費價(jià)格表,翻譯公司收費標準,翻譯公司北京,翻譯公司上海。

上一篇：世聯(lián)翻譯公司完成安裝使用說(shuō)明中文翻譯
下一篇：世聯(lián)翻譯公司完成汽車(chē)介紹中文英文翻譯

收藏打印

“貴司提交的稿件專(zhuān)業(yè)詞匯用詞準確，語(yǔ)言表達流暢，排版規范，且服務(wù)態(tài)度好。在貴司的幫助下，我司的編制周期得以縮短，稿件語(yǔ)言的表達質(zhì)量得到很大提升”

華東建筑設計研究總院
“我單位是一家總部位于丹麥的高科技企業(yè)，和世聯(lián)翻譯第一次接觸，心中仍有著(zhù)一定的猶豫，貴司專(zhuān)業(yè)的譯員與高水準的服務(wù)，得到了國外合作伙伴的認可！”

世萬(wàn)保制動(dòng)器（上海）有限公司
“我公司是一家荷蘭駐華分公司，主要致力于行為學(xué)研究軟件、儀器和集成系統的開(kāi)發(fā)和銷(xiāo)售工作，所需翻譯的英文說(shuō)明書(shū)專(zhuān)業(yè)性強，翻譯難度較大，貴司總能提供優(yōu)質(zhì)的服務(wù)�！�

諾達思（北京）信息技術(shù)有限責任公司
“為我司在東南亞地區的業(yè)務(wù)開(kāi)拓提供小語(yǔ)種翻譯服務(wù)中，翻譯稿件格式美觀(guān)整潔，能最大程度的還原原文的樣式，同時(shí)翻譯質(zhì)量和速度也得到我司的肯定和好評！”

上海大眾
“在此之前，我們公司和其他翻譯公司有過(guò)合作，但是翻譯質(zhì)量實(shí)在不敢恭維，所以當我認識劉穎潔以后，對她的專(zhuān)業(yè)性和貴公司翻譯的質(zhì)量非常滿(mǎn)意，隨即簽署了長(cháng)期合作合同�！�

銀泰資源股份有限公司
“我行自2017年與世聯(lián)翻譯合作，合作過(guò)程中十分愉快。特別感謝Jasmine Liu, 態(tài)度熱情親切，有耐心，對我行提出的要求落實(shí)到位，體現了非常高的專(zhuān)業(yè)性�！�

南洋商業(yè)銀行
“與我公司對接的世聯(lián)翻譯客服經(jīng)理，可以及時(shí)對我們的要求進(jìn)行反饋，也會(huì )盡量滿(mǎn)足我們臨時(shí)緊急的文件翻譯要求。熱情周到的服務(wù)給我們留下深刻印象！”

黑龍江飛鶴乳業(yè)有限公司
“翻譯金融行業(yè)文件各式各樣版式復雜，試譯多家翻譯公司，后經(jīng)過(guò)比價(jià)、比服務(wù)、比質(zhì)量等流程下來(lái)，最終敲定了世聯(lián)翻譯。非常感謝你們提供的優(yōu)質(zhì)服務(wù)�！�

國金證券股份有限公司
“我司所需翻譯的資料專(zhuān)業(yè)性強，涉及面廣，翻譯難度大，貴司總能提供優(yōu)質(zhì)的服務(wù)。在一次業(yè)主單位對完工資料質(zhì)量的抽查中，我司因為俄文翻譯質(zhì)量過(guò)關(guān)而受到了好評�！�

中辰匯通科技有限責任公司
“我司在2014年與貴公司建立合作關(guān)系，貴公司的翻譯服務(wù)質(zhì)量高、速度快、態(tài)度好，贏(yíng)得了我司各部門(mén)的一致好評。貴司經(jīng)理工作認真踏實(shí)，特此致以誠摯的感謝！”

新華聯(lián)國際置地（馬來(lái)西亞）有限公司
“我們需要的翻譯人員，不論是筆譯還是口譯，都需要具有很強的專(zhuān)業(yè)性，貴公司的德文翻譯稿件和現場(chǎng)的同聲傳譯都得到了我公司和合作伙伴的充分肯定�！�

西馬遠東醫療投資管理有限公司
“在這5年中，世聯(lián)翻譯公司人員對工作的認真、負責、熱情、周到深深的打動(dòng)了我。不僅譯件質(zhì)量好，交稿時(shí)間及時(shí)，還能在我司資金周轉緊張時(shí)給予體諒�！�

華潤萬(wàn)東醫療裝備股份有限公司
“我公司與世聯(lián)翻譯一直保持著(zhù)長(cháng)期合作關(guān)系，這家公司報價(jià)合理，質(zhì)量可靠，效率又高。他們翻譯的譯文發(fā)到國外公司，對方也很認可�！�

北京世博達科技發(fā)展有限公司
“貴公司翻譯的譯文質(zhì)量很高，語(yǔ)言表達流暢、排版格式規范、專(zhuān)業(yè)術(shù)語(yǔ)翻譯到位、翻譯的速度非�？�、后期服務(wù)熱情。我司翻譯了大量的專(zhuān)業(yè)文件，經(jīng)過(guò)長(cháng)久合作，名副其實(shí)，值得信賴(lài)�！�

北京塞特雷特科技有限公司
“針對我們農業(yè)科研論文寫(xiě)作要求，盡量尋找專(zhuān)業(yè)對口的專(zhuān)家為我提供翻譯服務(wù)，最后又按照學(xué)術(shù)期刊的要求，提供潤色原稿和相關(guān)的證明文件。非常感謝世聯(lián)翻譯公司！”

中國農科院
“世聯(lián)的客服經(jīng)理態(tài)度熱情親切，對我們提出的要求都落實(shí)到位，回答我們的問(wèn)題也非常有耐心。譯員十分專(zhuān)業(yè)，工作盡職盡責，獲得與其共事的公司總部同事們的一致高度認可�！�

格萊姆公司
“我公司與馬來(lái)西亞政府有相關(guān)業(yè)務(wù)往來(lái)，急需翻譯項目報備材料。在經(jīng)過(guò)對各個(gè)翻譯公司的服務(wù)水平和質(zhì)量的權衡下，我們選擇了世聯(lián)翻譯公司。翻譯很成功，公司領(lǐng)導非常滿(mǎn)意�！�

北京韜盛科技發(fā)展有限公司
“客服經(jīng)理能一貫熱情負責的完成每一次翻譯工作的組織及溝通。為客戶(hù)與譯員之間搭起順暢的溝通橋梁。能協(xié)助我方建立專(zhuān)業(yè)詞庫，并向譯員準確傳達落實(shí)，準確及高效的完成統一風(fēng)格�！�

HEURTEY PETROCHEM法國赫銻石化
“貴公司與我社對翻譯項目進(jìn)行了幾次詳細的會(huì )談，期間公司負責人和廖小姐還親自來(lái)我社拜訪(fǎng)，對待工作熱情，專(zhuān)業(yè)度高，我們雙方達成了很好的共識。對貴公司的服務(wù)給予好評！”

東華大學(xué)出版社
“非常感謝世聯(lián)翻譯！我們對此次緬甸語(yǔ)訪(fǎng)談翻譯項目非常滿(mǎn)意，世聯(lián)在充分了解我司項目的翻譯意圖情況下，即高效又保質(zhì)地完成了譯文�！�

上海奧美廣告有限公司
“在合作過(guò)程中，世聯(lián)翻譯保質(zhì)、保量、及時(shí)的完成我們交給的翻譯工作�？蛻�(hù)經(jīng)理工作積極，服務(wù)熱情、周到，能全面的了解客戶(hù)的需求，在此表示特別的感謝�！�

北京中唐電工程咨詢(xún)有限公司
“我們通過(guò)圖書(shū)翻譯項目與你們相識乃至建立友誼，你們報價(jià)合理、服務(wù)細致、翻譯質(zhì)量可靠。請允許我們借此機會(huì )向你們表示衷心的感謝！”

山東教育出版社
“很滿(mǎn)意世聯(lián)的翻譯質(zhì)量，交稿準時(shí)，中英互譯都比較好，措辭和句式結構都比較地道，譯文忠實(shí)于原文。TNC是一家國際環(huán)保組織，發(fā)給我們美國總部的同事后，他們反應也不錯�！�

TNC大自然保護協(xié)會(huì )
“原英國首相布萊爾來(lái)訪(fǎng)，需要非常專(zhuān)業(yè)的同聲傳譯服務(wù)，因是第一次接觸，心中仍有著(zhù)一定的猶豫，但是貴司專(zhuān)業(yè)的譯員與高水準的服務(wù)，給我們留下了非常深刻的印象�！�

北京師范大學(xué)壹基金公益研究院
“在與世聯(lián)翻譯合作期間，世聯(lián)秉承著(zhù)“上善若水、厚德載物”的文化理念，以上乘的品質(zhì)和質(zhì)量，信守對客戶(hù)的承諾，出色地完成了我公司交予的翻譯工作�！�

國科創(chuàng )新（北京）信息咨詢(xún)中心
“由于項目要求時(shí)間相當緊湊，所以世聯(lián)在保證質(zhì)量的前提下，盡力按照時(shí)間完成任務(wù)。使我們在世博會(huì )俄羅斯館日活動(dòng)中準備充足，并受到一致好評�！�

北京華國之窗咨詢(xún)有限公司
“貴公司針對客戶(hù)需要，挑選優(yōu)秀的譯員承接項目，翻譯過(guò)程客戶(hù)隨時(shí)查看中途稿，并且與客戶(hù)溝通術(shù)語(yǔ)方面的知識，能夠更準確的了解到客戶(hù)的需求，確保稿件高質(zhì)量�！�

日工建機（北京）國際進(jìn)出口有限公司