Visual editor

The Visual Editor handles all the image work alone: cleaning, balloons and typesetting are done by one person. It is used in small-team workflows such as Single Track (translator → visual editor); a workflow that splits cleaning and typesetting into separate steps has no visual editor.

The top of the screen, the Workflow panel and Notes work the same on every step: What every step screen shares.

When it opens

When the text track is done: when the proofreader approves if the workflow has one, otherwise when the translator sends the text. You can open the screen before your turn; the buttons under Downloads work then too, so you can download the RAW and the translation ahead of time and prepare.

The sidebar

• Downloads: whatever the chapter has — Download RAW Files, Download Cleaned Files, Download Translation (TXT), Download Translation (DOCX).
• Translation Source: the translator, the source of the translation, source note, translator note and the SFX Translations Included mark.
• Workflow.
• Fonts: if the series has fonts; download them one by one or with Download All (ZIP), and open the series fonts page with View All / Manage (Series fonts).

The translation panel and line comments

The Translation panel at the top of the work area shows the whole translation line by line; click its header to open or close it. When closed, the first non-empty line is shown.

If the workflow has no proofreader, nobody else reads the text line by line before you, so the right to comment on lines passes to you:

1. Open the panel and click the line you want to comment on (for several lines, Shift-click the last one).
2. Add Comment → Comment Type (Error, Suggestion, Question, Praise) → your comment → Add.
3. The Comments (N) button opens all comments; the number in brackets is the total, and the badge next to it is the number of unresolved comments.
4. To ask the translator for a fix, use Request Revision in the header: for a text target, write your reason and send the request. Your comments are attached automatically; the translator sees them next to the lines in revision mode.

In a workflow with a proofreader the panel is read-only; text fixes you request go to the proofreader.

Step by step

1. Download the translation, the RAW and (if any) the cleaned files; do the editing in your own program.
2. On the Choose Source Type card pick Upload Files and upload the edited pages. Accepted types: PNG, JPG/JPEG, GIF, WebP, PSD and PDF; up to 100 MB per file. If you share the pages on Drive, MEGA or similar, choose External Link.
3. The pages appear in the Visually Edited Files grid; reorder them by dragging or with Move Up / Move Down, delete a wrong file.
4. Complete in the header. At least one file or an external link is needed ("Please upload at least one file or add an external link.").

If the workflow has Quality Control, the work moves on to it. Otherwise your completion finishes the chapter; in that case you cannot complete while the chapter has an open revision ("There is an open revision on this chapter; it must be resolved before the chapter can close.").

Asking for a fix

Request Revision goes two ways:

• Text: to the proofreader, or the translator if the workflow has no proofreader. No file selection; you write your reason.
• Image: to the cleaning steps or the RAW uploader if the workflow has them (the balloon cleaner, otherwise the cleaner, otherwise the RAW uploader). You can flag pages and add notes, or ask for the whole chapter to be redone.

How a request travels: Proofreading and revisions.

Who can do this

The person assigned to the Visual Editor step in this series, plus the team owner, Fansub Admin and Fansub Moderator (Step assignments). To add line comments you also need write access on the step: an assigned member can only read the panel before their turn.