679 posts Cudazi
  • Top Monthly Author
  • Weekly Top Seller
  • Elite Author
  • 6 Years of Membership
+13 more
cudazi
Envato team
says

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…)

3439 posts
  • Author Level 4
  • Collector Level 2
  • Community Superstar
  • United States
+2 more
organicbee
says

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

679 posts Cudazi
  • Top Monthly Author
  • Weekly Top Seller
  • Elite Author
  • 6 Years of Membership
+13 more
cudazi
Envato team
says

Thanks Chris, it’s always just a version away when I need things. :) It just gets ugly with the mix of text/php.

701 posts
  • 7 Years of Membership
  • Affiliate Level 1
  • Canada
  • Collector Level 6
chrismccoy
says

check out glotpress

223 posts
  • Affiliate Level 1
  • Collector Level 3
  • 6 Years of Membership
  • Exclusive Author
agusmu
says

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.

679 posts Cudazi
  • Top Monthly Author
  • Weekly Top Seller
  • Elite Author
  • 6 Years of Membership
+13 more
cudazi
Envato team
says

Thanks!

by
by
by
by
by
by