OASIS XML Localisation Interchange File Format (XLIFF) TC

 View Only
  • 1.  Locked vs translate

    Posted 10-03-2012 13:22
    Hi all, Since this topic is being discussed for 2.0. Here is an example where a tool uses an extension to provide a 'locked' information. http://tech.groups.yahoo.com/group/okapitools/message/3285 This specific case could probably be handled with 1.2 approved='yes', but it illustrates that some users do feel that using translate='no' is not the proper solution in all cases. The solution that Fredrik proposed yesterday (translate="yes no locked") may be workable. For "no": not translatable. For "yes locked": translatable, but possibly currently protected. The interest is that it is reversible without affecting the translate='no' entries. And you would never have cases like translate='yes'+locked='no'. Just some thoughts... cheers, -yves