GNU gettext - Bugs: bug #37236, Facilty to lock strings for...
You are not allowed to post comments on this tracker with your current authentication level.
bug #37236: Facilty to lock strings for further editing
Submitter: | Rajesh Ranjan <rajeshr> | ||
Submitted: | Fri 31 Aug 2012 11:36:14 AM UTC | ||
Category: | Translator tools | Severity: | 3 - Normal |
Item Group: | None | Status: | None |
Privacy: | Public | Assigned to: | None |
Open/Closed: | Open |
Thu 27 Nov 2014 06:18:37 AM UTC, comment #4: |
Daiki Ueno <ueno> |
Thu 28 Feb 2013 05:52:07 AM UTC, comment #3: Thanks for the reply.
|
Rajesh Ranjan <rajeshr> |
Wed 27 Feb 2013 02:42:53 AM UTC, comment #2: 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?
|
Daiki Ueno <ueno> |
Tue 26 Feb 2013 10:38:31 AM UTC, comment #1: ping! |
Rajesh Ranjan <rajeshr> |
Fri 31 Aug 2012 11:36:14 AM UTC, original submission:
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.
|
Rajesh Ranjan <rajeshr> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 3 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2016-11-27 | haible | Category | None | Translator tools | |
2012-08-31 | rajeshr | Carbon-Copy | - | Added -email is unavailable- | |
Carbon-Copy | - | Added -email is unavailable- |
Powered by Savane 3.13-3230.
Corresponding source code
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?