Is there a best practice for internationalizing large amounts of text for built-in theme documentation or similar other than just wrapping in the __() or _e() functions?
Maybe providing ways of including different txt files based on language settings? (en_EN-setup-info.txt, bg_BG-setup-info.txt,, es_ES-setup-info.txt, etc…)
I suggest sticking to _() or _e() as in WordPress 3.3 they are adding language packs for core/plugins/and themes ….. I haven’t had time to dig into what it will actually do and theres not much docs on it yet
Thanks Chris, it’s always just a version away when I need things. 
It just gets ugly with the mix of text/php.
check also CodeStyling plugin,
http://wordpress.org/extend/plugins/codestyling-localization/we recommend it to our theme buyers… it also has built-in scanner to update the translation file.
1,656,655
Total Marketplace Items1,620,476
COPYRIGHT © 2012 ENVATO| TERMS OF USAGE| SUPPORT/HELP| ICONS BY TANGO + WEFUNCTION + FAMFAMFAM
Adobe®, Flash®, Flex®, Fireworks®, Photoshop®, Illustrator®, InDesign® and After Effects® are registered trademarks of Adobe Systems Incorporated.
Request processing...