Re: [phpesp-dev] Translations

[Matthew G. <gr...@mu...>]

Yup, translations are going to be a pain.

Do the PEAR port first, basing it on the CVS phpESP code, before making any other
changes to phpESP.  That way it can be used by the community.

On Tue, Sep 30, 2003 at 10:23:04AM +0000, Stefan Champailler wrote:
> It looks difficult to add translation capabilities to phpESP.
> I've evaluated several scenarios but I'm quite disappointed overall.
> 
> My best try is to mark a survey as a "model" and make copies of, marked as 
> "localisations". Copies are independant (thus there's a risk of discrepancies 
> with the model).
> 
> From the acl point of view, we have : 
> 
> - Model belongs to one group, one designer.
> - Models are viewable for a given set of groups (those wich are going to 
> translate)
> - A translation is a copy of a model, owned by the translator and kept inside 
> the group of the translator.
> - The memeber of the group of the model have access to the copies (and only 
> the copies), even if they are outside the group.
> 
> I don't like this scenario because it breaks the idea that groups are private 
> (you are only allowed to see the surveys that are in you group). A nice 
> solution would be to allow that a person can belong to several groups. But 
> this require a lot of code refactoring.
> 
> I'd like to have your ideas here, because if I'm going to make big changes,it 
> is likely that my Pear port will be useless to the community. A bad thing.
> 
> stF
> 
> 
> 
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> phpESP-devel mailing list
> php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpesp-devel
> 

-- 
mcg
-------------------------------------
The IT Lab (http://www.itlab.musc.edu)