Do you have people visiting your Legal Center who want to view your Contracts in languages other than English? Well PactSafe's support for Contract Translations in your Legal Center is just the thing! With Contract Translations, you can store translated versions of your Contracts in PactSafe together with your English versions and give Legal Center users the option to read Contracts in their preferred language.
When you use Contract Translations, the people who view your Legal Center can choose their preferred language from a drop-down. If a Contract has a translation in that language, then that's what appears. If a Contract doesn't happen to have a translation in that language, then it appears in English.
We'll need to get a few things settled before we can really get started:
Only HTML Contracts can have translations at this time; PDF Contract Translations are not currently supported. So, if the English version of the Contract is a PDF, now's a good time to re-create it as an HTML Contract. See the Adding a Contract page if you could use some pointers.
Contract Translations appear only in the Legal Center, so a Contract has to appear in the Legal Center in order for users to see the translation. You can add a translation to a Contract that isn't in your Legal Center (isn't marked as Public), but your Signers won't have any way to see the translation. Check out the Making a Contract Public page for step-by-step instructions.
You need to have the Contract translated before you can add a Contract Translation. The Contract Translation feature displays the translation, but it doesn't do the actual translating. Of course, you'll want a translation expert with knowledge of your business and your Contracts to do the actual translating.
Got all that taken care of? Then let's get going!
Step 1: Getting to the Version Details screen
You add a translation on the Version Details screen. A Contract has to have a version that's in Draft status for you to add a translation. If you want to add a translation to a Contract that's already Published, you can create a new version, but if the Contract already has a version in Draft status, you can just use that one. You can also add a translation to a brand new Contract, before it's published.
Getting to the Versions Details screen is a little bit different for these three cases, so first we'll look at how to get to that screen. Once everyone's found their way, we'll move on to adding a translation.
To get to the Version Details screen on an already published Contract:
Click the Contracts icon in the left navigation to open the Contracts screen.
Find the Contract that you want and click the green New Version button. The Contract appears in the editor window. You can make changes to the English version here if you need to. If not, just go on to the next step.
Click the back arrow at the top left of the screen to open the Version Details screen. A section called Translations appears here. Scroll down to Step 2 to see where to go from here.
To get to the Version Details screen on a Contract that already has a Draft version:
Click the Contracts icon on the left navigation bar to open the Contracts screen.
Find the Contract that you want and click the name of the Contract. The Contract Details screen appears.
Click the latest version in the Versions section (not the pencil; just click the row). The Version Details screen appears, including a section about Translations. Scroll down to Step 2 to see where to go from here.
Note: You could also get to this screen on a Contract with a draft version by following the same steps that we used above when dealing with a published Contract. The only difference is the button you click is called Edit Version instead of New Version.
To get to the Version Details screen on a new Contract:
Click the Contracts icon in the left navigation bar to open the Contracts screen.
Click the green button with the + sign in the lower right corner to start a new Contract.
Upload or edit your new Contract. See the Adding a Contract doc if you need help.
Click the back arrow at the top left of the screen to open the Version Details screen. Now let's continue to Step 2!
Step 2: Adding a Translation
Now that we're all in the same place, we can proceed together.
Here on the Version Details screen, you'll notice the Translations section. It shows a list of all the translations you have for this Contract, including:
Title of the translation
Language & Locale
Just click the Add Translation button (the plus sign at the top-right) to add a new translation. The Add Translation window appears.
In this window you can:
type in the Translated Title of the Contract
choose the Language & Locale of the translation. You can have one translation of the Contract for each value in the Language & Locale drop-down. There are over 100 different language/locale values, so you shouldn't feel limited!
enter the text of the Contract. You can use HTML here to control the formatting, but not fields or tokens. (Fields and tokens don't make a lot of sense in the Legal Center anyway, since it's mostly just a place for people to reference the text of the Contracts. If you are trying to capture signatures, see the docs on Signature Requests, Groups, and SmartPacts.)
Tip: We expect that you'll want to keep your translated Contracts looking as much like their English counterparts as possible. To do that, you should keep the HTML of your English Contract and translate only the text. That's why the Add Translation window doesn't have sophisticated editing tools that you see when you're creating the original English contract.
Now you just click Create to add the Contract Translation. You can add another translation in another language if you want, or you can just publish the Contract.
Step 3: Publish the Contract
What users see
Now when someone goes to your Legal Center, next to the list of Contracts they'll see a drop-down list of languages. They choose their preferred langue to read Contracts in.
There are several steps here, but if you run in to problems, we're ready to help. Just start a chat or email us at firstname.lastname@example.org.