Because node_perm() uses a non-standard format (i.e. not just a plain array but also programmatically generated values), they are not included in the translation template.

Comments

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented
Status: Active » Postponed (maintainer needs more info)

We cannot include programatically generated text in PO files, since these depend on user interaction. Do you have a suggested fix to identify misbehaving _perm hooks, and do not try to parse their contents?

kkaefer’s picture

kkaefer commented

extractor.php is already not parsing node_perm() because it's malformed. However, all the other permissions which are not programmatically generated, are not parsed as well.

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented
Status: Postponed (maintainer needs more info) » Fixed

Ok, comitted a not-too-nice solution to CVS. Now we have a special case for node_perm. Crafting a special regexp for node_perm would be as unique as listing the permission names themselfs, so now the node.module strings will have the static permission names listed at least.

Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)