Re: [Phpgroupware-developers] Addressbook Communications

[Alex Borges]

Yup, same here.....

I guess the answer is this was fubar a long time ago. The idea back then
was to provide a separate "communications api" for this.

What we are actually doing (spanish) is modifying parts of the
addressbook and related classes (it aint too much of a change really) to
pass those through lang calls but actually using the english
descriptions... then adding the translations to the lang system.

Its hard to make multilanguage dynamic descriptions as we didnt find an
obvious way to do this with the current lang() capabilities in 16. I
think modifying the description managers to provide language support
there (something like sitemgr does) would be the best way to go.




On Fri, 2004-06-11 at 07:20, Philipp Kamps wrote:
> Hi ya'll,
> 
> I got some questions about the addressbook communications:
> 
> What is the difference between:
> 
> Communication Types Manager* 
> and
> Communication Descriptions Manager*
> 
> What happens if I rename a communication in the
> Communications Description Manager? (Our german
> customer doesn't like theses english descriptions ;-)
> 
> I'm pretty sure that the sync won't work anymore.
> The logic is based on the description strings like
> 'home email' etc.
> But I'm pretty sure that the vcard/CSV Import/Export
> will break as well.
> 
> What would be the best solution for us (non-english people)?
> 
> Cheers, fips
> 
> 
> 
> 
> 
> _______________________________________________
> Phpgroupware-developers mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/phpgroupware-developers
>

signature.asc
Description: This is a digitally signed message part