I am not the author of this plugin. I hope he will have a look at it.

I don't use the plugin and do not have time to dive into the code.
Thus, just a guess:
I found that the strings_german.txt is stored as "UTF-8 with BOM".
Does storing the file as "UTF-8 without BOM" fix the issue?

Hello,

I spent way to much time to get to this point ... wait

Hey atrol,

you hit the bulls eye. Only the german file is stored with BOM.
Changed it and it works.

Please do not fix!
I doing my first steps with git on github and willing to prepare an PR.

Thx.

Please do not fix!
Don't worry ;-)
I have hardly any time to fix bugs in MantisBT core, so I will not invest time in fixing bugs of 3rd party plugins.

Just wanted to create PR.
So I forked code from https://github.com/mantisbt-plugins/Reminder to https://github.com/rakekniven/Reminder and there my doubt came up:
The german file has no BOM.
Next step was to check commit log.
No changes on german file the last years.
What happened? Where is the pain causing BOM? Who killed it?

What happened?
Really strange, no idea at the moment.
Maybe a temporary bug in GitHub and/or Git

@rakekniven

The original file from the ZIP files which I used as the source to create the Git repository had (ref. tag v1.22)

strings_german.txt:  PHP script, UTF-8 Unicode (with BOM) text, with CRLF line terminators

I converted all files to use Unix line endings [1], which actually fixed the BOM issue. I can only assume that you were using the plugin based on the original release from cas.

Anyway I hope this clarifies.

[1] see commit https://github.com/mantisbt-plugins/Reminder/commit/7b8f2053cd6bf59878d950d5b03ec30965e424b8

Let us know if this issue can be closed.

Please close it and still saying "Happy new year".
Loving mantisbt a lot.