Re: [midgard-user] Midcom again. Gack.

[Nico Kaiser]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Marcin Soltysiak wrote:

|>Maybe this is they key here:
|>header("Content-type: text/html; charset=UTF-8");
|
|
| hmm.. line 162 of main i causes
|
| Warning: Cannot add header information - headers already sent by (output
| started at ROOT:4) in code-global(119) : eval()'d code(44) : eval()'d
| code(888) : eval()'d code on line 162
Well, in what case does this occur? The header should be better in
can_handle or something, but this may occur because the MidCOM admin
components assume they are called with their own style (in which there
is no output outside of MidCOM), so they can use header() anywhere...
| Does it really need UTF?

Yes, yes, yes! That's what the l10n thing is all about. How else would
you display *all* possible characters (Finnish, Russian, German, ...) on
all systems correctly?!
	Nico.

- --
Nico Kaiser     ::
[EMAIL PROTECTED] :: http://siriux.net/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQE/uhFB9OD/ECTIzj8RAq3nAKCI8riflSAZFbFq0lYJ3oUQY5yA2QCdFGi8
rvTCzwXgie5SscVy0wC+TaM=
=Q4Jy
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]