#4289: i18n::translate method accepting a language parameter and a new __l()
function in basic accordingly
---------------------------------------------------+------------------------
    Reporter:  franiglesias                        |         Owner:         
        Type:  Enhancement                         |        Status:  new    
    Priority:  Very Low                            |     Milestone:  1.3.x.x
   Component:  Core Libs                           |       Version:         
    Severity:  Trivial                             |    Resolution:         
    Keywords:  i18n translate language basics.php  |   Php_version:  n/a    
Cake_version:                                      |  
---------------------------------------------------+------------------------
Comment (by achew22):

 Maybe I'm wrong here, but if you have a __l() call where you know the
 language is hard-coded (not read from a config file) and the string is
 hard-coded as well, don't you just have a function that repeats the same
 call over and over again? Why can't you just put the translated string in
 UTF-8 into your .ctp file? That would be faster and it wouldn't require
 another core function.

-- 
Ticket URL: <https://trac.cakephp.org/ticket/4289#comment:4>
CakePHP : The Rapid Development Framework for PHP <https://trac.cakephp.org/>
Cake is a rapid development framework for PHP which uses commonly known design 
patterns like ActiveRecord, Association Data Mapping, Front Controller and MVC. 
Our primary goal is to provide a structured framework that enables PHP users at 
all levels to rapidly develop robust web applications, without any loss to 
flexibility.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"tickets cakephp" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/tickets-cakephp?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to