If we wanted to localize documentation content, here are some factors involved (based on my experience with this):
vendor to do translation (for example, internal vs external) and pricing
format of files to provide to vendor and receive in return
process for vendor to ask questions about uncertain terms
process for verification of quality
better enforcement/automated tests for simplified language and proper style guide use to ease translation
storage for the translation and the translation memory database (and how it hooks into documentation)
documentation website updates to allow for language switching
adding a URL that includes language code (also needed for versioned documentation, see Figure out a way to version documentation for different releases #30
publishing process to output different languages
process for translating new or updated files
processes to "lock down" files that have been translated and avoid unnecessary changes in source content
@randymeech wants to start thinking about translating documentation, particularly for Korean.
If we wanted to localize documentation content, here are some factors involved (based on my experience with this):
@randymeech wants to start thinking about translating documentation, particularly for Korean.