Discuss fanfiction, get writing advice, or get your story reviewed

Search /fic/ threads

Name  
Email  
Subject  
Message  
File     
Password  (for post and file deletion)

File 132553528743.jpg - (35.58KB , 1014x634 , CheerileeBoard.jpg )
75545 No. 75545
https://docs.google.com/document/d/1xemG7BLk2rvAmQCREIaj5wX2ubvmVt7WziEvh7xXV9g/edit?hl=en_US

So I took it upon myself to write a guide to writing, based on some of the stuff I've learnt, and the repeat errors I've seen when doing reviews here. I'm not a published guy or even an English/Linguistics Major, but I like to believe I've learnt a few things about stuff in my time.

I'd like you guys to tell me what I got wrong. A lot of the guide is basically opinions, backed up by (I think) good reasons, but there's a section on grammar at the beginning and I'd like for that to be correct.

There are probably also two or three things that need to be expanded upon. I await /fic/'s thoughts on the matter.

I had fun writing this guide and I hope it's a least a little bit fun to read, and maybe informative as well.
Unspoiler all text  • Expand all images  • Reveal spoilers
>> No. 75546
>>75545
thanks for making, hopefully it'll help me improve too.
>> No. 75550
File 132553659230.png - (23.28KB , 295x374 , Sum_Pony_came.png )
75550
That's one hell of a nice-looking guide. Easy to follow, well-organized and well-structured, and even color coded. You should ask the EqD prereaders to take a look at it and link to it in the Editor's Omnibus if they think it's worthwhile.
>> No. 75551
>>75550
I should add, however: you may want to make the red and green a little more distinct shades. Filler (who is colorblind) says he can't tell them apart.

Also, your section on show versus tell touches on an important point that I haven't seen in almost any other show-don't-tell guide: expose details and let readers come to their own conclusions. The only gray area I can see is where this intersects with third person omniscient narrative, in which the emotions are given detail. Maybe it boils down to not spelling out obvious causal connections or purposes for x, y & z for being there - but making them more obvious through other means.
>> No. 75567
Currently skimming through your thing up in another tab. I noticed you enabled comments, and I've seen a few minor things. Hope you don't mind me pointing at them.

I'm not done yet because I keep pausing to do other things, but I've got a question. It's a little outside the scope of a 'guide' and I doubt anyone can really give any good rule. It's probably doomed to be looked at on a case-by-case basis forever.

Readers are smart. Let them infer things. Trust them. All that jazz. There's a LIMIT to it, ja? I have some difficulty knowing where to draw that line. Right now the best advice I've heard for this is to just have a handful of people read it. If the majority of them understand what was implied, you're good to go. If not, go back and try to make things more obvious.

I don't like that. Surely there's a better way?

ALSO, while I'm well aware that typography is srs bsns, I think you rant a little too much about the double space thing. I'm guilty of it (although here the software seems to filter it out of posts) and while I can't come up with a good argument in FAVOR of it, I really don't see what the big deal is. It's not particularly noticeable on any of the common fonts unless you've got your eye against the page.

No, I'm not just saying that because I'm too lazy to make the effort to correct myself. No, the real reason I bring this up is not any better than that.
>> No. 75569
I actully enjoyed it:) I want to become a better writer too and ill take some advice from this, the only problem i have is ofcourse the opinions, this was written for ALL writers, so your opinions may get in the way of possibly something better they could do.
>> No. 75573
File 132554204498.jpg - (42.48KB , 600x318 , giant ass spike approves.jpg )
75573
hmm, this guide I can use, Thank you Ezn.
>> No. 75738
Thanks to everyone who left comments in the doc. I've addressed the issues that needed to be addressed.

>>75551
I changed the green colour slightly, but it's probably not by enough. I'd like to work out a balance between visible and garish.

>Also, your section on show versus tell touches on an important point that I haven't seen in almost any other show-don't-tell guide: expose details and let readers come to their own conclusions. The only gray area I can see is where this intersects with third person omniscient narrative, in which the emotions are given detail. Maybe it boils down to not spelling out obvious causal connections or purposes for x, y & z for being there - but making them more obvious through other means.
Hmm. I'll give this matter some more thought. I've always found show vs tell to be one of the very hardest things to explain.

>>75567
>Readers are smart. Let them infer things. Trust them. All that jazz. There's a LIMIT to it, ja? I have some difficulty knowing where to draw that line. Right now the best advice I've heard for this is to just have a handful of people read it. If the majority of them understand what was implied, you're good to go. If not, go back and try to make things more obvious.

>I don't like that. Surely there's a better way?
I don't know that there is. It's all just so subjective.

There are always going to be people who get it and others who don't get it. I've read a few short stories where I didn't get the twist, and remember having to explain what had happened in a story to my (linguistic-masters-having) mother when my English teacher had lauded it for its great brilliance or something.

Personally, I'd err on the side of vagueness, so I can pretend to be deep.

I'll think about it some more, but for now I really think that that advice is good advice, and I can't see any alternatives right now.

>ALSO, while I'm well aware that typography is srs bsns, I think you rant a little too much about the double space thing. I'm guilty of it (although here the software seems to filter it out of posts) and while I can't come up with a good argument in FAVOR of it, I really don't see what the big deal is. It's not particularly noticeable on any of the common fonts unless you've got your eye against the page.
Two spaces killed my parents.

Yeah, I'm far too zealous about that. I didn't notice it for the longest time, but then one day I was correcting an error for someone and I saw these two spaces, which reminded me of that Slate article (which I read years ago), and then the spell was broken and I started seeing them everywhere.

They're rather ugly to my eye, but still, I'll see about toning down my ranty two space hate.

>>75569
Well, I'm afraid I've only got opinions. I've tried to make the point that I don't know everything, and that you should evaluate my stances on stuff for yourself and decide whether or not you agree.

I could probably stand to give it a read-through and rework anything that comes off as me pushing my personal agenda first and being helpful second.

>>75573
Happy to help!
>> No. 75829
File 132559228773.jpg - (8.38KB , 200x200 , Color56.jpg )
75829
>>75738
I can't tell the difference between the green and black or the difference between the red and the... gold? Is that gold?

Pic marginally related.
>> No. 76010
>>75829
I've changed gold and red; please tell me if it's any better.

Gold is a little garish, but it's not used very often in the document, so eh.
>> No. 76011
File 132566084541.jpg - (30.60KB , 359x478 , colorblind[1].jpg )
76011
>>76010
>> No. 76381
>>76010
Yup.

Mostly.
>> No. 76733
File 132596279522.gif - (55.62KB , 650x450 , 04111.gif )
76733
Added a bit about time-related words ("today", "now", "current", etc) to the section on tenses.

https://docs.google.com/document/d/1xemG7BLk2rvAmQCREIaj5wX2ubvmVt7WziEvh7xXV9g/edit?hl=en_GB#heading=h.f633617b4c44

Also mentioned you helpful guys from this thread in the Acknowledgments.

https://docs.google.com/document/d/1xemG7BLk2rvAmQCREIaj5wX2ubvmVt7WziEvh7xXV9g/edit?hl=en_GB#heading=h.b54e530aa191

(used Google account names; tell me if you want them changed)

Now to watch that episode...
>> No. 85572
File 132968257321.png - (41.97KB , 800x582 , DvW8N.png )
85572
Bump for a few miscellaneous updates made recently. Added some stuff on tags, a little more about LUS, one or two things about dialogue punctuation, and probably some other things I've forgotten.

Don't be shy about calling me out on my errors.

Same link as always:
https://docs.google.com/document/d/1xemG7BLk2rvAmQCREIaj5wX2ubvmVt7WziEvh7xXV9g/edit?hl=en_US
>> No. 92110
There's a shortlink now: http://derpy.me/EznGuide

Many updates and additions have been made since the last time this thread saw Page 0. Check out the thing on passive voice, the extended thing on crossovers, the technical note on dashes and also the bit I just revised about thesaurus use.

As always, comments are enabled and please do jump in and offer your perspective and correct my errors. This guide's really just a collection of stuff I've learnt, rather than any attempt to be an authority on fiction-writing.

Thanks to Kurbz, Cassius, DashAnon, Pav Feira and anyone else who's helped out recently.

Coming soon: "Plot" subsections dealing with Shipping, Grimdark and Sad. I've got some general ideas about what to write for all of them, but any help from people who actually have experience in those genres would be greatly appreciated.
>> No. 96741
File 133429442249.png - (398.23KB , 640x462 , 161592 - artist briskby artist raikoh14 camera Featherweight squirrel.png )
96741
And I think another bump is in order. I've added and changed various things here and there since the last bump – the Plot section now has subsections on Grimdark, Shipping and Comedy, and there's a bit on quotation marks that I dumped in the Style section.

Future additions being considered/worked on in secret:
- Something on Sad for the plot section
- Appendices:
-- One for common MLP terms (like http://ponyfictionarchive.net/viewpage.php?page=terms but with a bit more stuff) and little rants about why you shouldn't call stallions "bucks", FoE fans.*
-- One for links to other pony guides, writing software, and helpful pages about writing on the internet.

*"Male deer and goats are referred to as bucks (larger species of male deer such as elk or moose are called bulls)"
-http://en.wikipedia.org/wiki/Buck
>> No. 104316
File 133823772744.jpg - (193.03KB , 703x1135 , twilight_by_mewpan-d4zbfog.jpg )
104316
Added those appendices and will be fattening them up over the next few days! Feedback is appreciated, as always.

http://derpy.me/EznGuide
[Return] [Entire Thread] [Last 50 posts]


Delete post []
Password    
Report post
Reason