Translate the GUI into another language - Revision history

Nite man: /* Preparation */

2009-10-09T10:00:41Z

Preparation

←Older revision		Revision as of 10:00, 9 October 2009
Line 26:		Line 26:
	* default charset for server should be set to utf8 in the /etc/mysql/my.cnf:		* default charset for server should be set to utf8 in the /etc/mysql/my.cnf:
	[mysqld]		[mysqld]
	default-character-set=utf8		init_connect='SET NAMES utf8; SET collation_connection = utf8_general_ci;'
			default-character-set=utf8
			character-set-server=utf8
			collation-server=utf8_general_ci
			skip-character-set-client-handshake
	* default charset for client should be set to utf8 in the /etc/mysql/my.cnf:		* default charset for client should be set to utf8 in the /etc/mysql/my.cnf:
	[client]		[client]

Nite man: /* Preparation */

2009-10-08T13:22:41Z

Preparation

←Older revision		Revision as of 13:22, 8 October 2009
Line 41:		Line 41:
	$dbh->do('SET NAMES utf8');		$dbh->do('SET NAMES utf8');

	~~Для~~ C++ ~~сразу после вызова~~ mysql_init() ~~и перед~~ mysql_connect() ~~или~~ mysql_real_connect() ~~нужно выставить опцию utf8 с помощью функции~~ [http://dev.mysql.com/doc/refman/5.0/en/mysql-options.html mysql_options()]:		For C++ right after calling mysql_init() but before mysql_connect() or mysql_real_connect() using function [http://dev.mysql.com/doc/refman/5.0/en/mysql-options.html mysql_options()] we can set UTF8 charset for connection:
	mysql_options(&mysql, MYSQL_SET_CHARSET_NAME, 'utf8');		mysql_options(&mysql, MYSQL_SET_CHARSET_NAME, 'utf8');

			and run the SQL statement right after connection will be done:
			mysql_options(&mysql,MYSQL_INIT_COMMAND, 'SET NAMES utf8');

	===Translation===		===Translation===

Nite man: /* Preparation */

2009-10-07T08:10:55Z

Preparation

←Older revision		Revision as of 08:10, 7 October 2009
Line 37:		Line 37:
	alter table Text_LS modify column `Description` longtext CHARACTER SET utf8 COLLATE utf8_general_ci		alter table Text_LS modify column `Description` longtext CHARACTER SET utf8 COLLATE utf8_general_ci
	* the client - PHP or Perl script, C++ libs etc should tell mysql that connection is in utf8. Here is an example for Perl:		* the client - PHP or Perl script, C++ libs etc should tell mysql that connection is in utf8. Here is an example for Perl:
	my $dbh = DBI->connect("dbi:mysql:pluto_main;host=localhost", 'root~~', ''~~) or die "Cannot connect to database: $DBI::err!";		my $dbh = DBI->connect("dbi:mysql:pluto_main;host=localhost", "root") or die "Cannot connect to database: $DBI::err!";
	$dbh->{'mysql_enable_utf8'} = 1;		$dbh->{'mysql_enable_utf8'} = 1;
	$dbh->do('SET NAMES utf8');		$dbh->do('SET NAMES utf8');

Nite man: /* Working with the database */

2009-10-07T08:10:19Z

Working with the database

@@ Line 20: / Line 20: @@
 ==Working with the database==
 As stated above, all text elements are stored in the main database (pluto_main). The tables of particular interest are "[[Database.pluto_main.Text|Text]]", "[[Database.pluto_main.Text_LS|Text_LS]]" and "[[Database.pluto_main.Language|Language]]".
 : "Text" : Contains all text elements that are used by the GUI. The single text elements are identified by the field PK_Text

Chriss: /* Working with Designer */

2009-07-07T20:39:19Z

Working with Designer

←Older revision		Revision as of 20:39, 7 July 2009
Line 61:		Line 61:

	The process of updating your database before editing and committing your changes after editing are the same as described above.		The process of updating your database before editing and committing your changes after editing are the same as described above.

			''Note: IMHO there currently is no option to define new languages in HADesigner [[User:Chriss\|chriss]] 22:26, 7 July 2009 (CEST)''

	Designer has a comfortable interface for changing and translating text elements. First select the text tab on the DesignObj Browser:		Designer has a comfortable interface for changing and translating text elements. First select the text tab on the DesignObj Browser:
Line 67:		Line 69:
	Find the items to translate in the categories and double-click on the element to open up the editor window. The editor window will expand if there are more languages defined.		Find the items to translate in the categories and double-click on the element to open up the editor window. The editor window will expand if there are more languages defined.
	[[Image:Designer_edit_text.png]]		[[Image:Designer_edit_text.png]]

	~~''Note: IMHO there is no option to define new languages in HADesigner [[User:Chriss\|chriss]] 22:26, 7 July 2009 (CEST)''~~

	=For developers=		=For developers=

Chriss: /* How to translate */

2009-07-07T20:33:53Z

How to translate

←Older revision		Revision as of 20:33, 7 July 2009
Line 28:		Line 28:

	When creating or modifying rows of the tables make sure to never touch the fields called psc_<something>. These are part of the sqlCVS system and are handled by sqlCVS upon checkin/update etc. If you leave these fields alone MySQL inserts the default values which are just fine.		When creating or modifying rows of the tables make sure to never touch the fields called psc_<something>. These are part of the sqlCVS system and are handled by sqlCVS upon checkin/update etc. If you leave these fields alone MySQL inserts the default values which are just fine.

			Never (!) update/overwrite an existing row when creating a new translation. Only change existing rows when you make a correction to an already existing translation.

	===Update database===		===Update database===

Chriss: Described translation process in Designer

2009-07-07T20:26:42Z

Described translation process in Designer

←Older revision		Revision as of 20:26, 7 July 2009
Line 56:		Line 56:

	==Working with Designer==		==Working with Designer==
	[[Designer]] is a software to modify the GUI of LinuxMCE. It can also be used to create new text element and the corresponding translations.		[[Designer]] is a software to modify the GUI of LinuxMCE. It can also be used to create new text element and the corresponding translations. Check the linked page and the wiki on how to get hold of Designer and how to make it start up.
	''~~TBD~~''
			The process of updating your database before editing and committing your changes after editing are the same as described above.

			Designer has a comfortable interface for changing and translating text elements. First select the text tab on the DesignObj Browser:
			[[Image:Designer_obj_browser.png]]

			Find the items to translate in the categories and double-click on the element to open up the editor window. The editor window will expand if there are more languages defined.
			[[Image:Designer_edit_text.png]]

			''Note: IMHO there is no option to define new languages in HADesigner [[User:Chriss\|chriss]] 22:26, 7 July 2009 (CEST)''

	=For developers=		=For developers=

Chriss: Completed description for work with database tools

2009-07-07T18:30:02Z

Completed description for work with database tools

←Older revision		Revision as of 18:30, 7 July 2009
Line 1:		Line 1:
	[[Category:Languages]]		[[Category:Languages]]
	[[Category:Tutorials]]		[[Category:Tutorials]]


	~~'''Work in progress!!!''' [[User:Chriss\|chriss]] 11:39, 7 July 2009 (CEST)~~

Chriss: /* Check in translation */

2009-07-07T18:29:23Z

Check in translation

←Older revision		Revision as of 18:29, 7 July 2009
Line 54:		Line 54:

	===Check in translation===		===Check in translation===
	You can use web admin again to check in your work. Go to ''Advanced->sqlCVS->CheckIn''. The configuration should be the same as above. Scroll down and tick the check box at ''Designer'' and under Designer you also need to tick the check boxes at ''Language'' and ''Text_LS''. Watch the progress in the pop-up window.		You can use web admin again to check in your work. Go to ''Advanced->sqlCVS->CheckIn''. The configuration should be the same as above. Scroll down and tick the check box at ''Designer'' and under Designer you also need to tick the check boxes at ''Language'' and ''Text_LS''. Finally enter a comment to describe what you are checking in and hit ''Next''. Watch the progress in the pop-up window.

	After successfully translating the GUI and checking in all changes please create a ticket in [http://svn.linuxmce.org/ Trac], make it a feature_patch, name it "translation to <yourlanguage>" and give all the sqlCVS batch numbers in the description to have a developer approve the changes to the database.		After successfully translating the GUI and checking in all changes please create a ticket in [http://svn.linuxmce.org/ Trac], make it a feature_patch, name it "translation to <yourlanguage>" and give all the sqlCVS batch numbers in the description to have a developer approve the changes to the database.

Chriss: Details on checking in changes

2009-07-07T18:28:02Z

Details on checking in changes

←Older revision		Revision as of 18:28, 7 July 2009
Line 54:		Line 54:

	===Check in translation===		===Check in translation===
	''~~TBD~~''		You can use web admin again to check in your work. Go to ''Advanced->sqlCVS->CheckIn''. The configuration should be the same as above. Scroll down and tick the check box at ''Designer'' and under Designer you also need to tick the check boxes at ''Language'' and ''Text_LS''. Watch the progress in the pop-up window.

	~~After successfully translating~~ the ~~GUI~~ and ~~checking in all changes please create a ticket in [[Trac]], make it a feature_patch, name it "translation~~ to ~~<yourlanguage>"~~ and ~~give all~~ the ~~sqlCVS batch numbers~~ in the ~~description to have a developer approve the changes to the database~~.

			After successfully translating the GUI and checking in all changes please create a ticket in [http://svn.linuxmce.org/ Trac], make it a feature_patch, name it "translation to <yourlanguage>" and give all the sqlCVS batch numbers in the description to have a developer approve the changes to the database.

	==Working with Designer==		==Working with Designer==