Book a demo

Start free trial

← Back to Help Center

File translation

24 articles

Connect Google Docs with Smartcat

Google Docs integration with Smartcat | Smartcat Help Center Google Docs is an online word processor included as part of the free, web-based Google Docs Editors suite. The integration between Smartcat and Google Docs enables localization managers to connect a Google Drive folder to Smartcat and create a continuous localization flow for the documents stored in that folder. 1. Pre-requisites The only parameter required to set up the integration is the URL of the Google Drive folder that you want to connect to Smartcat. For best results, create a new Google Drive folder where you will be placing Google Docs ready to be translated and copy the URL of that folder. 2. Configuring the integration To configure the Google Docs integration, log in to Smartcat and complete the following steps. Create a new integration project.In the Integrations tab, click Set up integration in the Google Docs integration tile. 3. Paste the URL of the target Google Drive folder. Click Sign in with Google. Select your Google Account and grant access to Smartcat. As a part of initial integration setup, Smartcat will automatically import previous translations, populating the project translation memories (TM) and allowing you to reuse them in the future. Smartcat will ensure that all the translatable content is available for translation as soon as possible, and that translations are pushed back into your CMS automatically, without having to monitor the process. Specify the source and target languages and choose the appropriate workflow. You can safely ignore the rest of the parameters and click Translate. 3. Using the integration If the integration is created successfully, the content of the folder whose URL you indicated in the settings is synchronized with the current Smartcat project and all the documents stored in the folder appear as Smartcat project documents. After a document translation is completed, return to the integration settings, open the Settings tab, make sure that Push translations back is selected (default) and click Sync Now. The target documents will be pushed to Google Docs and appear in a separate folder in the same location where the original documents reside. If new source segments were added to the integrated space since the previous sync, the Smartcat documents will be updated accordingly. By default, a sync disregards incomplete translations. You can, however, instruct the integration to include them in every sync by enabling the option Publish incomplete documents. For each source document Smartcat will create a folder with a _translations suffix and store the translated documents there. Instead of explicitly performing sync by clicking Sync Now, you can schedule a sync at the required intervals. To do this, click on Do not repeat and select the appropriate option from the drop-down menu.

Configure settings for uploading popular file formats

Upload settings for formats | Smartcat Help Center Smartcat offers different options to process files depending on the original format. Below are some explanations for these options. Excel Generally, processing files using CAT tools required the users to copy and paste content from file to file if only some rows or columns needed to be processed. Smartcat simplifies the process greatly and eliminates the need to prepare files in advance. If you click on an Excel file that was added in the first step of the project creation process, these options will be shown on the right side: You can choose to split segments based on Sentences or Cells.If a cell contained the following content — Lorem ipsum. Dolor sit amet. And you were to choose the “Cell-based” option, you would end up with one segment in the editor:Lorem ipsum. Dolor sit amet.Whereas, if you chose the Sentence-based option, the content would be split into 2 segments: Lorem ipsum.Dolor sit amet.It is generally better to segment by sentences as it is more helpful to your Translation Memory to have smaller segments because you will have fewer matches to entire paragraphs than you would with smaller sentence segments.This option will tell Smartcat whether to parse the excel spreadsheet horizontally (by rows) or vertically (by columns)Determines whether the sheet names are included in the document upload.Determines whether the hidden cells and sheets are included in the document upload.Determines whether the header and footer content is included in the document upload.Determines whether the comments are included in the document upload.Determines  whether the graphics are included in the document upload.Determines  whether the text from shapes is included in the document upload.Determines whether the text from nested presentations is included in the document upload.If you select either the “Upload selected ranges” or “Do not upload selected ranges” you are presented with the following options: In this section, you can decide exactly which portions of an excel file are uploaded or not to the project. To select columns, enter the names of the first and last columns you need, for example, A:H. To select rows, enter the names of the first and last lines you need, for example, 1:50. Or you can use a combination of the two. For instance, if you wanted to translate a document that had columns A-Z and rows 1 through 100 but you wanted to omit column B you would apply the following rules: If you had selected “Do not upload selected ranges” the only column that would be included in the upload of Sheet1 would be column B. You can also create rules for each of the sheets in your excel file: And you can apply separate rules for each sheet like so: Here, in one sheet column, A would be processed and in the other, it would be column B. Smartcat gives you a lot of flexibility to deal with Excel files — no need to hide columns or copy and paste the content to be translated. XLIFF XLIFF is a standard file format used to exchange translation data between tools. They can be produced by Content Management Systems (CMS) or other CAT tools. It is convenient because the file can contain both source and target languages already segmented as well as some information regarding the status of the segments. There are many advanced file options for XLIFF documents when they are imported in Smartcat. Here is a basic overview: (1) This option allows you to choose between keeping the segmentation of the document exactly as it is in the original document by selecting “Like the source file” or splitting existing untranslated segments into sentences by selecting “Additionally segment untranslated units”. This option can be useful if the document was segmented by paragraphs originally since you have better chances to find matches in the TM with single sentences. This will be done automatically during the processing of the file. (2) This option refers back to the first option. If you selected the “Additionally segment untranslated units” option and split the original segments into sentences - the first option would revert the segmentation back to the segmentation of the original file when you export the file. If you select the “No, use Smartcat segmentation” option, the exported file would be segmented in the same way that Smartcat processed it and re-segmented the file. Typically, it is better to revert the file’s segmentation to the original segmentation because otherwise, it could cause problems when the file is reimported by the client. (3) When you import an XLIFF file it may already have translations inserted. If you want to keep these translations, you would choose the “Yes” option. This would be particularly useful if you had translated the file with a different CAT tool and then wanted to assign an editor through Smartcat. If you were to select “No” the translated segments would be ignored and the translation would have to be restarted from scratch. (4) If the file has pre-translated segments this option allows you to choose when the segments are confirmed inside of Smartcat. So for instance, if your project had TEP (Translation, Editing, Proofreading) workflow stages and you selected the option “Yes, at the last stage” the segments would be confirmed as having been Proofread and locked for the linguistic team. If you selected the option “Yes, at the first stage” the segments would be confirmed as having been translated but would still require Editing and Proofreading confirmation. If you select the option “Yes, for segments with the status:” it will open a popup as shown below: Here, you would be able to customize the confirmation of segments based upon their status as indicated in the XLIFF file and their workflow stage in Smartcat. For example, in the screenshot above, segments with the "final" status in the XLIFF file would be approved as Proofread in Smartcat. Segments with the status "translated" would be approved only for the translation stage. (5) This option allows you to completely lock segments so that no further action can be taken. If you select the “Yes, with statuses:” option then a popup will open displaying the statuses shown in the previous picture. You will be able to select specific statuses and when Smartcat parses the document it will lock all the segments containing matching statuses as the ones you selected. If you were to choose the “Yes, with translations inserted from file and confirmed” option then the segments which had been confirmed through (4) would also become locked. (6) Although it is not common, checking this box off will allow the use of intersecting tags as shown in the help text: (7) Placeholders are used to protect part of the text that should not be translated. See our article about placeholders for more information. (8) This is not used when processing XLIFF files. (8) This is not used when processing XLIFF files. XML There are several different types of XML file parsing methods that Smartcat handles besides the powerful flexible XML method : The structure of files varies depending on the types of tags you expect to see in the file type. With XML you are free to create whatever tags you would like to create. This can cause difficulty in the parsing of the file so each of these parsing methods follows a standard of expected tags based on the XML type. For instance, in a standard HTML document, you would expect to see(Paragraph) tags but in a DITA XML file you can expect to find predefined tags in the DITA standard such as which is shown below: By adhering to these standards the file can be parsed appropriately. For instance, in the example above the document might split segments when it hits the opening tag, but because the tag is recognized by the DITA standard, the segments are not inappropriately divided here. If you choose DITA or standard XML you will see another dropdown with the following options: They allow a user to split segments either by sentences or by tags and attributes. For instance, you may have multiple sentences contained within a paragraph tag:<p> Lorem ipsum. Dolor sit amet. </p>If you choose T ag and attribute-based, you will end up with one segment:Lorem ipsum. Dolor sit amet.Whereas, if you chose Sentence-based , the text will be segmented as follows:Lorem ipsum.Dolor sit amet.As with the other format, it is generally better to segment XML files by sentences as it is more helpful to your translation memory to have smaller segments. You will have fewer matches to entire paragraphs than you would with smaller sentence segments. (1) Some Content Management Systems (CMS) will use CDATA sections and in these CDATA blocks, they will store sections of HTML code. If you select this option, Smartcat will first parse the entire document and then go through the CDATA blocks and parse those sections again to look for HTML tags to protect them.(2) By using placeholders (see our Placeholder article), you can import and protect variables contained in XML files. PDF When you add PDF files (or any graphic files) to a project, the files are first processed using Optical Character Recognition (OCR) to extract the text to be translated as well as maintain the format whenever possible. There are very few Advanced File Options for a PDF file like using OCR or not and checking the source layout. Please note that the file should not exceed 30 MB in size to be recognized. If your PDF is too large, consider splitting it into smaller parts, and upload as separate PDF files to avoid error. PowerPoint The PowerPoint advanced file options can be seen here: These options are fairly straightforward.(1) allows you to upload slides even if they are hidden.(2) allows you to upload the notes section of each slide.(3) allows you to upload spreadsheets that have been inserted into the PowerPoint presentation. Word (DOCX) There are only two unique options for Word files as shown below: (1) allows you to upload text from a Word file even if it is hidden.(2) allows you to upload the comments from a Word file.

Translate marketing images with AI (Image Translation 2.0)

Translate marketing images with AI (Image Translation 2.0) Overview Image Translation 2.0 uses generative AI to create commercial-quality, translated images that require zero design adjustments. Instead of the traditional OCR-based workflow that requires manual editing of fonts, positioning, and layout, this new pipeline automatically preserves your original style, fonts, and visual identity. The generative pipeline processes images through three stages: Text extraction: AI analyzes the image and extracts text blocksTranslation: Text is translated using your glossaries and Translation MemoryImage generation: AI generates the final image while preserving the original brand style ———————————————————————————————————————— When to use it Use the generative image translation pipeline when you need to: Translate marketing banners and ad creatives for international campaignsLocalize social media graphics for Instagram, Facebook, or LinkedInTranslate images embedded in e-learning courses and training materialsProcess product packaging graphics and labelsTranslate infographics and visual content while maintaining brand consistency 💡 This pipeline works best for marketing and visual content where preserving the original design style is important. For document scans and screenshots, use the traditional OCR pipeline instead. ———————————————————————————————————————— How to use it Select the generative pipeline during project creation Create a new project in your Smartcat workspaceNavigate to the image upload wizardIn the What kind of images to translate? dropdown, select Marketing & Visuals. This activates the generative AI pipeline ⚠️ Selecting Documents & Scans uses the traditional OCR pipeline Upload your images (banners, graphics, marketing materials)Configure your translation settings, including target languages, glossaries, and Translation MemorySubmit the project for processing The system processes your images using generative AI to extract, translate, and regenerate the content. Review and edit translations Open the translated image in the CAT editorThe image preview displays the original image initiallyReview the translated text in the segment grid ⚠️ Layer editing tools (Move, Resize, Font Select) are not available with the generative pipeline Edit text directly in the segment grid if needed. The system displays a soft warning if translated text is significantly longer than the originalOnce all segments are confirmed, click Update to regenerate the preview with your changes The preview updates to show the AI-generated translated image. Download the final image Confirm all segments are completeClick Done and Download to generate the final image ⚠️ Final generation may take up to 30 seconds If the AI output contains errors, click Regenerate to create a new version Your translated image downloads with the original style, fonts, and layout preserved. Requirements Project must use the Marketing & Visuals image type selectionGlossaries and Translation Memory are recommended for consistent terminologyAll segments must be confirmed before generating the final image FAQs What's the difference between Marketing & Visuals and Documents & Scans? Marketing & Visuals uses the new generative AI pipeline that creates complete translated images preserving your brand style. Documents & Scans uses the traditional OCR pipeline with manual layer editing tools, which is better suited for document screenshots and scanned content. Can I edit the font, position, or size of text in the generative pipeline? No. The generative pipeline does not support manual layer editing. The AI automatically handles font matching, positioning, and sizing to match the original image style. If you need manual control over these elements, use the Documents & Scans pipeline instead. What happens if the translated text is too long? The system displays a soft warning when translated text is significantly longer than the source. The AI attempts to fit the text appropriately, but you may need to shorten the translation or use the Regenerate button if the result is not satisfactory. How long does final image generation take? Final image generation typically takes up to 30 seconds. The Done and Download button triggers the AI to create the final high-quality output. Can I use glossaries and Translation Memory with this feature? Yes. Glossaries and Translation Memory are applied during the translation stage to ensure consistent terminology across your images.

Translate any file in any language with Smartcats AI in 3 steps

AI translation in 3 steps | Smartcat Help Center Your brief 3-step guide to AI-translate any file in any language with Smartcat With Smartcat you can translate hundreds or even thousands of pages in a matter of seconds using Smartcat's AI automatic translation. And your page layout format stays intact too. So a translated PDF file, for instance, will look the same as your original PDF file in the source language. Translate any file in Smartcat in three easy, quick steps Follow these steps to AI-translate any document in Smartcat in a few minutes. Step 1: Log in and start a new translation task Log into your Smartcat account and click Translate a file, as shown below. If you don't have an account yet, create your free trial account in a few seconds. Step 2: Choose languages and upload your documents You are now on the Translate a file settings page, as shown below. I. Choose your language pair - source and target languages II. Upload or drag-and-drop your file(s) III. Click Translate files Step 3: Download, edit, and share your translation Most AI automatic translations on Smartcat take seconds. Once complete, it's up to you what to do next. You have a few options. A. Download your AI translation immediately Download and use it immediately in your preferred file format by clicking on the icon with three dots on the top right. B. Share your translation Share your translation with your own team or external translators by inviting them to work on it via the Share button. Once you click on Share, you will see the following screen, where you can input collaborator email and decide permission privileges. C. Hire a professional editor on Smartcat Marketplace Invite a Smartcat Marketplace linguist in your translation's language pair to review and edit your AI automatic translation. You can choose manually or use AI matching. With AI matching, Smartcat pairs you with a best-match human professional linguist in seconds. You'll then be able to hire subject matter experts from the world's largest vetted marketplace to review and edit your AI automatic translation! With Smartcat AI matching, the hard work's done for you as Smartcat AI pairs you with the top-match linguist in seconds according to your translation requirements! Now you should be able to translate any document on your Smartcat account.

Accept your project

Accepting your project Response to the invitation Have you been invited to a project? Congrats! Improving your profile has indeed paid off. Now it’s your move! Respond to the invitation by accepting or rejecting it. Don’t leave the customer hanging.Study the project details including net rates for repetitions and matches, payment terms, and other information.If you have any questions, you can contact the customer using the built-in chat. Getting started Does the job look appealing? Go ahead and take the opportunity then. First, accept the invitation. Depending on the project settings, you either will be able to start right away or will have to wait for the customer’s approval. Once you’re approved, you will receive a notification about that. Linguists use the Smartcat Editor to work on translation projects whether a project is assigned or created by a linguist. The Editor is a convenient tool that breaks documents into manageable segments. You can view the original text in the left column while translating in the right column. Once you have done translating a segment, you need to mark it as confirmed (the corresponding hotkey is Ctrl+Enter). Please keep in mind that in projects with several assignees, the first one who confirms a segment will be paid for that segment. Let the client know if you have spotted an error in the original text while translating to point it out. This will also show the client that you care not only about the quality of your work but also about the quality of the client's project. Some projects may include translation memories and glossaries, which output, as well as comments, can be viewed right in the Editor. Do not use AI translation unless you are working on the post-editing of AI-translation output. By the way, you can check the project statistics anytime right on the project page. (Here is more about statistics and cost calculation). Completion Once you have completed the task, you are welcome to get in touch with a client via the built-in chat. Clients have to accept your work before they could form an invoice on their end to pay you. You may need to reply to a few questions or make some adjustments before a client confirms that the task is completed. Getting paid Payment will be made as outlined in the project details. You will receive your earnings within 5 business days after a client successfully processes the payment to Smartcat. Make sure that you have selected a payout method that works for you to receive earning on the My Payouts page. Payment disputes It's important to check a client's dispute resolution policy for missed deadlines or low-quality translation on the project page. FAQ I cannot complete a project or document. What should I do? If you cannot complete a project, it means that one or a few segments are still not confirmed. In this case the button Done is inactive, and a document (and a project as well) does not change its status to Completed.To check if there are any unconfirmed segments, you can use the hotkey F9 in the Editor or the button Go to the next unconfirmed segment on the tool panel. What is the right way to accept a job invitation? Before you agree to participate in a project, we suggest you do the following:Review the document for possible errors that can hinder your work and if there are any, notify the client about them. Estimate the word count and determine how much you can translate without compromising on quality. The client can assign the rest of the text to another translator thus speeding up the process.Discuss special terminology with the client, if you found any. You can also ask for a glossary or other reference material. Before getting started, discuss the deadline, cost, and volume of work to be completed. Ask if there are any special requirements that may affect these aspects. If multiple participants will be working on the same document and the segments will not be split between them, ask the client to provide a list of segments assigned to you.If it was the client’s choice to use AI translation in the project, ask them via built-in chat whether they expect post-editing of AI translation output or unaided human translation from scratch. Please avoid using AI translation without prior approval from the client. 

Resolve file upload issues

File upload issue resolution | Smartcat Help Center Below you'll find the common reasons why Smartcat fails to upload your files.File size. Smartcat supports files of the following formats not bigger than 6 GB so there maybe issues when uploading .docx and .pptx files of substantial size. Files exceeding the maximum upload limits cannot be processed. Smartcat's file size limits are:Document/Project files: 6 GBReference Files: 4 GBTranslation Memories: 1 GBGlossary imports: 10 MBMost files under 6 GB should upload successfully, but large files may take longer to process. For optimal speed, consider splitting very large files (greater than 1 GB) into smaller parts, removing unnecessary embedded media, or compressing images within documents. 2. Image size. If your document is larger than 100 MB (for non-image PDFs) or contains images larger than 30 MB for OCR text extraction, you may encounter upload issues. Solution: Split the document into smaller parts. You can use PDF tools for editing documents, for example, PDF-XChange Editor, Adobe Acrobat and others. 3. Parsing error. The platform may be unable to recognize the content of the slides. Solution: exclude all extras (e.g. hidden slides, slide masters, etc.) when loading the file into the project. To remove these elements you can also convert your presentation to *.pdf, then back to * .pptx. 4. Text export error. Your text can contain elements Smartcat can't recognize. Solution: Modify the original document and delete elements like:invalid characterslarge pictures or videos that can cause presentation to freezeshapes and objects that differ from the rest visually or by some attributesgraphs and diagrams. Protected PDF files. Password protected or secured PDF files cannot be processed normally.  Solution: Remove password protection before uploading, orUpload-as-is, which results in image-only processing consuming 1 Smartword per image pageContact support if you cannot remove protection but need text extraction API upload errors. You receive 500 errors or timeouts when uploading files via API.  Solutions:Ensure file size is under 6 GBCheck your API authentication credentialsTry uploading smaller batches if processing multiple filesContact support with your API request details if the error persists FAQ Can I process TS files in Smartcat? TS files cannot be processed natively in Smartcat but it is possible to convert them using a free app called QT Linguist which is part of a larger development framework but can be installed separately. Using QT Linguist, these TS files can be converted to XLIFF which can be processed using Smartcat. Upon translation, they can be converted back to TS format using QT Linguist.QT Linguist can be downloaded from here. Is it possible to upload .jpg file for reference? You would like to upload screenshots for reference, and they are in the .jpg format. There are 2 options:You can add these files as reference to the project as described in Can I add reference files to my project? This is the easiest and fastest process but when dealing with references such as screenshots, it might create some work for the translation team to find the image that corresponds to the string being translated.You can upload individual graphic files for each segment where needed using the Camera [Alt-Insert] button in the toolbar. A picture icon will be displayed in the segment and the translator will be able to click on the icon to show the screenshot. This process takes longer but creates more targeted references. This feature needs to be enabled in the account, it is not enabled by default. Why does my .pptx file fail to process even though it's under 6 GB? Complex elements like embedded Excel graphs, advanced math formatting, or SmartArt objects can cause processing failures. Try removing these elements or converting to PDF first.  Can I upload subtitle files (SRT/VTT)? Yes, but ensure proper segmentation. Each subtitle segment should align with your translation workflow requirements.

Articulate Storyline Translation

Articulate Storyline Translation Overview Smartcat supports native translation of Articulate Storyline files, enabling users to localize full packages without exporting and re-importing XLIFF files. Instead of translating Storyline course content outside the original format, Smartcat allows you to upload Storyline files directly into a project and translate them with slide preview context in the CAT editor. This helps translators and reviewers understand how content appears within the course while translating. The workflow also supports translating images and videos, helping teams localize complete training experiences more efficiently. This functionality reduces file import errors, avoids fragile tag handling, and shortens review cycles when localizing Storyline courses. The Smartcat Storyline preview helps users understand context and verify text placement for the translated content without having to switch between platforms. Smartcat supports translation and review. Structural edits such as creating new slides or scenes should be done in Storyline. Subtitles translation with Storyline files - Watch Video When to use it Use Storyline translation with visual preview: Translate Articulate Storyline courses into multiple languagesProvide translators with visual slide context during translationLocalize images or embedded videos within training contentReduce issues caused by XLIFF export/import workflowsImprove review efficiency for complex interactive courses How to use it Select the Learning Content Agent in the platformCreate a Smartcat project .Upload your Articulate Storyline file to the project.Select the assets you want to translate: 1. Text segments 1. Images 1. Embedded videosOpen the file in the CAT editor.Translate the text while using the slide preview to see the content in context.If needed, translate images by using the slide preview to navigate between the slide and the CAT segments.Optionally translate subtitles or dubbing for videos.After translation and review are complete, export the translated file.Import the file back into Articulate Storyline for final adjustments and publishing. Requirements and limitations Requirements Articulate Storyline fileAccess to a Smartcat workspace and projectStable internet connection for previews and asset processing Limitations Audio files inside Storyline are not supported yet. Audio must be translated separately and reinserted into the course manually. FAQs Why use native Storyline file translation instead of XLIFF? Traditional XLIFF workflows can introduce fragile tag handling and provide limited context for translators. Native Storyline files support allows translators to work with slide previews and assets directly, reducing errors and review cycles. Why does the preview sometimes look different from Storyline? Smartcat provides a static preview to give translation context. The final layout and animations are handled inside Storyline after export.

Smartcat Subtitle Editor: Universal Guide for All Types of Teams

Smartcat Subtitle Editor: Complete Guide Explore our interactive demo to learn how to use the Smartcat Subtitle Editor. Accessing the Subtitle Editor You can open the Subtitle Editor from different areas of your workspace, depending on your role and workflow: Organizations and LSPs :You can access subtitle files from the Files, Tasks , or Overview pages in your project. Click on the subtitle file you want to work on to open it in the editor. Freelancers:You can open the subtitle file by accessing the details of the incoming task Subtitle Editor Layout There are both languages in two parallel columns in Subtitle Editor, the source text on the left and the corresponding translation on the right shown in so-called “cues”. In the Subtitle Editor, we prioritize dividing text into cues with specified durations rather than full sentences. This approach optimizes subtitles for readability, synchronization, and audience engagement. Note that the source text is non-editable and serves as a reference for creating accurate translations. On the far right, you'll find the preview area and the timeline panel. The timeline panel shows how subtitles are distributed over time, providing a clear visual representation of their placement and duration. For organizations: To manage multiple target languages, click the “Language selector” and switch between versions. The preview area lets you see how subtitles align with the video, while the timeline panel shows how subtitles are distributed over time, providing a clear visual representation of their placement and duration. Below the preview area is the Settings section, where you can configure parameters such as CPS (Characters Per Second) limits, ensuring consistent quality across the subtitle file. {Note: These settings are applied locally on a user’s level.} How to work with cues in Subtitle Editor All your work takes place on the right side of the Editor. Here you can add, edit and review translations. To make edits in the cue, simply click on its text and apply the necessary changes. If the subtitles are not aligned with the video, you can easily adjust their start and end times to control their duration. Each cue has a CPS (characters per second) value, which indicates whether the reading speed is too high and whether the subtitles may not match the timing and need to be modified. CPS limit value can be changed in the Settings tab. If you think a multi-line cue should be split into separate cues, no problem! Simply click the 'Split by lines' button, and it will divide the cue into the exact number of lines you have. Remember, to create multiple lines within a cue, press the Enter button. To split a multi-line cue, click the Split by lines button. Press Enter to create multiple lines within a cue. Need to merge cues, delete existing ones, or add new ones? It's easy! Just click the Dots button and select the desired option from the dropdown menu For a faster experience, simply hover over a border and click the Insert cue button. Track your progress When you’re satisfied with a cue translation, mark it as processed. Don’t worry — it’s possible to continue editing the cue if you spot areas for improvement, right up until you click the “Mark Processed” file button in the control bar. Track your progress by clicking on the Progress button, which will show how much of the file you have completed working on. What to do when you are done When you believe that the translation of the file is ready click the “Mark Processed” button in the control bar to finish working on the subtitles. Note that you can use this button even if no cues have been marked as processed. If you’re not ready to finish the task, you can export the subtitle file by clicking the Download button above the language version and choosing your desired file type. Subtitle files can be exported in two file formats: SRT and VTT. Get translated video To get a video in another language (one of the target languages of the project) or dub with AI voice, simply select the desired language in the selector under the Preview section. After that preview AI voices and select the appropriate one. Select another AI voice and preview your video with it. Once you're happy with the result, click the Download button above the video preview. You can choose the output parameters for the video: Keep the selected AI voiceBurn-in subtitles in your chosen language onto the video This allows you to create any combination of voiceover and subtitle languages in the final file. After selecting your preferences, confirm and start the export.You can preview the completed video with embedded subtitles. If everything looks good, click the Confirm button to save the final version to your computer.

Use flexible XML parsing methods

Flexible XML parsing methods | Smartcat Help Center It's common knowledge that sometimes preset XML parsers do not allow accomplishing the desired outcome like uploading only specific strings and elements for translation or adding IDs and length limits for segments in the CAT Editor. With the Smartcat flexible XML parser, you can set models for each case you have to deal with. The first thing to do is to check the Settings section in your account then go further to File Formats where you will find the settings. Secondly, you should set models here to be able to apply them for documents you are planning to upload. Of course, you may set several models that match requirements for this or that project. Before rushing to set new XML models, it's better to check the XPath syntax since the system will be looking for paths to elements in XML files according to it. Another thing to employ is a test environment that will indeed help to try out whether a model works or need to be adjusted. Be sure that Xpather will do the job. Setting a custom XML parsing method The form for setting a model has a few fields, some of them are optional while two are key and therefore mandatory. Let's begin with them. Import setting name: The name of a future parsing method. Segment-forming elements: This field is used for setting a path to XML elements you want to put in the Editor. You may set several more than one element that the system looks through a whole document.For example, the path //test-string or /test/test-string display the string Translate me from the XML file below: It's not possible to save a model without filling in, at least these two fields. Let's move on to the optional fields and checkbox. Besides the core fields, you may set the paths to translatable and untranslatable nodes, string IDs, comments, and length limits. Another available setting is whether you want to protect HTML tags in CDATA sections, which we will cover later. Translatable text: Segment-forming elements comprise nodes — other elements, their attributes, or text that can be translated. That being said, the setting is relative to segment-forming elements and are searched for within only the elements set there. More than one path could be set as well. Example: The XML file has an element test, an attribute attribute-1 , and another element test-string. Two segments will appear in the Editor: Translate me and Well. Untranslatable inline elements: It's optional to set a path to an element that you don't want to translate; thus, the element will not get to the Editor. The element's content will be marked as a tag in the Editor. More than one value can be set in this field too. Basically, the setting makes it possible to not show technical pieces or else that you don't want to translate. Here is a simple example: String ID: The field allows selecting a unique node that will be used as a segment ID in the Editor. Even though the setting is optional, it's a powerful tool that lets you update a document keeping the segment revisions as well as assignments. Only one node can be specified. Important: The field value has to be unique for each segment within the file. In the example below, the path to the attribute ID of the element test-string is used as unique identificator in Smartcat. As you may see, the segment has the ID placed at the bottom. Comments: The field, which you may use for adding comments that will be shown in the Segment comments section in the Editor. It's possible to set more than one comment.Example: Segment length limit: Here it's possible to set the path to a node, which should be an integer of the string type. The integer will indicate how many characters are possible to write in a segment. Only one length limit can be set. In the following example we are going to use these settings: Segment-forming element: //test-string Segment length limit: @max A linguist who is working on the segment cannot confirm it if the length of translation exceeds the limit. Protect HTML tags in CDATA sections: Depending on whether the box marked or not, HTML tags will be shown as an editable piece of text of substituted by Smartcat tags. Without protection, tags and the text within will look like this text within will look like this <br>text</br>. If tags are protected, Smartcat tags substitute HTML ones . It is worth mentioning that for the successful use of the custom XML parser in Smartcat, files must contain repeating elements, each of which, in turn, will be turned into a source segment.

Translate memoQ documents in Smartcat

Translating memoQ docs | Smartcat Help Center To translate memoQ documents in Smartcat, do the following: Export files from memoQ To do this, select the desired files and click Export Bilingual in the context menu.Choose memoQ XLIFF and click Plain XLIFF for other tools. Upload the obtained.mqxliff files in Smartcat Create a Smartcat project or add files to an existing project. Note that the language pair of the Smartcat project must match the one of the memoQ document. You can configure the following settings when importing the document: (1) This option allows you to choose between keeping the segmentation of the document exactly as it is in the original document by selecting “Like the source file” or splitting existing untranslated segments into sentences by selecting “Additionally segment untranslated units”. This option can be useful if the document was segmented by paragraphs originally since you have better chances to find matches in the TM with single sentences. This will be done automatically during the processing of the file. (2) This option refers back to the first option. If you selected the “Additionally segment untranslated units” option and split the original segments into sentences - the first option would revert the segmentation back to the segmentation of the original file when you export the file. If you select the “No, use Smartcat segmentation” option, the exported file would be segmented in the same way that Smartcat processed it and re-segmented the file. Typically, it is better to revert the file’s segmentation to the original segmentation because otherwise, it could cause problems when the file is reimported by the client. (3) When you import an XLIFF file it may already have translations inserted. If you want to keep these translations, you would choose the “Yes” option. This would be particularly useful if you had translated the file with a different CAT tool and then wanted to assign an editor through Smartcat. If you were to select “No” the translated segments would be ignored and the translation would have to be restarted from scratch. (4) If the file has pre-translated segments this option allows you to choose when the segments are confirmed inside of Smartcat. So for instance, if your project had TEP (Translation, Editing, Proofreading) workflow stages and you selected the option “Yes, at the last stage” the segments would be confirmed as having been Proofread and locked for the linguistic team. If you selected the option “Yes, at the first stage” the segments would be confirmed as having been translated but would still require Editing and Proofreading confirmation. If you select the option “Yes, for segments with the status:” it will open a popup as shown below: Here, you would be able to customize the confirmation of segments based upon their status as indicated in the XLIFF file and their workflow stage in Smartcat. For example, in the screenshot above, segments with the "final" status in the XLIFF file would be approved as Proofread in Smartcat. Segments with the status "translated" would be approved only for the translation stage. (5) This option allows you to completely lock segments so that no further action can be taken. If you select the “Yes, with statuses:” option then a popup will open displaying the statuses shown in the previous picture. You will be able to select specific statuses and when Smartcat parses the document it will lock all the segments containing matching statuses as the ones you selected. If you were to choose the “Yes, with translations inserted from file and confirmed” option then the segments which had been confirmed through (4) would also become locked. Importing the translated document to memoQ When you have finished working with the document, export the translation from Smartcat and import it to memoQ by using the Import/update bilingual button or the Import menu. Choose Update as the action to be performed on the document.

Show more