Re: translation of core files

Jean-Christophe Michel wrote:
> Hi all,
> 
> In cvs version (the soon-to-come rc4), there is now a way to translate
> all strings for user on the fly, and to prepare core files (binarycloud/
> and vortex/) to see developper messages (Log and Exceptions) translated too.
> 
> See the #207 on issue list. For those who don't follow issues, here's a
> copy. Please help to localize ! Probably bc will be among the first dev
> systems that fully handle unicode/utf-8 and that let people see messages
> in their own lang!

IMHO that seems like overkill.  I remember this came up at one point on 
the PEAR-Dev lists -- whether exception messages needed to be 
translated.  I'm sure that I argued that since the target audience for 
exception messages is always developers, this didn't make any sense.  By 
that logic, you would also need to provide translations of the API docs 
themselves.

So, while personally thinking that exception messages are a step too 
far, you are not alone in thinking that this is useful -- or the first, 
as Horde also does translation of error & log messages.

On a related note, I didn't find support on Creole mailing lists for the 
incorporation of iconv() in our Creole version.  The consensus seems to 
be that character translations does not belong in the database layer and 
that having the database in a different charset from the PHP script is 
just a bad idea.  Of course, I could see why you guys would want this, 
but apparently this is too much of a fringe usecase to warrant 
introducetion of more complexity in the Creole drivers.  Probably the 
better solution from integration with PHP5 Creole would be to simply 
have a CharsetConverting catch-all driver.  At least Creole was built 
with this sort of extension in mind.

Cheers,
Hans
_______________________________________________
dev mailing list
dev-PnctHDZWAvB/Cz2I37pSEPZ4XP/[email protected]
http://lists.binarycloud.com/mailman/listinfo/dev