On Monday 14 August 2006 09:59, Sergey Poznyakoff wrote: > The changes aimed to make Savane determine automatically whether a > requested translation is available and to provide for a flexible > algorithm of selecting a matching translation.
Hello Sergey, thanks a lot for your contribution. I'll probably apply most of your patches for the localisation issues. However, I'm not sure that we need the change in i18n.php. You're right that we need to change that file each time a new translation is added. On the other hand, this does not happen too often, and the file i18n.php is parsed on *every* page view that Savane generates. So even if the overhead is quite small, I think that we should keep the files which get parsed on every run as small as possible. Apart from that, we will most likely never get translations for all your additions, so that most locale combinations are simply not needed. [...] > This scheme is rather weak. First, it does not fully describe the > localization: in the above example, at least de_AT and de_CH are > missing, so a person which has any of them set in his browser > preferences will never get the German translation. Secondly, given > sufficient number of available localizations, this array will grow very > large and difficult to maintain. As Stéphane already pointed out, this is not true. The current code copes well with missing locales and provides a sane alternative. P.S. Do you need CCs or are you subscribed to our mailing list? Regards, Tobias -- Tobias Toedter | Absolutely nothing should be concluded from these Hamburg, Germany | figures except that no conclusion can be drawn from them.
pgp7G3PNCyJ2L.pgp
Description: PGP signature
_______________________________________________ Savane-dev mailing list [email protected] https://mail.gna.org/listinfo/savane-dev
