Page MenuHomePhabricator

Evaluate the Open API of Naver for external translation server of CX
Open, MediumPublic1 Estimated Story Points


To integrate a external translation server of Naver with Content Translation Tool, it is needed to evaluate the open API of Naver. The primary targets are the translation from English to Korean and from Japanese to Korean.

The web interface of the translation service is at
and the documentation for the open API is at .

Event Timeline

Ryuch created this task.Apr 5 2016, 6:03 AM
Restricted Application added subscribers: revi, Aklapper. · View Herald TranscriptApr 5 2016, 6:03 AM
Arrbee added a subscriber: JanWMF.Apr 12 2016, 5:43 AM

ping @JanWMF . Can you please take a look at this request for a first pass? Thanks.

Amire80 moved this task from Needs Triage to Bugs on the ContentTranslation board.Apr 13 2016, 4:56 PM
Amire80 triaged this task as Medium priority.May 19 2016, 5:46 PM
Arrbee moved this task from Bugs to Enhancements on the ContentTranslation board.Jun 22 2018, 1:30 PM
Arrbee moved this task from Enhancements to MT on the ContentTranslation board.
Ryuch updated the task description. (Show Details)Sep 16 2019, 8:27 AM
Ryuch set the point value for this task to 1.
revi added a comment.Feb 4 2020, 4:03 PM

Note that the NMT (used for Papago) is on entirely different API endpoint of (docs - both unfortunately only in Korean). NMT has 10,000 chars/day limit, probably needs some deal with Naver Corp?

Aklapper removed Arrbee as the assignee of this task.Jun 19 2020, 4:23 PM
Aklapper added a subscriber: Arrbee.

This task has been assigned to the same task owner for more than two years. Resetting task assignee due to inactivity, to decrease task cookie-licking and to get a slightly more realistic overview of plans. Please feel free to assign this task to yourself again if you still realistically work or plan to work on this task - it would be welcome!

For tips how to manage individual work in Phabricator (noisy notifications, lists of task, etc.), see for available options.
(For the records, two emails were sent to assignee addresses before resetting assignees. See T228575 for more info and for potential feedback. Thanks!)