Preparing a Blog Post for Translation

If you're going to have a blog post translated, you can save yourself and the translators steps by doing the following:

  1. In Roller, Edit the blog entry you want to translate.
  2. If you're not already in Code View, pressed the code view button in the toolbar to see the raw HTML code.
  3. Copy and paste all of that, along with the title, into a text editor, save it as a TXT file. (I title each file with the initials of the blog owner and the English title of the post.) By giving the translators all the HTML code, they can translate the language portions while preserving your links and images - which will mean a lot less work for you later.
  4. Batch up the txt files into a zip file and send it to the translation team.

Publishing Foreign-Language Posts

  1. I have not been able to find a way to get OpenOffice Writer to display Chinese-language files correctly; this may have to do with the fonts I have installed. I open the translated HTML files in Word, which automatically recognizes the character set as Chinese Simplified(GB2312).
  2. Copy and paste the entire HTML from Word into a new Roller entry (again in code view!).
  3. You should now have a translated post looking exactly like the original as far as images and links.
  4. When I have a batch of translated posts to publish, I use Roller's pub time/date feature (under Advanced Settings at the bottom of the page) to space the posts over several days (usually only weekdays), to give people something to come back to read.

To get your translated blog posts to show up separately from the main language of your blog, see Adding Language Selector Links to a Roller Theme.

Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Sign up or Log in to add a comment or watch this page.


The individuals who post here are part of the extended Sun Microsystems community and they might not be employed or in any way formally affiliated with Sun Microsystems. The opinions expressed here are their own, are not necessarily reviewed in advance by anyone but the individual authors, and neither Sun nor any other party necessarily agrees with them.

Copyright 1994-2009 Sun Microsystems, Inc.
Powered by Atlassian Confluence
Sun Guidelines on Public Discourse Privacy Policy Terms of Use Trademarks Site Map Employment Investor Relations Contact