[SOLVED] PLEASE CHANGE THIS TO ENGLISH !

I can’t imagine how possibly NetMake sells software as English version and put those non-English default variables ?
PLEASE CHANGE IT ! I BOUGH SOFTWARE THAT SUPPOSED TO WORK IN ENGLISH AND I WANT IT THAT WAY. If one day I decide to work with Portugese I will buy Poretugese version of Scriptcase. What you guys (NetMake) doing with the language is just insane! All mixed up! I work with other developers who need to access certain variables, table names etc (although they do not use SCRIPTCASE and they are just getting nuts with all this non-English crap (starting from code and ending up on help files and documentation).
I’m not even talking about the style or grammar, but simply completely wrong approach. You (NetMake) try to offer discount for potential customers hoping they will buy the product, but how the hell they supposed to stay with the product in a long term if there are so many issues (especially with the language barrier and never fixed bugs) (?)
This topic was brought million times already by other developers who are very unhappy with the whole language approach and for the recent 3-4 years nothing has been improved. I use (for example) software development tools for mobile devices from ISRAEL. The do not have problem with English, all documentation is in English, they provide excellent support in English and there is nothing in Jewesh that I could find. Why NetMake cannot just do the same ?
There are thousands companies around the world where developers do not speak/write native English but they start development from English (then translate everything to their local language).
DOING OPPOSITE IS A TERRIBLE MISTAKE !

Dear NetMake developers - just look below at this terrible English x Portugese mess and tell me if this is professional ? If not - then you should offer SC license for free until this stuff is fixed.

Database Variables [TABLE=“class: macros_desc_table”]
[TR]
[TD] Global variables containing database access values used by main connection.
[TABLE=“border: 0”]
[TR]
[TD=“width: 15%, align: left”]Variables[/TD]
[TD=“align: left”]Description[/TD]
[/TR]
[TR]
[TD=“class: corpo1, align: left”]sc_glo_servidor[/TD]
[TD=“class: corpo1, align: left”]Server name.[/TD]
[/TR]
[TR]
[TD=“class: corpo1, align: left”]sc_glo_banco[/TD]
[TD=“class: corpo1, align: left”]Database name.[/TD]
[/TR]
[TR]
[TD=“class: corpo1, align: left”]sc_glo_tpbanco[/TD]
[TD=“class: corpo1, align: left”]Database type (mssql, oracle, mysql, etc).[/TD]
[/TR]
[TR]
[TD=“class: corpo1, align: left”]sc_glo_usuario[/TD]
[TD=“class: corpo1, align: left”]Connected user name.[/TD]
[/TR]
[TR]
[TD=“class: corpo1, align: left”]sc_glo_senha[/TD]
[TD=“class: corpo1, align: left”]Database password access.[/TD]
[/TR]
[TR]
[TD=“class: corpo1, align: left”]sc_glo_senha_cript[/TD]
[TD=“class: corpo1, align: left”]Encrypted password (S/N).[/TD]
[/TR]
[TR]
[TD=“class: corpo1, align: left”]sc_glo_decimal_db[/TD]
[TD=“class: corpo1, align: left”]Used decimal separator (point or comma).[/TD]
[/TR]
[/TABLE]

		[B]Ex. 1:[/B]
		$my_database = [sc_glo_banco];
		
		
		These variables only reference the values without updating it (it is not possible to attribute/modify the values). To define user and the password to connect to the database, use the following variables:
		[TABLE="border: 0"]
			 					[TR]
					[TD="width: 15%, align: left"][B]Variables[/B][/TD]
					[TD="align: left"][B]Description[/B][/TD]
				[/TR]
				[TR]
					[TD="class: corpo1, align: left"]sc_db_master_usr[/TD]
					[TD="class: corpo1, align: left"]User login to be used.[/TD]
				[/TR]
				[TR]
					[TD="class: corpo1, align: left"]sc_db_master_pass[/TD]
					[TD="class: corpo1, align: left"]Password to be used.[/TD]
				[/TR]
				[TR]
					[TD="class: corpo1, align: left"]sc_db_master_cript[/TD]
					[TD="class: corpo1, align: left"]Encrypted password (S/N) (see sc_encode macro).[/TD]
				[/TR]
			 			[/TABLE]
		[B]Important:[/B] [I]These variables only take effect during next application execution remaining valid during all the session (unless modified). [/I]
		
		[B]Ex. 2: [/B]An application type "control" with a form created with information "login" and encrypted "password". These data must be used to connect to the database, during the system applications execution.
		$temp_pass = sc_encode({password});
		[sc_db_master_usr] = {login};
		[sc_db_master_pass] = $temp_pass;
		[sc_db_master_cript] = "S";
		[/TD]
	[/TR]
 [/TABLE]

Hello,

I understand your question. The scriptcase was created this way, with the variable name in Portuguese, but we our documentation have a description in English and Spanish.

I reported to our development team for they check the possibility of creating an internationalization of these names. I waiting for they reply.


Best regard,
Netmake team

Creating non-english variables is insane approach. As long as you sell your product out of Brazil you need to start from English (ten later translate to Portugese). Doing it opposite way is like taking a dog for a walk by the tail !

Hello,

This problem will be fixed in the next update.

Hello,

This problem has been solved in update 8.1.016.
Please, update your ScriptCase.

​Thank you!

Hi,

After upgrading from v8 to 8.1, I get this message on a control app after saving and generating:

[SIZE=12px]Notice: Undefined index: sc_glo_servidor in …c[/SIZE]ontrol_depart[SIZE=12px].php on line 1291
Notice: Undefined index: sc_glo_usuario in …c[/SIZE]ontrol_depart[SIZE=12px].php on line 1291
Notice: Undefined index: sc_glo_senha in …c[/SIZE]ontrol_depart[SIZE=12px].php on line 1291
Notice: Undefined index: sc_glo_banco in …c[/SIZE]ontrol_depart[SIZE=12px].php on line 1291

This is part of code generated but it’s not in my code :[/SIZE]

1288 if (substr($cadapar[0], 0, 11) == “SC_glo_par_”)
1289 {
1290 $cadapar[0] = substr($cadapar[0], 11);
1291 $cadapar[1] = $_SESSION[$cadapar[1]];
1292 }
1293 nm_limpa_str_control_depart($cadapar[1]);

Are the name of those variables changed ?? if yes what are the new names and why nothing was written in change.log ?
Thanks

Hello,

The change was only to support the translation of some variables. Behind, the routine is the same and you can continue using the old way without problems.