Hi,
we use v2.0.4 in productive mode in utf8-mode and the applied workaround
described in http://bugs.otrs.org/show_bug.cgi?id=799
Now, I test the migration towards v2.1-beta2 without the workaround
applied. I use a DB-copy of our productive system.
I get strange behaviour:
=> Some data from DB is displayed correct (with german umlauts), some
are displayed wrong (as "double-encoded" utf8),
e.g. umlauts within articles are displayed correct, umlauts within
ticketfreetext-field are wrong - both are correct stored as utf8 within
the DB.
Why are any charset-details missing within the generated html-pages?
Bye, Alex
_______________________________________________
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
Support orr consulting for your OTRS system?
=> http://www.otrs.com/
