Jump to content
💬 Smartcat Community

Search the Community

Showing results for tags 'qa'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Forums
    • Smartcat talks
    • Introduce yourself
    • Translating & freelancing
    • Managing projects & running an agency
    • Linguistic discussions
    • Anything
    • Archive


  • Smartcat Freelancer Essentials
  • Smartcat Tips and Tricks
  • Smart Agents
  • Senior Blitz!
  • Smartcat Wave


  • Senior Blitz!


  • Contests
  • Webinars
  • Webinars (RU)
  • Meetups


  • Collaborations
  • Private Teams

Found 4 results

  1. User Script for Better QA Usability

    Hello everyone. I've been using Smartcat for a year already and got to know some of its pros and contras. One of the features I'm not quite happy about is QA: the default interface is hard to use during the whole day when you are working with dozens and hundreds of pages. While the interface cannot be customized via settings, it can be improved by using user scripts. Before: After (image scaled, text size is the same as in the image above): The script uses the current browser window size to change the QA window size dynamically. I'm not a programmer so the changes are limited to increasing the window size and dimming/hiding some unnecessary text strings. How to: 1. Install TamperMonkey extension to your browser. From Chrome: https://chrome.google.com/webstore/detail/tampermonkey/dhdgffkkebhmkfjojejmpbldmpobfkfo For Firefox and other supported browsers: https://tampermonkey.net/ 2. After installation, there will be the extension icon on the browser’s toolbar: 3. Left-click the extension button –> Create a new script… Delete all text in the script editor window; copy the required script text (I've added it below) and paste it in the script editor window, then save it (click the floppy disk icon). 4. Reload the browser tab where you are viewing your projects. If everything was done correctly, on the extension icon there will be a red square with the number of scripts running on the current page (1 by default): The script: // ==UserScript== // @name Enlarge QA window in SmartCAT // @namespace http://tampermonkey.net/ // @version 0.2 // @description Larger QA window in SmartCAT project error search, autoenlarge error frame // @author Alexey Kushnirov // @match https://smartcat.ai/Workspac* // @match https://smartcat.ai/workspac* // @match https://smartcat.ai/Project* // @match https://smartcat.ai/project* // @grant none // ==/UserScript== (function() { 'use strict'; function addGlobalStyle(css) { var head, style; head = document.getElementsByTagName('head')[0]; if (!head) { return; } style = document.createElement('style'); style.type = 'text/css'; style.innerHTML = css; head.appendChild(style); } addGlobalStyle('.x-segment-tinymce-editor{min-height:50px}'); addGlobalStyle('.l-qa-check-report-scroll { overflow-y: scroll; max-height: 70vh; width: 100%;}'); addGlobalStyle('.l-qa-check-report-popup {width: 90%;}'); addGlobalStyle('.l-qa-check-segment-text-header {height:1px; COLOR: #EFEFEF}'); addGlobalStyle('.l-qa-check-documentTitle-column {COLOR: #EFEFEF}'); })(); Known issues: If you open the QA window and Smartcat shows a notification at the same time, the QA window may look distorted. Just close it by pressing Escape, close the notification and open QA again.
  2. Most of you must have noticed that simple typos pass you by even though you've read your text fifteen times, under certain circumstances. That's also why it's a good idea to get someone else to proofread your own work, or other alternatives. But that's another matter. I want to share with you why that can happen in the first place. The essence of this small post on Wired, by Nick Stockton, is that our brains are optimized in a certain way to derive important meaning from what is around us. When we, ourselves, made something, that something is familiar, and thus the brain, in order to consume less power, doesn't pay that much attention to the details. And in order to make yourself more efficient in catching in your own mistakes, there are a few dissociative techniques you can use. The one recommended: I'll look for more information to share on this to help you cheat this. Meanwhile, feel free to share your own techniques, or talk about your sad & funny experiences in correcting your own work.
  3. Yesterday we spoke about why catching your own typos can be difficult and we glazed at the idea of how you can dissociate yourself from your own writing in order to do a better job in the proofreading run(s). Today I'm giving you a few tips from a writer, Leah McClellan, on how to do better in catching mistakes. The first portion of the post is mostly for the writing professional (though I'd argue that translation is a fairly lot like writing, if not writing mutated), but I'll be mostly skipping them here and go straight for the tips. You can read the entire post here. And from the previous share, we have a couple more techniques (though similar in nature): - Change fonts and color from your work. - Read out loud, and even read backwards, from @Jane Ruessmann. Additionally, the post gives you some resources to polish your grammar skills at the end! I believe you don't need to employ all of these techniques. What you have to do is find one, two or even three that you feel are adequate for you, and stick with them. Whatever works better to distance yourself from your translation. Then proofread. Impeccable writing must follow!
  4. When you confirm a segment after you translate it, SmartCat will display a warning icon in case it finds an error. If you click on it, you can see the type of error and you can choose to fix it or ignore it if you see it's not a real error. Now, I was wandering if I can set SmartCat to ignore certain types of errors automatically. For example, "source and target are equal" or "the segment starts with two capital letters."