[Erp5-dev] TaskConstraint proposition

[Mikolaj Antoszkiewicz]

Romain Courteaud wrote:
> * Mikolaj Antoszkiewicz [2008-05-19 12:43:01 +0200]:
> 
>>> I don't understand why such Constraint class is required.
>>> It seems easier to configure a PropertySheet on the Task Line Level
>>> which uses CategoryExistence constraint, isn't it?
>> And check each line's consistency on the workflow script level, right?
>> That is in the script that conducts consistency check for the Task.
> 
> The checkConsistency method is called automatically on Task Lines.
> 
>> Well, I used T which was to mean T(ranslate), and I couldn't find the 
>> convention about that.
>> Why N_ then?
> 
> Because of:
> http://svn.erp5.org/erp5/trunk/bt5/erp5_forge/SkinTemplateItem/portal_skins/erp5_toolbox/ERP5Site_getToBeTranslatedMessageListFromEntireSystemAsPot.xml
> But, as Jean-Paul said, it is better to use 'translateString' variable.
> 

Yes, especially that translateString's output is a string and Message 
function outputs Message class instance which is un-decodable by the 
email module methods.
But I was wondering why N_? What does it stand for?

Mikolaj