Source control is a process where you store a copy of your project on a server, allowing you to “check in” and “check out” files and keep your local changes in sync with the server version fo the project, and with changes from other writers. Source control is even useful for single authors because it provides a means for maintaining a constant backup of all project files.
Lingo provides integrated support for the following source control applications:
- Apache Subversion
See About Apache Subversion.
See About Git.
- Microsoft Team Foundation Server
See About Microsoft Team Foundation Server.
See About Perforce.
No. Lingo does not use a proprietary source control system within the application. Instead, Lingo allows you to connect (or "bind") your project to an existing third-party source control application that is separate from Lingo.
This depends on how you work in your company. Someone (perhaps a network administrator) needs to set up your source control program (such as Microsoft Team Foundation Server) and create the necessary database(s) in it. This individual may also set up the "rights" to all persons who have access to the necessary databases and files. If you are working on a multi-person team, each person on the team needs to have a local copy of the Lingo project and will be responsible for checking in and checking out files as necessary.
Important: If you are using source control, do not include your local termbase (.litdb3) and translation memory (.db) files in your project folder. These files do not function correctly when used with source control, and can cause conflicts. Instead, you should use a server termbase or translation memory. This will allow other users to have access to the terms in the database while avoiding possible conficts.