Re: [SMARTY] I18N/L10N: Best practice
v3rb0 <[email protected]>
| Newsgroups | gmane.comp.php.smarty.general |
|---|---|
| Message-ID | <[email protected]> |
also create some stresstests and take a look at execution times/system load - sometimes localization maintainability is less important thn application performance in production environment. -- v On 08/08/05, Martin Braun <[email protected]> wrote: > Wolfram Schlich wrote: > > My thoughts so far: > > - pro-db: > > - easier maintainability > > - contra-db: > > - in case of an unavailable database, all the error messages > > would only be available in the original language (english > > for example), which would be very unsatisfying for the > > corresponding user when he/she is no native english speaker > > hi, > > if your app is DB driven anyway, I'd recommend this - your app will have > bigger problems than english messages if your DB is down. > > cheers > martin > -- > Warum freie Software? Darum: http://www.deshalbfrei.org/ > > Please use my public PGP key: http://www.mbant.de/mbant-gpg-key > > -- > Smarty General Mailing List (http://smarty.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > > -- Smarty General Mailing List (http://smarty.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php