There are a few different ways you can use Safari Portal to create proposals in other languages.
Option 1: The quick and dirty way
The quickest way to create a proposal in another language is to enable the language translation add-on, build it as normal in English, and share the link with your guest. They will be able to select the language of their choice from the little gray widget on the left side of the proposal.
- Doesn't require any content creation or even knowledge of the other language
- Uses Deepl for the translation which is best in class translation software
- Machine translation will never be 100% accurate to the same degree as if it were manually translated by a native speaker
- Will translate the Property names as well which can be inappropriate (ie Casa de Lewa for Lewa House)
- Doesn't pull through into the PDF (there is a workaround for this - you can export it to PDF and then upload it to Deepl to translate the whole PDF)
Option 2: The still quick and slightly less dirty way
If you have a working or expert knowledge of the other language you can write out everything in the details tab, the title, the costs, etc all in the other language but still pull in content from the Content Library that is written in English.
Share the proposal and have your guests use the language translation add-on to translate the rest of the itinerary. This ensures that the overview, costs, and any other content you wrote in the other language (e.g., terms and conditions, an introduction note) will be a perfect translation, but still keeps the speed of not having to manually translate the other pages.
Option 3: The Ideal Way
If you are only dealing with travelers who speak a language other than English, and you are fluent in that language, it might make sense to have all the content in your Content Library in that language already.
You can duplicate existing Safari Portal content by clicking the three dots to the right of the page name on the Content Library and clicking Duplicate, and then adding a tag for example for "Spanish." Then translate the content (maybe copying and pasting back and forth into a translation service like deepl.com (or if you have the language translation add-on you could Share the page, also from the three dots, and then use the translation widget to translate the whole page into the language of your choice, and copy paste that back into the duplicated page). Tweak as needed and save back to your Content Library and voila! - you now have re-usable content in that language.
We would suggest building these pages out organically as you need them.
- Have perfectly translated pages
- Translated content pulls into the PDF versions of the proposals
- Takes longer to set-up
- If you are building itineraries in Classic builder (rather than lookbooks), the dates will still display in English (unless you still asked guests to click the translation widget if you had the language add-on)
- In Calendar builder, use the Display Settings to translate the bits like "Transfer departs" or "Flight departs" - dates will still show in English by default