I often enjoy reading the blog/website Anglotopia, as it is written by a person who loves England and UK stuff as much as I do (if not more) and is making a living doing it (lucky!). This latest article that was posted there is yet another example about localized English, and in this case, translation. We talk about standardizing English for easier translation, whether it’s for machine translation or localization purposes, and this article is a perfect example of how even an American like me would need a translation of the “Yorkshire” English first, but fortunately I understand enough French that I can figure out the translation of the expressions from the French instead. This had to be a little bit complicated to do, but it’s an excellent exercise!
Evidently, Siobhan Thompson is back, and BBC’s Anglophenia must be doing a series on the difference between British English and American English. Here’s another gem on British colloquialisms–some you may have heard before, and some that, well, my British friends will have heard more often than we Yanks….
As I find more, I will continue to post these! I find these fascinating!
If you have suggestions for articles or videos you’ve seen for other versions of English for comparison as well, email me and let me know so we can share with everyone! For example, I’d love to see a video comparing Canadian English and American English, or even Canadian English and British English. Or Australian English, Indian English, or South African English, for that matter. 🙂
It seems these kinds of articles are coming out nonstop these days. While this one doesn’t have a video (awwwww), it’s short and to the point, and is another example of why spoken English can be rather confusing. We have pronunciation confusion here in the States with certain towns and such, some due to the same issue mentioned in this article from the names of towns that we took from Mother England, but also incorporating other languages like Native American, Spanish, and French just to name a few.
As a follow-up to my fun post, “No Wonder (Verbal) English is confusing!“, here’s a follow-up that really shows how crazy it can get. Although I think in the end, there is some (okay, a lot of) Celtic actually thrown in there rather than simply English spoken with a Scottish brogue, it proves that even in the United Kingdom–other than Wales who definitely have their own language with Welsh–that English is NOT the same everywhere. Here to prove that is Karen Gillam, who played Amy Pond on Doctor Who.
We definitely didn’t hear this panel say to any of us, “I’m afraid you’re just too darn loud!”
I apologize for my blog coverage of the 2014 STC Summit edition of Adobe Day being delayed–it’s been a busy month! But hopefully, you’ll feel it’s been worth the wait, and you had a chance to see my live Twitter feed as it happened.
The STC’14 Adobe Day felt a little bit different this year. One of the things I noticed was that as much as Adobe says that these Adobe Day events are Adobe-product free, lately, they haven’t been. HOWEVER, they are still not one big, in-person infomercial either. Adobe products are not brought up much, but if they are, it’s to show that they can be tools to use to create solutions to common tech comm issues. So, it might be an inadvertant infomercial in that respect, but it’s not done in a blatant way that screams, “YOU NEED TO BUY ME!!!!!! PLEASE BUY OUR PRODUCTS!!!” Adobe continues to do a good job in showing what tech comm issues are out there, and as leaders in the software field, they are tuned into these issues and are creating products that benefit the technical communicator. I think that’s fair enough. The talks, overall, were broader topics that in some instances used Adobe Tech Comm Suite tools to provide solutions. And you have to remember, while these talks are aimed to be product-free for the most part, it’d probably look pretty bad if you had someone declaring all the glories of a competitive product when Adobe is hosting the event. Y’know?
With that out of the way, I observed some other things that made this a little bit different. First, there were fewer speakers this year. I felt that was a good thing, because in the past with more speakers, each speaker would be racing to get his/her presentation completed in a very short amount of time, and there would be little time for questions or discussion. Since there were fewer speakers this year, each one could elaborate more on their topic, which allowed for more time for questions and discussion. More networking time during the breaks was also a benefit from having less speakers.
The other difference I saw dealt with the speakers themselves. While they were all familiar, established voices in the tech comm world, it wasn’t the same crowd that one usually sees at Adobe Day events. All of them have participated in Adobe events or other tech comm events before, but in the past, it usually is most of the same speakers up on the podium. While I like all the “usual suspects” very much, and consider them my mentors and have become friends with several of them, seeing these new “players” was actually refreshing to me. I hope that Adobe continues to change up the speaker lineups with future Adobe Days, as all the speakers I’ve heard have a clear voice that’s worth listening to, and hearing as many of those voices as possible provides both variety and fresh perspectives going forward. As I go through each presentation in forthcoming blog posts, hopefully you’ll see what I mean.
But as tradition in this blog dictates, I always start with the panel that capped off the Adobe Day event. I find that these panel talks bring an umbrella perspective to where we are as a profession through several points of view, and seeing where there are agreements and disagreements in the issues at hand.
The Adobe Day Panel L to R: Matt Sullivan, Bernard Aschwanden, Joe Welinske, Marcia Riefer Johnston, and Kevin Siegel
Matt started with the point that tech comm is more than tech writing now, so what do we need to improve short-term and long-term? Kevin responded first, saying that we need to do more with less on smaller displays and adapting the content appropriately for mobile. Marcia added to that, saying that using less can mean writing tighter as well. (She has a technique she taught during the STC Summit, in fact!) Joe agreed with Marcia, adding that technical communicators need to put in the time to make concise content meaningful, and to look at simplified English as part of that objective. Bernard felt that attending workshops and demonstrations were important, because technical communicators need to continually learn and adapt in this industry! He added that SMEs (Subject Matter Experts) should contribute to content, but technical communicators should control it. Kevin also agreed with Bernard, saying that SMEs are writing content more often now, so teaching them to write tighter will help. Marcia chimed in that many people are now being required to write, but don’t have the skills. We need to help with that.
Moving onto topics about how technology affects technical communication, Kevin said that new technology, like Google Glass and other wearables, is emerging, and we need to understand how these work. Joe pointed out that the Pebble watch now is starting to have user docs now, and more will be emerging. Bernard added that gesture based technology similar to the Xbox Kinect will need documentation.
Matt then asked, “What should we look forward to in the next five years?” Bernard felt that less specialization will be needed so that the right people write the right content, such as an engineer who can write. Specialized writing will be very important. Joe added that we need to agree on taxonomy and terminology, and use style sheets more often for consistency. Marcia believed that topic-based writing will be emerging more as a growth area. Kevin explained that in e-learning, there is a need to develop learning for new devices that responds to user displays, thus accomodating multiple screens.
The next question asked about how to help educate and help with adapting certain generations adjust between print and digital writing/designing. The consenus was that we just need to adapt. The panel encouraged the audience to get to know your UX/UI people, as they will help you learn to adapt, especially if you aren’t as tech-adaptive.
The last question centered on customers customizing their content–is this a trend? Bernard leapt into a response with, “GOOD! DO IT!” He encouraged us to help customers to start doing personalized help, or personalizing any information, for that matter! Moderator Matt closed by saying that rich media that engages users is going to be about content strategy, but it will also be about content marketing. The group agreed that personalized, concise information going forward will be best!
“I guess you guys aren’t ready for that yet–but your kids are going to love it!”
And that was it! The session went by quickly, but as you can see, there was a lot of great information that many technical communicators can take and use going forward in their own work. While it might take some time to adapt, sure enough, it will bring the field forward as technology and the way we access it moves ahead.
Coming soon: The individual presentations at Adobe Day #STC14 Edition!
I often enjoy reading the blog/website Anglotopia, as it is written by a person who loves England and UK stuff as much as I do (if not more) and is making a living doing it (lucky!). This latest article that was posted there is yet another example about localized English, and in this case, translation. We talk about standardizing English for easier translation, whether it’s for machine translation or localization purposes, and this article is a perfect example of how even an American like me would need a translation of the “Yorkshire” English first, but fortunately I understand enough French that I can figure out the translation of the expressions from the French instead. This had to be a little bit complicated to do, but it’s an excellent exercise!
TechCommGeekMom 
You must be logged in to post a comment.