Tag Archives: google

Top tips for non-Word working

Editors may be most familiar with Microsoft Word and Adobe Acrobat but clients are increasingly publishing content on other platforms, such as Google Docs and content management systems (CMS). Hannah Sapunor-Davis demystifies some of these newer ways of working.

First, a bit of context: I don’t work on books, and I don’t work with typical publishers. I primarily work with designers, non-profits, business owners and digital publishing agencies. I find myself more often in Adobe, Google Docs, various content management systems (CMS) and product information management (PIM) systems than in Word.

So I wanted to share some insight into how working on non-Word platforms might change up your regular editing routines. I won’t go into detail about how the functionality and tools differ. There are lots of tutorials online for that, and it really depends on what platform you’re using, what updates have happened, and, maybe most importantly, how your client uses the platform.

But most of all, I’m here to tell you that stepping outside of the Word bubble is nothing to fear.

Real-time collaboration

Real-time collaboration is great when you need to put two heads together on a project. This can be especially helpful when you need to test functionality with a client, or when you are giving feedback in a live call. For some non-publishers, documenting changes and versions is not as important as the finished product. I found the real-time feature helpful when walking a client through edits to a webpage. We were able to come up with some new text and make changes together.

On the flip side, it can get messy quickly. A clear communication system is necessary to mitigate confusion about who should be doing what and when. In a CMS, this might be in the form of changing a status field from ‘Editing in progress’ to ‘Editing complete’, for example. For other platforms, like Google Docs, this might be communicated through an email or Slack message to the client to signal I have finished my review.

Working in the cloud

The obvious upside of working in the cloud is that you can work from most locations and most devices, as long as you have a stable WiFi connection. In the past, this has meant that I did not have to schlep my computer along with me on a trip because I knew I had access to a computer and WiFi at my destination. Even better, working in the cloud means I avoid having to store a lot of big files locally on my computer.

The other side of that coin is that if WiFi is not working properly, it can cause a major problem in your schedule. Likewise, I’ve had several instances where the platform I was supposed to work on suddenly had unscheduled maintenance. The client has always been understanding when system disruptions like this happen, but that doesn’t necessarily help when it causes a domino effect on the timelines of other clients’ projects. And I have also had it written into project agreements that I cannot work on the material on unsecured networks, which is something to be mindful of (and also good practice in general).

Different checklists

Most editors are used to creating checklists and using them in various projects. But checklists for non-Word platforms may go beyond the stylistic choices we typically navigate. For example, when editing a CMS:

  • In which order should you check all the parts when it’s not in a typical top-down, left-right order layout?
  • Are there any functionalities that need to be tested, such as clicking to open fields or sliding a navigation bar to the side?
  • Do you need to add any steps, such as clicking ‘Save’ periodically if the platform doesn’t save automatically?

Having this order of operations clarified helps develop a rhythm for catching all the parts in design-heavy material. For example, for one retail client, I have to check marketing copy against internal product information and photos. There are a lot of different fields to review, and I have developed my own visual pathway to reviewing all the crucial spots. The order looks like this, starting with 1:


Communication with clients

Here are a few extra questions that I recommend asking your client before getting started on a project:

  • Do I have all the permissions to view and edit what I need for the job? Sending screenshots or looking at your screen together with the client might help. You might not realise that a field is hidden from your view.
  • Is it possible to test the functionality of the platform without making changes to the system? This could be in the form of a draft, test user account or what is sometimes called a ‘sandbox environment’.
  • How will I know when I should start editing, and how will I let others know that I am done with my review? Deciding on one means of communication is key here.
  • What exactly needs to be reviewed? There may be parts that don’t need to be reviewed, such as certain text fields or formatting.
  • How should you save your work? The platform might save automatically or you might need to save it manually when finished.
  • Do you need to document your changes? The client might not care about seeing your changes. Or maybe you need to export the copy when you’ve finished editing to have a record of your ‘version’.
  • How should you send feedback? There might be a field where you can add comments and queries, or maybe you send them separately in a message.

Ready to branch out?

I didn’t follow any formal training for specific platforms. The training that I took at the CIEP and PTC covered most of what I needed to know for working with common non-Word platforms, such as Adobe and WordPress. For the rest, I learned by doing. (That’s my preferred way to learn anyway.) Each time I began using a new-to-me platform, clients understood that there was a learning curve and that certain editing functions that editors are used to, such as making global changes, might not be possible.

It doesn’t hurt to get familiar with basic HTML (HyperText Markup Language) coding. This has come in handy when I’ve noticed funky formatting, such as a word in bold that shouldn’t be or a missing paragraph break. In such cases, I can go to the HTML view and change that. And that’s one less query for the client to deal with. Of course, you should only do that if you have the permission to do so. Some clients might not want you to touch the formatting in any case. The good news is that basic HTML formatting looks very similar to the editing markup that most people learn in editing courses.

But in my experience, the skills needed for this type of work have less to do with technical know-how and more to do with a few specific soft skills. Beyond your foundational editing training and experience, you will do well if you:

  • adapt to different systems easily
  • learn relatively quickly
  • communicate precisely.

Having worked in a variety of programs and platforms has enabled me to feel confident about approaching businesses, especially those unrelated to the publishing industry. After all, the saying goes: Everyone needs an editor. And I would like to add to that: But not everyone uses Word.

About Hannah Sapunor-Davis

Hannah is a freelance editor in Germany, originally from Northern California. She has degrees in History/Art History and Arts Management and now loves helping individuals and small businesses write clear communication for their passionate audiences. In her free time, she likes to sew, swim, listen to podcasts or tramp through the nearby forest with her dog, Frida.

 

About the CIEP

The Chartered Institute of Editing and Proofreading (CIEP) is a non-profit body promoting excellence in English language editing. We set and demonstrate editorial standards, and we are a community, training hub and support network for editorial professionals – the people who work to make text accurate, clear and fit for purpose.

Find out more about:

 

Photo credits: computer clocks by Gerd Altmann from Pixabay; bubbles by Willgard Krause from Pixabay.

Posted by Julia Sandford-Cooke, CIEP information commissioning editor.

The views expressed here do not necessarily reflect those of the CIEP

Being open to editing in Google Docs

Are you considering taking on an editing project in Google Docs? Hetty Marx describes her experience of development editing in Google Docs and explains why, despite her initial doubts, it has opened up welcome opportunities.

Agreeing to edit in Google Docs

The first time I was offered a project that involved editing in Google Docs, my gut reaction was a clear ‘no’. I’d had a very busy few months, with a long and complex project, plus I’d been home-schooling my children through the first Covid lockdown. The idea of having to learn how to edit in a different program (one I’d not heard good things about) seemed too much.

But I was really intrigued by the project and was keen on the idea of working with this new client. I wondered if it would seem manageable once I was under less time pressure. The client agreed a later deadline, and a few weeks later I got started.

And … it really wasn’t that bad. Google Docs feels familiar to someone used to working in Word, so it was possible to get started editing and pick things up as I went along. There were some irritations but overall it wasn’t as dreadful as I’d feared. And the client and project were even better than I’d hoped. I continued working with them and edited around another 25 documents in Google Docs over the following two years. I’m now a third of the way through editing a 20-chapter, 400,000+-word textbook for the same client, again in Google Docs.

I still prefer editing in Word, but being open to editing in Google Docs has given me the opportunity to work with some wonderful authors and edit what have turned out to be some of my favourite projects to work on.

In this blog post, I’ll cover a few of the techniques that have helped me adapt to editing in Google Docs. Note that as I am a development editor, my edits involve a heavy use of comments, plus amending sentences using tracked changes/suggesting mode; copyeditors may face different challenges when editing in Google Docs.

1. Use Word alongside Google Docs

Consider using Word alongside Google Docs during your edit, to make use of the various features and functionality that are not available in Google Docs. I download the file as a Word document and keep it open on my second screen.

I find this invaluable for things like ‘Find’ (there are more extensive searching options), using macros (for analysing or finding things, rather than making changes), viewing changes and comments (I think some of the options in Word provide a clearer view) and checking word counts of a particular section.

2. Agree a workflow with authors

The biggest worry about editing in Google Docs for many editors is that the author can make changes while you are editing. There are solutions within Google Docs for this, like restricting others from editing the file during your edit (using the ‘Sharing’ options) but an upfront discussion about the workflow may be more appropriate.

Agree with the authors which of you will be working on the document at each point and make sure there are clear handovers. With Word, this is clear-cut as you need to send the file to the next person; in Google Docs you could tag someone in the document or email them so they know the file is ready.

Be open to a different workflow. Could the author finish the conclusion or work on a standalone aspect (like exercises) while you start editing the chapter? I’ve found this doesn’t cause any issues and it’s helped to keep to the schedule. But I also agree that other revisions during my edit would make the editing process significantly more complicated and less effective, so clear communication about what will work – and what won’t – is important.

3. Understand who can see your comments and edits and when

Some editors don’t like the feeling of having their editing watched in real time. While that doesn’t worry me, I do miss the chance for a final check-through of my comments before sending them to the author.

There are a few things to remember when commenting in Google Docs:

  • Once you click ‘Comment’, that comment is visible to anyone who has access to the document.
  • If a user has email notifications set up, they will receive the comment and may see it even if you delete it later.
  • If you or your client ‘Resolve’ comments (rather than delete them), they disappear from view but are still available and might be read by anyone who currently has access (or who is later given access) to the document.

In Google Docs, I only post comments that are ready for the authors to see. This means I need to spend a little longer during the edit to make sure my comments are clearly phrased and free of typos (a process I’d usually do at the end of an edit). But I still recommend that the authors wait until I’ve completed my edit before reading the comments, as I will sometimes amend or delete comments based on what I read later in the chapter.

4. Allow for more time

I find editing in Google Docs takes longer than editing in Word. I don’t have all my usual shortcuts, I spend time flipping between the Google Doc and Word document, some of the navigation is more clunky, etc. It doesn’t necessarily add a lot of time, but it certainly adds some (and it may be more for a copyeditor who uses more macros or programs like PerfectIt).

Wrapping up: Why I’m open to editing in Google Docs

I would still choose Word over Google Docs for development editing. But I’m glad I took on that first project. Being open to editing in Google Docs has led to two years of a steady stream of interesting work from a delightful client.

About Hetty Marx

Hetty Marx is a textbook development editor. She has nearly 20 years of publishing experience, including in-house as a commissioning editor at Cambridge University Press and as a development editor at Pearson. She is an Advanced Professional Member of the CIEP and author of the forthcoming CIEP guide Editing Textbooks.

 

About the CIEP

The Chartered Institute of Editing and Proofreading (CIEP) is a non-profit body promoting excellence in English language editing. We set and demonstrate editorial standards, and we are a community, training hub and support network for editorial professionals – the people who work to make text accurate, clear and fit for purpose.

Find out more about:

 

Photo credits: Lights by Enrique from Pixabay; desk by Olena Sergienko on Unsplash.

Posted by Julia Sandford-Cooke, CIEP information commissioning editor.

The views expressed here do not necessarily reflect those of the CIEP

Why general knowledge is not a trivial pursuit

By Julia Sandford-Cooke

A TV producer friend once told me that he was learning Icelandic to keep his brain active because his job wasn’t intellectually stimulating enough. I found this astonishing, as it’s not a problem we editorial professionals report very often. This itself is probably astonishing to certain people outside our industry, who like to tell us that all we do is spot typos and otherwise engage our brains very little. Of course, we need to know grammatical rules well enough to apply them to our projects – and also well enough to be confident about when to break those rules. But, as is made obvious each year at the conference quiz, many editors have a vast and varied general knowledge. Not even my extensive familiarity with obscure song lyrics has been enough to beat certain erudite colleagues to the coveted title of Winning Team.

It’s often the quirky, stylistic anomalies that stick in our minds; for example, it’s Spider-Man but Batman and Iron Man (you’d be surprised how often knowing that has been useful in my work).
But we also represent that unfashionable but, in my opinion, vital concept – gatekeepers of quality. Many of us are subject specialists, perhaps as a result of previous jobs, often with as much in-depth understanding of our area as our authors – and sometimes more.

But a good general knowledge is also a valuable asset in our line of work. We editors are an inquisitive bunch, always interested in learning something new. If we don’t understand an argument or trust a fact in a manuscript, neither will our readers. We might raise an author query, but frequently, we don’t have enough time or access to the author to await their response, so we simply need to check for ourselves.

On a day-to-day basis then, as far as essential editorial tools go, Google is right up there with PerfectIt. Other search engines are, of course, available, but ‘to google’ is now a transitive verb sufficiently common to be an effective, lowercase shorthand for ‘carrying out an internet search’. Google itself reportedly discourages the term, preferring ‘to search with Google’. I fear, however, that it is far too late to retrieve that particular phrase from the black hole of the internet.

While thinking about all this, I realised just how often I google words and phrases in the course of my work, so I started to keep a log of what I’d searched for, and what I’d found out. The list that follows is just a taster – I’ve omitted or slightly changed some examples to maintain client confidentiality. Note too that these days even editors accept that normal capitalisation and punctuation don’t apply to internet searches.


Term: turn on word spell check

Why? Mental block. I’m updating a brochure about my town, Fakenham, for a friend. I’m using last year’s text as a basis, but on a previous project I’d switched off Word’s functionality for checking spelling as I type. Now I can’t remember how to turn it back on!

Outcome: The top link is from Microsoft, the horse’s mouth, and all the information I need appears on the search page. It’s File/Options/Proofing/Check spelling as I type. The red squiggles reappear. Hoorah!


Term: james beck auctions

Why? I need to increase the number of attractions in the brochure from 15 to 20 (my friend wants ‘20 attractions for 2020’), so I’m splitting up the market and auction entry and want to lengthen the auction text by about 20 words.

Outcome: The search took me straight to the auction house’s website, which confirmed the numbers and types of items typically up for auction. New text covered. Success!


Term: hempton bell

Why? I’m checking the name of the local pub known for its folk jam sessions.

Outcome: Its URL is thehemptonbell.co.uk but the text on the website is The Bell Public House. I’ll go with The Hempton Bell, which is what locals call it, to avoid the current wordiness of ‘the Bell Public House in nearby Hempton’ …


Term: fakenham christmas tree festival 2020

Why? Last year’s text states last year’s Christmas Tree Festival dates. Fakenham established one of the first Christmas tree festivals in the country about 20 years ago, and now it makes thousands of pounds for charities and the church, so I want to ensure this year’s dates are correct.

Outcome: Rare Google fail. The parish church website doesn’t state this year’s dates yet, and nor does anywhere else, so I’ll add a query to the text.


Term: arts and crafts fakenham

Why? I need another entry to make it a round 20. How about art? I know there’s a ‘have a go’ crafts shop, and an annual Norfolk and Norwich art trail, but is there anything else?

Outcome: Hmm, the results reveal only the shop I was thinking of, plus (inevitably) The Works chain for art supplies, and a picture framer. That’s not enough.


Term: norfolk and norwich open studios

Why? This is my favourite event of year but not many artists participate in my town.

Outcome: It takes me to the event’s website but the search mechanism there doesn’t allow me to search by location so I have to download last year’s brochure. I search the PDF for ‘Fakenham’ but only one artist was based in the town. Forget that idea, then! What else does Fakenham offer?


Term: pensthorpe norfolk

Why? I read the brief again and my friend had suggested including Pensthorpe Natural Park,
a tourist attraction on the outskirts of town.

Outcome: The search takes me directly to the website, where there’s plenty to fill 50 words.
I’d forgotten that BBC’s Springwatch was filmed there a few years ago. Job done.


Term: Neprajzi Muzeum artefacts

Why? A client with whom I’m working on a new edition of a travel guide to Budapest has heard that one of the main attractions, which we knew was relocating, won’t reopen until 2022. No photos of the new building are available. We only have photos of the original building, which are now wrong.

I wonder if we can use photos of some of the major artefacts, as they will probably still be on display when the museum does finally reopen.

Outcome: The image search revealed some distinctive artefacts so I suggest we include these, which would avoid having to restructure the book to accommodate a new (as-yet unspecified) attraction to fill the space. The updater of the book later copies me into an email to the client suggesting the same thing, and the client agrees. Success! Now it’s up to the poor picture researcher to source appropriate photos.


Term: karpatia restaurant budapest

Why? Are the accents correct in Kárpátia? It also appears as Kárpàtia in the text.

Outcome: Kárpátia is correct. I amend the text.

 


Term: musee picasso

Why? In a Paris guide this time, I need to amend a photo caption to something more meaningful. The image showed a gallery in the museum but the picture credit only includes the name of the museum, not the artwork that is featured.

Outcome: I can’t find any images of the exact gallery, but reviews and descriptions say it’s a calm and peaceful place to view Picasso’s art, so I incorporate that into the caption.


Term: THE Steak House Circus Circus

Why? Are those weird capitals correct in this Las Vegas travel guide?

Outcome: Apparently so. Hoorah for branding.


Term: edingburgh castle

Why? The source image seems to show the whole city, not the castle specifically.

Outcome: ‘Showing results for edinburgh castle. Search instead for edingburgh castle?’ Yes, thank you for patronising me, Google. But it was indeed an image of the whole city. I add a query to the PDF.


Term: personal care elderly frail

Why? I’m editing a report that contains this rather depersonalised phrase. Is it in common use?

Outcome: The search suggests not. I will change the text to ‘personal care for frail elderly people’ but will add a query to confirm whether the original phrase is acceptable.


Term: is bristol in north somerset

Why? I’m from Bristol originally and I’m pretty sure it’s a county in itself. I know it’s certainly not in the long-obsolete Avon, a common mistake that drives me crazy.

Outcome: Bristol is indeed a county (and/or a unitary authority), its population twice as large as the two bordering counties, South Gloucestershire and Bath & North East Somerset (is the ampersand correct? Google doesn’t have a definitive answer to that).


Term: rail services patchway

Why? Is there a station in Patchway?

Outcome: Yes, there is.


Term: CrossCountry and GWR lines

Why? Is the brand for CrossCountry rail services one camelbacked word?

Outcome: Yes, it is.


Term: Supportive of or supportive to

Why? In a proofread, the text reads ‘the parents are supportive to the child’ but I would normally expect to see ‘supportive of’. Is ‘to’ common in such a context?

Outcome: I find a website that says ‘of’ is a much more common construction. However, another web forum suggests ‘towards’ as an alternative, which I think fits the context better. I change the text accordingly.


Term: IDE (Integrated Development Environment)

Why? I don’t think the definition should be capitalised but it might be a branded or copyright expression.

Outcome: It’s not. Lowercase.


Term: lower case

Why? Mental block – is lowercase one word?

Outcome: ‘According to The Associated Press Stylebook and the Microsoft Manual of Style, you should write “lowercase” as one word when being used as an adjective and as a noun.’ So there you go. I check my PDF mark-up.


Term: personal identification number

Why? Is this what PIN stands for, rather than ‘personal identity number’?

Outcome: Various sources say so. Wikipedia (which incidentally always needs to be backed up with another source) has an amusingly passive-aggressive answer: ‘A personal identification number, or sometimes redundantly a PIN number … ’


So what can we conclude from this little experiment? A few things, I think:

  • Although we’re rarely asked specifically to check facts, it’s always worthwhile maintaining an open, questioning approach so that we can pick up on anything that doesn’t quite ring true. Perhaps ironically, the more you know, the more you question and the more you find yourself verifying the text.
  • Taking 30 seconds to search the internet takes much less time and effort than reflexively raising an author query. As an occasional author myself, I’d much prefer my editor to proactively check something that doesn’t sound right instead of just asking me, as long as I have the chance to see any amendments afterwards.
  • That said, the internet doesn’t provide all the answers. Sometimes, we do need to use other sources, such as the CIEP forums, the client, the author or subject specialists.
  • Our work exposes us to a huge volume and variety of information. It’s a form of continuous professional development (CPD) – on-the-job learning with the side benefit of a mental library of interesting facts.
  • Fluency in Icelandic is optional.

Julia Sandford-CookeJulia Sandford-Cooke of WordFire Communications has 20 years’ experience of publishing and marketing. She has written and edited numerous textbooks, specialising in vocational education, media studies, construction, health and safety, and travel. Her team has twice won the Fakenham Library quiz; her quiz superpower is song lyrics.

 


Photo credits: jukebox – Alex Holyoake; Christmas tree Aurelio Arantes; Budapest – Lucas Davies; Clifton suspension bridge – Nathan Riley, all on Unsplash

Proofread by Alice McBrearty, Entry-Level Member.
Posted by Abi Saffrey, CIEP blog coordinator.

The views expressed here do not necessarily reflect those of the CIEP.