Martin Gruner

``` [13] pry(main)> "t\e$(D+W\e(Btatsu".force_encoding('iso-2022-jp-2').encode('utf-8') Encoding::ConverterNotFoundError: code converter not found (ISO-2022-JP-2 to UTF-8) from (pry):13:in `encode' ``` https://stackoverflow.com/questions/23852059/convert-from-iso-2022-jp-2-to-utf-8-in-ruby-2-1 Not sure if this encoding is actually supported by Ruby. `iconv` does not...

I also think it needs to go through specification. It's been like this probably from the start of Zammad.

Maybe partially related to #4832

@mantas AFAIR `Expected Behaviour` must first be specified. We discussed logging errors by default, but also the possibility for an admin to turn on logging (globally?) for all requests for...

Sorry, wrongly closed.

This should also work correctly when rendering dates on the back end side, e.g. in notification templates.

@martini maybe the time zone of the browser, but an offset is not a possibility, as it changes (e.g. on DST switch).

@mantas what about dates rendered server-side, say a date field in a notification. This can only use the users' stored offset (and not their time zone), and will therefore be...

> > This should also work correctly when rendering dates on the back end side, e.g. in notification templates. > > Right now we use the system timezone (`timezone_default`) for...

https://github.com/zammad/zammad/commit/c2793174b0f0a9608728e1e4c91fc737b4b19d3c perhaps this could be a solution here as well: using `dir="auto"`.