@Agile Apricot
You can use any field you want, body=>body_jp, extras=>extras_jp, other_stuff=>other_stuff_jp. It’s entirely up to you.
@Mark Bowen
Thanks, forgot to update the language file, I’ll fix that now. Also I went with “translator:simple” for the exact reason ingmar mentioned. Who knows someday there may be a translator:advanced or just a translator module or a translator:quick or translator:utf8.
Hi Ingmar / Mark,
Thanks for the explanation. Pretty much understood now so thanks for that.
@Mark Have already updated this on my language file because knowing me I would probably forget the syntax if I hadn’t. I’m always going into the Settings / Documentation for plugins and extensions because my head is so full of code that I can never remember it all!! 😊 Thanks for saying that you will update it though. I’m sure it will help others…
…that is if anyone else has a head like a sieve like me!! 😊
Thanks again for all your continued excellent work for use with EE!!
Best wishes,
Mark
I’ve just had an idea! Would it be possible to also make this plugin switch section/weblog based on the language selected using the prefix method?
The trouble I’m faced with is I’m making a big site where each language needs it’s own weblog (for SEO reasons and so translators don’t overwrite each other).
The problem with this idea is the extension works based on url, BUT what if it was based on a unique custom field ID? I’m just trying to make it so I only have to make one set of templates for this site.
I’m not suggesting you change the plugin i’m just asking if you think this would work, I have a PHP programmer I can get to build it. Thanks Mark.
Hi Mark,
Great update, thanks for that! I think you may still need to update the language file to deal with the {exp:language:switcher} bit though 😊
Thanks again for all your fantastic work with EE. Absolutely one of the best people out there…
…oh and a very good name you have too!! 😊 😊
Best wishes,
Mark
alright textdriven, 1.0.9 should switch global variables now. it works the same as always, use {branding} for your default language, and {branding_ja} for japanese specific content.
as for embeds, it is a little trickier as I don’t have access to the template through an extension. You could however do this with a conditional:
{if simple_language == "English"}
...
{if:elseif simple_language == "German"}
...
{/if}
Thanks Mark. So If a global viable doesn’t have renditions in other languages it will still use the normal one for all languages? I have a quite a few cases where it is just html in a variable that doesn’t need to change
For embeds I just meant embed names. Like this one…
{embed="global/communication_en"}
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.