No announcement yet.

READ before and after taking the test - Updated Proofreaders Guide!

This topic is closed.
This is a sticky topic.
  • Filter
  • Time
  • Show
Clear All
new posts

  • READ before and after taking the test - Updated Proofreaders Guide!

    So, after reading Claudia's thread, and before starting with the PR test (or to proofread, in general) you should consult the following guide, which is a summary and an update of this other guide (credits to Claudia, Ivries and Enkida).
    Any suggestion can be made in that thread.

    Proofreader Senseis = Enkida and Toady.

    The Proofreader's job is to:
    • Check for errors in grammar, flow and punctuation in the translated script.
    • Check the raws together with the script to make sure the translator hasn't missed a bubble translation.
    • Check that the page numbers in the script coincide with the pages in the RAWs, or with the cleaned file, if it is numbered differently from the RAWs.

    All proofreaders should submit their proofread script as soon as possible, write a post in the appropriate thread to indicate they are working on it, and another post when they've finished.

    If someone has more than one project and they all come at once, no one will spank you to deliver them all at the same time, but don't keep us waiting for too much.

    If, at some point, you need help or cannot meet deadlines, inform the QC of your project or an admin. If you are going to be absent for many days, write a post in the absent thread.

    You can also join our Discord channel to speak with an admin or consult the TL in a faster way. However, note that not all of the staff is on Discord, and that forum posts remain mandatory.



    1. Write your name on the PRed document, just below the TL name.

    2. Change the font to Courier New. It is one of the most used monospacing fonts, so, for the sake of uniformity, no other font is accepted. Not doing so in the PR test will be considered a serious mistake, since it is specifically requested.

    3. When proofreading, highlight with blue text whatever changes you make to the script.
    For example:
    If a bubble says:
    Hello you spoke England very best.

    Leave the translation intact and add a new line below it, in blue text, which will be your correction to the translator's writings. As in:
    Hello you spoke England very best.
    Hello, you speak very good English.

    4. When you are finished with whatever project you are currently working on, place it on the FTP in the appropriate script folder (after renaming it to <*filename*_PR>), and then make a post on the status thread of your project.
    This way, the typesetter/editor knows that the proofread chapter is ready for typesetting.

    5. The format of the proofread file should be in .rtf (Rich Text Format), .doc or .docx



    1. Do not use unnecessary quotation marks when you make your corrections according to the format.
    I good at English.
    My English is good.
    I good at English
    "My English is good."

    It is hard for typesetters to read it. To emphasise something, make it bold, instead.

    3. Don't double space between your sentences.
    You'll anger the typesetters, and you won't like them when they're angry.

    4. There are only 3-period ellipses.
    Always... No Matter What...
    (Let's cut the typesetters some slack)

    5. There is always a space between an ellipsis and the following word, even when the ellipsis is at the beginning of a sentence (usually, this happens when a sentence starts in a bubble and ends in another).
    I...wanted to apologize. <----wrong
    I... wanted to apologize. <----correct

    6. Every bubble must have some kind of punctuation mark in the end.
    (May it be "." or "," or "..." or ";" or whatever~) This makes it easier for QCers not to make a mistake.
    However, putting a grammatically incorrect comma or other sign of punctuation at the end of a sentense is a serious mistake. In such cases, consider using an ellipsis.

    7. SFX written in bubbles ALWAYS end with an appropriate punctuation mark.

    8. All SFX must have the format: SFX: blabla
    They shall not be written *blabla*, sfxblabla nor any other thing.
    When a translator writes:
    SFX: walking noise
    You must convert to:
    SFX: step

    9. Some text issues:
    ?!... <----wrong
    ...?! <----correct
    !? <------- wrong
    ?! <----correct
    However, if a cleaner didn't clean an interrobang because it was the only thing in a bubble, leave it as it is. No one will come after you with a pickaxe (why a pickaxe? Don't worry about such details...).

    10. Look out for "special symbols/characters" that MS Word might change/insert/whatever.
    Basically, if you see a strange symbol which makes no sense, erase it and check the sentence to see if something is missin.

    11. Honorifics.
    When the dialogue insist on having honorifics for the names such as -chan, -kun, -sama etc.
    You correct the names like this: Mungen-sama or mach-kun or Oskye-chan
    and not oskyechan.

    12. Missing Bubbles
    You need to check the script and perhaps count the bubbles and what the translator has translated for every page to make sure there is not a missing bubble translation in the script.
    ---> When you find a missing bubble note it down on the proofread script. Then you can post in the status thread so the translator sees it and look it up, or you ca write to the TL on Discord. The working relationship between TL and PR is different for everyone. [/quote]

    13. Check if there is a "cheat sheet" or a "character guide" in the script folder on FTP. If there is, DOWNLOAD AND USE IT! If not, create it.
    This (usually .txt) document should contain enough background information / character names to help familarize you with a series if you happen to be asked to sub it or pick it up midway through. This is especially important to create continuity with character names between proofreaders, given, particularly the Chinese and Korean comics we do.

    Also, should your TL introduce a new character to the series that isn't mentioned in the cheat sheet, for the love of continuity, UPDATE THE CHEAT SHEET! Add the date it was last modified, the new character's name, and then overwrite the former cheat sheet so that the next proofreader can continue to correct things properly without having to backread an entire series to double-check the names of the characters.



    As stated at the beginning, a proofreader's main job is to fix a translator's script to Standard English.
    There are two main elements in this.
    1. Mechanics
    Fix ALL spelling/grammar mistakes. Check for correct punctuation, verb tense, proper word usage. Did your translator forget to punctuate? Misuse the subjunctive? Use the wrong preposition/verb tense/part of speech? That becomes YOUR job, for every single line. Does the script mix up it's/its? your/you're? their/there/they're? It's your job to fix!
    2. Flow
    Re-write awkward portions so that they read smoothly/naturally. This can be tricky, as sometimes you'll need to adjust the tone; in this respect, always look at the RAWs while proofreading, and know who the characters are. If it is polite, suave character speaking, he/she will probably not say "The meat was soooo yummy!". If you see that in the script, it is your sworn duty to change it to something like: "The meat was rather tasty" or "quite good".
    If you're unsure of the meaning, or if you believe you are making considerable changes, speak with the translator. They don't bite, usually...
    Another Flow example: If the translator says:
    However! We must not let that happen
    you must convert it to something like:
    However, we must not let that happen!
    Sometimes, doing so will mean breaking grammar rules. Loach of Chaser isn't going to speak with perfect grammar. Shiho of BLAST likes to say "gotta" and "the hell?!" Every now and then, you might even have to (GASP) split an infinitive. This is mostly dialogue--not your PhD dissertation. When people talk in real life, they speak in fragments and slang and non-standard contractions all the time ("What're you PR-ing next, fool?"/"I gotta do Under Prin."/"Word."). Make sure the script sounds like something the character would say.
    Flow can be tricky if you don't know how much you can change the script without messing with the integrity of the translation. That's when Part II becomes important...
    P.S. Punctuation is extremely important and should not be omitted. Remember that punctuation saves lives: "Let's go eat grandma" makes you a cannibal; "Let's go eat, grandma" makes you a nice grandson/granddaughter.

    So you're a PR, and you can barely tell Korean/Chinese/Japanese apart. Why should you have to check the raws??
    1. Make sure there aren't any missing bubbles in the script. If you find any, alert your translator (page #, bubble #, who's speaking, etc).
    2. Checking raws helps you fix the flow. Another lame example:
    Let's say you have the following picture --

    Translator's script says: Wish you didn't do!
    Newbie PR might say: I wish you would not do that!
    Pro PR who checks raws might say: What the hell are you doing?! <--- This is what we want.

    The last sentence fits the context much better and it gives the script a better flow.
    As a PR, You can change the words completely if it'll convey the meaning more effectively. You have that much power, wield it responsibly. Still, always talk with the TL.

    In case of doubt, you can consult with another PR. Better to ask than to make a mistake.
    Last edited by Shaka; 09-27-2019, 01:29 AM.

    Believe nothing, no matter where you read it, or who said it, no matter if I have said it, unless it agrees with your own reason and your own common sense.
    Siddharta Gautama