[wp-polyglots] Finnish (fi_FI) translation complete

[K Suominen]

On Thu, 24 Feb 2005 10:42:57 +0100, Stefano <steagl at people.it> wrote:
> Il Thu, 24 Feb 2005 10:14:44 +0100, Xavier Borderie
> <xavier.borderie at gmail.com> scrive:
> 
> >We're almost done translating the theme in fr_FR, and we chose to mix
> >the two : keep the _e() strings, and translated the regular ones.
> >Took me some time to remember that the "Links" on the homepage was not
> >to be translated in the PO or the theme, but directly in the Links
> >Categories interface :)
> 
> I think we will go for this way too, even if it doens't satisfy me, i
> was for a full hard coded version.

This is what I did, too.  I'd prefer a version that uses __() and _e()
as much as possible.

> >As for UTF-8/ISO-8859-1, thus far it's the first one, and using a
> >converter might help making the two available to users.
> 
> We decided to write accented chrs in html form, to avoid differences
> between chrs encoding. SO we have only one distro.

I think using entities really is the best way to go.  I will be
re-doing the fi_FI distro that way.  It actually fixes a big problem
with the following files:

lisenssi.txt (translated license.txt)
readme.html
wp-admin/install.php
wp-admin/setup-config.php
wp-admin/upgrade.php

The php files use a <meta> tag to set the Content-Type.  But it is too
late, if the web server (either from its own config or as controlled
by PHP and php.ini) has already sent Content-Type in the response
headers.  The charset from the response headers wins.

The php files can (and should) be fixed to call header() to set
Content-Type.  I think the best approach for the html and txt files
would be to convert them to php files (so we can call header() before
outputting the content).

In addition, using entities of course has the already identified
benefit that the user can then freely select any character set in the
blog settings, without worrying about the charset used by the
templates and the core files.

Regards,
+ Kim

P.S.  I've already raised the header vs. meta issue on hackers, asking
how to reopen Mosquito issue #857.