Hi,

Great module - thanks. It's a real time saver!

Might I suggest though, that since the install process is a bit non-standard, that it could use some better documentation to get people started? The readme file as is is pretty confusing. There were a lot of extra links that threw me a bit, they may really confuse a newbie struggling to get started. There is also some typos / wrong data with what's currently there.

Note, this issue also references some of what I'm fixing below.
http://drupal.org/node/812402

In the Readme's 6.x Install instructions section, something like this might make more sense:

Installing

(0)
If you don't already have it, download the rules module and extract to sites/all/modules
  http://drupal.org/project/rules

(1)
Extract i18n_auto module to sites/all/modules

(2)
Download the latest GTranslate PHP library from:
  http://code.google.com/p/gtranslate-api-php/downloads/list
and extract the contents

Or, if you would prefer, get the code directly from SVN by following the instructions here:
  http://gtranslate-api-php.googlecode.com/svn/trunk/

(3)
Copy the files into sites/all/modules/i18n_auto/gtranslate-api-php

(4)
Enable the "Auto draft translation" module


At this time there are no settings. A rule is automatically enabled to manage the translations. You may edit the rule/create your own rules to manage how your auto-translations are generated. The provided
Rules action is called "Translate a node into every enabled language" and is in the Node actions.  If you can not find the Rules administration tools, ensure that the module "Rules Administration UI" has been enabled!

Also, this sentence on the project page doesn't make much sense, and confuses way more than it helps:

At this time the latest package for GTranslate misses out the main PHP library, so we advise you take the files from the Subversion:
http://code.google.com/p/gtranslate-api-php/source/checkout

I confirmed that the latest package and what's in subversion are currently identical. I would just delete this statement altogether as it makes things seem much more complicated than they are. SVN knowledge isn't always commonplace - you're average joe may not be comfortable with it.

Hope that helps!

-Ben

Comments

greg.harvey’s picture

greg.harvey
Primary language English
Location Occitanie, France
commented
Category: task » bug
Status: Active » Reviewed & tested by the community

Thanks for this. Will definitely incorporate. For the record, when that line was added to the project page it was true - the latest download did NOT match Subversion and was missing critical files. In fact, the whole project looked quite unmaintained, so that someone has bothered to fix it is encouraging. =)

klonos’s picture

klonos
he/him
Primary language English
Location 90% Melbourne, Australia - 10% Larissa, Greece
commented

@bbenone: Thank you for sharing your experience/insight Ben!

@greg.harvey: ...while you're at it can you please make the link to the limit of 1500 chars in the project's page point to: http://code.google.com/p/gtranslate-api-php/issues/detail?id=12

There's also a comment there by josedasilva that states that the limitation has changed to 5000 characters. I checked the link to the Google terms and conditions and verified that this is true. Please update this in the module's front page too.

Thanx.

PS: Greg, I see you are being a bit kinda 'inactive' lately (last commit dates back in April, but last post was in mid-June) and I totally understand luck of time, but could you please give some love to this module?

klonos’s picture

klonos
he/him
Primary language English
Location 90% Melbourne, Australia - 10% Larissa, Greece
commented

Another possible change for the module's front page...

#593048: _pathauto_alias_exists handles language-neutral aliases wrong was fixed for 6.x-2x towards the end of July and Dave promised a backport to 6.x-1.x too. So using a latest dev build of pathauto (say Aug 2010 and newer) will most likely *not* cause duplicate URL alias warnings when translations are created any more. Anyone having this issue can confirm this is now fixed(?) and we can then provide this information in the front page as well. Something like:

This issue is now reported fixed when using a latest dev release of pathauto!

klonos’s picture

klonos
he/him
Primary language English
Location 90% Melbourne, Australia - 10% Larissa, Greece
commented

...and if Dave actually considers my request, there will soon be a 'stable' release of pathauto that fixes this instead of a dev. Let's see.

klonos’s picture

klonos
he/him
Primary language English
Location 90% Melbourne, Australia - 10% Larissa, Greece
commented

Actually Dave and the other maintainers of pathauto intended to make a new release anyways: #845498: Please make a release on the 2.x branch. Great news, since this will happen within the week if all goes well!

greg.harvey’s picture

greg.harvey
Primary language English
Location Occitanie, France
commented

@klonos - if you have CVS access, co-maintainer is welcome.

klonos’s picture

klonos
he/him
Primary language English
Location 90% Melbourne, Australia - 10% Larissa, Greece
commented

I don't have CVS access and I am not still familiar with drupal module coding, but I can take care of things like documentation and the front page. In fact I just turned 1 year old (in drupal.org) a couple of days ago, so I guess I should start someplace. Plus, I live in a country that its people are not natively English-speakers, this module is of great interest to me. If it is ok with you, than I am more than happy to accept the invitation ;)

...and since it is a requirement in order to receive CVS access, here is my application too: #878634: Application for co-maintainership

greg.harvey’s picture

greg.harvey
Primary language English
Location Occitanie, France
commented

Replied. Hope the powers that be give you access. =)

greg.harvey’s picture

greg.harvey
Primary language English
Location Occitanie, France
commented
Status: Reviewed & tested by the community » Fixed

Committed to 6.x-2.x-dev. Updated README will be available within 12 hours.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.