0014685: When a module is created, the ad_menu_trl is not exported

(0031368)
alostale (manager)
2010-09-27 08:38

Did you follow the steps defined in the documentation for translation modules [1]?

-Create a translation module
-Export the translation
-Copy xml files to your module

[1] http://wiki.openbravo.com/wiki/ERP/2.50/Developers_Guide/Concepts/Modularity#Translations [^]

(0031371)
albertobg (reporter)
2010-09-27 09:32

If we implement a module whose language is Spanish, we have to make a Spanish translation module too (???)

(0031372)
alostale (manager)
2010-09-27 09:35

If you implement a Spanish module, that module's artifacts texts should be in Spanish. This module would require translation to any other language (such as English).

(0031373)
albertobg (reporter)
2010-09-27 09:47
edited on: 2010-09-27 09:48

Agree, as I have said, the menus do not accept some characters, so we have to create a record in menu_trl with Spanish language (although the module is already in Spanish), then te application show the texts correctly in development environment, but when whe package the module, this is not exported, and the texts are wrong in production environment.
Example:
-Text in menu: Region
-Text in menu_trl (ES_es): Región
If we try to put "Región" in menu, the application does not compile.
This is applicable to tabs too.

(0031374)
alostale (manager)
2010-09-27 10:12

Ok,

I think now I understand the problem:

-The menu name is always copied from window name.
-Window or tab name does not accept special characters as these names are used to generate Java classes.
-Therefore a module in a language that needs to use special characters is not allowed to being limited to standard ones.

(0031376)
albertobg (reporter)
2010-09-27 10:48

Yes, thats the problem
Thanks!

(0031377)
alostale (manager)
2010-09-27 10:53

Issue set as scheduled.

Meanwhile workaround: if your module requires names for windows/tabs with special characters, your module should have English as base language so your windows/tabs would have their names with standard characters and you should create a translation module to your language for that one where you could use the actual characters you need.

(0052471)
AugustoMauch (administrator)
2012-09-24 23:27

Impact: mid
Plan: mid

Issue History
Date Modified	Username	Field	Change
2010-09-23 15:46	albertobg	New Issue
2010-09-23 15:46	albertobg	Assigned To	=> alostale
2010-09-27 08:38	alostale	Note Added: 0031368
2010-09-27 08:38	alostale	Status	new => feedback
2010-09-27 09:32	albertobg	Note Added: 0031371
2010-09-27 09:32	albertobg	Issue Monitored: albertobg
2010-09-27 09:35	alostale	Note Added: 0031372
2010-09-27 09:47	albertobg	Note Added: 0031373
2010-09-27 09:48	albertobg	Note Edited: 0031373	View Revisions
2010-09-27 10:12	alostale	Note Added: 0031374
2010-09-27 10:48	albertobg	Note Added: 0031376
2010-09-27 10:50	alostale	Status	feedback => scheduled
2010-09-27 10:50	alostale	fix_in_branch	=> pi
2010-09-27 10:53	alostale	Note Added: 0031377
2011-11-16 16:04	alostale	Type	defect => design defect
2011-11-16 16:04	alostale	fix_in_branch	pi =>
2012-09-24 23:27	AugustoMauch	Note Added: 0052471
2012-09-24 23:27	AugustoMauch	Priority	high => normal
2017-03-31 14:36	alostale	Status	scheduled => acknowledged
2017-04-10 14:34	alostale	Assigned To	alostale => platform
2022-02-01 08:08	alostale	Assigned To	platform => Triage Platform Base

Notes
(0031368) alostale (manager) 2010-09-27 08:38	Did you follow the steps defined in the documentation for translation modules [1]? -Create a translation module -Export the translation -Copy xml files to your module [1] http://wiki.openbravo.com/wiki/ERP/2.50/Developers_Guide/Concepts/Modularity#Translations [^]

(0031371) albertobg (reporter) 2010-09-27 09:32	If we implement a module whose language is Spanish, we have to make a Spanish translation module too (???)

(0031372) alostale (manager) 2010-09-27 09:35	If you implement a Spanish module, that module's artifacts texts should be in Spanish. This module would require translation to any other language (such as English).

(0031373) albertobg (reporter) 2010-09-27 09:47 edited on: 2010-09-27 09:48	Agree, as I have said, the menus do not accept some characters, so we have to create a record in menu_trl with Spanish language (although the module is already in Spanish), then te application show the texts correctly in development environment, but when whe package the module, this is not exported, and the texts are wrong in production environment. Example: -Text in menu: Region -Text in menu_trl (ES_es): Región If we try to put "Región" in menu, the application does not compile. This is applicable to tabs too.

(0031374) alostale (manager) 2010-09-27 10:12	Ok, I think now I understand the problem: -The menu name is always copied from window name. -Window or tab name does not accept special characters as these names are used to generate Java classes. -Therefore a module in a language that needs to use special characters is not allowed to being limited to standard ones.

(0031376) albertobg (reporter) 2010-09-27 10:48	Yes, thats the problem Thanks!

(0031377) alostale (manager) 2010-09-27 10:53	Issue set as scheduled. Meanwhile workaround: if your module requires names for windows/tabs with special characters, your module should have English as base language so your windows/tabs would have their names with standard characters and you should create a translation module to your language for that one where you could use the actual characters you need.

(0052471) AugustoMauch (administrator) 2012-09-24 23:27	Impact: mid Plan: mid

Relationships [ Relation Graph ] [ Dependency Graph ]