search

GALAglobal / translationapi

The API is for anyone who wants to adopt best practices for a translation services API to interact with counterparts directly from your application or content management system. The API helps ensure interoperability for the most common tasks.
https://translate.taus.net/translate/taus-translation-api
MIT License
12 stars 3 forks source link

Server created creationDatetime and modificationDatetime are in incorrect format #32

Closed achimr closed 9 years ago

achimr commented 9 years ago

Steps to reproduce:

  1. Launch server with "node tausapiserver.js"
  2. Post new translation request: { "translationRequest": { "id": "2b575fdc-f6af-4b9e-850d-9dc0884c6597", "sourceLanguage": "de-DE", "targetLanguage": "en-US", "source": "Hallo Welt", "professional": true, "mt": false, "updateCounter": 0, "status": "initial" } } Server response: { id: "2b575fdc-f6af-4b9e-850d-9dc0884c6598" sourceLanguage: "de-DE" targetLanguage: "en-US" source: "Hallo Welt" mt: false professional: true status: "initial" creationDatetime: "Wed, 12 Nov 2014 15:54:28 GMT" modificationDatetime: "Wed, 12 Nov 2014 15:54:28 GMT" updateCounter: 0 [...] Expected: creationDatetime and modificationDatetime in ISO-8601 format in UTC time zone.

Remark: Times/dates in version 2.0j already get returned in correct format when the client provides creationDatetime and modificationDatetime. Just not when the server creates the date/time string.

heartsomeXPhantom commented 9 years ago

Corrected: replaced UTC with ISO.

achimr commented 9 years ago

Verified. Works well now.