- Sold between 250 000 and 1 000 000 dollars
- Referred between 500 and 999 users
- Envato Staff
- Author had a File in an Envato Bundle
- Has been a member for 4-5 years
- Author was Featured
- Support Staff
- Was featured in a podcast
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…)
- Community Superstar
- Sold between 1 000 and 5 000 dollars
- Bought between 10 and 49 items
- Has been a member for 2-3 years
- United States
- Exclusive Author
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
- Sold between 250 000 and 1 000 000 dollars
- Referred between 500 and 999 users
- Envato Staff
- Author had a File in an Envato Bundle
- Has been a member for 4-5 years
- Author was Featured
- Support Staff
- Was featured in a podcast
Thanks Chris, it’s always just a version away when I need things. 
It just gets ugly with the mix of text/php.
- Bought between 1000 and 4999 items
- Canada
- Has been a member for 4-5 years
- Referred between 1 and 9 users
check out glotpress
- Has been a member for 4-5 years
- Indonesia
- Exclusive Author
- Bought between 50 and 99 items
- Referred between 1 and 9 users
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.
Request processing...