Comment 2 for bug 1586041

Workaround right now is to update a single translation for all documents on all languages to produce the correct date. I am still getting more information on why this is happening.