Comments on: How To Prepare a CMS for Website Translation http://www.searchlaboratory.com/blog/2009/09/how-to-prepare-a-cms-for-website-translation/ Search Marketing Blog Tue, 24 Jan 2012 08:09:37 +0100 hourly 1 http://wordpress.org/?v=3.1.1 By: Expanding Abroad – Do’s and Don’ts | Search Laboratory http://www.searchlaboratory.com/blog/2009/09/how-to-prepare-a-cms-for-website-translation/#comment-19 Expanding Abroad – Do’s and Don’ts | Search Laboratory Wed, 22 Dec 2010 08:50:37 +0000 http://www.searchlaboratory.com/blog/?p=73#comment-19 [...] you are doing this for the first time then get some expert help.  Have a look at this introduction to internationalising a website as it contains some things you should [...] [...] you are doing this for the first time then get some expert help.  Have a look at this introduction to internationalising a website as it contains some things you should [...]

]]> By: Ramon http://www.searchlaboratory.com/blog/2009/09/how-to-prepare-a-cms-for-website-translation/#comment-18 Ramon Mon, 02 Aug 2010 13:29:55 +0000 http://www.searchlaboratory.com/blog/?p=73#comment-18 As a professional translator, I specially liked #1, as using this kind of "helping" capabilities reduces my productivity to just a fraction of what it could be. Using my own tools, on the contrary, would improve my productivity ten-fold. For this reason, when I get customers that ask me to use their CMS, I charge them more. Though I agree with the indicated steps, I must state my disagreement with the indicated at the end of #8, that error messages should not be translated. That is exactly the detail that makes visitors recognize a page as being or not in their language. I actually wrote recently an article on this subject: http://www.seo-translator.com/did-you-localize-your-error-pages/ Finally, I'd like to point out that these steps, though, necessary, are not the only ones. In particular, for #5 there are many more things associated that simply having SEO-friendly page names... As a professional translator, I specially liked #1, as using this kind of “helping” capabilities reduces my productivity to just a fraction of what it could be. Using my own tools, on the contrary, would improve my productivity ten-fold. For this reason, when I get customers that ask me to use their CMS, I charge them more.

Though I agree with the indicated steps, I must state my disagreement with the indicated at the end of #8, that error messages should not be translated. That is exactly the detail that makes visitors recognize a page as being or not in their language. I actually wrote recently an article on this subject: http://www.seo-translator.com/did-you-localize-your-error-pages/

Finally, I’d like to point out that these steps, though, necessary, are not the only ones. In particular, for #5 there are many more things associated that simply having SEO-friendly page names…

]]> By: James Keddie http://www.searchlaboratory.com/blog/2009/09/how-to-prepare-a-cms-for-website-translation/#comment-17 James Keddie Thu, 01 Oct 2009 02:10:08 +0000 http://www.searchlaboratory.com/blog/?p=73#comment-17 I've read many articles on preparing for web localization but most don't point out the simple, but necessary steps you cover on the 'under the hood stuff'. An excellent article Ian! Hope you are keeping well :-) James I’ve read many articles on preparing for web localization but most don’t point out the simple, but necessary steps you cover on the ‘under the hood stuff’. An excellent article Ian!

Hope you are keeping well :-)

James

]]> By: Tom Crowe http://www.searchlaboratory.com/blog/2009/09/how-to-prepare-a-cms-for-website-translation/#comment-16 Tom Crowe Fri, 25 Sep 2009 11:03:22 +0000 http://www.searchlaboratory.com/blog/?p=73#comment-16 This is a very useful article and points out a lot of things that need to be considered when localising content for the web. I am sure this will answer a lot of questions for anyone considering multilingual content. This is a very useful article and points out a lot of things that need to be considered when localising content for the web.

I am sure this will answer a lot of questions for anyone considering multilingual content.

]]>