Archive of Our Own and Other Blatherings

[alixtii]

So I posted my dw_femslash fic to the AoOO, with fake cuts pointing to it from my DW/LJ/IJ/JF and from dw_femslash itself. Largely this was because somehow it ended up with a lot of crap HTML (I think I'm going to go back to composing in Semagic until Dreamwidth introduces draft functionality, even though I'm not posting from Semagic anymore since DW has its nifty crossposter) and I had to fight to get it formatted correctly for AoOO and I didn't want to have to do all that again for Dreamwidth/LJ/IJ/JF.

Partly also because my shiny new AoOO account is shiny and new and I wanted to test it out. I don't expect to start posting solely to AoOO as a general rule anytime soon, though.

I spent most of today getting my fic up onto AoOO. I have to say that it's the most pleasant uploading experience I've had with an archive: the Rich Text Editor actually seems to understand what I want the text to do and does it. (I do wish it would auto-format line breaks the way DW and LJ do, though.) Most of my fic's there now, with three exceptions: 1) fic written for yuletide, 2) Buffy/Angel fic, and 3) Firefly fic. 2 and 3--or really just 2 by itself, even--are pretty significant exceptions, though.

I have an invitation to the AoOO to give out if someone wants it (and they should!).

Comments

[zvi]

FYI: posting via Semagic will now crosspost, if you have your crossposting set up to be automatically crosspost.

[alixtii]

Yeah, but since I can crosspost without Semagic using DW, there isn't really any advantage to posting from Semagic. Dreamwidth does pretty much everything I want to do--except compose multiple projects at the same time and save them from session to session (yet). So I downloaded Semagic to my new laptop just for that.

[zvi]

*nod* I just wanted to encourage you to crosspost by having Semagic trigger DW's crossposter, as opposed to having Semagic post separately to everywhere you post. The advantage to doing it through DW is that the crossposter and the importer then know that the entries are the same, and if you edit or delete on DW, it propagates to the other journals.

[alixtii]

Yes, certainly. I remember that being one of the things I really hated about Semagic, how difficult it was to go back and edit afterwards.

[copracat]

I just wanted to say what an excellent tagger you are for a tag wrangler to wrangle. Thank you for your full names in characters and pairings and for your alpha order of pairing names.

Uploading is pretty gorgeous isn't it?

[alixtii]

Why, thank you! I try to follow directions.

And uploading is gorgeous indeed.

[frogfarm]

If you still has an AoOO invite, I'd like it very much.

[alixtii]

I do! Email?

Never mind. I remember what it is.

[http://users.livejournal.com/peasant_/]

What's different about how the archive formats line breaks?

There are actually accessibility/standards compliance issues related to how line breaks are formatted. That may be what is making the difference.

[alixtii.livejournal.com]

LJ and DW's HTML editor (as opposed to the Rich Text) one includes an "auto-format" option which will convert line breaks to [br] tags but let you put in the raw HTML for everything else. AoOO doesn't have that; you have to either put in the [br] tags yourself or else use the Rich Text editor.

Which, fair enough, that's what "HTML" and "Rich Text" mean, but for the most part the reason why I'm finding the AoOO's editor so intuitive compared to FF.net or eFiction is because it works more or less the same way DW and LJ do.

[http://users.livejournal.com/peasant_/]

The archive is still in beta, no? Then you should definitely mention your complaint in their suggestions section. Formatting line breaks is very easy to do in most coding languages, I doubt ruby is any different. And it should definitely be available as an option just like LJ - so the end user can tick/untick a simple box to request that line breaks be formatted or not.

I'm actually slightly concerned by the accessibility implications that such a fundamental thing hasn't been built in from the start - it implies a very worrying attitude because it means they haven't even considered the implications of the difference between the line break tag and the paragraph tag.