No Good Deed by ga unicorn (NC-17*)

[katstale.livejournal.com]

Rec Category: Action/Adventure
Pairing: none
Category: H/C, A/A, Atlantis,
Warning: Slight language, some violence, a little torture
Author on LJ:ga_unicorn
Author's Website: unknown
Link: No Good Deed

Summary: No good deed goes unpunished...McKay decides to help Zelenka, then Sheppard gives up his day off to track them down.  And they all end up with regrets.

 *Note: Though the author rated this as NC-17, that seems a bit harsh for the content to me.  I'd probably have put at it R, possibly even PG-13.

Why This Must Be Read:  Though A/A, this story takes place entirely on Atlantis.  The author does a wonderful job with all of the characters and sets a nice pace for the action.  Nice character interaction interspersed with some lovely humorous bits.  Her OCs are fleshed out enough to be scary/threatening, but still retain an air of mystery.  I, for one, would dearly love to see a sequel to this wherein Atlantis unknowingly visits the planet from which the visitors originated. 

Comments

[hsapiens.livejournal.com]

Would you please check your html tags? I believe that you've left an open < em > tag and it's screwing up my f-list after your post. Thank you!

[katstale.livejournal.com]

I've checked the tags as requested and found no open tag. My flist is okay, so I have no idea why you are having issues. Is anyone else having a problem?

[katstale.livejournal.com]

I am stumped. I checked the code, and everything was closed (and the slashes were in the right place, in front of the em tag) on my screen. I have no clue why some are seeing it differently. Maybe I should just delete the entire entry and start over...

[hsapiens.livejournal.com]

Your entry ends with:

< em / >< br / >< /span >

That first tag should be < /em >. Without the spaces, of course. :)

[katstale.livejournal.com]

This is bizzare. I used the lj rich text editor when posting this. When I click the source button to show the code it is not showing the slash after the em on the last tag, but before the em where it should be. I have no idea why it's showing up differently for you. :)

[hsapiens.livejournal.com]

I guess it's a bug in the rich text editor. I've never used it so I can't say for certain. I can look directly at the code - and it matches what was e-mailed to me when I commented - and that's where I found the incorrect tag. If you reply to your own post, you'll see in the e-mail not what the rich text editor thinks is there but the code that actually is there.

Thanks for looking into it. My community permissions won't allow me to edit your entry myself so I'll send a note to the admins and see if they can do this since the rich text editor is apparently broken. :(

Differences in f-list appearances are due to differing LJ-styles. I'm guessing mine doesn't automatically correct for bad coding by "closing" any open tags when an entry is done. In any case, it will be off my f-list by morning but I imagine others who have this problem might not be so fortunate.

[angelsgracie.livejournal.com]

They won't let me go in and correct it either. Any corrections that are made to an actual entry have to be made by the person posting the entry. My suggestion is not to use the rich text editor and just post normally because I can see that the entry looks different through the link that I was given. But I did check my flist too and yeah, all my entries are italics too after this one. So my suggestion, and the only one I can do, is to suggest not to use the rich text editor.

[katstale.livejournal.com]

In actually looking at the end code, there was no reason for any em tag to be there at all. I've deleted that, so can someone tell me if it fixed the problem? If not, I'm just going to delete the entry and redo it in the plain text mode.

[angelsgracie.livejournal.com]

I just refreshed my flist and yes, it looks like the coding correction worked. The font is still pretty big though, but the rest of my flist is back to normal-sized type. I'd say probably just use the plain text for the rest of your recs.

(Honestly, I don't know what rich text editor is. I'm a bit unfamiliar with the nuances of LJ sometimes.)

[katstale.livejournal.com]

Whew, glad to hear that at least the em tag problem is fixed. I have no idea why the text is so large. I think the stupid thing was on crack this evening when I posted. :)

The rich text editor is the one that has the buttons at the top for bold, italics, lj cuts, lj users, hyperlinks, etc. that is supposed to insert the code for you so you don't have to do it yourself. For lazy peoples like me... ::grins:: I've used it before with no problems at all. I think I'll go back to typing it all myself from now on, though. Much less hassle in the long run. :)

[angelsgracie.livejournal.com]

AH!!! See, learn something new every day!

On crack, huh? I bet it was the special kind. *g* But yeah, it made the font really big. I was talking to [Bad username or site: @ livejournal.com] about it and she said that she's seen rich text just freak out at random before. Guess you were chosen for the random freak out tonight. Hehehe!

[katstale.livejournal.com]

Oh yay, lucky me! ::grins::

Yep, very special stuff, it was. Made from a derivative of the Wraith enzyme, I'm told... ::giggles:: Not that I'd know from experience or anything... ::cough, cough::

Yeah, um, anyway...think I'll be sticking to using the plain text from now on. :)

[hsapiens.livejournal.com]

Yay! Problem is fixed. Thank you! *smooches*

The irony is not lost on me that the rich text editor went ka-blooey on a rec for a fic entitled, "No Good Deed..." ha! Bad LJ!

Thank you for pursuing the problem. I appreciate it. :)

[katstale.livejournal.com]

You're welcome--thanks for pointing out the problem! I'm just so glad it's fixed. I sure didn't want to cause anyone problems from my post; these recs are supposed to helpful not aggravating, lol.

ROTFLMAO! Yes, leave it to me to find a glitch when rec'cin something titled "No Good Deed"... =)

Again, you're very welcome! I'm just glad it was something we could resolve eventually. :)