Blissbook has several different options for handling multiple or non-english languages that you can use to meet your project goals. These options range in scope, size, and utility. If you need help deciding which method to use, please ask for help!
The first method is to translate your document into the language of your choice outside of Blissbook and then embed it as a PDF in your base language document in Blissbook. This is a good option if all translations are in PDF form already and you’d prefer to keep them that way. Here's how to embed PDFs in a document: Upload/Embed a PDF.
Bottom-line: Use this if it's easier for your team to maintain non-default language variants outside of Blissbook, AND/OR you don't want to spend a time figuring out the other methods below.
Low impact and less setup work on the front end in Blissbook.
Easy for employees to click a link and open a PDF.
Employees sign off on one document and your reporting in Blissbook is contained within one document.
PDFs don’t have that Blissbook “feel” of design; this also means it won’t be digitally optimized for viewing.
Blissbook's viewing interface will be in the language of the base (e.g. English) document.
Employees can only sign the base (e.g. English) version in Blissbook even though they can download other languages.
You'll need to maintain the translations/content outside of Blissbook, likely in a Word document.
You have to replace the PDF in Blissbook and re-publish any time there are changes. However, you could host the PDF on your own internet file storage platform (sharepoint, box, dropbox, drive, etc.) and link to it from Blissbook instead of embedding it in Blissbook. As long as the link/filename stays the same, it'll always open the latest version of the file.
The second method is to create separate documents (one for each language) in Blissbook and then set the language of each document. Here's how to set the language on an entire document: Handbook Language Settings.
Bottom-line: Use this method if separate groups of employees are getting separate documents that just happen to be in a different language, OR if you need signatures from your single population on all language versions of a document, OR your documents are view-only (you aren't collecting signatures) and you want to maintain separate documents.
All your handbooks/documents are digital, branded, and consistently designed.
You can collaborate on editing each document with separate groups of people.
Blissbook's viewing interface and calls to action for employees will be in the set language of the document.
You can collect electronic signatures on each document with acknowledgement forms in the same language as each document.
If you're collecting signatures, each handbook/document will have separate acknowledgements. This means: (A) employees will be prompted to sign each document separately and (B) you'll need to switch between documents in your Documentation Center.
If you have a mixed population where people should have access to both language documents: (A) it can be cumbersome for viewers to switch between documents, or to know that other language versions exist and (B) viewers/signers will be prompted to sign each document separately, and if you're using automated reminders, they would get them for each variant they haven't signed.
Multiple Languages in One Document:
The last method is to have several languages all within one handbook. You'll set the language of individual sections within the entire document, and your viewers will then see a language picker when they open the document, which they can use to choose which language they'd like to view the document in. Since it's all technically the same document, they sign once and you report on it in one place. Learn how to set the language on individual sections here: Language Setting by Section.
Bottom-line: Use this method when you have a population of employees who need to view different language variants of the same document, you want those with access to the document to sign a single acknowledgement form, and you want to report on those signatures and other data in one place.
All varying languages can be housed in one document with one signature and can be tracked easily in the documentation center.
Users will not get reminders to sign other documents in other languages once they've signed.
When viewers change languages within the document, Blissbook's interface will change to match the language selection.
Signed acknowledgements in the doc center will show which language the document was being viewed in when it was signed.
Setup is a bit more complex and requires more effort during implementation.
Since documents have one set of collaborators, all editors can access & edit the entire document (all languages).
This can be cumbersome for editors and administrators as the document from the editing perspective can become quite long, although Blissbook has tools to minimize this inconvenience.
It may take some technical acumen from your employees. We try to make the language picker obvious, but users will need to understand how to change the language from the document's default language to the language of their choice. You may need to provide a small amount of training for this.