![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png){kind=small}
Entry tags:
Copy editing is go!
Hot on the heels of introducing the site copy team, it's now time for me to introduce the copy editing team. Everyone, say hello to:
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
bohemianeditor
chasy_la
cheyinka
ivorygates
rainbow
ryan
Their job will be to go over all the text written by the site copy team and the userdoc team, and correct all the dumb typos we inevitably make. OK, all the dumb typos I inevitably make, and possibly one or two made by the rest of the team.
Copy editors, here's what I want you to be doing now:
I'm afraid you're going to be grappling with the translation system. I'm so very very sorry. There's a guide to it on the wiki thatkatieastrophe wrote for us, but here are the cliff notes:
* Go to http://www.dreamwidth.org/translate/edit.bml?lang=en_DW (I've given you the privs you need)
* In the top left frame, scroll down and select prf: no and upd: yes, then hit search.
* Select one of the pages in the bottom left frame to bring up a list of translation strings.
* In the list, select "edit" for one of the strings, then copy edit it, and select proofed.
* When you're done with the age, click save at the bottom.
In proof reading you should be checking for:
* typos
* spelling mistakes
* grammar and punctuation
* Manual of Style compliance
* correct use of terminology
(Please read through both of these thoroughly before you get started.)
If you see any problems with any of these, change them and mark the string as being proof read. If you proof read a string and see that it's fine as it is (hopefully most of them will be!) then mark it as proofed without making any changes. If you see anything that you think needs a more substantial rewrite, then don't update it yourself, but instead comment here letting me know which string you think needs rewriting, and what you think the problem is. We might revisit this if we end up with a lot that need substantial rewrites, but we'll go with this for now.
Above all, have fun with it, and don't be shy of contacting me if you have any questions.
bohemianeditorchasy_lacheyinkaivorygatesrainbowryanTheir job will be to go over all the text written by the site copy team and the userdoc team, and correct all the dumb typos we inevitably make. OK, all the dumb typos I inevitably make, and possibly one or two made by the rest of the team.
Copy editors, here's what I want you to be doing now:
I'm afraid you're going to be grappling with the translation system. I'm so very very sorry. There's a guide to it on the wiki that
katieastrophe wrote for us, but here are the cliff notes:* Go to http://www.dreamwidth.org/translate/edit.bml?lang=en_DW (I've given you the privs you need)
* In the top left frame, scroll down and select prf: no and upd: yes, then hit search.
* Select one of the pages in the bottom left frame to bring up a list of translation strings.
* In the list, select "edit" for one of the strings, then copy edit it, and select proofed.
* When you're done with the age, click save at the bottom.
In proof reading you should be checking for:
* typos
* spelling mistakes
* grammar and punctuation
* Manual of Style compliance
* correct use of terminology
(Please read through both of these thoroughly before you get started.)
If you see any problems with any of these, change them and mark the string as being proof read. If you proof read a string and see that it's fine as it is (hopefully most of them will be!) then mark it as proofed without making any changes. If you see anything that you think needs a more substantial rewrite, then don't update it yourself, but instead comment here letting me know which string you think needs rewriting, and what you think the problem is. We might revisit this if we end up with a lot that need substantial rewrites, but we'll go with this for now.
Above all, have fun with it, and don't be shy of contacting me if you have any questions.
no subject
The updated version seems very awkward to me, but I'm not sure how substantial my substantial changes are compared to what you might think. So just in case, I'm posting to you here rather than editing there.
This is what I'd suggest:
"Dreamwidth offers two types of relationships between users: subscription and access. Subscribing to a user allows their entries to show on your Reading page so you can easily keep track of new entries. Granting Access to another user lets them see protected entries in your journal. The accounts you subscribe to and the accounts you grant access to form your Circle. You can also subscribe to communities and feeds."
I've capitalised "Circle" as that seems to be what the Manual of Style suggests; "Access" seems like it could also be capitalised in this instance because it's capitalised on the profile pages.
Carys
no subject
no subject
no subject
no subject
I've noticed an awkward bit,though:
their entries will be included on your Reading Page so you can easily keep up with their entries
Now that the paragraph is written so much more clearly overall, the awkwardness of the phrasing there (with the doubling of "entries") really stands out (and yes, I did it _exactly_ the same in the example I gave you earlier. Ashes on my head, and all that).
Something like, "their entries will be included on your Reading Page where you can easily keep up with them" would eliminate the doubling, or it could be broken down into two statements: "When you subscribe to a personal journal, community, or feed, their entries will be included on your Reading Page. This allows you to keep up with their entries."
Or something else entirely. Or ignore it.
And do let me know if I'm worrying too much about grammar or driving you crazy. I love editing and can get a bit..er... enthusiastic about it... *g*
no subject
For cases like this where it's just changing one word to avoid a clumsy repetition, feel free to change it over yourself, though.
no subject
And cool. Thanks :)