Sugar Translation Suite

[romaing]

Hello all,

we wish to announce the release of this suite of tools that we believe could bring benefits to the sugarcrm translation community.

This tool has been developped to help and organize the translation work for SugarCRM. It includes features such as :

- Utilization and administration of a dictionary (stored in database) to reduce the amount of work needed for the translation.
- Automatic generation of language packs.
- Management of language pack versions, in order to support different translation versions (3.5/4.0 OS/EE ...).
- Reports to display and compare two language pack version or to view the current translation status.

You will find this tool at the following location : Sugar Translation Suite

We have been using this tool for our own translation and it has demonstrated to be very useful. We have not noticed any problems yet. However feel free to send us your inputs and comments, they will be appreciated.

[ruchida]

romaing

I look like a great tool!
Does this work with PHP5 only? I have a problem in running this tool with PHP4.

Great thanks to your contribution!

[romaing]

romaing

I look like a great tool!
Does this work with PHP5 only? I have a problem in running this tool with PHP4.

Great thanks to your contribution!

Hi,

Yes, for now, it's only working with php5 as it uses some php5 only functions and features.
It "should" be possible to make it php4 compatible. We'll try to have a look at it when we'll have time.

regards.

[romaing]

Hello all,

we've just released on SugarForge a new version of the Sugar Translation Suite that is fully working with PHP4.
We've also corrected a minor (but annoying) bug (thanks a lot to Wojtek Kaluzinski for his bug report).
The new archive can be downloaded here.

If you got any questions about this tool and how it works don't hesitate, we'll try to give you an answer as fast as possible.

best regards
The Grupa-Atlantis team.

[ruchida]

romaing,

Thank you so much for the PHP4 compatibility!
This is really a great tool. Very neat user interface.

One problem with the Japanese language pack. It has a suffix ja(.lang.php) which is not like the "en_us" style, so I encounter the error below and can not go forward.

 The expected syntax for the lang_file_suffix property is [:alpha:]{2}_[:alpha:]{2} ex : ('en_us') 
  

Your help would be greatly appreciated.

[romaing]

Thank you so much for the PHP4 compatibility!
This is really a great tool. Very neat user interface.

Thanks a lot!

One problem with the Japanese language pack. It has a suffix ja(.lang.php) which is not like the "en_us" style, so I encounter the error below and can not go forward.

 The expected syntax for the lang_file_suffix property is [:alpha:]{2}_[:alpha:]{2} ex : ('en_us') 
  

Your help would be greatly appreciated.

Here is how you can correct this problem:

Edit the manifest.class.inc file which is located in the /inc directory and find line 72:

 else if (!strlen( $this->get("lang_file_suffix")) == 5 || ! eregi("[a-z][a-z]_[a-z][a-z]", $this->get("lang_file_suffix"))) return "The expected syntax for the lang_file_suffix property is [:alpha:]{2}_[:alpha:]{2} ex : ('en_us')"; 
  

replace it with this one:

 else if (! eregi('^[a-zA-Z]{2}(_[a-zA-Z]{2})?$', $this->get("lang_file_suffix"))) return "The expected syntax for the lang_file_suffix property is [:alpha:]{2}_[:alpha:]{2} or [:alpha:]{2}  ex : ('en_us', 'ja')"; 
  

This new line will allow your 'ja' file tag.
It will also allow upper-case characters for people who need them.

best regards

[ruchida]

romaing

Thanks for the help!
I have successfully generated a language pack with this great tool in a couple of minutes, which I spent hours before!

A few problems I had are;
* "UTF-8" for LBL_CHARSET becomes "UTF8".
* Most of default key values are translated, which should not be. Is there any way to prevent this from happening?

If a multiple headers can be managed to create Ent/Pro/Os language packs, it would be great.

I really appreciate your decision to contribute this tool to the forum.

[swider]

Hello,

Sugar Translation Suite looks really nice, however I've got some problems with installation. When I run install.php and click "Process" button after setting all up i get something like this:

---
Connexion to DB: OK
DB creation: OK
User creation: OK

Error: 1064: You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near 'CURRENT_TIMESTAMP, PRIMARY KEY (`id`) ) ENGINE=InnoDB' at li
Error: can't create database
---

and after that when i run Sugar Translation Suite i get:

---
SQL ERROR : Table 'sugar_lang.sugar_versions' doesn't exist
---

in "Edit Manifest" and "Translation Management".

Any ideas what is wrong?

Thanks
Łukasz

[romaing]

Hi,

A few problems I had are;
* "UTF-8" for LBL_CHARSET becomes "UTF8".
* Most of default key values are translated, which should not be. Is there any way to prevent this from happening?

We have now corrected the problems and released a new version. We have also included the fix related to the lang_file_suffix property in the manifest page.
The new version can be found at the usual download page

If a multiple headers can be managed to create Ent/Pro/Os language packs, it would be great.

If I understand well those are the commented headers in each of the lang file. We shall include such functionality in a new release once we gather other requests.

Concerning swider SQL problem, i'm investigating to find out what is going wrong. But I believe that this could be a MySQL version problem due to the CURRENT_TIMESTAMP property.
The SQL script used during installation is "sugar_lang.sql" (or "sugar_lang_replace.sql" if you specifie a custom charset) and is located in the /inc directory.
I would propose you to :
- Drop the partially created sugar_lang database
- Edit the sql file and remove this property in the create statement for the table sugar_version (line 82).
- Run the Installation again.

Let me know if you have any problem.

Best regards,

[swider]

Hi,

After removing default value from the line:

---
`added` timestamp NULL default CURRENT_TIMESTAMP,
---

the rest of installation went smoothly without any errors, and everything seems to be working OK.

Thanks a lot,
i pozdrawiam!
Łukasz