The problem is not speed.
The problem appears when there are missing translations.
Then you will get the message id... when it is a english one, most people
will understand it.
But when you are using a cryptic key there is no way for your user to know
what you've meant.
Greetings
Thomas Weidner, I18N Team Leader, Zend Framework
http://www.thomasweidner.com
----- Original Message -----
From: "Aleksey Zapparov" <[email protected]>
To: "Andreas Kraftl" <[email protected]>
Cc: <[email protected]>
Sent: Wednesday, March 31, 2010 11:07 AM
Subject: Re: [fw-general] Good practice - translate html
Hello,
I use second variant in my projects. But with a little modification.
My translation IDs looks like: 'view:user.manage:warning',
'form:login:username' etc. Of course probably _('Realn english text') makes
it faster on non-existing translations, but with caching I guess it would be
impossile to distinguish any difference.
2010/3/31 Andreas Kraftl <[email protected]>:
Hello,
what is a good practice to translate static content like contracts, ...
something like
$translate->_('<h2>Something</h2><p>...</p></ul><li>..</li></ul>');
doesn't looks like good for me ;-).
$translate->_('contract'); looks better, but is it a good choice?
What about some static Text which is something long on sites and have
not a real good static name like 'contract'?
Thx for some ideas
Andreas
--
Kraftl EDV - Dienstleistungen
Linux, Linuxschulungen, Webprogrammierung
Autofabrikstraße 16/6
1230 Wien
--
Sincerely yours,
Aleksey V. Zapparov A.K.A. ixti
FSF Member #7118
Mobile Phone: +34 617 179 344
Homepage: http://www.ixti.ru
JID: [email protected]
*Origin: Happy Hacking!
