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:
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.
no subject
* Things like
* Things like <a [[aopts]]>log in</a>, for instance.
no subject
[WARNING! Techie bit follows!]
In this case, the [[aopts]] will get replaced with something like href="http://www.dreamwidth.org/login.bml" so the whole thing will expand to give a full HTML link.
If you aren't comfortable with this, or with HTML, feel free to just leave any that you're unsure of.
(no subject)
The Management
Re: The Management
Re: The Management
no subject
Suggest page. *ducks*
no subject
no subject
My question with this addresses no lapse in due diligence upon the part of he or she who wrested it from the primordial bml.ylem, but rather, one of the great metaphysical questions of our age: since the person whose comm it may well be is now an administrator, and may indeed be a comm's sole suzerain, language in messages such as this, which speaks of "another moderator", may perhaps be unduly confusing, since a comm may have no moderators at all.
no subject
I hereby decree that we shall keep this as it is now, partly because I think it's sufficiently clear that there won't be any great misunderstandings, but mainly because I totally can't think of anything to change it to that would be better.
(no subject)
(no subject)
no subject
I click the edit box. The text I see is "Change Status". <-- That's all I'm copy editing on this string, correct? So then I check "Proofed" and move on to the next string which is "There has been a database error processing your request." (And is also spelled correctly, etc.)
I guess it seems "too simple" so I'm wondering if I'm misinterpreting what's supposed to be happening here.
Halp!
no subject
Some translation strings are very short. A air few are just one word. But then there are also some that are complete paragraphs. The whole system is a confusing mess, I'm afraid.
(no subject)
no subject
English:
[[ljuser]]'s status in your circle has been updated.
I'm thinking "ljuser" might be an error?
no subject
(no subject)
(no subject)
(no subject)
no subject
no subject
(no subject)
no subject
Is there an IRC Participation Guide for the Clueless? I may need a real-time HALP! resource.
no subject
(no subject)
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)
(no subject)
(no subject)
no subject
no subject
(no subject)
no subject
English:
There was an error getting the journal entries to edit:
Is "getting" referring to the act of the retrieving the entries or the act of editing the entries?
no subject
(no subject)
no subject
English:
Did you know you can now easily add a photo?
Is this purposefully phrased as an interrogative? It seems to me that it would fit with the rest of the section better as a declarative (ie "Add a photo").
no subject
(no subject)
no subject
English:
New Friends
The edited version for this one is "New People". That works if it's only personal journals, but if it's also comms and feeds, "New Subscriptions" would be clearer.
no subject
(no subject)
no subject
English:
You've hidden one or more tips, and so you won't see them here. If this makes you sad, you can restore them:
Is the mood relevant, or can this be changed to a preference for seeing all tips?
no subject
(no subject)
no subject
English:
The following are the most related users to [[user]]
Unclear. "most related" = "most similar" (since that the coding) or ?
no subject
(edited copy from the page rather than orig)
The interests you deselected were successfully removed from your interests list. However, you selected too many interests to add. You may only have [[intcount]] interests in total. None of the selected interests were added to your interests list. You may wish to go back and try again, selecting fewer interests to add or deleting some old ones.
That's the same copy as for Code: /interests.bml.results.del_and_toomany -- is it meant to also mention deselecting? The original copy for the code doesn't ("You selected too many interests to add. You may only have [[intcount]] interests in total. None of the selected interests were added to your interests list. You may wish to go back and try again, selecting fewer interests to add.")
no subject
Code: /lostinfo_do.bml.lostpasswordmail.part3
Here's what I suggest
This information was requested on the website from [[remoteip]].
Don't worry if you didn't make this password request; you're the only person who received this email. The user who made the request may have mistakenly thought he or she controlled this username or may have made a typo in a username or email address.
(Although I'd prefer to stick in Dreamwidth rather than "the website", but I don't grok the deep magic *g* )
no subject
(no subject)
no subject
English:
Adding [[user]] allows you to read new content from it on your reading page.
This is another awkward one. "It" works for a comm or feed, but not so much for a person.
Suggest: "Adding [[user]] will allow you to read (user)'s new content on your reading page."
no subject
English:
Image size must be [[size]] or less to disable the lj-cut.
Is "lj-cut" being used here (outside of the double brackets)?
another one
The orig string is "You could not be authenticated as the specified user."
The updated is "Your account could not be authenticated as the account that you specified."
Could it be simplified to "The specified account could not be authenticated" or "You could not be authenticated as (deep magic brackets for user)"?
/community/pending.bml.success.added
is currently
You've added [[num]] [[?num|person|persons]] to this community.
Is there a good reason it's not person|people? "You've added n people" sounds better than "You've added n persons", at least to me...
/manage/circle/index.bml.about
is currently
Would it be worthwhile to add "even if they don't subscribe to your journal" to the last sentence? (I did mark it as having been proofed, since I think it's still relatively-easily findable even with that, and it's certainly fine as it is.)