Chantal Bossé got hooked on PowerPoint while doing instructional design in the mid-90s. Convinced there was a better way to present, she started CHABOS in 2004 and became a presentations & visual communications expert. She helps entrepreneurs, speakers, and trainers improve their presentations' impact by having a clear message, great visuals, and a memorable delivery, whether in French or English. Chantal has been a speaker at various business events and a few international webinars, she is a presentation coach for the TEDxQuebec event.
In this conversation, Chantal discusses her tricks on working with multiple proofing languages within PowerPoint.
Geetesh: Chantal, you work with both English and French PowerPoint slides. What are the frustrations you face with multiple proofing languages, and how do you cope up with and overcome these issues?
Chantal: My operating system and Office installations are in French, but I regularly need to work in English too, and it can sometimes be a challenge. There are many variables at stake, like the language the file was created in, and a mysterious mix of your operating system and Office user interface language, and your keyboard language. I say "mysterious" because many times I have seen the proofing language switched in my file without doing changes myself. For a while, I just thought that I had to be lucky to set all language parameters the right way, and that was really frustrating.
Besides the fact that this language mess was making me less productive, the most important element was that I did not want my clients wondering why they had so many red-underlined words in their file. Knowing regular users will not always look for complicated solutions, I tried to find what could be done within Windows & Office. I first tried using Microsoft's Language Interface Pack – LIP - for Office, but it became a nightmare because I would need to save all my user customization before I changed the interface language. And that still meant battling with my default keyboard language.
Then I stumbled on the feature allowing us to change the default input language in Windows. With my LIP installed that meant I could simply configure Office so it would display in the same language than Windows. What a relief! I stopped losing my customizations and my work became more effective when working on English files.
As long as we respect the order of the two-step process, it works like a charm. But you are still required to switch back and forth every time you are changing project language, which is still a waste of time if you need to do it often in a day. But it is way better than trying to manually fix the language on all slide objects one by one!
Readers should read these two Support articles from the Microsoft site to help them determine how to proceed, according to their Windows and Office versions.
April 2003 | May 2003 | December 2003 | January 2004 | February 2004 | March 2004 | April 2004 | May 2004 | June 2004 | July 2004 | August 2004 | September 2004 | October 2004 | November 2004 | December 2004 | January 2005 | February 2005 | March 2005 | April 2005 | May 2005 | June 2005 | July 2005 | August 2005 | September 2005 | October 2005 | November 2005 | December 2005 | January 2006 | February 2006 | March 2006 | April 2006 | May 2006 | June 2006 | July 2006 | August 2006 | September 2006 | October 2006 | November 2006 | December 2006 | January 2007 | February 2007 | March 2007 | April 2007 | May 2007 | June 2007 | July 2007 | August 2007 | September 2007 | October 2007 | November 2007 | December 2007 | January 2008 | February 2008 | March 2008 | April 2008 | May 2008 | June 2008 | July 2008 | August 2008 | September 2008 | October 2008 | November 2008 | December 2008 | January 2009 | February 2009 | March 2009 | April 2009 | May 2009 | June 2009 | July 2009 | August 2009 | September 2009 | October 2009 | November 2009 | December 2009 | January 2010 | February 2010 | March 2010 | April 2010 | May 2010 | June 2010 | July 2010 | August 2010 | September 2010 | October 2010 | November 2010 | December 2010 | January 2011 | February 2011 | March 2011 | April 2011 | May 2011 | June 2011 | July 2011 | August 2011 | September 2011 | October 2011 | November 2011 | December 2011 | January 2012 | February 2012 | March 2012 | April 2012 | May 2012 | June 2012 | July 2012 | August 2012 | September 2012 | October 2012 | November 2012 | December 2012 | January 2013 | February 2013 | March 2013 | April 2013 | May 2013 | June 2013 | July 2013 | August 2013 | September 2013 | October 2013 | November 2013 | December 2013 | January 2014 | February 2014 | March 2014 | April 2014 | May 2014 | June 2014 | July 2014 | August 2014 | September 2014 | October 2014 | November 2014 | December 2014 | January 2015 | February 2015 | March 2015 | April 2015 | May 2015 | June 2015 | July 2015 | August 2015 | September 2015 | October 2015 | November 2015 | December 2015 | January 2016 | February 2016 | March 2016 | April 2016 | May 2016 | June 2016 | July 2016 | August 2016 | September 2016 | October 2016 | November 2016 | December 2016 | January 2017 |
Microsoft and the Office logo are trademarks or registered trademarks of Microsoft Corporation in the United States and/or other countries.