Difference between revisions of "User:John Woodward"
Jump to navigation
Jump to search
m |
m |
||
| Line 2: | Line 2: | ||
I started BT in July and gained some wisdom I wish I knew when I started editing: |
I started BT in July and gained some wisdom I wish I knew when I started editing: |
||
| − | # Be courteous to other editors and especially translators |
+ | # Be courteous to other editors and especially translators (They are most in demand). Courtesy is checking messages and communicating asap. In some cases, it is rude to add references just for comments. Instead, use hide tags<ref>Hide tags are < ! - - Blah Blah Blah - - >, where the ends have no spaces.</ref>. In general, treat them as you would want to be treated. |
| − | # Edit in a word processor |
+ | # Edit in a word processor. MS Word, Wordperfect, etc. are fine; be careful with line returns and etc. |
| − | # |
+ | # When edits are input-ready: copy and paste your edits from word processor into a line-by-line, freshly new, script. I use MATLAB's script. Though I imagine Java, Eclipse's scripts work too, and others as well. The key is to keep all of the original formatting from BT and avoid manually re-formatting return lines to match up for hours. I learned this trick is possible after: select+all then delete in the revision, select+all then copy + paste from script directly to freshly deleted editting page, click "Changes". If successful, the comparisons will almost totally line up (unless you did change line returns in the word processor). Congrats, you transferred every edit from word processor to BT automatically. |
| − | # Editors order should be to patch: Chapter's verb-tense edit (save page)--> Line-by-line's grammar/spelling/style (save page) --> Double or triple checking grammar/spelling/style |
+ | # Editors order should be to patch: Chapter's verb-tense edit (save page)--> Line-by-line's grammar/spelling/style '''''compared to the original translation'''''(save page) --> Double or triple checking grammar/spelling/style with spell checker to cleanup. |
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | <references/> |
||
Revision as of 18:57, 18 August 2014
Currently a Project Editor for Mushoku Tensei, I'm an Industrial Engineer graduate looking for work currently, so I have loads of free time. ;)
I started BT in July and gained some wisdom I wish I knew when I started editing:
- Be courteous to other editors and especially translators (They are most in demand). Courtesy is checking messages and communicating asap. In some cases, it is rude to add references just for comments. Instead, use hide tags[1]. In general, treat them as you would want to be treated.
- Edit in a word processor. MS Word, Wordperfect, etc. are fine; be careful with line returns and etc.
- When edits are input-ready: copy and paste your edits from word processor into a line-by-line, freshly new, script. I use MATLAB's script. Though I imagine Java, Eclipse's scripts work too, and others as well. The key is to keep all of the original formatting from BT and avoid manually re-formatting return lines to match up for hours. I learned this trick is possible after: select+all then delete in the revision, select+all then copy + paste from script directly to freshly deleted editting page, click "Changes". If successful, the comparisons will almost totally line up (unless you did change line returns in the word processor). Congrats, you transferred every edit from word processor to BT automatically.
- Editors order should be to patch: Chapter's verb-tense edit (save page)--> Line-by-line's grammar/spelling/style compared to the original translation(save page) --> Double or triple checking grammar/spelling/style with spell checker to cleanup.
- ↑ Hide tags are < ! - - Blah Blah Blah - - >, where the ends have no spaces.
