This is a wonderfull module! We are waiting for a D7 version.

CommentFileSizeAuthor
#36 transauto.zip1.66 KBVote_Sizing_Steve
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

klonos’s picture

subscribing... so I know when there's something to test ;)

greg.harvey’s picture

This can be done when Rules stabilises:
http://drupal.org/project/rules

greg.harvey’s picture

Assigned: Unassigned » greg.harvey

Rules is looking good, there's a stable 'alpha' and Drupal 7 is released, so I think it's time to do this...

greg.harvey’s picture

Category: support » task

Oh, and it's a task!

klonos’s picture

Great news Greg!

BrightBold’s picture

What klonos said in #1.

j.slemmer’s picture

Greg,

Is there a sort of road plan? We have a possible client coming, up that needs automatic translation.
So if we score that client, are there options to work together on getting a d7 version working?

Looking forward to your awnser

Jons

klonos’s picture

Title: D7 Port » i18n Auto Translate port to D7

...lots of issues vaguely named "D7 port" or similar. Specifying project in title to make it clear in our dashboards ;)

greg.harvey’s picture

The module only contains three functions - so a straight port is very simple:

1. Update the Rules hooks and rule code to the D7 version of Rules
2. Ensure all the i18n functions called in the translate function are still valid and sane

That's it!

I won't be able to look at this until later in the week at the *earliest* (as we currently don't have a client need) but anyone who is vaguely competent at PHP and Drupal could tackle this so, as ever, patches welcome! =)

alpp’s picture

thanks for this great coding, it really is a time saving module. how is the progress about drupal 7 version? is it going to be available soon?

greg.harvey’s picture

It would be great if people started helping with this, instead of just subscribing. As of TODAY, you don't need to be a Drupal developer to convert the rules to the new API. Yay! \o/

See: http://drupal.org/node/997474#comment-4242324

If someone could import and export the old Rule in the new format, that's already a start.

klonos’s picture

Greg, I want to help but I'm confused, what exactly do you want done? What rule do you want imported then exported to the new format?

alpp’s picture

auto translate rule? well i guess it means that on latest 7.x-2.x-dev version rules which ran online today, has a feature to upgrade and import drupal 6 rules? if that is so simple, it's easy, but what else should we do? auto translate for version 6 can not be installed on 7, so it seems i won't be able to test this upgraded rule on a 7 site.

alpp’s picture

i installed rules 7 dev version and tried, unfortunately it was impossible to import the version 6 auto translate rule:

* Import failed.
* Unable to parse the pasted export.

greg.harvey’s picture

Ok, what a shame! Obviously Rules still needs work. Thanks for trying - appreciate it.

Still hoping someone with more time than me will post a patch, since it's only two hooks. I'll have to try and find time one weekend for this otherwise. It's on my TODO, but so are a million other things. =(

alpp’s picture

maybe there is something more to do about this, because i tried importing the default example rule of rules 6, to rules in drupal 7, and i got the same error, but this guy said that it is fixed? so maybe "upgrading" is not just importing the rule as usual? i don't know.

alpp’s picture

yes i was missing the whole thing, it wasn't just an import, i think it needs a site that is upgraded (with the rules) to drupal 7 for this, i can try that, but also there is a line in the readme saying that:

"if you used an action provided by a third party module, make sure the module is in place and upgraded"

so i think it means, it needs a drupal 7 version of auto translate, to be able to convert the old rules?

greg.harvey’s picture

I wouldn't upgrade your site - just make a blank D7 integration and try to run the Rule through the updater (export from Drupal 6, copy and paste in to Drupal 7 update tool) to see if it treats it. If so, post it back here and the port is half done! =D

alpp’s picture

i just tried that, on the rules conversion page, the example rules are there waiting to be converted, but unfortunately it does not see the auto translate rule.

i think the reason was the rules upgrade instruction i have pasted above: "if you used an action provided by a third party module, make sure the module is in place and upgraded" :(

alpp’s picture

there is no copy paste conversion, the upgrade tool of rules needs the site to have the version 6 rules inside, to be able to convert them.

here is what i did briefly:

1. i set up a new drupal 6 site with i18n, rules and auto translate modules, the auto translate rule was there, everything was working ok.

2. i upgraded whole site to drupal 7, updated i18n and rules modules with the proper versions (of course i used the dev version of rules that was published today).

3. i went to the rules upgrade path which is: admin/config/workflow/rules/upgrade, found the example rule and ruleset there, they were ready to get converted, but the auto translate rule wasn't there.

i think, in a way you can imagine that the rules are "ready" and waiting for the rest of the auto translate module to get accomplished? because the rules version 2 is ready to convert the rules (of the upgraded modules) whenever they are installed. i tested the rule upgrade tool for the example rule and it worked perfectly fine, so rules module is ready for the task. it means whenever you publish a drupal 7 dev version of auto translate, we will be able to get the upgraded auto translate rule (instantly).

when do you think that can be done? i guess it doesn't need to be a perfectly working version, a dev version of the old auto translate could be ok, to let us get the converted rules, and finally you will be able to test it for a recommended version.

alpp’s picture

greg, can you guess when you will be able to work on this issue? i would like to know because i am planning to start a site using this feature, and i think major upgrades are a bit risky for loaded sites, so this will change my decision about using drupal 6 or 7.

alpp’s picture

Priority: Normal » Major
alpp’s picture

Priority: Major » Normal
greg.harvey’s picture

Marked #793318: Port to drupal 7 as a duplicate of this issue.

klonos’s picture

Issue tags: +D7 porting, +port to d7, +d7 ports

...just adding tags ;)

klonos’s picture

Title: i18n Auto Translate port to D7 » i18n auto translate port to D7

+ correct module name capitalization in issue title

FatherShawn’s picture

following

greg.harvey’s picture

Priority: Normal » Critical
Status: Active » Postponed

Wow, this could be a show-stopper folks: #1215426: Google Translate API no longer free - replacement required - please make suggestions

Thoughts? Suggestions? Alternative APIs?

Without a replacement for the Google Translate service we're dead in the water. Google seem to have no intention of offering one.

Vote_Sizing_Steve’s picture

My 6.x autotranslate is still working well, but would welcome a version 7 for my new site!

greg.harvey’s picture

There can be no D7 version until an alternative to the Google Translate API is suggested, I'm afraid. Please read #1215426: Google Translate API no longer free - replacement required - please make suggestions

greg.harvey’s picture

Some movement in #1215426: Google Translate API no longer free - replacement required - please make suggestions (although the guy who posted it annoyed the hell out of me with his tone... ;-) ... As of last week the Translate API was re-opened as v2 as a paid service.

It's still not a direct replacement though. I think a better approach might be to now look at making an API for translation services for D7 instead of getting hung up on Google Translate going AWOL. That way people can plug their own solutions. I'll think on this...

greg.harvey’s picture

Version: 6.x-2.x-dev » 7.x-3.x-dev
Priority: Critical » Normal
Status: Postponed » Needs work

Thanks to my company now having a "contrib hour" policy, work is properly under way on this. I'm somewhat disappointed *nobody* else is prepared to work on this, though lots of people clearly want it, but there you go. I've created a new branch for this work and some initial pushing around of files has happened, but this module is totally broken. Don't even try to use it. Check it out if you want to help, by all means, patches welcome, but I'm basically giving some serious thought to the architecture of this module before continuing. More next week...

alpp’s picture

great news greg. i'm not a coder so i can't help with that but i surely can help for testing. may i ask which service will you be using for the next release? if not google, is it bing or something independent?

greg.harvey’s picture

Probably Bing, but there's scope for continuing to support Google for those who don't mind paying. Problem is, I need to pay to test it! =/

alpp’s picture

you could ask it from the people who will go the google way. an independent source would be wonderful but i guess it is out of limits for now.

i just thought that links for human translation could be added as an add-on to the module. so that the native speaking users of a language could correct the auto-translated content via a "suggest a -better- translation" linked form.

by the way, will there be a d6 backport of this new bing + google version?

Vote_Sizing_Steve’s picture

FileSize
1.66 KB

Attached is a d7 Bing translate module that I asked my developer to build.

It doesn't integrate with rules, and I'm not yet sure about defaulting the Content type -> Synchronize translations -> Configurable fields; but it does add a translated node when clicking on the 'Auto Translate' tab from node view.

Hope this helps with the further development in D7 of this very useful module.

greg.harvey’s picture

@Vote_Sizing_Steve, thank you very much for sharing that - much appreciated! I'm sure it will be very useful, will review next week. =)

greg.harvey’s picture

Made some progress on this today. Decisions are:

- Move Rules support as optional inside individual translation services modules, Rules are not core, Actions are
- Implement the translation using Actions
- Create a UI to allow the selection of a translation service
- Allow pluggable translation services to provide a "callback" for translating the node

Committed this morning's work, for anyone who's interested:
http://drupalcode.org/project/i18n_auto.git/commit/36587e0

Edit: clarification - "Drop Rules support" changed to explain the purpose - not to remove Rules, but to make any Rules implementations the responsibility of the translation services modules, as there is very little to the old Rules-based module anyway.

eloivaque’s picture

I test module of comment #36 but i don't work.

greg.harvey’s picture

Assigned: greg.harvey » slv_

I've passed the buck here... ;-)
But now something might actually get done!

RaulMuroc’s picture

Some advance on that?

RaulMuroc’s picture

Status: Needs work » Closed (won't fix)

:'( sadly, you can read in the module homepage:

UPDATE (2011-07-13): Bad news! Seems Google are going to pull the Google Translate API. Without a replacement service, this whole module will no longer be viable.

Refer to this link: http://drupal.org/project/i18n_auto

BrightBold’s picture

Status: Closed (won't fix) » Needs work

@RaulMuroc — true, but if you read this very thread you can see that was discussed and the work since then was supporting Bing. So it seems inappropriate to close this.

squinternata’s picture

some news on this module?
it s still not working. it ask me for actions module but for drupal 7 this module doesn t exist right?

greg.harvey’s picture

Status: Needs work » Closed (won't fix)