Cheers Mark. I’m glad it was just that, I was worried it was some PHP error.

Thank you for making this great extension!

It works great. Is it easy/possible add custom fields named something other than “body” or “title”?

Also there are areas of the site that need to change based on the language like the footer and branding. I thought I would make a new section called “snippets” with a text area custom fields for each language. There just do something like this…

...is this the best method for doing this?

Hi Mark,

WOW!!! This is an absolutely amazing solution, thanks a lot. We just finished creating a site in two languages and although the method we used in the end was pretty straightforward, this solution is really impressive. Thanks.

Just one thing I did notice though. When you go to Extensions -> Simple Translator -> Settings the instructions tell you to use :

as opposed to :

which is what it is supposed to be I think?

Sorry if this has already been mentioned. I did read through most of the replies but sometimes do miss a thing or two!!

Once again though, thanks for a simply fantastic extension. Very greatfully received.

Best wishes,

Mark

Hi Mark,

Sorry to be a pain on this again. I was just wondering why you chose to write the tag as :

instead of :

PLEASE NOTE THE CODE SHOWN BELOW IS NOT THE CORRECT CODE

Just thought that it might be easier to remember in that way as it is the name of the extension?

I could be sleeping whilst writing this though so if there is a reason for it then please don’t feel bad in telling me even if it is blatantly obvious as my head sometimes stops working every now and then and just needs a slight kick-start to get it going again!!

Best wishes,

Mark

Actually, this top-down approach is quite common in software, and particular programming. This leaves room for {exp:translator:advanced} or similar, while still showing their common heritage or purpose, as it were.

@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.

@Agile Apricot

I think this could absolutely work.  It would most likely behave the exact same way as the category switching.

@Agile Apricot,

The new version now allows switching weblogs in a very similar manner to the way categories are switched.  The documentation has been updated in the extension settings page.

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

Thanks, Mark.  Don’t know how that tag snuck back in there, it should be out now.

Hi Mark,

Thanks for the update and a massive thank you again for all the great work!!

Just one word really…

...F-A-N-T-A-S-T-I-C!!!

Best wishes,

Mark

Mark Huot - 14 May 2007 10:19 AM

@Agile Apricot,

The new version now allows switching weblogs in a very similar manner to the way categories are switched.  The documentation has been updated in the extension settings page.

Excellent. Thank you so much Mark.

Hi Mark.

I’m back. Is it possible to get this plugin to switch global variables based on the selected language. For example…

{branding_en}

would switch to…

{branding_de}

If you were viewing it in German.

textdriven - 06 June 2007 07:53 AM

Hi Mark.

I’m back. Is it possible to get this plugin to switch global variables based on the selected language. For example…

{branding_en}

would switch to…

{branding_de}

If you were viewing it in German.

Opps, add embeds to that request too.

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:

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”}