bugGNU gettext - Bugs: bug #37236, Facilty to lock strings for...

 
 

You are not allowed to post comments on this tracker with your current authentification level.

bug #37236: Facilty to lock strings for further editing

Submitted by:  Rajesh Ranjan <rajeshr>
Submitted on:  Fri Aug 31 11:36:14 2012  
 
Category: Translator toolsSeverity: 3 - Normal
Item Group: NoneStatus: None
Privacy: PublicAssigned to: None
Open/Closed: Open

Thu Nov 27 06:18:37 2014, comment #4:

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?

Daiki Ueno <ueno>
Project Administrator
Thu Feb 28 05:52:07 2013, comment #3:

Thanks for the reply.

Like we have #fuzzy, a tag can be created similarly so that once approved by a community we can lock that strings for further editing.

At tool level it is difficult to ask everybody. I accept tool can be created to handle such things but once the tag is being incorporated in the gettext format, everybody will do implement it automatically, hence good for the translation community.

For translation perspective, it will add value in the gettext format that is currently a popular format in open source world.

Rajesh Ranjan <rajeshr>
Wed Feb 27 02:42:53 2013, 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?

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

Daiki Ueno <ueno>
Project Administrator
Tue Feb 26 10:38:31 2013, comment #1:

ping!

Rajesh Ranjan <rajeshr>
Fri Aug 31 11:36:14 2012, 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.

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.

Rajesh Ranjan <rajeshr>

 

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by haible (Updated the item)
  • -unavailable- added by ueno (Posted a comment)
  • -unavailable- added by rajeshr (Submitted the item)
  • -unavailable- added by rajeshr
  • -unavailable- added by rajeshr
  •  

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    Follow 3 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Sun Nov 27 01:30:04 2016haibleCategoryNone=>Translator tools
    Fri Aug 31 11:36:14 2012rajeshrCarbon-Copy-=>Added -unavailable-
      Carbon-Copy-=>Added -unavailable-

    Back to the top


    Powered by Savane 3.1-cleanup