<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Writing for (y)EU &#187; behind the scene</title>
	<atom:link href="http://www.writingforyeu.eu/tag/behind-the-scene/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.writingforyeu.eu</link>
	<description>A blog for a team.</description>
	<lastBuildDate>Fri, 03 Feb 2012 07:21:35 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>The day we invented the synopsis</title>
		<link>http://www.writingforyeu.eu/2008/07/the-day-we-invented-the-synopsis/</link>
		<comments>http://www.writingforyeu.eu/2008/07/the-day-we-invented-the-synopsis/#comments</comments>
		<pubDate>Thu, 17 Jul 2008 08:03:30 +0000</pubDate>
		<dc:creator>Tayebot</dc:creator>
				<category><![CDATA[The day when...]]></category>
		<category><![CDATA[behind the scene]]></category>
		<category><![CDATA[editorial stuff]]></category>
		<category><![CDATA[working together]]></category>
		<category><![CDATA[writings]]></category>

		<guid isPermaLink="false">http://www.pheukeudeuk.com/blog02/?p=19</guid>
		<description><![CDATA[Here is a simple question that tormented us for quite a long time when we were just drafting the organisation, the process and the methods that we now use daily. Those were the days when we were about to start to write and publish on the Headlines and when we were slowly gathering the small team that became our Team - and our Unit.]]></description>
			<content:encoded><![CDATA[<p style="text-align: justify;">Here is a simple question that tormented us for quite a long time when we were just drafting the organisation, the process and the methods that we now use daily. Those were the days when we were about to start to write and publish on the <a href="http://www.europarl.europa.eu/news/public/default_en.htm" target="_blank">Headlines</a> and when we were slowly gathering the small team that became our Team &#8211; and our Unit.</p>
<blockquote>
<p style="text-align: justify;">How do you write an article in 22 languages about the very same subject without translating it ?</p>
</blockquote>
<p style="text-align: justify;">Not that we have anything against translation nor translators. They are the salt of the European Parliament good way of working. Since it is a fundamental right to run for an election whatever your skills, experience or knowledge might be, you cannot ask to the Members to be fluent in foreign languages. Hence the essential needs for translation, so that your chosen ones can read, work, amend, debate and vote in their mother tongue. </p>
<p style="text-align: justify;">But for our own editorial needs, translation wouldn&#8217;t do the job. We are a team of writers devoted to every street guys. We do our best to write in a comprehensive language, free of eurojargon, with its vitality, its charm, its colloquial ways of informing about the acts and decisions of the Parliament. All that flavour is sometimes lost in translation.</p>
<p style="text-align: justify;">Also, when composing the team, we wanted as much as possible people from the journalism or communication fields. We work as closely as possible as a news agency would do. This requires specific profile with many talents &#8211; but adding the translating skills to the check list would have been asking for too much. </p>
<p style="text-align: justify;"><strong>So we brainstormed&#8230;</strong></p>
<p style="text-align: justify;">After some gallons of coffee, we came up with the idea of the synopsis. The synopsis is what the French having studied in Science-Pô would call &#8220;un plan détaillé&#8221;. It is a detailed draft of the story, a skeleton well structured, which provides all facts, quotes, figures, examples. It is written in a basic English to be understood by everyone. It is almost always written by two editors (it provides a second pair of eyes to challenge the structure) and it should be no longer than two pages. Before it is sent to the rest of the team, the synopsis is reviewed (and formally &#8220;approved&#8221;) by Steve, the Boss-of-the-pop, and sometimes revised by some of our colleagues from the <a href="http://www.europarl.europa.eu/news/expert/default_en.htm" target="_blank">Press Room</a> who cover <a href="http://www.europarl.europa.eu/activities/committees/committeesList.do?language=EN" target="_blank">the Committees</a>. We call them the &#8220;specialists&#8221; because they follow deeply all legislative matters and they are the best to check the facts and the political positions.</p>
<p style="text-align: justify;">From the synopsis, the editors write. In their language. They stick to the synopsis but they add the flavor, the spices, the taste of the final text. All our stories are the same in 22 languages but none of them are identical. Our writers have their style, even their voice. For example, Gaëlle&#8217;s writings (she&#8217;s our French editor), sound like my eldest sister explaining me the European affairs. Without the naughty comments about my fashion tastes.</p>
<p style="text-align: justify;"><strong>And we still brainstorm</strong></p>
<p style="text-align: justify;">Synopses belong to the list of most debated subjects in our staff meetings. Despite our common rules, the fact that we produce two to three of them every day lead to different perspectives. Different schools in the way we perform the task. Some prefers long (too long ?) and very well detailed synopses. Some write in their best English, which can be gratifying but also painful for others. Some editors have a touch for extremely short and bullet-points style synopsis &#8211; which others hate because they need more information to feed their prose with more details. That&#8217;s what we call diversity.</p>
<p style="text-align: justify;">So we discuss, we exchange, we improve, we criticise - oh, and we complain a lot too. We even have theories explaining the different levels of quality in our synopses (one of them puts the blame on Steve but don&#8217;t tell him).</p>
<p style="text-align: justify;">But we stick to the synopsis because there is no better way, to this date, to ensure a good European coverage of the Parliament&#8217;s news with the same pieces of information for 22 languages and 27 countries.</p>
<p style="text-align: justify;">Next time you meet an editor, ask him or her about his/her favorite synopsis. And about the worst ones he had to write from lately. And don&#8217;t forget to change the subject after a while, after all, all those chats about works can be sooo dreadful.     </p>
<p style="text-align: justify;"> </p>
<p> </p>
]]></content:encoded>
			<wfw:commentRss>http://www.writingforyeu.eu/2008/07/the-day-we-invented-the-synopsis/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

