Ticket #104 (enhancement)
Opened 3 years ago
Last modified 1 year ago
Multilingual Tracks
Status: assigned
| Reported by: | nic | Assigned to: | bsag (accepted) |
|---|---|---|---|
| Priority: | lowest | Milestone: | 2.0 |
| Component: | Design/Appearance | Version: | |
| Severity: | normal | Keywords: | multilingual |
| Cc: |
If there is interest, at some stage we should consider adding Multilingual support.
Change History
08/20/05 10:42:04: Modified by bsag
- status changed from new to assigned.
08/30/05 06:54:23: Modified by schilke
I would offer my help to translate into German ;) bsag.tt.check[atxoxy.net]
09/20/05 13:55:26: Modified by anonymous
I have problems with german umlaute. They didn't shown correct. Or is it a missconfiguration of my mysql db? i use utf-8
09/27/05 17:50:39: Modified by bsag
anonymous: characters like umlaut work fine here, so I would think it's a misconfiguration somewhere else along the line.
09/29/05 11:18:40: Modified by schilke (tracks.tt.check@xoxy.net)
> characters like umlaut work fine here
same here, you should consider that each involved party has some influence on the display of characters: web server, database (engine) and browser - and finally at three stages: input, modification and output/view.
09/30/05 19:58:55: Modified by nanokid
switching to utf-8 in my safari resolved the umlaute-issue for me. firefox worked out of the box !
10/08/05 00:14:56: Modified by nanokid
of course this ist only a very short-term solution, but according to this changeset things should be resolved in a future release of tracks - meanwhile you might just want to patch the file manually.
02/07/07 12:52:01: Modified by Denis Pankratov at [fotki_zp_ua]
I've summarised all the needed stuff to support utf-8 with safari & hopefully other browsers.
10/08/07 07:30:46: Modified by lrbalt
- milestone changed from Version 1.10 to 2.0.
Sure, that would be good in the long term.