Choosing a text mode for a view

No policy governing access to VOBs is enforced on the basis of a view’s text mode. A user who edits a file in a view that has the "wrong" text-mode configuration can cause problems for other users who need to edit that file. Most sites with supported development platforms should adopt a policy that allows users of the primary development platform to create views in transparent text mode and that limits the use of strip_cr or insert_cr text modes to those platforms that require different line-termination conventions.

Regardless of the policy you adopt, it is important to maintain a consistent combination of client platform, view text mode, and element. For example, if a user on Linux or the UNIX system creates a version of an element in a view that has a strip_cr or insert_cr text mode and another user creates a version of the same element in a transparent text mode view, the two versions will be difficult to compare or merge.