Copy editing is go!
Apr. 1st, 2009 04:39 am![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
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:
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 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.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
![[profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
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 that
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
* 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.