i18n (german)

[seb-zh]

Hey guys,

just wanted to check the status of german umlauts etc. again. We've to hold back 2 major and 1 minor installations because of missing i18n.

We've bought our own hosted version some months ago and have been told to use our helpdesk productive (still non productive!) "very shortly". We cannot send out crippled emails to major clients in the publishing industry.

We use Cerb 2 and 3 for years now and even are listed in the clients area - but finally we want to use cerb4. Please...

Thanks!

Seb

[TylerRick]

+1

i18n is good.

[jstanden]

I know I say this all the time, but i18n is on my short list of the most important dev work, along with comment importing, inline comments and time tracking.

Full UTF-8 is a little tougher than what German needs. German really just needs the ability to swap strings.

As for umlauts, that shouldn't be a problem in fairly recent builds of 4.0 as long as your database is in latin1. If your database is in UTF-8 the multibytes (over 7-bit) may still get mangled.

We're going to flip the UTF-8 switch soon, but using mbstring overloads to do it is a major hack (that can affect every app on a server) compared to having PHP6 finally do it natively. The biggest hurdle there is converting existing databases.

Again, though, we don't need UTF-8 to support German. Are you on the latest Subversion build?

[seb-zh]

Again, though, we don't need UTF-8 to support German. Are you on the latest Subversion build?


Thanks Jeff - it's the hosted version we use.
I can send you screenshots where characters will be messed up.

Just let me know.

Sorry for pushing things forward - we just have to.