Sorry for the long delay, but it's still unclear to me what you want from gettext in this regard.

I can think of some enhancements to gettext tools:

- msgmerge to recognize a new attribute, say "locked", and do not alter the locked definitions as fuzzy or obsolete
- msgattribute to recognize the attribute

Will those match your requirements?  Or do you have anything else in mind?

Although I understand the needs, I have no idea how gettext can help this.  Isn't it a PO editors' (such as KBabel, GTranslator, PO Mode, Zanata, etc) job, rather than gettext?

Could you elaborate a little further what you want gettext to do?

There is a great need to provide facility in .po file to lock the strings for further editing. It is always very difficult for a coordinator or commmitter of any project to track change of all the translation again. So there should always be a facility so that a coordinator or a community can lock the strings so that file can be translated/editable only for new or fuzzy strings.

The benefit of this facility is great. Assume, if one community thinks that present translation of 'gedit' is fine for their locale, the community can lock all the strings or some strings where they are having consensus that these are fine. In this process the usability will be increased much and review will become very easier.