A guide for new editors: Difference between revisions
No edit summary |
|||
(2 intermediate revisions by one other user not shown) | |||
Line 1: | Line 1: | ||
[[File:style.jpg|thumb|200px]] | |||
This is a guide to help editors new to GenderIT.org to understand the priorities for the site and provide a quick reference to important documents that you may need in your work. | This is a guide to help editors new to GenderIT.org to understand the priorities for the site and provide a quick reference to important documents that you may need in your work. | ||
Line 20: | Line 20: | ||
* Make sure that language is as simple as possible. Writers, especially those fluent in English, may use colloquialisms or long words. It is particularly important for readers whose first language is not English to simplify these. ''Example: '''Time seemed to fly''', the conference was '''so packed''' with exciting speakers. Instead: The conference had lots of exciting speakers.'' | * Make sure that language is as simple as possible. Writers, especially those fluent in English, may use colloquialisms or long words. It is particularly important for readers whose first language is not English to simplify these. ''Example: '''Time seemed to fly''', the conference was '''so packed''' with exciting speakers. Instead: The conference had lots of exciting speakers.'' | ||
* As far as possible check accuracy. If there was an event, check the dates, that names are spelt correctly etc. Google is definitely your friend! | * As far as possible check accuracy. If there was an event, check the dates, that names are spelt correctly, etc. Google is definitely your friend! | ||
* Check footnotes and references, for both style and completeness. If you think something needs to be referenced, ask for the writer to put that in. | * Check footnotes and references, for both style and completeness. If you think something needs to be referenced, ask for the writer to put that in. | ||
Line 26: | Line 26: | ||
* For some writers (but certainly not all), this may be the first time they are publishing something in English. Your role MAY be to guide and advise them. It is usually clear from the text itself if this is the case. Always phrase guidance respectfully and positively. | * For some writers (but certainly not all), this may be the first time they are publishing something in English. Your role MAY be to guide and advise them. It is usually clear from the text itself if this is the case. Always phrase guidance respectfully and positively. | ||
* | * It's important that you encourage the writers to provide as many links within the text as possible. Some writers might not be used to writing in online platforms, so we should try to make the text as fluid and rich as possible. The articles can't cover all the contextual information that understanding the content of the article might require, but links can be quite useful for that. | ||
* Editors should also help writers understand how important is to save some time to search in the website and select related articles and resources as much as possible. This way we build on previous writings and we offer the readership a much prolific reading experience. And we increase our chances | * Editors should also help writers understand how important it is to save some time to search in the website and select related articles and resources as much as possible. This way we build on previous writings and we offer the readership a much more prolific reading experience. And we increase our chances for readers to get interested in related materials and to stay on the website! | ||
== '''Editing a translation''' == | == '''Editing a translation''' == | ||
Many GenderIT.org articles are translations (from English to Spanish or vice versa). Editing translations has its own challenges, since the mediation of the translator is a second voice that shows in the final article. Always edit the translated article with the original in hand, so you can double-check that the translator didn't misunderstand any phrase or word. In some cases, when translators do not understand a very specific word or expression, they might highlight it for your consideration, so be ready to solve that quiz. Going back to the author and asking for synonyms or alternative ways of saying it might help. | |||
Many | |||
== '''Quick links''' == | == '''Quick links''' == | ||
Line 49: | Line 48: | ||
1. Does the piece as a whole make sense? Is the argument/ are the points clear? Is there any repetition, and if so, does it serve a purpose? | 1. Does the piece as a whole make sense? Is the argument/are the points clear? Is there any repetition, and if so, does it serve a purpose? | ||
2. Is the language clear? Are there any colloquialisms? Are there any words or phrases that a person whose first language is not English may have difficulty understanding? | 2. Is the language clear? Are there any colloquialisms? Are there any words or phrases that a person whose first language is not English may have difficulty understanding? | ||
Line 58: | Line 57: | ||
5. Is there anything missing? Is there an argument or idea that the writer could have followed up on that would strengthen the article? Are there any suggestions you'd like to make to the writer? | 5. Is there anything missing? Is there an argument or idea that the writer could have followed up on that would strengthen the article? Are there any suggestions you'd like to make to the writer? | ||
Some pieces may need two or three rounds of editing. Be prepared! |
Latest revision as of 22:57, 16 May 2016
This is a guide to help editors new to GenderIT.org to understand the priorities for the site and provide a quick reference to important documents that you may need in your work.
Introduction
The editor is the link between the writer and the audience, and the main aim of the editor is to improve communication between the two. While all stories should follow GenderIT.org style and editorial guidelines, and be in line with the core principles of the site, as far as possible, the editor keeps the words and flow of the original writer. The writer is usually an expert in their field, often with many years of campaigning or struggle in their own country – often in languages that are not English. It is important to respect the writer, and ask them questions and permission for any substantive changes.
It is not always easy to follow these guidelines!
Editing tips
- Read through the entire piece first. This gives some sense of what the story is about, and often points that are confusing can be clarified later on.
- Use a lighter touch for blogs such as Feminist Talk. Just check for spelling and readability – only if something is very confusing, make an amendment. Always track changes.
- Check for points that are made more than once. If there is new information, try to meld the two together for brevity, and readability.
- Make sure that language is as simple as possible. Writers, especially those fluent in English, may use colloquialisms or long words. It is particularly important for readers whose first language is not English to simplify these. Example: Time seemed to fly, the conference was so packed with exciting speakers. Instead: The conference had lots of exciting speakers.
- As far as possible check accuracy. If there was an event, check the dates, that names are spelt correctly, etc. Google is definitely your friend!
- Check footnotes and references, for both style and completeness. If you think something needs to be referenced, ask for the writer to put that in.
- For some writers (but certainly not all), this may be the first time they are publishing something in English. Your role MAY be to guide and advise them. It is usually clear from the text itself if this is the case. Always phrase guidance respectfully and positively.
- It's important that you encourage the writers to provide as many links within the text as possible. Some writers might not be used to writing in online platforms, so we should try to make the text as fluid and rich as possible. The articles can't cover all the contextual information that understanding the content of the article might require, but links can be quite useful for that.
- Editors should also help writers understand how important it is to save some time to search in the website and select related articles and resources as much as possible. This way we build on previous writings and we offer the readership a much more prolific reading experience. And we increase our chances for readers to get interested in related materials and to stay on the website!
Editing a translation
Many GenderIT.org articles are translations (from English to Spanish or vice versa). Editing translations has its own challenges, since the mediation of the translator is a second voice that shows in the final article. Always edit the translated article with the original in hand, so you can double-check that the translator didn't misunderstand any phrase or word. In some cases, when translators do not understand a very specific word or expression, they might highlight it for your consideration, so be ready to solve that quiz. Going back to the author and asking for synonyms or alternative ways of saying it might help.
Quick links
Checklist
1. Does the piece as a whole make sense? Is the argument/are the points clear? Is there any repetition, and if so, does it serve a purpose?
2. Is the language clear? Are there any colloquialisms? Are there any words or phrases that a person whose first language is not English may have difficulty understanding?
3. Are the grammar and spelling correct?
4. Are all quotes or other materials adequately referenced, following the house style?
5. Is there anything missing? Is there an argument or idea that the writer could have followed up on that would strengthen the article? Are there any suggestions you'd like to make to the writer?
Some pieces may need two or three rounds of editing. Be prepared!