I would recommend you post PRIVATELY in your own journal (making sure it's in default style, not your journal's style), look at all the formatting, and change whatever doesn't look like you want it to.
If your story is too long for one LJ entry, you should definitely code in your emdashes, section breaks, and such. (We have an html conversion macro, but this way gives you total control over it.)
I would recommend you post PRIVATELY in your own journal (making sure it's in default style, not your journal's style), look at all the formatting, and change whatever doesn't look like you want it to.
So, just to be clear, when we e-mail you our story file, we send you a version that shows all the code, like when we're editing and coding something to be posted in our journal?
I'm guessing that, 'cause it looks like you'll have to copy/paste all our entries (Aagh, lots of work!) and it seems like it'd be easier for you to manage if we send you a version showing the html codes, and you can just pop it whole into the posting window. Yes? No?
Sorry if I'm asking an idiotic question, but Y'hello, Luddite here. I don't even know what an emdash is, let alone how to code one, or whether I should. I don't think so, my story fits one LJ post. But you see my point. Technomoron, me. *embarrassed sigh*
hee! For long fics, we have a macro that will change MS Word formatting into html, so we won't need to ask people to code their own. It's automatic and zippy. :)
As long as we have everyone's .txt or .doc file on hand, copying and pasting should be a piece of cake. :D
Also, an emdash is like this: "Oh, god. Just likedid you rememberplease, moreto let Dief out?"
(If you look up "dash" on wikipedia, you'll learn more than you ever wanted about emdashes, endashes, and double hyphens. :P)
Comments 11
Reply
If your story is too long for one LJ entry, you should definitely code in your emdashes, section breaks, and such. (We have an html conversion macro, but this way gives you total control over it.)
Reply
For example, if you *always* use section breaks like this:
~*~*~*~
we would ask you to use plain old boring generic asterisks instead. :)
Thanks!
Reply
Reply
Reply
Reply
So, just to be clear, when we e-mail you our story file, we send you a version that shows all the code, like when we're editing and coding something to be posted in our journal?
I'm guessing that, 'cause it looks like you'll have to copy/paste all our entries (Aagh, lots of work!) and it seems like it'd be easier for you to manage if we send you a version showing the html codes, and you can just pop it whole into the posting window. Yes? No?
Sorry if I'm asking an idiotic question, but Y'hello, Luddite here. I don't even know what an emdash is, let alone how to code one, or whether I should. I don't think so, my story fits one LJ post. But you see my point. Technomoron, me. *embarrassed sigh*
Reply
As long as we have everyone's .txt or .doc file on hand, copying and pasting should be a piece of cake. :D
Also, an emdash is like this: "Oh, god. Just likedid you rememberplease, moreto let Dief out?"
(If you look up "dash" on wikipedia, you'll learn more than you ever wanted about emdashes, endashes, and double hyphens. :P)
Reply
Reply
Grab the zip file & follow the instructions. Easy as pie. :)
Reply
Leave a comment