Am I breaking any “php good practice” in the following php array which deals with 3 (human) languages?

Question

This is the most optimal way of dealing with a multilingual website I can think of, right now (not sure) which doesn\'t involve gettext, zend_translate or any php plugin or

Answer 1

Wouldn't it have been better to post code and briefly explain this issue to us?

Anyway, putting each language in its own file and loading it through some sort of language component seems okay. I'd prefer using some sort of gettext, but this is okay too, I guess.

You should make a function for calling the language keys rather than relying on an array, something like <?php echo lang('yourKey'); ?>

Answer 2

It's OK generally. For instance, punBB's localization works this way. It is very fast. Faster than calling a function or an object's method or property. But I see a problem with this approach, since it doesn't support language fallbacks easily. I mean, if you don't have a string for Chinese, let it be displayed in English.

This problem is topical when you upgrade your system and you don't have time to translate everything in every language.

I'd better use something like

lang.en.php

$langs['en'] = array(
    ...
);

---

lang.cn.php

$langs['cn'] = array(
    ...
);

---

[prepend].php (some common lib)

define('DEFAULT_LANG', 'en');
include_once('lang.' . DEFAULT_LANG '.php');
include_once('lang.' . $user->lang . '.php');
$lang = array_merge($langs[DEFAULT_LANG], $langs[$user->lang]);

Answer 3

Looks all right to me also, but:

Seems that you have localization for multiple modules/sites, so why not break it down to multidimensional array?

$localization = array(
  'module' => (object)array(
    'heading' => 'oh, no!',
    'perex'   => 'oh, yes!'
  )
);

I personally like to creat stdClass out of arrays with

$localization = (object)$localization;

so you can use

$localization->module->heading;

:) my 2 cents

Answer 4

One thing to watch for is interpolation; that's really the only place XSS could sneak in if your server settings are sensible. If you at any point need to do something along the lines of translating "$project->name has $project->member_count members", you'll have to make sure you escape all HTML that goes in there.

But other than that, you should be fine.

Answer 5

Looks all right to me, although I personally prefer creating and using a dictionary helper function:

<?php echo dictionary("showcase_li2"); ?>

that would enable you to easily switch methods later, and gives you generally more control over your dictionary. Also with an array, you will have the problem of scope - you will have to import it into every function using global $language; very annoying.

You will probably also reach the point when you have to insert values into an internationalized string:

You have %1 votes left in the next %2 hours.
Sie haben %1 stimmen übrig für die nächsten %2 stunden.
Sinulla on %1 ääntä jäljellä seuraavan %2 tunnin ajassa.

that is something a helper function can be very useful for:

<?php echo dictionary("xyz", $value1, $value2 ); ?> 

$value1 and $value2 would be inserted into %1 and %2 in the dictionary string.

Such a helper function can easily be built with an unlimited number of parameters using func_get_args().

Answer 6

The only way that this could be xss is if you have register_globals=On and you don't set $lang['showcase_lil'] or other $lang's. But I don't think you have to worry about this. So I think your in the clear.

as an xss test: http://127.0.0.1/whatever.php?lang[showcase_lil]=alert(/xss/)