[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-i18n-doc
Subject:    Re: patch to kteamtime for the branch
From:       Adriaan de Groot <groot () kde ! org>
Date:       2004-08-24 6:27:23
Message-ID: 200408240827.23684.groot () kde ! org
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Monday 23 August 2004 22:53, Karl Ove Hufthammer wrote:
> Diego Iastrubni <elcuco@kdemail.net> wrote in
> news:200408231124.44537.elcuco__944.36084987155$1093253221$gmane$
> > whats wrong about plain old space?
>
> The solution is to use a non-breaking space (U+00A0) instead of an
> ordinary space. But the problem is that this character isn't
> available in the US-ASCII character encoding.

Yes, so?

> I know the GNOME guys have switched to UTF-8 for all their source
> files (and .POT and PO files), and seem very happy with this. This

As did KDE, years ago. In _principle_, our sources are UTF-8. Unfortunately, 
the QString constructors don't default to UTF-8 but either to latin-1 or 
local 8-bit, so

	QString foo("Äegypten");

is likely to break. i18n() takes a UTF-8 encoded string though, so

	QString foo(i18n("Äegypten")); //  Bad German orthography :)

_will_ work. I rather suspect that the biggest problem is that the editors KDE 
developers use have sub-optimal UTF-8 support (kate, for instance, doesn't 
default to UTF-8 and will seriously kill UTF-8 encoded sources).


- -- 
Don't worry, 't ain't no shame to be stupid - ol' mouse.
    GPG: FEA2 A3FE Adriaan de Groot
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)

iD8DBQFBKt/LdqzuAf6io/4RAmaaAJ97IVhLqUCilVDS3cpVxOL+h0Py0gCfVSRt
6t7Xq3DdkfU4SRkv9wIcbNE=
=Omig
-----END PGP SIGNATURE-----
[prev in list] [next in list] [prev in thread] [next in thread]