{"id":1702,"date":"2012-06-18T13:50:36","date_gmt":"2012-06-18T18:50:36","guid":{"rendered":"http:\/\/blog.cpanel.net\/?p=1702"},"modified":"2012-06-18T13:50:36","modified_gmt":"2012-06-18T18:50:36","slug":"2012-06-18-update","status":"publish","type":"post","link":"https:\/\/devel.www.cpanel.net\/blog\/products\/2012-06-18-update\/","title":{"rendered":"2012-06-18 Update"},"content":{"rendered":"

Our last article brought you up to date on some aspects of our localization efforts. However the team working on integration with the translation service have not stood still. What have they accomplished since the last article? What are they currently working on? What do we intend in the future for localization in cPanel & WHM?<\/p>\n

What the team has accomplished <\/h2>\n

The translation service wants data sent in an XML format, rather than YAML. Specifically the service uses the XLIFF DTD. The last few sprints were devoted to converting our internal tools to generate XLIFF. <\/p>\n

The last big hurdle, completed recently, was supporting the quant function. As shown in the Maketext documentation, the quant function is a useful way of quantifying a noun. As different locales make quantifying complex in different ways, it required extra care, testing and coordination with the translation service provider.<\/p>\n

What the team is currently working on<\/h2>\n

With our internal tools now able to generate XLIFF output for all the current phrases in cPanel & WHM the next step is testing the quality of the service. To do that we will submit a request for localization to Spanish (specifically Latin American Spanish, or locale es_419 ). <\/p>\n

The testing will occur with the Spanish locale because:<\/p>\n