User:John Woodward - Revision history

John Woodward at 08:31, 21 August 2014

2014-08-21T08:31:24Z

John Woodward: Undo revision 383312 by John Woodward (talk)

2014-08-19T00:52:13Z

Undo revision 383312 by John Woodward (talk)

← Older revision		Revision as of 00:52, 19 August 2014
Line 7:		Line 7:
	## In general, treat them as you would want to be treated.		## In general, treat them as you would want to be treated.
	# Edit in a word processor (MS Word, Wordperfect, etc.) and be careful with line returns and etc.		# Edit in a word processor (MS Word, Wordperfect, etc.) and be careful with line returns and etc.
	# ~~'''[Time saver]'''-~~ To keep all of the original formatting from BT. When edits are input-ready:		# To keep all of the original formatting from BT. 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. I imagine Java or Eclipse's scripts work too, and others too. So as not to have to manually re-format line-by-line for hours:		##copy and paste your edits from word processor into a line-by-line freshly new script. I use MATLAB's script. I imagine Java or Eclipse's scripts work too, and others too. So as not to have to manually re-format line-by-line for hours:
	##select all for the revision		##select all for the revision
Line 13:		Line 13:
	##check with comparisons. If successful, you transferred every edit from word processor to BT automatically.		##check with comparisons. If successful, you transferred every edit from word processor to BT automatically.
	# Editors order should be to patch:		# Editors order should be to patch:
	## Chapter's verb-tense edit ~~(save page)~~		## Chapter's verb-tense edit & grammar/spelling/style '''''compared to the original translation'''''
	~~## Line-by-line's grammar/spelling/style (save page)~~		## Double or triple checking grammar/spelling/style.
	~~##Double or triple checking~~ grammar/spelling/style '''''compared to the original translation'''''.		## Possibly message translator check (TLC) for major line or paragraph edit/s
	# Specifically for Mushoku Tensei's style:		# Specifically for Mushoku Tensei's style:
	##as well, honestly speaking, etc. the author using tons of filler. Although translators will get upset if you edit too much of this verboseness (losing the informalities of the story and deviating from the translation), it's safer if your sentence in a word processor's stricter grammar check says 'check wordiness'.		##as well, honestly speaking, etc. the author using tons of filler. Although translators will get upset if you edit too much of this verboseness (losing the informalities of the story and deviating from the translation), it's safer if your sentence in a word processor's stricter grammar check says 'check wordiness'.
	## Sounds are like 'boom' or [boom], depending on the translator.		## Sounds are like 'boom' or [boom], depending on the translator.
	## "Dialogue is usually each on it's own return line and with quotations." [Some translators will use square brackets] and fewer use the unique brackets.		## "Dialogue is usually each on it's own return line and with quotations." [Some translators will use square brackets] and fewer use the unique brackets.




	<references/>		<references/>

John Woodward at 00:47, 19 August 2014

2014-08-19T00:47:36Z

← Older revision		Revision as of 00:47, 19 August 2014
Line 20:		Line 20:
	## Sounds are like 'boom' or [boom], depending on the translator.		## Sounds are like 'boom' or [boom], depending on the translator.
	## "Dialogue is usually each on it's own return line and with quotations." [Some translators will use square brackets] and fewer use the unique brackets.		## "Dialogue is usually each on it's own return line and with quotations." [Some translators will use square brackets] and fewer use the unique brackets.




			<references/>

John Woodward at 17:19, 18 August 2014

2014-08-18T17:19:45Z

← Older revision		Revision as of 17:19, 18 August 2014
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 ~~(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.		# Be courteous to other editors and especially translators, they are the ones most in demand.
	# Edit in a word processor. MS Word, Wordperfect, etc. ~~are fine;~~ be careful with line returns and etc.		## Courtesy is checking messages and communicating asap.
	# 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.		## In some cases it is rude to add references just for comments, instead of using hide tags<ref>Hide tags are < ! - - Blah Blah Blah - - >, where the ends have no spaces.</ref>.
	# 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~~.		## In general, treat them as you would want to be treated.
			# Edit in a word processor (MS Word, Wordperfect, etc.) and be careful with line returns and etc.
			# '''[Time saver]'''- To keep all of the original formatting from BT. 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. I imagine Java or Eclipse's scripts work too, and others too. So as not to have to manually re-format line-by-line for hours:
			##select all for the revision
			##copy and paste word to script directly then to freshly deleted editting page
			##check with comparisons. If successful, you transferred every edit from word processor to BT automatically.
	~~<references/>~~		# 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 '''''compared to the original translation'''''.
			# Specifically for Mushoku Tensei's style:
			##as well, honestly speaking, etc. the author using tons of filler. Although translators will get upset if you edit too much of this verboseness (losing the informalities of the story and deviating from the translation), it's safer if your sentence in a word processor's stricter grammar check says 'check wordiness'.
			## Sounds are like 'boom' or [boom], depending on the translator.
			## "Dialogue is usually each on it's own return line and with quotations." [Some translators will use square brackets] and fewer use the unique brackets.

John Woodward at 16:57, 18 August 2014

2014-08-18T16:57:02Z

← Older revision		Revision as of 16:57, 18 August 2014
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~~, they~~ are ~~the ones~~ most in demand. Courtesy is checking messages and communicating asap. In some cases it is rude to add references just for comments, ~~instead of using~~ 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.		# 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 (MS Word, Wordperfect, etc.~~) and~~ be careful with line returns and etc.		# Edit in a word processor. MS Word, Wordperfect, etc. are fine; be careful with line returns and etc.
	# ~~'''[Time saver]'''-~~ 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. I imagine Java or Eclipse's scripts work too, and others ~~too~~. The key is to keep all of the original formatting from BT~~. So as not to have to~~ manually re-~~format line-by-line~~ for hours, select all ~~for~~ the revision, copy ~~and~~ paste from script directly to freshly deleted editting page~~- check with comparisons~~. If successful, you transferred every edit from word processor to BT automatically.		# 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 ~~'''''compared~~ to ~~the original translation'''''~~.		# 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/>

John Woodward at 03:48, 18 August 2014

2014-08-18T03:48:25Z

← Older revision		Revision as of 03:48, 18 August 2014
Line 1:		Line 1:
	Currently ~~assisting on~~ Mushoku Tensei		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 the ones most in demand. Courtesy is checking messages and communicating asap. In some cases it is rude to add references just for comments, instead of using 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 (MS Word, Wordperfect, etc.) and be careful with line returns and etc.
			# '''[Time saver]'''- 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. I imagine Java or Eclipse's scripts work too, and others too. The key is to keep all of the original formatting from BT. So as not to have to manually re-format line-by-line for hours, select all for the revision, copy and paste from script directly to freshly deleted editting page- check with comparisons. If successful, 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 '''''compared to the original translation'''''.

Onizuka-gto: Created page with "Currently assisting on Mushoku Tensei"

2014-08-01T06:10:28Z

Created page with "Currently assisting on Mushoku Tensei"

New page

Currently assisting on Mushoku Tensei

← Older revision		Revision as of 08:31, 21 August 2014
Line 3:		Line 3:
	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, they are the ones most in demand.		# Be courteous to other editors and especially translators, they are the ones most in demand.
	## Courtesy is checking messages and communicating asap.		## Courtesy is checking messages and communicating asap. Including at least a dialogue with the TL before a major edit. (To give a heads up and not surprise them)
	## In some cases it is rude to add references just for comments, instead of using hide tags<ref>Hide tags are < ! - - Blah Blah Blah - - >, where the ends have no spaces.</ref>.		## In some cases it is rude to add references just for comments, instead of using 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.		## In general, treat them as you would want to be treated.
Line 13:		Line 13:
	##check with comparisons. If successful, you transferred every edit from word processor to BT automatically.		##check with comparisons. If successful, you transferred every edit from word processor to BT automatically.
	# Editors order should be to patch:		# Editors order should be to patch:
	## Chapter's verb-tense edit & grammar/spelling/style '''''compared to the original translation'''''		## Chapter's verb-tense edit
	## ~~Double or triple checking grammar/spelling/style.~~		## Double or triple checking grammar/spelling/style '''''compared to the original translation'''''
	~~## Possibly~~ message ~~translator check (TLC)~~ for major ~~line or paragraph edit/s~~		## Sometimes message translators for major edits incoming.
	# Specifically for Mushoku Tensei's style:		# Specifically for Mushoku Tensei's style:
	##as well, honestly speaking, etc. the author ~~using tons of filler~~. Although translators will get upset if you edit too much of this ~~verboseness~~ (losing the informalities of the story and deviating from the translation), it's safer if your sentence in a word processor's stricter grammar check says 'check wordiness'.		## "As well, honestly speaking, etc." the author speaks casually with verboseness. Although translators will get upset if you edit too much of this sometimes wordiness (losing the informalities of the story and deviating from the translation), it's safer if your sentence in a word processor's stricter grammar check says 'check wordiness'. Be mindful of each translator.
	## Sounds are like 'boom' or [boom], depending on the translator.		## Sounds are like 'boom' or [boom], depending on the translator.
	## "Dialogue is usually each on it's own return line and with quotations." [Some translators will use square brackets] and fewer use the unique brackets.		## "Dialogue is usually each on it's own return line and with quotations." [Some translators will use square brackets] and fewer use the unique brackets.



	<references/>		<references/>