2.19.0
_Edit: see third comment for a proper bug report._

Disagree

@McLoo Do you have system language set to Deutsch?
I can only reproduce this if system language is different than TS language. E.g. system: English; TS: Deutsch.
Steps to reproduce:

Tested on TextSecure 2.19.0 with
confirmed.
seems to be #2815 related to another "the absolute system locale monarchy decides" issue, I currently can't find issue
Hmm... wasn't #2815 caused by rotation changes? This happens if system language and TS language are different.
yeah #2815 is a pain cause by screen rotation and can only be resolved by moving all our dynamic language stuff into the base activity classes from which all other activities extend.
I found the root cause of this problem:
To get formatted timespan strings usually the class DateUtils inside the Signal project is used. This class' methods consider the language set within Signal. Such methods are used for the message bubble timestamps and the timestamps in the conversation list.
For the media preview's timestamp currently a method of Android's DateUtils is used, which considers the system language.
I am going to work on this.
Most helpful comment
I found the root cause of this problem:
To get formatted timespan strings usually the class
DateUtilsinside the Signal project is used. This class' methods consider the language set within Signal. Such methods are used for the message bubble timestamps and the timestamps in the conversation list.For the media preview's timestamp currently a method of Android's
DateUtilsis used, which considers the system language.I am going to work on this.