String externalization practices and considerations for UNIX shell scripts
Enable your product's shell scripts for global audience
From the developerWorks archives
Date archived: December 19, 2016 | First published: December 24, 2013
In this article, we provide practical "How-Tos" and experiences
on externalizing shell script messages in a product. Also, we provide
suggestions on what to consider before and during translation enablement from
a globalization perspective.
The target audience is product developers who would like to enable their shell scripts for translation. After reading this article, readers can understand the considerations for externalizing shell script messages, realize the end-to-end process of string extraction and translation, and be aware of some known issues and their solutions.
This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some steps and illustrations may have changed.